Problem with interpreted types
Issue #875
new
They behave unexpectedly.
Correctly working: http://dtai.cs.kuleuven.be/krr/idp-ide/?src=6dbda9ceec57c1c57e60
Not working: http://dtai.cs.kuleuven.be/krr/idp-ide/?src=31c8e1e76ebf02e572ff
they are identical, except that in the one, there is type Int = {0..100} while in the other hte interpretation is moved to the structure
Comments (4)
-
reporter
-
reporter
improved optimal propagation.
Optimal propagate passed the option 'nbmodelsequivalent = false' to mx. Even though this is correct, this is not efficient, since all models will be generated (and in the test case I added, there are way too much models...) See #875
→ <<cset 3dfd9c604edf>>
-
improved optimal propagation.
Optimal propagate passed the option 'nbmodelsequivalent = false' to mx. Even though this is correct, this is not efficient, since all models will be generated (and in the test case I added, there are way too much models...) See #875
→ <<cset 25a7019159ec>>
-
improved optimal propagation.
Optimal propagate passed the option 'nbmodelsequivalent = false' to mx. Even though this is correct, this is not efficient, since all models will be generated (and in the test case I added, there are way too much models...) See #875
→ <<cset 25a7019159ec>>
- Log in to comment
Two problems... 1. Optimalpropagate is sometimes inefficient 2. Difference between two almost identical representations.
No clue for 2; 1 is fixed in branch "optimalpropagate".