TimefoldAI / TimefoldAI/timefold-solver
Feat: Construction Heuristic should allow configuring move selectors for list variables
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.
Currently, it is impossible to configure move selectors for the CH when list variables are
used, unlike chained and normal planning variables. This means it impossible
to configure a filter that prevent values that will break hard constraints
from being picked.
Describe the solution you'd like
It should be possible to configure CH move selectors when list variables are used in the SolverConfig:
<constructionHeuristic>
<constructionHeuristicType>FIRST_FIT</constructionHeuristicType>
<listChangeMoveSelector>
<filterClass>...Filter</filterClass>
...
</listChangeMoveSelector>
...
</constructionHeuristic>
Additional context
https://github.com/TimefoldAI/timefold-solver/discussions/814
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 at the SolverConfig constructionHeuristic configuration and use discussion #814 for the surrounding context. Add support for configuring a listChangeMoveSelector, including filterClass, when list variables are used with the construction heuristic; done means the XML configuration is accepted and the selector affects construction heuristic moves.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- ai
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100