Check behavior of timestep when using GriddynRunner
Open
Nobody has claimed this yet.
- Dominant language
- MATLAB
- Stars
- 63
- Forks
- 27
- Avg merge
- 12h 9m
- Merged PRs (30d)
- 33
Description
See how the timestep parameter is used when running in a coupled simulation -- should be treated as the maximum time delta from the current time? vs telling GridDyn what time it should be at after returning from the step function.
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 file or test is named. Start by locating the GriddynRunner entry point and tracing how the timestep parameter is passed during coupled simulation; document whether it is a maximum delta or the target time after the step, with tests or examples showing the agreed behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- matlab
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100