GitLab

- Deleting constant alternative names from importer mappings
- Importing timeseries form of unit efficiency data into a separate parameter efficiency_ts and similar update to the exporter

This can be used in non-anticipativity constraint equations to speed up equation creation for the model.

Fix `storageValueUseTimeseries` not exporting to `p_gn` as in da2665c9

Replacing relationship classes restype_released_for_realization, restype_inertia, and unit_fail with parameters that have value 1 if the objects should be included in the corresponding Backbone sets

- Adding other efficiency curve related parameters for units in the `efficiency` Map
- Renaming input_output object class to io
- Renaming restype__direction relationship class to restype__up_down
- Renaming effLevel__group__unit relationship class to effLevel__effSelector__unit
- Moving boundary data from grid__node to grid__node__boundary
- Including p_groupPolicyUnit data in unit__group instead of creating a new group__unit relationship class
- Deleting commodity mappings
- Including ts_priceChange data in node

Remove commodity set and replace it with a parameter

See merge request !21

Issue #161

There was mixed contents with file name referring to Backbone v1.3 and content to v1.4.

Issue #161

Issue #161

Issue #161

First attempt to remove commodity set and replace it with a parameter telling if ts_priceChange should be used

Issue #161

Calculation of start-up costs and start-up fuel consumption

See merge request !20

Updating 'annual' energy constraints

See merge request !19

Issue #159

Issue #162

Introduced a new set `mst` with combinations of models, samples and t's.
Using projections in for calculating some lower-dimension subsets.

Previous solution was slow when there were many s's.

The parameters are in timeseries format.

Issue #160

Start-up fuels (=nodes) are now defined in p_uStartupfuel with fixedFuelFraction. They do not need to be included in p_gnu_io.

Issue #160

Poor performance when there were multiple samples used.

Also removed filter config files as they should be local.

Spill variable `v_spill` is actually treated as spill rate (MWh/h) in the equations, so fixed the description.
Result parameter `r_spill` is expressed in absolute energy, so rate must be multiplied with the step length.

# Conflicts:
#   defModels/building.gms
#   defModels/schedule.gms

- q_transferTwoWayLimit1 is used if investments not enabled
- q_transferTwoWayLimit2 is used if investments enabled and initial capacities are the same in both directions

If investments are enabled and initial capacities are not the same in both directions, a similar constraint would become nonlinear.

Issue #158

Issue #159

From user perspective:
- Deleting the p_groupPolicy(group, 'energyMaxVgenSign') parameter. For a minimum energy constraint, the user should now add a positive p_groupPolicy(group, 'energyMin').
- For constraints with p_groupPolicy(group, 'energyShareMax') or p_groupPolicy(group, 'energyShareMin'), the user should now also add the consumption units to be considered in the constraint to gnuGroup. Previously they were automatically considered if they connected to nodes in gnGroup. This was problematic for storage units.

From model code perspective:
- Rearranging q_energyMax(group), q_energyShareMax(group), and q_energyShareMin(group) constraints to q_energyLimit(group, min_max) and q_energyShareLimit(group, min_max) constraints.

Issue #157

Adding a check to ensure that the start-up fuel node is in gnGroup.

Issue #156

r_gnnTransferMarginalValue updates: checking correct end node for marginal value with leftward and rightward transfers. Multiplying with trasferLosses. Removing unnecessary 10e-6 scaling.