Repository navigation
Conversation
…(to be closer to the terms of the article)
|
Tick the box to add this pull request to the merge queue (same as
|
|
#1237 must be amended accordingly |
There was a problem hiding this comment.
You are right. This is legacy but not correct.
ArthurGodet
left a comment
There was a problem hiding this comment.
For me, modifications are OK, but as @jgFages said, I agree there is a forcePropagate() to change.
That said, the failing test should also be investigated on why it is failing
Done 😉 |
|
I’ve just spent a bit of time looking into what the problem is with the test that’s failing. Given the complexity of the algorithm and the underlying structures, the fact that the original contributor cannot be easily contacted, and the time I have already spent on this issue, I am reluctant to look into it further. I propose amending this pull request to add a comment explaining the use of the constraint in question and opening a separate issue to describe the bug. |
|
I plunged back into the 2nd error and it seems that there is a bug in the neighbourhood. |
+ new assertion that check the trees consistency + add new tests that exhibit propagation strength
Branch fix_1231 brings the following improvements to the Knapsack module:
• Propagators (PropKnapsack, PropKnapsackKatriel01)
• Data structures (13 files)