Closed rachelwang closed 10 years ago
It means that the ODE for the variable v
is not provided in the model.
I see. So, essentially, if I want to use a variable within the definition of an ODE, and do not want to add extra assertions for it. I'd better use #define
to give it a fixed value, or (for my tool) define it as a random variable.
Thanks.
So, after your modification, each call to dReach will return 3 paths and 3 sat/unsat results?
SMT: numodel_4_0.smt2, PATH : [1,2,1,2,3]
unsat
SMT: numodel_4_1.smt2, PATH : [1,2,3,2,3]
unsat
SMT: numodel_4_2.smt2, PATH : [1,2,3,4,3]
unsat
unsat
dReal Options:
SMT: numodel_4_0.smt2, PATH : [1,2,1,2,3]
unsat
SMT: numodel_4_1.smt2, PATH : [1,2,3,2,3]
unsat
SMT: numodel_4_2.smt2, PATH : [1,2,3,4,3]
unsat
unsat
dReal Options:
SMT: numodel_4_0.smt2, PATH : [1,2,1,2,3]
unsat
SMT: numodel_4_1.smt2, PATH : [1,2,3,2,3]
unsat
SMT: numodel_4_2.smt2, PATH : [1,2,3,4,3]
unsat
unsat
BFTI 0.9 1000 1 1 0.01: Reject Null hypothesis, successes = 0, samples = 3
Elapsed cpu time: 0.007947
Elapsed wall time: 0
3 is for the gear model, I mean "multiple" in general...
I still need to see the model, but it seems that is the case. In general, dReach
enumerates possible paths until it sees a SAT
path or there is no path to enumerate.
So, after your modification, each call to dReach will return 3 paths and 3 sat/unsat results?
Is there any problem with it? Otherwise, please close the issue.
I see. Then, I need to modify codes for statsmt_sq as well, as previously we only have one .output file per each call.
After updating the bmc, I encounter the following error when running the gear_shift model attached.
the numodel.drh: