You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The incorrect simplification (changing the bound to 95.0) is now fixed in the compiler. The fact that a>b is violated is a bug in Gecode, not in MiniZinc (I will close this bug here and report it for Gecode).
Although Guido managed to fix the flattening bug, the fix has only been implemented on the development branch. (We haven't released any new versions since the bug was fixed). This is also the reason that the issue is still open.
If you are still experiencing problems and you can't wait until the next release, then you might want to try to compile the develop branch and use that mzn2fzn binary. The problem should be fully fixed on that branch. (Although the problem in Gecode is a different issue as Guido mentioned)
Activity
a1880 commentedon Apr 10, 2017
I tried to uncover some rounding problems and modified the example:
The output is:
Dekker1 commentedon Oct 4, 2017
This bug seems to be caused by a faulty internal transformation. The resulting FlatZinc for this model is:
Fix incorrect simplification of float domain constraints. Fixes #159.
guidotack commentedon Oct 6, 2017
The incorrect simplification (changing the bound to 95.0) is now fixed in the compiler. The fact that a>b is violated is a bug in Gecode, not in MiniZinc (I will close this bug here and report it for Gecode).
feserafim commentedon Oct 20, 2017
I have just updated MiniZinc IDE (bundled) newest version (2.1.6) and executed
but I am still getting the same result as @Dekker1.
Am I doing anything wrong?
Dekker1 commentedon Oct 20, 2017
Hello @feserafim,
Although Guido managed to fix the flattening bug, the fix has only been implemented on the development branch. (We haven't released any new versions since the bug was fixed). This is also the reason that the issue is still open.
If you are still experiencing problems and you can't wait until the next release, then you might want to try to compile the
developbranch and use thatmzn2fznbinary. The problem should be fully fixed on that branch. (Although the problem in Gecode is a different issue as Guido mentioned)