TimefoldAI / TimefoldAI/timefold-solver
Detect the constraint causing a score corruption
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 228
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 46
Description
Is your feature request related to a problem? Please describe.
When the solver hits a score corruption coming from constraints, it's often tedious to minimize the dataset and active constraints to isolate it.
Describe the solution you'd like
Imagine hitting a score corruption (e.g. with a TRACKED_FULL_ASSERT mode) and getting the score analysis diff (last state before and after a SC). Instead of trying which constraints (or their combination) create the SC, the diff would already report the suspects.
Moreover, if we can also get the matches, that would simplify even minimizing the dataset.
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 with TRACKED_FULL_ASSERT mode and the existing score analysis diff around a score corruption (SC), comparing the last state before and after the corruption. Define the work around reporting suspect constraints or constraint combinations and, if possible, their matches; done means the report helps identify both without manually minimizing the dataset and active constraints.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100