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
While trying to implement limited functions we needed to disable MBQI.
Since the usual approach of disabling both smt.mbqi and auto_config caused flaky behaviour in some of our tests, we had the
(unconventional) idea of using smt.mbqi.id to achieve this goal.
The documentation states:
Only use model-based instantiation for quantifiers with id's beginning with string
So the idea is to set it to some value that is not a prefix of any quantifier id, but this had surprising behaviour.
Take this program
The model seems wrong. In particular, setting exp to always be 0 is in conflict with exp(definitional).
Setting model_validate did not change anything.
Does anybody know what is happening here? Are we misinterpreting what the option does? Is our usage unsoud or is this a bug?
Any insight is appreciated!
The text was updated successfully, but these errors were encountered:
While trying to implement limited functions we needed to disable MBQI.
Since the usual approach of disabling both
smt.mbqi
andauto_config
caused flaky behaviour in some of our tests, we had the(unconventional) idea of using
smt.mbqi.id
to achieve this goal.The documentation states:
So the idea is to set it to some value that is not a prefix of any quantifier id, but this had surprising behaviour.
Take this program
uncommenting the
set-option
turns the result fromunsat
tosat
(Tested with 4.13.3 - 64 bit and 4.13.4 - 64 bit) and the given model isThe model seems wrong. In particular, setting
exp
to always be0
is in conflict withexp(definitional)
.Setting
model_validate
did not change anything.Does anybody know what is happening here? Are we misinterpreting what the option does? Is our usage unsoud or is this a bug?
Any insight is appreciated!
The text was updated successfully, but these errors were encountered: