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
22
stars
36
forks
source link
[TASK] Include Windows testing for ipopt, cbc #334
With its setup as of this writing, the Windows test is skipping tests using ipopt and cbc as solvers due to either (1) the solvers not being on the machine, or (2) inability to correctly recognize if the solver is on the machine. See for example from #333 :
We should try to do one or more of the following:
Find a way to install ipopt and cbc via normal installation processes.
Assure ipopt and cbc are on the regression testing machines and point users to how to obtain these solvers for themselves.
Determine how to include openly available solvers as part of one-step installation processes.
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.
[ ] 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?
Issue Description
With its setup as of this writing, the Windows test is skipping tests using ipopt and cbc as solvers due to either (1) the solvers not being on the machine, or (2) inability to correctly recognize if the solver is on the machine. See for example from #333 :
We should try to do one or more of the following:
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.