1. 03 May, 2020 1 commit
  2. 04 Mar, 2020 1 commit
  3. 28 Feb, 2020 2 commits
  4. 21 Feb, 2020 1 commit
  5. 20 Feb, 2020 1 commit
  6. 20 Dec, 2019 1 commit
  7. 22 Nov, 2019 1 commit
    • Niina Helistö's avatar
      A fix related to issue #112: changed omCosts from p_unit to p_gnu and renamed... · 5e29f514
      Niina Helistö authored
      A fix related to issue #112: changed omCosts from p_unit to p_gnu and renamed to vomCosts. It is possible to give vomCosts also to input units, but in that case the user should select the sign carefully. The objective function includes a term:
      + sum(gnuft(grid, node, unit, f, t), + v_gen(grid, node, unit, s, f, t) * p_gnu(grid, node, unit, 'vomCosts'))
      which means that positive vomCosts result in decreasing objective function value when multiplied with negative v_gen. Positive vomCosts could be interpreted as an increase in consumer's utility. In this way, this fix may also be able to implement feature #76.
      5e29f514
  8. 24 Sep, 2019 1 commit
    • Niina Helistö's avatar
      Updating the two ROCOF constraints so that they apply to a group of nodes... · b89322d8
      Niina Helistö authored
      Updating the two ROCOF constraints so that they apply to a group of nodes instead of individual nodes.
      
      The transfer ROCOF constraint considers failures of interconnectors with one end inside the group and one end outside the group. 'DefaultFrequency' and 'ROCOF' are now p_groupPolicy parameters instead of p_gn parameters.
      b89322d8
  9. 05 Sep, 2019 1 commit
  10. 03 Sep, 2019 1 commit
  11. 02 Sep, 2019 3 commits
  12. 30 Aug, 2019 1 commit
  13. 27 Aug, 2019 1 commit
  14. 10 Jul, 2019 1 commit
  15. 17 Jun, 2019 1 commit
  16. 28 May, 2019 1 commit
  17. 27 May, 2019 1 commit
  18. 03 Apr, 2019 2 commits
  19. 28 Mar, 2019 1 commit
  20. 27 Mar, 2019 1 commit
  21. 19 Mar, 2019 1 commit
  22. 12 Mar, 2019 1 commit
  23. 04 Mar, 2019 1 commit
    • Niina Helistö's avatar
      Making it possible to choose in the modelsInit.gms file whether to include the... · 83dc0fda
      Niina Helistö authored
      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.
      83dc0fda
  24. 27 Feb, 2019 1 commit
    • Ciara O'Dwyer's avatar
      Incremental heat rate bounds 1-3 removed · 5022fd30
      Ciara O'Dwyer authored
      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)
      5022fd30
  25. 26 Feb, 2019 3 commits
  26. 22 Feb, 2019 1 commit
  27. 12 Feb, 2019 1 commit
  28. 07 Feb, 2019 1 commit
  29. 29 Jan, 2019 2 commits
  30. 28 Jan, 2019 2 commits
  31. 18 Jan, 2019 1 commit
  32. 16 Jan, 2019 1 commit