07-03-2017, 11:17 PM
For any interested Forumers:
Thanks to Anjana, the demand problem was resolved as being caused by a few spurious timeslice mappings in the set TS_PARENT (a set specific to ANSWER-TIMES ). It also seems possible that the similar problem reported earlier by a Norwegian user was caused by the same issue (because these spurious entries were somehow introduced when importing a new region to an existing model).
Thanks to Anjana, the demand problem was resolved as being caused by a few spurious timeslice mappings in the set TS_PARENT (a set specific to ANSWER-TIMES ). It also seems possible that the similar problem reported earlier by a Norwegian user was caused by the same issue (because these spurious entries were somehow introduced when importing a new region to an existing model).