Bug/restore full weekends - #200
Merged
Merged
Conversation
… full weekends calculation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Objective
Enforce a minimum number of full free weekends per planning horizon and make backend tests deterministic with the new solver constraint.
Breaking Change Notice
No API change.
This update adds a stricter hard solver constraint and can make some previously feasible schedules infeasible when
min_free_weekends_per_horizonis too high for the selected horizon.Scope
enforce_min_free_weekends_per_horizonto solver hard constraints.solver.min_free_weekends_per_horizonthrough solver context/engine.min_free_weekends_per_horizon=0where not under test).Validation
backend/.venv/Scripts/python.exe -m pytest -q backend/tests -qResults
82/82(100%).backend/config.jsonside effects.Risks and Mitigations