- 04 Apr, 2019 1 commit
-
-
Topi Rasku authored
#65: *v_startup* divided into *v_startup_LP* and *v_startup_MIP* variants to avoid undesired behavior when using integer online variables.
-
- 03 Apr, 2019 12 commits
-
-
Topi Rasku authored
Replacing *IntervalStepCounter* with *tt_aggregate* due to the poor performance of *intervalStepCounter*.
-
Topi Rasku authored
*intervalStepCounter* now uses (counter, t) instead of (counter, counter_) due to the counter set being too limited in size.
-
Topi Rasku authored
-
Topi Rasku authored
-
Topi Rasku authored
Commenting out a couple *v_startup* and *v_shutdown* limits due to them being extremely slow, and not strictly necessary. The removed limits only aim to ensure that no startup and shutdown is performed if the unit online variable horizon doesn't extend far enough to cover the consequences. This is already ill-adviced, but should'nt have a significant impact on the model anyhow.
-
Topi Rasku authored
-
Topi Rasku authored
Rewriting large portions of *3c_inputsLoop.gms* to make it more compact, and hopefully increasíng performance as well.
-
Topi Rasku authored
-
Topi Rasku authored
-
Topi Rasku authored
-
Topi Rasku authored
-
Topi Rasku authored
-
- 29 Mar, 2019 1 commit
-
-
Erkka Rinne authored
Also a minor speedup for setting model dimension (set `msft` etc.)
-
- 28 Mar, 2019 5 commits
-
-
Erkka Rinne authored
-
Erkka Rinne authored
Changed behaviour of `mSetting` 't_perfectForesight' so that it’s defined from zero (not after 't_jump') The setting does not have any effect if 't_perfectForesight' is less than 't_jump'.
-
Erkka Rinne authored
-
Topi Rasku authored
-
Topi Rasku authored
Allow perfect foresight beyond realization horizon See merge request !5
-
- 27 Mar, 2019 10 commits
-
-
Erkka Rinne authored
New model setting `t_perfectForesight` gives number of time steps after `t_jump` where realization foreast is used
-
Erkka Rinne authored
-
Erkka Rinne authored
-
Erkka Rinne authored
# Conflicts: # inc/3b_periodicLoop.gms
-
Erkka Rinne authored
-
Erkka Rinne authored
-
Erkka Rinne authored
Standard deviations of scenario data now needs to be given as input.
-
Erkka Rinne authored
-
Erkka Rinne authored
-
Erkka Rinne authored
Uses new set `fts(f, t, s)` which is the same as `sft` but different order of domains.
-
- 22 Mar, 2019 1 commit
-
-
Topi Rasku authored
-
- 20 Mar, 2019 1 commit
-
-
Niina Helistö authored
-
- 19 Mar, 2019 1 commit
-
-
Erkka Rinne authored
Parameter `df_scenario` should be used only for stochastic data (nodes). Also using maximum downward slack and minimum upward slacks in time series aggregation as this was not implemented.
-
- 18 Mar, 2019 1 commit
-
-
Erkka Rinne authored
-
- 13 Mar, 2019 2 commits
-
-
Niina Helistö authored
-
Erkka Rinne authored
Also added some default values to scheduleInit_temp.gms
-
- 12 Mar, 2019 2 commits
-
-
Erkka Rinne authored
-
Erkka Rinne authored
-
- 11 Mar, 2019 2 commits
-
-
Erkka Rinne authored
-
Erkka Rinne authored
Also removed unnecessary set `s_stochastic`.
-
- 08 Mar, 2019 1 commit
-
-
Niina Helistö authored
Fixing the first part of issue #72. If ramping capability is too small compared to the min. load of the unit and the current interval length, the unit is allowed to ramp from zero to min. load in the start-up and from min. load to zero in the shutdown.
-