Storm.automatic

Benchmark
Model:mapk_cascade v.1 (CTMC)
Parameter(s)N = 4, T = 30
Property:activated_time (exp-reward)
Invocation (automatic)
/home/tq429871/storm/build/bin/storm --prism /rwthfs/rz/cluster/home/tq429871/git/storm-qcomp-benchmarks/qcomp/benchmarks/ctmc/mapk_cascade/mapk_cascade.prism --prop /rwthfs/rz/cluster/home/tq429871/git/storm-qcomp-benchmarks/qcomp/benchmarks/ctmc/mapk_cascade/mapk_cascade.props activated_time --constants N=4,T=30 --prismcompat --engine automatic --sylvan:maxmem 4096 --sylvan:threads 4 --timemem
Automatic selection Use `--prismcompat` to ensure compatibility with prism benchmark.
Execution
Walltime:2.554002046585083s
Return code:0
Relative Error:5.3739436547206275e-08
Log
Storm 1.6.2

Date: Sat Sep  5 20:45:55 2020
Command line arguments: --prism /rwthfs/rz/cluster/home/tq429871/git/storm-qcomp-benchmarks/qcomp/benchmarks/ctmc/mapk_cascade/mapk_cascade.prism --prop /rwthfs/rz/cluster/home/tq429871/git/storm-qcomp-benchmarks/qcomp/benchmarks/ctmc/mapk_cascade/mapk_cascade.props activated_time --constants 'N=4,T=30' --prismcompat --engine automatic '--sylvan:maxmem' 4096 '--sylvan:threads' 4 --timemem
Current working directory: /rwthfs/rz/cluster/home/tq429871/git/storm-qcomp-benchmarks

 WARN (Program.cpp:178): The input model is a CTMC, but uses probabilistic commands like they are used in PRISM. Consider rewriting the commands to use Markovian commands instead.
 WARN (Program.cpp:1277): The model uses synchronizing Markovian commands. This may lead to unexpected verification results, because of unclear semantics.
 WARN (Program.cpp:1277): The model uses synchronizing Markovian commands. This may lead to unexpected verification results, because of unclear semantics.
 WARN (Program.cpp:1277): The model uses synchronizing Markovian commands. This may lead to unexpected verification results, because of unclear semantics.
 WARN (Program.cpp:1277): The model uses synchronizing Markovian commands. This may lead to unexpected verification results, because of unclear semantics.
 WARN (Program.cpp:1277): The model uses synchronizing Markovian commands. This may lead to unexpected verification results, because of unclear semantics.
 WARN (Program.cpp:1277): The model uses synchronizing Markovian commands. This may lead to unexpected verification results, because of unclear semantics.
 WARN (Program.cpp:1277): The model uses synchronizing Markovian commands. This may lead to unexpected verification results, because of unclear semantics.
 WARN (Program.cpp:1277): The model uses synchronizing Markovian commands. This may lead to unexpected verification results, because of unclear semantics.
Time for model input parsing: 0.006s.

 WARN (Program.cpp:1277): The model uses synchronizing Markovian commands. This may lead to unexpected verification results, because of unclear semantics.
 WARN (Program.cpp:1277): The model uses synchronizing Markovian commands. This may lead to unexpected verification results, because of unclear semantics.
 WARN (Program.cpp:1277): The model uses synchronizing Markovian commands. This may lead to unexpected verification results, because of unclear semantics.
Automatic engine picked the following settings: 
	engine=sparse	 bisimulation=false	 exact=false
 WARN (Program.cpp:1277): The model uses synchronizing Markovian commands. This may lead to unexpected verification results, because of unclear semantics.
 WARN (Program.cpp:1277): The model uses synchronizing Markovian commands. This may lead to unexpected verification results, because of unclear semantics.
Time for model construction: 1.832s.

-------------------------------------------------------------- 
Model type: 	CTMC (sparse)
States: 	99535
Transitions: 	901842
Reward Models:  time
State Labels: 	3 labels
   * deadlock -> 0 item(s)
   * (kpp = 4) -> 1461 item(s)
   * init -> 1 item(s)
Choice Labels: 	none
-------------------------------------------------------------- 

Model checking property "activated_time": R[exp]{"time"}=? [F (kpp = 4)] ...
Result (for initial states): 40.67650519
Time for model checking: 0.659s.

Performance statistics:
  * peak memory usage: 164MB
  * CPU time: 2.471s
  * wallclock time: 2.503s