A more general way to set initial conditions for state variables
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 11
- Forks
- 11
- Avg merge
- 8h 6m
- Merged PRs (30d)
- 1
Description
This is more of a philosophical issue. From my point of view, initial conditions are more related to particular runs of a given model than to the general definition of the dynamics and parameters. In other (code) words:
<Parameter name="x0" description="initial condition"/>
...
<OnStart>
<StateAssignment variable="x" value="x0"/>
</OnStart>
and then define x0 in each run. It would be interesting having mechanisms to grab initial conditions from data files, possibly generated by a previous simulation. That would require the definition of a standard format for storing timeseries.
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
No files, tests, or entry points are mentioned. Begin by locating the handling of Parameter, OnStart, and StateAssignment in the Java interpreter, then clarify the proposed per-run input and timeseries format requirements. Done would require an agreed design and implementation scope rather than a small isolated edit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100