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
One thing that's confusing me is that there's no MiniSat with Unsat Core solver in the latest release. However there is a minisat.solver which (is the only one that) enables the core minimization and granularity options, so I'm assuming this is what MiniSat with Unsat Core used to be and the documentation is just outdated.
However, running the following model highlights nothing (obtained as an example from here):
sig Node {
edge: some Node
}
fact {some Node}
run {no edge}
Additionally, the right pane output doesn't contain any message like "Core reduced from ..." which is visible in the linked docs.
I'm beginning to suspect it's somehow broken, but maybe I'm just not holding it right.
The text was updated successfully, but these errors were encountered:
I think when this is fixed, it would also be prudent to re-add the string "Unsat Core" to that solver's menu item. This will reduce confusion for people coming to Alloy from old articles that mention it by that name.
How is unsat core supposed to work? Judging from http://alloytools.org/quickguide/unsat.html, it's supposed to highlight the core in red, but this is not happening for me.
One thing that's confusing me is that there's no
MiniSat with Unsat Core
solver in the latest release. However there is aminisat.solver
which (is the only one that) enables the core minimization and granularity options, so I'm assuming this is whatMiniSat with Unsat Core
used to be and the documentation is just outdated.However, running the following model highlights nothing (obtained as an example from here):
Additionally, the right pane output doesn't contain any message like "Core reduced from ..." which is visible in the linked docs.
I'm beginning to suspect it's somehow broken, but maybe I'm just not holding it right.
The text was updated successfully, but these errors were encountered: