1. 29 Oct, 2019 1 commit
  2. 03 Oct, 2019 1 commit
  3. 27 Sep, 2019 1 commit
  4. 04 Apr, 2019 2 commits
  5. 27 Mar, 2019 1 commit
  6. 08 Mar, 2019 2 commits
  7. 26 Feb, 2019 1 commit
  8. 12 Feb, 2019 1 commit
  9. 11 Feb, 2019 1 commit
  10. 01 Feb, 2019 1 commit
  11. 22 Jan, 2019 1 commit
  12. 11 Jan, 2019 1 commit
  13. 05 Dec, 2018 1 commit
  14. 03 Dec, 2018 1 commit
  15. 16 Nov, 2018 1 commit
  16. 15 Nov, 2018 1 commit
  17. 14 Nov, 2018 1 commit
  18. 11 Nov, 2018 1 commit
  19. 05 Nov, 2018 1 commit
  20. 02 Nov, 2018 2 commits
  21. 19 Oct, 2018 1 commit
  22. 12 Oct, 2018 1 commit
  23. 11 Oct, 2018 1 commit
  24. 09 Oct, 2018 1 commit
  25. 08 Oct, 2018 2 commits
  26. 05 Oct, 2018 2 commits
  27. 14 Sep, 2018 1 commit
  28. 11 Sep, 2018 1 commit
  29. 30 Aug, 2018 1 commit
    • Niina Helistö's avatar
      Changing results_t_start to t_initializationPeriod (=the number of time steps... · 0f1c9279
      Niina Helistö authored
      Changing results_t_start to t_initializationPeriod (=the number of time steps in the beginning of the simulation that are solved but not included in the results) and t_omitTrajectories to t_trajectoryHorizon (the number of time steps when start-up and shutdown trajectory constraints are 'active' in the beginning of each solution).
      0f1c9279
  30. 14 Aug, 2018 1 commit
  31. 24 Jul, 2018 1 commit
    • Niina Helistö's avatar
      Several updates · d90cd515
      Niina Helistö authored
      * taking investment costs into account in cost results calculation
      * adding transfer link investment possibility sets
      * moving run-up and shutdown trajectories into their own 'blocks' to speed up the model
      * commenting out some forecast related sets that are not used anymore
      * updating info file writing
      d90cd515
  32. 19 Jul, 2018 1 commit
  33. 14 Jul, 2018 1 commit
  34. 09 Jul, 2018 1 commit
  35. 10 May, 2018 1 commit
    • Juha Kiviluoma's avatar
      Changing the way reserves are treated. An additional penalty variable... · 13b9ebe3
      Juha Kiviluoma authored
      Changing the way reserves are treated. An additional penalty variable vq_resMissing can now be used to mitigate lack of reserves after gate closure while the former vq_resDemand is used only for the later time periods. This allows to fix reserves for the time periods between gate closure and reserve update-frequency. In this way problems arising from the forecast errors (VG cannot do what promised) can be mitigated by the vq_resMissing and it is then visible separately from the vq_resDemand (and they can have different penalty values). Released tertiary reserves cannot now be used to mitigate primary and secondary reserves - this could be re-implemented as an option if seen beneficial (and of course in a reserve type agnostic manner).
      13b9ebe3