Holistic Energy Resource Optimization Network (HERON) is a modeling toolset and plugin for RAVEN to accelerate stochastic technoeconomic assessment of the economic viability of various grid-energy system configurations, especially with application to electrical grids and integrated energy systems (IES).
Apache License 2.0
24
stars
38
forks
source link
[TASK] Update HERD to be compatible with newest DISPATCHES release #245
Is your feature request related to a problem? Please describe.
The newest DISPATCHES release upgrades to the newest IDAES version which adds functionality to the MultiPeriod class (it is now more compatible with stochastic runs). Within HERON, HERD should be able to use the MultiPeriod class when running the nuclear case study, just like the nuclear case study notebook in DISPATCHES. DISPATCHES also did some directory reorganizing, so paths need to be updated.
Describe the solution you'd like
HERD should build the MultiPeriod class and use it to create the Pyomo model. HERD should link functions in the init call of the MultiPeriod for fixing DoF, flowsheets, etc.
For Change Control Board: Issue Review
This review should occur before any development is performed as a response to this issue.
[x] 1. Is it tagged with a type: defect or task?
[x] 2. Is it tagged with a priority: critical, normal or minor?
[x] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
[x] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
[x] 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)
For Change Control Board: Issue Closure
This review should occur when the issue is imminently going to be closed.
[x] 1. If the issue is a defect, is the defect fixed?
[x] 2. If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
[x] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
[x] 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
[x] 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?
Issue Description
Is your feature request related to a problem? Please describe. The newest DISPATCHES release upgrades to the newest IDAES version which adds functionality to the MultiPeriod class (it is now more compatible with stochastic runs). Within HERON, HERD should be able to use the MultiPeriod class when running the nuclear case study, just like the nuclear case study notebook in DISPATCHES. DISPATCHES also did some directory reorganizing, so paths need to be updated.
Describe the solution you'd like HERD should build the MultiPeriod class and use it to create the Pyomo model. HERD should link functions in the init call of the MultiPeriod for fixing DoF, flowsheets, etc.
For Change Control Board: Issue Review
This review should occur before any development is performed as a response to this issue.
For Change Control Board: Issue Closure
This review should occur when the issue is imminently going to be closed.