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
When declaring a constant in a properties file, but not defining it (neither in the file nor via command line) storm assumes the constant to be 0. For example, when calling storm --prism ./model.prism --prop ./props.prop
on the model
dtmc
const double p = 0.4;
const int N = 5;
module one
x: bool init true;
num_rounds : [0..N] init 0;
[a] x & (num_rounds<N) -> p : (num_rounds' = num_rounds+1)
+ (1-p) : (x' = false) & (num_rounds' = num_rounds+1);
[a] x & (num_rounds=N) -> p : true
+ (1-p) : (x' = false);
endmodule
and the properties file
const int k;
P=? [F num_rounds = k];
the result 1 is returned although k is not specified.
The text was updated successfully, but these errors were encountered:
When declaring a constant in a properties file, but not defining it (neither in the file nor via command line) storm assumes the constant to be 0. For example, when calling
storm --prism ./model.prism --prop ./props.prop
on the model
and the properties file
the result 1 is returned although k is not specified.
The text was updated successfully, but these errors were encountered: