GitLab

ran li authored Nov 25, 2019 and ran li committed Nov 25, 2019

Bug fix: in debugSymbols.inc, the p_nReserves and p_nuReserves are causing errors with debug mode 2, because they are actually deleted from the model. Fixing by replace both with p_groupReserves and p_gnuReserves

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.

Fixing a division by zero problem that sometimes occurred when writing results (very small but nonzero r_gnuTotalGen(grid, node, unit)).

Updating the order in which 1e_scenChanges.gms and changes.inc are read. Updating the contents of 1e_scenChanges.gms to match with the current naming of sets and parameters.

Probabilities of single scenarios can be slightly above one as returned
by SCENRED2. Limit the probabilities to one.

Merge branch 'LossOfLargestInterconnector' into dev. Includes updates related to issues #69, #90, #91.

Removing q_resDemandLargestInfeedTransferUp and q_resDemandLargestInfeedTransferDown, as q_resDemandLargestInfeedTransfer can handle both.

Added new parameter `ts_energy_(s)` to which total energy is
calculated. This parameter has the sample dimension last, as required
by the SCENRED2 tool. This allowed changing all other time series
to have indices `s, f, t` instead of previous `f, t, s` and dropping
the set `fts` completely.

Fixes #105

Fixes #106

Only use scenarios with positive probability in building the long-term
stochastic tree. Previously this was limited to the number of scenarios,
but this allows excluding a scenario (setting its prob. to zero).

There were warnings about nested $ifthen structures and stray names
with spurious commas in symbol declarations.

Contains a link to the wikipage containing small example datasets.

Adding the grid dimension to the reserve parameters and variables. Changes required to the input files. Removing the obsolete nuft set. Issue #69.

Updating constraints for maximum share of reserve provision, ROCOF limit, as well as reserve demand caused by largest unit infeed and largest transfer link import/export. Testing one constraint for reserve demand caused by largest transfer link import/export (instead of two separate constraints).

See #102

The parameters were not cleared at every loop.

See #99

Removed now obsolete scalar `errorcount`.

Solves #102

Fixes #100

Set `gn_forecasts(*, node, timeseries)` tells for which grid/flow/restype, node and timeseries combinations use forecasts and by default includes everything.

See: #99

First tests, disabling all reserve requirement constraints except q_resDemand. Adding some new parameters and sets (df_reservesGroup, restypeDirectionGroup, restypeDirectionGridNodeGroup) and changing the dimensions of some other parameters, sets and variables.

Nhniina bound cyclic

See merge request !7

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.