Execution Chart

We display below the execution chart for this examination (boot time has been removed).

Trace from the execution

Waiting for the VM to be ready (probing ssh)
..............
=====================================================================
Generated by BenchKit 2-2265
Executing tool marcie
Input is PolyORBNT-PT-S05J80, examination is ReachabilityBounds
Time confinement is 3600 seconds
Memory confinement is 16384 MBytes
Number of cores is 1
Run identifier is r078kn-ebro-143262779200671
=====================================================================

--------------------
content from stdout:

=== Data for post analysis generated by BenchKit (invocation template)

The expected result is a vector of booleans
BOOL_VECTOR

here is the order used to build the result vector(from text file)
FORMULA_NAME PolyORBNT-COL-S05J80-ReachabilityBounds-0
FORMULA_NAME PolyORBNT-COL-S05J80-ReachabilityBounds-1
FORMULA_NAME PolyORBNT-COL-S05J80-ReachabilityBounds-10
FORMULA_NAME PolyORBNT-COL-S05J80-ReachabilityBounds-11
FORMULA_NAME PolyORBNT-COL-S05J80-ReachabilityBounds-12
FORMULA_NAME PolyORBNT-COL-S05J80-ReachabilityBounds-13
FORMULA_NAME PolyORBNT-COL-S05J80-ReachabilityBounds-14
FORMULA_NAME PolyORBNT-COL-S05J80-ReachabilityBounds-15
FORMULA_NAME PolyORBNT-COL-S05J80-ReachabilityBounds-2
FORMULA_NAME PolyORBNT-COL-S05J80-ReachabilityBounds-3
FORMULA_NAME PolyORBNT-COL-S05J80-ReachabilityBounds-4
FORMULA_NAME PolyORBNT-COL-S05J80-ReachabilityBounds-5
FORMULA_NAME PolyORBNT-COL-S05J80-ReachabilityBounds-6
FORMULA_NAME PolyORBNT-COL-S05J80-ReachabilityBounds-7
FORMULA_NAME PolyORBNT-COL-S05J80-ReachabilityBounds-8
FORMULA_NAME PolyORBNT-COL-S05J80-ReachabilityBounds-9

=== Now, execution of the tool begins

BK_START 1432906766956

Model: PolyORBNT-PT-S05J80
reachability algorithm:
Transition chaining algorithm
variable ordering algorithm:
Calculated like in [Noa99]
--memory=6 --suppress --rs-algorithm=2 --place-order=5

Marcie rev. 1429:1432M (built: crohr on 2014-10-22)
A model checker for Generalized Stochastic Petri nets

authors: Alex Tovchigrechko (IDD package and CTL model checking)

Martin Schwarick (Symbolic numerical analysis and CSL model checking)

Christian Rohr (Simulative and approximative numerical model checking)

marcie@informatik.tu-cottbus.de

called as: marcie --net-file=model.pnml --mcc-file=ReachabilityBounds.xml --memory=6 --suppress --rs-algorithm=2 --place-order=5

parse successfull
net created successfully

(NrP: 1189 NrTr: 2350 NrArc: 14464)

net check time: 0m0sec

parse formulas successfull
formulas created successfully
place and transition orderings generation:0m11sec

init dd package: 0m5sec


before gc: list nodes free: 2793038

after gc: idd nodes used:16373946, unused:47626054; list nodes free:201405352

before gc: list nodes free: 2342203

after gc: idd nodes used:32872643, unused:31127357; list nodes free:133590849

before gc: list nodes free: 4195600

after gc: idd nodes used:41721870, unused:22278130; list nodes free:97170236

before gc: list nodes free: 4999693

after gc: idd nodes used:48604687, unused:15395313; list nodes free:69245405

before gc: list nodes free: 5565715

after gc: idd nodes used:54214037, unused:9785963; list nodes free:46308719

before gc: list nodes free: 6443739

after gc: idd nodes used:61741328, unused:2258672; list nodes free:15684774

RS generation: 48m37sec


-> last computed set: #nodes 61740283 (6.2e+07) #states 139,831,919 (8)


CANNOT_COMPUTE


BK_STOP 1432909823262

--------------------
content from stderr:

check if there are places and transitions
ok
check if there are transitions without pre-places
ok
check if at least one transition is enabled in m0
ok
check if there are transitions that can never fire
ok

.../home/mcc/workspace/dssz_util/src/dssz/idd/idd.cc:804: DD Exception: No free nodes

Sequence of Actions to be Executed by the VM

This is useful if one wants to reexecute the tool in the VM from the submitted image disk.

set -x
# this is for BenchKit: configuration of major elements for the test
export BK_INPUT="PolyORBNT-PT-S05J80"
export BK_EXAMINATION="ReachabilityBounds"
export BK_TOOL="marcie"
export BK_RESULT_DIR="/users/gast00/fkordon/BK_RESULTS/OUTPUTS"
export BK_TIME_CONFINEMENT="3600"
export BK_MEMORY_CONFINEMENT="16384"

# this is specific to your benchmark or test

export BIN_DIR="$HOME/BenchKit/bin"

# remove the execution directoty if it exists (to avoid increse of .vmdk images)
if [ -d execution ] ; then
rm -rf execution
fi

tar xzf /home/mcc/BenchKit/INPUTS/PolyORBNT-PT-S05J80.tgz
mv PolyORBNT-PT-S05J80 execution

# this is for BenchKit: explicit launching of the test

cd execution
echo "====================================================================="
echo " Generated by BenchKit 2-2265"
echo " Executing tool marcie"
echo " Input is PolyORBNT-PT-S05J80, examination is ReachabilityBounds"
echo " Time confinement is $BK_TIME_CONFINEMENT seconds"
echo " Memory confinement is 16384 MBytes"
echo " Number of cores is 1"
echo " Run identifier is r078kn-ebro-143262779200671"
echo "====================================================================="
echo
echo "--------------------"
echo "content from stdout:"
echo
echo "=== Data for post analysis generated by BenchKit (invocation template)"
echo
if [ "ReachabilityBounds" = "ReachabilityComputeBounds" ] ; then
echo "The expected result is a vector of positive values"
echo NUM_VECTOR
elif [ "ReachabilityBounds" != "StateSpace" ] ; then
echo "The expected result is a vector of booleans"
echo BOOL_VECTOR
else
echo "no data necessary for post analysis"
fi
echo
if [ -f "ReachabilityBounds.txt" ] ; then
echo "here is the order used to build the result vector(from text file)"
for x in $(grep Property ReachabilityBounds.txt | cut -d ' ' -f 2 | sort -u) ; do
echo "FORMULA_NAME $x"
done
elif [ -f "ReachabilityBounds.xml" ] ; then # for cunf (txt files deleted;-)
echo echo "here is the order used to build the result vector(from xml file)"
for x in $(grep '' ReachabilityBounds.xml | cut -d '>' -f 2 | cut -d '<' -f 1 | sort -u) ; do
echo "FORMULA_NAME $x"
done
fi
echo
echo "=== Now, execution of the tool begins"
echo
echo -n "BK_START "
date -u +%s%3N
echo
timeout -s 9 $BK_TIME_CONFINEMENT bash -c "/home/mcc/BenchKit/BenchKit_head.sh 2> STDERR ; echo ; echo -n \"BK_STOP \" ; date -u +%s%3N"
if [ $? -eq 137 ] ; then
echo
echo "BK_TIME_CONFINEMENT_REACHED"
fi
echo
echo "--------------------"
echo "content from stderr:"
echo
cat STDERR ;