New model setting `t_perfectForesight` gives number of time steps after `t_jump` where realization foreast is used

Also removed unnecessary set `s_stochastic`.

Making it possible to choose in the modelsInit.gms file whether to include the two additional incremental heat rate equations that use binary variables:
- mSettings(m, 'incHRAdditionalConstraints') = 0: use the constraints but only for units with non-convex fuel use
- mSettings(m, 'incHRAdditionalConstraints') = 1: use the constraints for all units represented using incremental heat rates
Enabling incremental heat rates also in the invest model (and potentially in the building model). Some clean-up to the incremental heat rate equations.

New data parameter hrsection defined (using section will change Lambda results)
Slope for incremental heat rates now defined based on max efficiency (not used in conversion constraints - approximation only required)

Also enables the use of scenario tree construction with SCENRED2

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

Replace the p_effGroupunit(*,*,*,'section') with p_effunit(*,*,*,'section') in constraints.gms to avoid misusing of section in directoutput efficiency

ran li authored Feb 14, 2019 and ran li committed Feb 14, 2019

fix the bug caused by messing up p_effunit and p_effgroupunit which lead to section not working and it is ok now

Adding support for long time intervals in the first block, according to the suggestion in issue #68. Adding a couple of checks for the compatibility of the first interval block and t_jump.

Issue #55: Added a new 'param_eff' set for 'ts_effUnit' and 'ts_effGroupUnit', used 'param_unit' for 'ts_unit' for the time being. Created 'unit_timeseries' set to simplify writing conditionals for units with time series data. "inputsLoop" should now work for 'ts_unit', but the nature of 'ts_effUnit' and 'ts_effGroupUnit' should be further discussed before their inclusion into "inputsLoop".

Errors with interval blocks now print the 'counter' on which the error occurred. Minor readability change to  'q_genRamp'.

Issue #32: Slightly cleaning up the trajectory equations by separating 'p_uCounter_runUp' and 'p_uCounter_shutdown' into minimum and maximum arrays to avoid doing partial time step calculations in '2b_constraints.gms'

Issue #32: Units should now be able to shut down at the end of the shutdown trajectory without enforcing the units to stay offline on the same step. Also fixing a bug in the 'dt_toShutdown' calculation.

Issue #32: Run-up and shutdown trajectories overhauled to permit SOS2 ramping on the last/first run-up/shutdown intervals, as well as include main fuel consumption during run-up/shutdown. However, this formulation still fails to consider changing interval lengths.

Fixing a bug in determining the 'dataLength' if not provided by user, which could result in errors with small model horizons.

Set `longtermSamples` was erroneously cleared too late

Now includes also t00

Fixing issue #32. The last time interval in the run-up phase had a wrong limit for the q_rampUpLimit, this was corrected by calculating a new parameter p_u_maxRampSpeedInLastRunUpInterval. This might not be the only thing wrong. Needs to be checked futher.

Aggregated groups appeared in the results although the model was not using the effLevel where the aggregation starts. This was fixed by moving the set creation for aggregated units to 3a_periodic_Init.gms (because it needed mSettings that has m indice) and changing the way unit_aggregator, unit_aggregated and unit_noAggregate sets are defined (units that are aggregates will not appear any more at all if they are not defacto in use).

Minor fixes to 'tmp_dt', 't_active', 'ft_realized', 'ft_realized', 'ft_realizedNoReset' and 'msft_realizedNoReset' to allow for arbitrary 'stepsPerInterval' immediately on the first interval.

Removing 'dt_noReset' as unnecessary, now that 't_active' and 'dt' cover the required model history.
Also fixing the calculation of 'dt' for the first time step in 't_active'.

Activate this feature using active('scenRed') and setting mSettings parameters 'red_num_leaves' or 'red_percentage'.

Implementing a settings check that aborts execution if there are more efficiency levels defined in the model than there are in data.
Also adding abort messages to existing data and setting checks, as well as removing 'unit_current' as an unused asset.