making future om lists easier to use
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 21
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
I think there could be some ways to make future om lists more user friendly.
I think it might be helpful to allow users to put in extra info than needed for cuustom future om lists, as there may be times when users decide to run less iterations or less years. This would allow them to do so without needing to change the custom list.
It would also be helpful if users were able to put "all" for the iterations they want to apply values to, and SSMSE could expand it to all iterations for the given scenario.
We could also do something similar for the model change lists, where changes that are beyond the end year of the simulation are simply ignored (this may already happen, not sure)...
Contributor guide
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.
Research direction
No files, tests, or entry points are named. Start by locating the code that reads future OM lists and model change lists, then determine how iteration ranges, year ranges, and the proposed "all" value are currently validated. Done should be defined separately for extra entries, "all" iterations, and changes beyond the simulation end year.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100