Time resolution for condition testing
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 11
- Forks
- 11
- Avg merge
- 8h 6m
- Merged PRs (30d)
- 1
Description
Checking a condition (OnCondition element in dynamics) at the end of a step is a bit inaccurate (see bounce example without zeroing the height for a serious failure). Integrators should at least interpolate, and maybe solve for the exact time when the condition is passed.
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
Start by tracing how OnCondition elements in dynamics are evaluated by the integrators, then reproduce the bounce example without zeroing the height. Determine how condition crossings are currently handled at step boundaries; done means condition timing is more accurate through interpolation or exact crossing-time handling, with regression coverage for the example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100