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
[DEFECT] Static Histories do not work with Bayesian Opt #381
Describe the defect
Running a HERON XML script that uses <CSV> or Static Histories valued param rather than <ARMA> or Synthetic Histories fails when paired with the Bayesian Optimization algorithm in opt mode.
What did you expect to see happen?
This should run in opt mode. I tried it with Gradient Descent and it worked.
What did you see instead?
I got a RuntimeError when running outer.xml:
Do you have a suggested fix for the development team?
There's likely something in template_driver.py that should be fixed.
Describe how to Reproduce
Steps to reproduce the behavior:
Screenshots and Input Files
I've highlighted the modifications I made to the tests/integration_tests/mechanics/static_history/heron_input.xml file to reproduce the error.
Platform (please complete the following information):
OS: Windows
Version: [e.g. 22]
Dependencies Installation: [CONDA or PIP]
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?
Defect Description
Describe the defect Running a HERON XML script that uses
<CSV>
or Static Histories valued param rather than<ARMA>
or Synthetic Histories fails when paired with the Bayesian Optimization algorithm inopt
mode.What did you expect to see happen?
This should run in opt mode. I tried it with Gradient Descent and it worked.
What did you see instead?
I got a RuntimeError when running
outer.xml
:Do you have a suggested fix for the development team?
There's likely something in
template_driver.py
that should be fixed.Describe how to Reproduce Steps to reproduce the behavior:
Screenshots and Input Files
I've highlighted the modifications I made to the
tests/integration_tests/mechanics/static_history/heron_input.xml
file to reproduce the error.Platform (please complete the following information):
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.