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] NE Case Study in HERD could be faster by cutting out redundant build steps #248
Is your feature request related to a problem? Please describe.
Building the Multiperiod model for the nuclear energy case study in HERD takes a while.
Describe the solution you'd like
In the DISPATCHES repo, the renewables case study has a way of speeding up construction of the full model. Instead of calling the flowsheet directly, it calls an intermediate function (e.g., "wind_battery_pem_tank_turb_mp_block" from here) that calls on the flowsheet once to create the model and on subsequent calls will clone the original model. It then proceeds to propagate any states using data pertaining to that timestep.
We can implement something similar for the nuclear case study in HERD to speed up the build process and the overall run time. It would also bring HERD closer to a more standardized structure (overall goal being to run any flowsheet in a generalized way). The intermediate function in DISPATCHES is made specifically for one case study, so HERD would need to create a more generalizable intermediate function instead.
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. Building the Multiperiod model for the nuclear energy case study in HERD takes a while.
Describe the solution you'd like In the DISPATCHES repo, the renewables case study has a way of speeding up construction of the full model. Instead of calling the flowsheet directly, it calls an intermediate function (e.g., "wind_battery_pem_tank_turb_mp_block" from here) that calls on the flowsheet once to create the model and on subsequent calls will clone the original model. It then proceeds to propagate any states using data pertaining to that timestep.
We can implement something similar for the nuclear case study in HERD to speed up the build process and the overall run time. It would also bring HERD closer to a more standardized structure (overall goal being to run any flowsheet in a generalized way). The intermediate function in DISPATCHES is made specifically for one case study, so HERD would need to create a more generalizable intermediate function instead.
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.