1. 04 Aug, 2017 1 commit
  2. 25 Jul, 2017 1 commit
  3. 19 Jul, 2017 1 commit
  4. 25 Jun, 2017 1 commit
  5. 16 Jun, 2017 1 commit
  6. 11 May, 2017 2 commits
  7. 26 Apr, 2017 1 commit
  8. 13 Apr, 2017 1 commit
  9. 07 Apr, 2017 1 commit
  10. 28 Mar, 2017 1 commit
    • Topi Rasku's avatar
      Major rewriting and cleanup of the efficiency approximations (directOff,... · 5c5c68b2
      Topi Rasku authored
      Major rewriting and cleanup of the efficiency approximations (directOff, directOn, lambda), and some of the related sets.
      
      Previously, the efficiency approximations required specific efficiency data, and no more than 2 points of data were used. Now the approximations use all the relevant input data they can find (up to the defined maximum indeces) when determining the parameters, and tests have been implemented in "1e_inputs.gms" to abort Backbone execution and warn the user of incompatible input data with the desired approximations.
      
      However, without minimum load, there are still issues with the "directOn" and "lambda" approximations that could perhaps be solved.
      5c5c68b2
  11. 24 Mar, 2017 1 commit
  12. 23 Mar, 2017 1 commit
  13. 22 Mar, 2017 1 commit
  14. 16 Mar, 2017 1 commit
    • Topi Rasku's avatar
      Adding "lb" parameters for the "lambda" efficiency approximation, since "lb"... · a8c64fcf
      Topi Rasku authored
      Adding "lb" parameters for the "lambda" efficiency approximation, since "lb" is used in "p_effGroupUnit" and "q_maxDownward".
      
      Since the "lambda" approximation doesn't use the "lb" parameter for anything, it is simply set to have the same value as each "rb" parameter. This should result in the correct value for the "p_effGroupUnit".
      a8c64fcf
  15. 15 Mar, 2017 1 commit
  16. 09 Mar, 2017 1 commit
    • Topi Rasku's avatar
      Added the final state and transfer variables to the results, as well as a... · 35d02677
      Topi Rasku authored
      Added the final state and transfer variables to the results, as well as a cautionary reminder regarding the way the length of the time series form data is determined in the model. This issue will need to be addressed at some point.
      
      The length of the time series data is currently determined as the maximum length of any provided "ts_energyDemand" input. However, this time series is not required for all modelling purposes, as it can be substituted by the "ts_absolute" in most (if not all) cases. If "ts_energyDemand" is not included in the input, the set "ct(t)" will not function properly, causing (at the very least) the looping of the timeseries data to fail. Then again, I'm fairly certain the loop also fails if the time series don't have compatible lengths, e.g. some time series input is shorter than the maximum length of "ts_energyDemand".
      35d02677
  17. 13 Feb, 2017 1 commit
  18. 13 Dec, 2016 1 commit
  19. 29 Nov, 2016 1 commit
  20. 04 Oct, 2016 2 commits
  21. 27 Sep, 2016 1 commit
    • Juha Kiviluoma's avatar
      Big changes. · 0913d330
      Juha Kiviluoma authored
      1) Units and nodes can be aggregated in later time steps
      2) Piecewise linear implementations (SOS1 and SOS2) for part-load conversion efficiency
      3) Piecewise linear implementation can change in later time periods
      0913d330
  22. 29 Aug, 2016 1 commit
  23. 22 Aug, 2016 1 commit
  24. 18 May, 2016 1 commit