SciML / SciML/EasyModelAnalysis.jl
violating constraint during optimization
Open
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 87
- Forks
- 14
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 19
Description
Currently, constraints are only checked at the point of intervention.
But it is possible a constraint is violated before the intervention happens, and then dips below it again.
I think the current approach will miss that?
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
Start by reading src/intervention.jl at lines 38-40 and trace how constraints are evaluated during optimization. Reproduce a case where a constraint is violated between interventions, then determine and document the expected behavior and add coverage showing that transient violations are detected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100