- 10 Jul, 2019 2 commits
-
-
ran li authored
-
- 26 Jun, 2019 1 commit
-
-
Niina Helistö authored
Updates related to issue #85: ignoring 'empty' units and changing the condition when to expand effLevelGroupUnit
-
- 25 Jun, 2019 1 commit
-
-
Niina Helistö authored
-
- 17 Jun, 2019 3 commits
-
-
Niina Helistö authored
-
Topi Rasku authored
*effLevelGroup* is now expanded so that subsequent *effLevels* are repeated from the previous *effLevel* if definition is missing. Execution is aborted if *level1* information is missing for any unit.
-
Topi Rasku authored
-
- 13 Jun, 2019 2 commits
-
-
Niina Helistö authored
-
Niina Helistö authored
-
- 10 Jun, 2019 2 commits
-
-
Topi Rasku authored
#82: All hard-coded *elec* grids have been removed and replaced by looping/summing over *gn* instead. This fix should work as long as no *node* belongs to multiple *grids*, which I think is already ill-advised (or even forbidden?).
-
Erkka Rinne authored
-
- 06 Jun, 2019 2 commits
-
-
Topi Rasku authored
-
Erkka Rinne authored
-
- 05 Jun, 2019 1 commit
-
-
Niina Helistö authored
-
- 28 May, 2019 2 commits
-
-
Niina Helistö authored
-
- 27 May, 2019 1 commit
-
- 24 May, 2019 4 commits
-
-
Juha Kiviluoma authored
Reading changes.inc just from the 1e_inputs.gms (it was also in 1e_scenChanges.gms). Updating sceleton.json and removing obsolete reference to includeInputdata_ext.inc.
-
Juha Kiviluoma authored
-
Juha Kiviluoma authored
-
Juha Kiviluoma authored
-
- 16 May, 2019 1 commit
-
-
Topi Rasku authored
(cherry picked from commit 45076128)
-
- 17 Apr, 2019 1 commit
-
-
Topi Rasku authored
-
- 15 Apr, 2019 1 commit
-
-
Topi Rasku authored
-
- 12 Apr, 2019 3 commits
-
-
Niina Helistö authored
Fixing a bug in ramp tier limits: For units with shutdown trajectories, the ramp tier limit was twofold at the interval when the shutdown begins.
-
Topi Rasku authored
-
Topi Rasku authored
-
- 11 Apr, 2019 3 commits
-
-
Niina Helistö authored
Resolved conflicts in inc/2d_constraints.gms (e.g. start-up and shutdown variables).
-
Niina Helistö authored
-
Niina Helistö authored
-
- 08 Apr, 2019 1 commit
-
-
Niina Helistö authored
Adding an example of a post-processing file: 4d_postProcess_invest2schedule_temp.gms. The contents of the file can be copied to a 4d_postProcess.gms file and saved in the input folder so that it is read by Backbone. The contents of the file is meant for saving the invest model results in a format that can be directly used by the schedule model. The results transfer works when running Backbone using Titan and when the schedule setup is a child of the invest setup in the Titan setup tree. The invest model writes and outputs a changes.inc file which is then read by the schedule model.
-
- 05 Apr, 2019 2 commits
-
-
Topi Rasku authored
-
Topi Rasku authored
# Conflicts: # inc/3c_inputsLoop.gms
-
- 04 Apr, 2019 7 commits
-
-
Topi Rasku authored
-
Topi Rasku authored
-
Topi Rasku authored
-
Topi Rasku authored
-
Topi Rasku authored
-
Topi Rasku authored
-
Topi Rasku authored
-