storm.sparse.evtfull-ovi-topo

Benchmark
Model: (kanban)
Parameter(s)t = 5
Invocation (sparse.evtfull-ovi-topo)
	$ARTIFACT_DIR/bin/storm --statistics --prism $ARTIFACT_DIR/benchmarks/ctmc/kanban/kanban.prism --constants t=5 --prismcompat --steadystate evt --eqsolver topological --topological:eqsolver native --native:method ovi --sound --engine sparse --timemem --precision 1e-06 --exportresult results_stationary/logs/exports/storm.sparse.evtfull-ovi-topo.1e-06.kanban.5.json
Sparse (default) engine Use `--prismcompat` to ensure compatibility with prism benchmark.
Execution
Walltime (MC-Time):> 1800.0s (NA) (Timeout)
Note(s):Export file results_stationary/logs/exports/storm.sparse.evtfull-ovi-topo.1e-06.kanban.5.json does not exist.
Log
Storm 1.9.1 (dev)

Date: Fri Sep 13 11:58:50 2024
Command line arguments: --statistics --prism /rwthfs/rz/clusterevts/evt-benchmarking/benchmarks/ctmc/kanban/kanban.prism --constants t=5 --prismcompat --steadystate evt --eqsolver topological '--topological:eqsolver' native '--native:method' ovi --sound --engine sparse --timemem --precision 1e-06 --exportresult results_stationary/logs/exports/storm.sparse.evtfull-ovi-topo.1e-06.kanban.5.json
Current working directory: /rwthfs/rz/cluster/hpcwork/tq429871/evt-experiments/experiments

 WARN (Program.cpp:238): 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:1633): The model uses synchronizing Markovian commands. This may lead to unexpected verification results, because of unclear semantics.
 WARN (Program.cpp:1633): The model uses synchronizing Markovian commands. This may lead to unexpected verification results, because of unclear semantics.
 WARN (Program.cpp:1633): The model uses synchronizing Markovian commands. This may lead to unexpected verification results, because of unclear semantics.
 WARN (Program.cpp:1633): The model uses synchronizing Markovian commands. This may lead to unexpected verification results, because of unclear semantics.
 WARN (Program.cpp:1633): The model uses synchronizing Markovian commands. This may lead to unexpected verification results, because of unclear semantics.
 WARN (Program.cpp:1633): The model uses synchronizing Markovian commands. This may lead to unexpected verification results, because of unclear semantics.
 WARN (Program.cpp:1633): The model uses synchronizing Markovian commands. This may lead to unexpected verification results, because of unclear semantics.
 WARN (Program.cpp:1633): The model uses synchronizing Markovian commands. This may lead to unexpected verification results, because of unclear semantics.
Time for model input parsing: 0.002s.

 WARN (Program.cpp:1633): The model uses synchronizing Markovian commands. This may lead to unexpected verification results, because of unclear semantics.
 WARN (Program.cpp:1633): The model uses synchronizing Markovian commands. This may lead to unexpected verification results, because of unclear semantics.
 WARN (Program.cpp:1633): The model uses synchronizing Markovian commands. This may lead to unexpected verification results, because of unclear semantics.
 WARN (Program.cpp:1633): The model uses synchronizing Markovian commands. This may lead to unexpected verification results, because of unclear semantics.
 WARN (Program.cpp:1633): The model uses synchronizing Markovian commands. This may lead to unexpected verification results, because of unclear semantics.
 WARN (Program.cpp:1633): The model uses synchronizing Markovian commands. This may lead to unexpected verification results, because of unclear semantics.
Time for model construction: 12.420s.

-------------------------------------------------------------- 
Model type: 	CTMC (sparse)
States: 	2546432
Transitions: 	24460016
Reward Models:  none
State Labels: 	2 labels
   * deadlock -> 0 item(s)
   * init -> 1 item(s)
Choice Labels: 	none
-------------------------------------------------------------- 

Computing steady-state probabilities ...


----------
Computation aborted after 1800.0072083473206 seconds since the total time limit of 1800.0 seconds was exceeded.