1. 09 Aug, 2019 2 commits
  2. 15 Jul, 2019 1 commit
  3. 10 Jul, 2019 2 commits
  4. 26 Jun, 2019 1 commit
  5. 25 Jun, 2019 1 commit
  6. 17 Jun, 2019 3 commits
  7. 13 Jun, 2019 2 commits
  8. 10 Jun, 2019 2 commits
  9. 06 Jun, 2019 2 commits
  10. 05 Jun, 2019 1 commit
  11. 28 May, 2019 2 commits
  12. 27 May, 2019 1 commit
  13. 24 May, 2019 4 commits
  14. 16 May, 2019 1 commit
  15. 17 Apr, 2019 1 commit
  16. 15 Apr, 2019 1 commit
  17. 12 Apr, 2019 3 commits
  18. 11 Apr, 2019 3 commits
  19. 08 Apr, 2019 1 commit
    • Niina Helistö's avatar
      Adding an example of a post-processing file:... · c203057f
      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.
      c203057f
  20. 05 Apr, 2019 2 commits
  21. 04 Apr, 2019 4 commits