[SCT- Workflow]: slc use case across risk-statement, affordability analysis, and coa
Open
@Cheng-Kevin2 is already working on this.
Since Apr 30, 2025.
- Dominant language
- No language data
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
SLC is already available from the risk statement, also ingesting it in the affordability analysis and COA exposes us to consistency problem with the assumption. To resolve there are several options:
- Remove SLC from risk-statement. This is not ideal as the risk-statement might be about a problem that only exists at a certain SLC scenario.
- Propagate the SLC assumption from the risk statement. This should work only with the affordability analysis, as there is only one risk statement for each analysis, but it would not work for COA without further restrictions. There can be multiple risk statements to a COA with different SLC.
- An option is to let the user specify the SLC for COA and limit the available selection of risk-statements to only those with a matching SLC.
Thoughts?
Split up into 2 tickets:
https://github.com/orgs/USACE/projects/17/views/13?pane=issue&itemId=108013818&issue=USACE%7Cchart-docs%7C277
https://github.com/orgs/USACE/projects/17/views/13?pane=issue&itemId=107981375&issue=USACE%7Cchart-docs%7C275
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.