Fix non-terminating sorted propagation#227
Open
zayenz wants to merge 1 commit into
Open
Conversation
zayenz
force-pushed
the
feature/sort-element-propagation
branch
from
0149f4d to
1bac56a
Compare
zayenz
force-pushed
the
feature/sort-element-propagation
branch
from
1bac56a to
a94f083
Compare
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
1 participant
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.
Sorted propagation could loop when domain narrowing left a matching component without an output interval compatible with an input variable. The component endpoint links to itself, so the lower- or upper-bound walk never advanced.
Treat an exhausted component as an infeasible matching instead. The reported FlatZinc model is retained as a regression and completes with all three solutions.
Checked with the focused regression, the native sorted tests, and repeated runs of the original model.
Closes #168.