GitLab

Parameter `msEnd` was not used with `tSolveFirst` causing wrong values
in later solves.

Previously forecast offset `df_scenario` was computed only when number of scenarios was
greater than one. Long-term scenario data should use a special label in the `f` dimension
in all cases.

Set `t_realized(t)` has the realized time steps in the simulation (excluding the starting point and any extra horizon).
This is included in file *results.gdx* as symbol `t`.

Closes #81

Adding example updates related to storage units for invest-schedule data transfer. Note that the file is just a template that can be used as an example when the user writes the actual file that is stored in the input folder and read by the model.

This reverts commit b3a87bcf

This is currently expressed by 'energyStoredPerUnitOfState'.

This way the explanations can be exported programmatically.

Updating Backbone inputData.gdx to Spine Toolbox specification and Spine Toolbox to Backbone specification

Including an example for changing the maximum page width in the 4d_postProcess_invest2schedule_temp.gms.

Including an example for changing the field width of set label output in the 4d_postProcess_invest2schedule_temp.gms.

Issue #137

Dev fix #130 132

See merge request !10

Converting from 1.2 to 1.3: include p_gn(grid,node,'nodeBalance')=1 for grid-nodes that don't have values in ts_priceChange.

Changing the interpretation of unitUnitEffLevel. The model was reading the input data so that 'effLevel to start aggregation' meant the start of the next level (e.g. using level3 resulted in the last time step of level3 in the internal parameter lastStepNotAggregated - in effect pointing to the start of Level4). Now this is read so that level3 means the start of level3