Moved reserve set definition from "periodicLoop" to "inputs". Minor changes to time series calculation, excluding unnecessary data in some cases.

Adding a small cost term to "v_spill" to avoid excessive spilling of hydro reserves. Also tweaking penalty factors and code readability.

Fixed an issue where the time series form reserve requirements were not calculated correctly for subsequent solves.

Minor correction to the online variable .up bounds, now imposed for the last realized state as well for safety.

Fixing the "v_spill" variable limits still being calculated as if the variable was in energy instead of power.

Value of keeping units online updated in the objective function, as well as minor tweaks to the penalty parameters.

Added a new displacement set "cf_Central" that binds the v_state variables of the shorter forecasts to the central forecast at the end of the forecast length to avoid issues with hydro reservoirs being overutilized in the shorter forecasts.

Rewrote the forecast update and improvement code into "inputsLoop", and fixed an issue where all capacity factor time series were being updated even if there was no data to update them.

Reimplemented the value of online units, but now using a set "uft_online_last" instead of the previous "p_uft_online_last" parameter.

Fixing an issue where the "v_reserve" variable for input units was being counted twice in the "q_resDemand" equation. Also limited the averaging of the "ts_reserveDemand_" time series to "t_reserveLength", as it is unnecessary to average the time series over the reserve horizon.

I'm unsure why the input units were handled separately in the "q_resDemand" equation, but it seems to me that this is a relic from versions past. No (node, unit) should be able to influence the properties of other nodes directly, as these types of interactions are handled either by the "v_transfer" or conversion units, which have separate (grid, node, unit) entities on each of the nodes concerned. These are included in the (node, unit, f, t) of their respective nodes, so there should be no need to include other reserve variables to the nodes.

Fixed the variable limits properly, as the issue was with the $onOrder $offOrder commands when determining interval averaging while data is being circulated.

Fixed an issue where the variable boundaries would not work correctly for long horizons where data needs to be circularly displaced.

Removed "p_uft_online_last" from use, as it is not currently working properly and possibly confuses the objective function.

At the moment, online variables are generated only for the time steps when they actually affect the v_gen variables. Thus, having this sort of incentive term to keep the units online at the end of the simulation is perhaps not necessary. The horizon extends over the t_end anyways, and the units keep on working as if they still had to keep on keeping on.

Fixing an isse of the online variables were not being recorded correctly, resulting in infeasibilities between solves.

Merge with "trtopi_develop" after first successful full-year simulation of the Northern European Power System.

Removed the "periodicLoopDispatch.gms" as unnecessary, as the optimization is no longer carried out in two separate stages.

Moved the initialization from "modelsLoop.gms" to "periodicLoop.gms" to get it in the repository. Various tweaks to make the code more readable.

Minor fixes to thew stored results, as well as only requiring upwards tertiary reserves to cover for the wind power fluctuations.

Variable values are wiped clean after each solve in order to conserve memory. References to previous variable values are now handled through the results parameters, e.g. "r_state". Additionally, initializing of the various sets, parameters etc. is now handled through the "Option clear" command, as I suspect it to be faster than the old method of resetting the values over the defined sets.

Before these changes, GAMS would occupy more and more memory the longer the model was set to run. This resulted in significant reduction of performance during simulations spanning e.g. a whole year with a large system, as every single variable value for each forecast time-step would be kept in memory, regardless of whether it was necessary for the current solve. In order to avoid this, temporary timeseries and variable values are now wiped clean between solves, and the desired results are committed to the results parameter arrays.

The results arrays will also bloat the memory requirements of each solve, but not as much as the unaltered variable values (and bounds). I imagine it would be possible to write these into some external file during the solve loop for safekeeping, and periodically wipe the results arrays as well in order to conserve memory for the calculations proper. However, this writing could slow the loop by itself, and might not be necessary for the current project work.

It seems that the equation values are still left in the debug file, and are presumably still carried along with the solves. Have to see if further changes are required to avoid unnecessary memory use.

Fixed an issue where the reserve variables common between the forecasts were not bound properly. Also removed an unnecessary index for q_resDemand.