Open benbrastmckie opened 2 months ago
I add documentation instructions to General.md
regarding using MIT's compute. It is very easy to log in. I tried adding the exhaustive constraint, but the process was killed. This suggests that there is something deeper going on.
I'm going to store various loose ends to come back to that pertain to Z3 optimization is this issue, the first of which was from when I was experimenting with different non-trivial proposition constraints.
# NOTE: if null verifiers are permitted, then null state verifies A
# but possible state c does not?
premises = ['A','B']
conclusions = ['(A boxright B)']
Here are some examples where the unsat_core
looks satisfiable:
# # NOTE: unsat_core seems satisfiable
# premises = []
# conclusions = ['(A vee neg A)']
# # NOTE: unsat_core seems satisfiable
# premises = []
# conclusions = ['neg (A wedge neg A)']
I've added benchmarking to
test_complete.py
in order to begin comparing results. Here is how the proposition constraints were originally defined:This ran with an execution time of .71 sec. I then replaced this constraint with:
This ran with an execution time of .18 seconds. This makes me curious what kind of improvements can be gained by removing all occurrences of
Exists
from the Z3 constraints generated by the functions insemantics.py
, replacing these with unique variables instead.