GitLab

`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.

r_genFuel was not working. Trying to fix it, but now it works only for units that have one input commodity - the results will be wrong if there are mutliple. Needs to be fixed later. I also added flow based generation. So, r_genFuel should really be r_genSource

#107

Changing the calculation of r_gnRealizedOperatingCost (and its derivatives) to use energy based allocation for fuel, emission and startup costs.

A couple of bug fixes to #107, according to suggestions in #107 (comment 14595)

Also some updates to 4d_postProcess_invest2schedule_temp.gms but using that for invest-schedule linking still doesn't really work with the dynamic generation portfolios.

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).

For results, vOM costs were calculated only from outputs, but they can also be in inputs nowadays. Corrected.

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)).

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

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.

First try to fix issue #97.

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

Diagnostic 'd_eff' and 'd_cop' now include +Eps to avoid inconsistent t-axes with GAMS plots. Minor readability changes.

Fixes to the diagnostic result vectors, as well as adding a command line argument to include them only when necessary.

Changing the 'p_nuRes2Res(node, unit, restype, up_down, restype)' description and function so that the first 'restype' also provides the second 'restype'.
Also moving the 'r_reserve2Reserve' calculation from "4a_outputVariant.gms" to "4b_outputInvariant" for efficiency.

Making "r_genUnittype" dimensions consistent with other result vectors, along with a minor performance improvement.

Changing results_t_start to t_initializationPeriod (=the number of time steps in the beginning of the simulation that are solved but not included in the results) and t_omitTrajectories to t_trajectoryHorizon (the number of time steps when start-up and shutdown trajectory constraints are 'active' in the beginning of each solution).

added 'fixedFuelFraction' for start-up fuels in param_unitFuel and replaced 'maxFuelFraction' for start-up fuels