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).
Describe the defect
When a HERON case is run on the HPC in the opt mode, the std_NPV is being reported as nan. This issue has started after a recent RAVEN update.
What did you expect to see happen?
std_NPV has been reported as a number for all the cases run up to the point before RAVEN was updated. Upon running older cases which had std_NPV reported as numbers, their std_NPVs are now generated as nan
This has been tested on another user's machine as well.
Do you have a suggested fix for the development team?
Describe how to Reproduce
Steps to reproduce the behavior:
Update RAVEN
Run a HERON case
Check std_NPV
Screenshots and Input Files
Please attach the input file(s) that generate this error. The simpler the input, the faster we can find the issue.
Platform (please complete the following information):
OS: Windows
Version: 10
For Change Control Board: Issue Review
This review should occur before any development is performed as a response to this issue.
[ ] 1. Is it tagged with a type: defect or task?
[ ] 2. Is it tagged with a priority: critical, normal or minor?
[ ] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
[ ] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
[ ] 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.
[ ] 1. If the issue is a defect, is the defect fixed?
[ ] 2. If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
[ ] 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)?
[ ] 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)?
[ ] 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?
std_NPV being produced as nan
Describe the defect When a HERON case is run on the HPC in the opt mode, the std_NPV is being reported as nan. This issue has started after a recent RAVEN update.
What did you expect to see happen?
std_NPV has been reported as a number for all the cases run up to the point before RAVEN was updated. Upon running older cases which had std_NPV reported as numbers, their std_NPVs are now generated as nan
This has been tested on another user's machine as well.
Do you have a suggested fix for the development team?
Describe how to Reproduce Steps to reproduce the behavior:
Screenshots and Input Files Please attach the input file(s) that generate this error. The simpler the input, the faster we can find the issue.
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.