[FEAT-Roadmap]: Create Incremental assumption analysis functionality
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
I received two major use cases in the form of user stories. We want to make sure our workflow design would be compatible to these two use cases.
Title: Incremental assumption analysis
User Story:
As a modeler, I want replicate past simulation runs sometimes with small changes to the inputs or assumptions so that I can do incremental analysis by evaluating the change between each simulation.
Notes:
Modeling is inherently an iterative process, your first simulation is probably not going to be the one that you need. It is very often the case that you do a run, saw that something is wrong, change one of the assumption or underlying data, then rerun. We want to make the comparison between the two modeling runs as easy as possible as to identify the incremental difference between the two. If you think of a side-to-side comparison, then you got the right idea.
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.
Research direction
The issue names no files, tests, or entry points. Start by reviewing the existing workflow design and how simulation runs, inputs, and assumptions are represented, then clarify the scope and acceptance criteria for comparing two runs with incremental changes. Done should be defined by an agreed design and workflow for the stated user story.
Written by the indexing model from the issue text.
Assessment
- Domain
- analytics, data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100