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.

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

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.

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.

#65: *v_startup* divided into *v_startup_LP* and *v_startup_MIP* variants to avoid undesired behavior when using integer online variables.

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

Not all paths were replaced by custom input dir.

Samples can now be used to describe uncertain future after the forecast horizon

Reserve dummy variables use similar indexing as other reserve variables (again), and should now "stack" properly on each other so that lacking reserves in the commitment phase (vq_resDemand) are not penalized again in the real-time phase (vq_resMissing).

Reserve feasibility variables are now generated for each forecast branch separately despite other reserve commitments being common between the branches.
This should avoid potential issues with different "ts_reserveDemand" values.

Renaming "df_nReserves" to "df_reserves", changing "mft_nReserves" to "ft_reservesFixed", as well as a lot of accompanying changes.

Fixing a bug where the node state value change term in the objective function would become unbounded if the forecasts converge on the last timestep of the model horizon.

Introduce 'balancePenalty' as an additional node property. Now, PENALTY_BALANCE is defined on node level and it is possible to either define it as a constant value or a time series.

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

* taking investment costs into account in cost results calculation
* adding transfer link investment possibility sets
* moving run-up and shutdown trajectories into their own 'blocks' to speed up the model
* commenting out some forecast related sets that are not used anymore
* updating info file writing

Implementing maxFuelCons and maxFuelFraction. For main fuels, the parameters function as their names suggest; for start-up fuels, maxFuelCons is not implemented and maxFuelFraction is treated as exact fraction.

Adding ramping costs. Upward and downward ramps separated into different tiers (or 'slacks') with different costs.

Enabled the inclusion of additional constraints from the input data, the replacement of the objective function and the addition of new terms to the objective function. The basic file structure was also changed to better accommodate these.

Enabled the inclusion of additional constraints from the input data, the replacement of the objective function and the addition of new terms to the objective function. The basic file structure was also changed to better accommodate these.

Enabled the inclusion of additional constraints from the input data, the replacement of the objective function and the addition of new terms to the objective function. The basic file structure was also changed to better accommodate these.