We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When computing Pmin=? [F x=2 || x=1] for the following PRISM Program, with Storm we get 0, although 0.3 should be correct.
Pmin=? [F x=2 || x=1]
0
0.3
mdp module main x : [0..2]; [] x=0 -> 0.7 : (x'=1) + 0.3 : (x'=2); [] x=1 -> 1 : (x'=1); [] x=2 -> 1 : (x'=1); endmodule
Storm 1.8.2 (dev) Date: Wed Feb 28 12:55:15 2024 Command line arguments: --prism conditional.nm -prop 'Pmin=? [F x=2 || F x=1 ]' Current working directory: Time for model input parsing: 0.000s. Time for model construction: 0.010s. -------------------------------------------------------------- Model type: MDP (sparse) States: 3 Transitions: 4 Choices: 3 Reward Models: none State Labels: 4 labels * init -> 1 item(s) * deadlock -> 0 item(s) * (x = 2) -> 1 item(s) * (x = 1) -> 1 item(s) Choice Labels: none -------------------------------------------------------------- Model checking property "1": Pmin=? [(F (x = 2)) || (F (x = 1))] ... Result (for initial states): 0 Time for model checking: 0.000s.
The problem seems to be an incorrect reduction from minimizing to maximizing queries.
The text was updated successfully, but these errors were encountered:
tquatmann
No branches or pull requests
When computing
Pmin=? [F x=2 || x=1]
for the following PRISM Program, with Storm we get0
, although0.3
should be correct.The problem seems to be an incorrect reduction from minimizing to maximizing queries.
The text was updated successfully, but these errors were encountered: