[TASK] Add support for using a CSV file to specify system design points #419
Description
Issue Description
The only sampling strategy currently supported by HERON is RAVEN's Grid sampler (MonteCarlo is also used, but for random variables and synthetic histories, not component capacities and the like). Often times, there are design points on a grid that just don't make sense, and it would be helpful to not have to run every point produced by a grid sampler. Adding support to specify exactly which design points you want the workflow to run would give users more fine-tuned control over their workflows, even allowing users to use sophisticated sampling schemes to select points to run, then running just those points. This could be implemented with a RAVEN CustomSampler.
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?