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).
Is your feature request related to a problem? Please describe.
It would be convenient for HERON to have a more streamlined workflow to solve techno-economic analyses. This would also allow for comparison between bilevel and single solutions for various systems.
Describe the solution you'd like
Access to an option within the input file to run an alternate workflow that has the same capabilities as the standard workflow using the default dispatcher.
Describe alternatives you've considered
In cases where the dispatcher is cooperative with the capacity selection (like in the case of the default pyomo dispatcher), it is unnecessary to have a bilevel optimization formulation. In these cases, a single level pyomo formulation should suffice.
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. It would be convenient for HERON to have a more streamlined workflow to solve techno-economic analyses. This would also allow for comparison between bilevel and single solutions for various systems.
Describe the solution you'd like Access to an option within the input file to run an alternate workflow that has the same capabilities as the standard workflow using the default dispatcher.
Describe alternatives you've considered In cases where the dispatcher is cooperative with the capacity selection (like in the case of the default pyomo dispatcher), it is unnecessary to have a bilevel optimization formulation. In these cases, a single level pyomo formulation should suffice.
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.