1. 07 Oct, 2019 2 commits
  2. 09 Sep, 2019 1 commit
  3. 06 Sep, 2019 1 commit
    • Niina Helistö's avatar
      Some changes related to issues #57 and #96: · 3821b6cf
      Niina Helistö authored
      q_maxUpward: Moving "not nuOfflineRescapable(restype, node, unit)" from equation condition to a condition for summing reserve variables
      
      q_maxUpward2: Removing many of the equation conditions (does not apply to consumption units, for example), cleaning up terms in the equation (hopefully not removing anything that should have stayed)
      
      q_maxUpward3: Not sure if this constraint is needed, so ignoring it in invest and schedule models -- can be included again if needed
      
      q_reserveProvision2: Some refinements to the equation conditions and the equation terms in order to make the constraint limit the online reserve provision of units with online variables
      
      q_rampUpLimit: Moving "not nuOfflineRescapable(restype, node, unit)" from equation condition to a condition for summing reserve variables
      
      q_rampUpLimit2: Not sure if this constraint is needed, so ignoring it in invest and schedule models -- can be included again if needed.
      3821b6cf
  4. 02 Sep, 2019 1 commit
  5. 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
  6. 28 Jan, 2019 1 commit
  7. 16 Jan, 2019 1 commit
  8. 13 Dec, 2018 1 commit
  9. 05 Nov, 2018 1 commit
  10. 01 Nov, 2018 2 commits
  11. 20 Aug, 2018 1 commit
  12. 17 Jul, 2018 1 commit
  13. 10 Jul, 2018 1 commit
  14. 06 Jul, 2018 1 commit
  15. 07 Jun, 2018 1 commit
  16. 10 Apr, 2018 1 commit
  17. 06 Apr, 2018 1 commit
  18. 28 Mar, 2018 2 commits
  19. 26 Mar, 2018 1 commit
    • Niina Helistö's avatar
      Several fixes to make the investment model work: · 6b70441c
      Niina Helistö authored
      Added fixed operation and maintenance costs for investment options
      Adding a new parameter unitOutputCapacityTotal to avoid division by zero
      Added unit investment result parameter
      Removed equation q_fixedGenCap1U
      Added default value calculation for reserves update frequency
      Moved tCounter update outside ms loop in 3c_periodicLoop.gms
      Updated the limits of v_invest_LP and v_invest_MIP (no more maxGenCap, minGenCap)
      Updated investInit_temp.gms
      And some smaller updates
      6b70441c
  20. 24 Oct, 2017 1 commit
    • Topi Rasku's avatar
      Model definition files included in the VCS now only include the GAMS... · 3498697c
      Topi Rasku authored
      Model definition files included in the VCS now only include the GAMS definition (list of included equations), all of which are read by Backbone to allow for easier swapping of models without having to tamper with the "3e_solve.gms" fole. Rest of model parameters are expected to be given as input through the renamed "modelsInit.gms" in the input folder (by default). "periodicLoop.gms" and "periodicInit.gms" now treated as integral parts of the Backbone model.
      
      Example input parameters provided by the "scheduleInit_temp.gms", "buildingInit_temp.gms" and "investInit_temp.gms" included in the defModels folder within the VCS.
      3498697c