This way the explanations can be exported programmatically.

Issue #137

new parameters added to p_groupPolicy to allow for selection of static and/or dynamic inertia constraints

`p_storageValue` is the constant form parameter, while `ts_storageValue` is the corresponding timeseries. `ts_storageValue_` is also added to handle time step aggregation and data circulation of `ts_storageValue` in the objective function. A new flag in `p_gn` called `storageValueUseTimeSeries` controls whether the constant `p_storageValue` or the timeseries `ts_storageValue` is used.

WIP: I have no clue what the file `1e_scenmChanges.gms` is supposed to do, so no changes have been made there. However, since the input data is affected by these changes, I assume that this file will need to be changed as well for this fix to work properly.

Replacing the "*" dimension with "param_policy" in some reserve parameters to avoid any typos and mistakes in input data

#107

Some clean-up to 1a_definitions.gms. Some of the unused params are now commented out but could also be deleted if we are agree that they will not be implemented in the near future.

Re-implementing dynamic generation portfolios (see issue #119). Unit investment variables still have the 't' dimension, although it is kind of redundant. Units have technical lifetimes (given in ut set) but links are assumed to stay in the system forever after they have been built. Cost discounting and multi-year horizons are considered in the objective function but not in the results outputting yet.

First working commit for the new inputs and outputs system. Probably buggy... In Google Drive there is 8unit system excel that works with this (vInputOutput.xlsx).

A fix related to issue #112: changed omCosts from p_unit to p_gnu and renamed to vomCosts. It is possible to give vomCosts also to input units, but in that case the user should select the sign carefully. The objective function includes a term:
+ sum(gnuft(grid, node, unit, f, t), + v_gen(grid, node, unit, s, f, t) * p_gnu(grid, node, unit, 'vomCosts'))
which means that positive vomCosts result in decreasing objective function value when multiplied with negative v_gen. Positive vomCosts could be interpreted as an increase in consumer's utility. In this way, this fix may also be able to implement feature #76.

Updating the two ROCOF constraints so that they apply to a group of nodes instead of individual nodes.

The transfer ROCOF constraint considers failures of interconnectors with one end inside the group and one end outside the group. 'DefaultFrequency' and 'ROCOF' are now p_groupPolicy parameters instead of p_gn parameters.

ran li authored Sep 03, 2019 and ran li committed Sep 03, 2019

Now the ReserveShareMax could control its reserve type and direction with the newly introduced p_nReserves3D which should also be reflected as a new sheet in the excel file.

Added a conditional to the equation and added the portion_of_transfer_to_reserve also to reserve transfers.

ran li authored Aug 27, 2019 and ran li committed Aug 27, 2019

The reserve for largest interconnector(transmission line) is included, with separate equations for up and down reserve

ran li authored Jul 10, 2019 and ran li committed Jul 10, 2019

Ciara's codes:minCons constraint allows to set the min load for PHS while still allowing foll reserve

*intervalStepCounter* now uses (counter, t) instead of (counter, counter_) due to the counter set being too limited in size.

Rewriting large portions of *3c_inputsLoop.gms* to make it more compact, and hopefully increasíng performance as well.

Changed behaviour of `mSetting` 't_perfectForesight' so that it’s defined from zero (not after 't_jump')

The setting does not have any effect if 't_perfectForesight' is less than 't_jump'.

New model setting `t_perfectForesight` gives number of time steps after `t_jump` where realization foreast is used

Parameter `df_scenario` should be used only for stochastic data (nodes). Also using maximum downward slack and minimum upward slacks in time series aggregation as this was not implemented.

Making it possible to choose in the modelsInit.gms file whether to include the two additional incremental heat rate equations that use binary variables:
- mSettings(m, 'incHRAdditionalConstraints') = 0: use the constraints but only for units with non-convex fuel use
- mSettings(m, 'incHRAdditionalConstraints') = 1: use the constraints for all units represented using incremental heat rates
Enabling incremental heat rates also in the invest model (and potentially in the building model). Some clean-up to the incremental heat rate equations.

New data parameter hrsection defined (using section will change Lambda results)
Slope for incremental heat rates now defined based on max efficiency (not used in conversion constraints - approximation only required)

Also enables the use of scenario tree construction with SCENRED2

Adding a possibility to use constant fuel prices instead of time series ones. NOTE! Contains a 'trick' to avoid additional inputs for convenience.

Renaming 'shutCost' to 'shutdownCost' to be more consistent with the current naming scheme, and included it in 'param_unit' to avoid errors if not defined in data.