Invocation (sparse.ovi-topo)
$ARTIFACT_DIR/bin/storm --statistics --prism $ARTIFACT_DIR/benchmarks/ctmc/embedded/embedded.prism --constants MAX_COUNT=6 --prismcompat --expvisittimes --eqsolver topological --topological:eqsolver native --native:method ovi --sound --engine sparse --timemem --precision 0.001 --exportresult results_evts/logs/exports/storm.sparse.ovi-topo.0.001.embedded.6.json
Sparse (default) engine Use `--prismcompat` to ensure compatibility with prism benchmark.
Storm 1.9.1 (dev)
Date: Sat Sep 14 00:55:46 2024
Command line arguments: --statistics --prism /rwthfs/rz/clusterevts/evt-benchmarking/benchmarks/ctmc/embedded/embedded.prism --constants MAX_COUNT=6 --prismcompat --expvisittimes --eqsolver topological '--topological:eqsolver' native '--native:method' ovi --sound --engine sparse --timemem --precision 0.001 --exportresult results_evts/logs/exports/storm.sparse.ovi-topo.0.001.embedded.6.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.006s.
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: 0.034s.
--------------------------------------------------------------
Model type: CTMC (sparse)
States: 6858
Transitions: 28907
Reward Models: none
State Labels: 2 labels
* deadlock -> 0 item(s)
* init -> 1 item(s)
Choice Labels: none
--------------------------------------------------------------
Computing expected visiting times ...
WARN (model-handling.h:1258): No information of state valuations available. The result output will use internal state ids. You might be interested in building the model with state valuations using --buildstateval.
Write to file results_evts/logs/exports/storm.sparse.ovi-topo.0.001.embedded.6.json.
Result (for 'true' states): [2.73324662e-27, inf] (range)
Time for model checking: 0.370s.
Performance statistics:
* peak memory usage: 66MB
* CPU time: 0.395s
* wallclock time: 0.418s