GitLab

# Conflicts:
#	inc/3d_setVariableLimits.gms

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.

Move options to a separate file (1_input.gms) in the input directory and make a template for that in the root directory (1_input_temp.gms).

Enable the use of advanced basis. Three options: use the latest solve, use all solves from the previous run, use the first solve from the previous run.

Include t00000 for storage and online variables for the results output (as long as there are variable values for the first time period).

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

Updated spineToolbox.json which is needed to get Backbone running under Spine Toolbox (does not work yet)

Also changing the length of the forecast horizon so that it is now possible to either keep a static length for the forecasts or to have a decreasing forecast horizon that only extends forward at every tForecastJump.

# Conflicts:
#	Backbone.gms

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.

changes.inc is loaded in the 1e_input.gms where the changes to the input files are made right after loading data from the gdx files

Removing an unnecessary conditional from the "q_startshut" equation, as well as a slight cosmetic change to "q_resDemand".

The condition ${ ord(t) + dt(t) > mSettings(m, 't_start') } is unnecessary, as the model can currently freely decide which power plants are online on t00 without any costs in the objective function. Thus, it should no longer be necessary to neglect this equation on the first active time step.

Fixing an issue where the state variable upper and lower bounds weren't imposed for the very first time step.

Made the mft_lastSteps calculations more robust, so that the horizons and time steps don't have to match exactly in order for the model to find the last active time step.