Changed unit investment variables to not depend on the time step. The time step when a unit becomes available ("when a unit investment decision can be made") is defined in the set ut(unit, t, start_end).

Added fixed operation and maintenance costs for investment options
Adding a new parameter unitOutputCapacityTotal to avoid division by zero
Added unit investment result parameter
Removed equation q_fixedGenCap1U
Added default value calculation for reserves update frequency
Moved tCounter update outside ms loop in 3c_periodicLoop.gms
Updated the limits of v_invest_LP and v_invest_MIP (no more maxGenCap, minGenCap)
Updated investInit_temp.gms
And some smaller updates

Continuing to fix the reserves in the deterministic mode. Now they should also work after the first solve.

Reorganizing the result calculation to improve performance by moving all possible calculations to the end of the solveloop.

Fixing a bug where the startup costs were not scaled to MEUR when calculating the result cost arrays.

Implementing "ts_fuelPrice" time series based on the input "ts_fuelPriceChange" to avoid needlessly time consuming summation over "tFull" in the objective funciton.

Implementing "ts_fuelPrice", which avoids summation over the "ts_fuelPriceChange" in the "q_obj" during every solve. Also minor performance tweaking to "inputsLoop".

Implementing most of the results arrays from trtopi_develop_RealValue due to their overall usefulness.

All parameters in the model definition files now include the mType dimension to avoid overwriting of parameters if multiple models are declared.

Rewriting the efficiency approximation calculations, as well as reimplementing diagnostic COP and efficiency results.

Some minor readability and performance upgrades as well.

Rewrote 4a_outputVariant to match the new forecast-time structure. Model should be able to run now, but the structure still has to be excessively debugged in order to make the outputs make sense.

Also moved ft_nReserves definition inside the interval loop in order to possibly save an insignificant amount of execution time.

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

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.

Fixing problems in using forecasts and reserves. May include some ad hoc changes that need to be cleared up later.

Also added diagnostic result vectors "d_cop" and "d_eff" that calculate the realized COP of energy conversion units and the efficiency of fuel units. These are mainly used for testing and debug purposes, as the COP and efficiency time series for norman operation aren't all that interesting.

Previously "ts_absolute" and "ts_energyDemand" were kind of redundant, and the name "ts_absolute" wasn't all that intuitive. The two time series are now replaced by a single time series called "ts_influx", that hopefully gets its point accross even slightly better.

Added the final state and transfer variables to the results, as well as a cautionary reminder regarding the way the length of the time series form data is determined in the model. This issue will need to be addressed at some point.

The length of the time series data is currently determined as the maximum length of any provided "ts_energyDemand" input. However, this time series is not required for all modelling purposes, as it can be substituted by the "ts_absolute" in most (if not all) cases. If "ts_energyDemand" is not included in the input, the set "ct(t)" will not function properly, causing (at the very least) the looping of the timeseries data to fail. Then again, I'm fairly certain the loop also fails if the time series don't have compatible lengths, e.g. some time series input is shorter than the maximum length of "ts_energyDemand".

1) Units and nodes can be aggregated in later time steps
2) Piecewise linear implementations (SOS1 and SOS2) for part-load conversion efficiency
3) Piecewise linear implementation can change in later time periods

Big name convention clean-up. Most parameters now start with p_... Underscore in sets is used to draw the line between dimensions and explanatory text. Dimensions with one letter shorthands are always first in the name, even when they are not first dimensions.