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-3253
Executing tool marcie
Input is S_TriangularGrid-PT-5046, examination is ReachabilityFireability
Time confinement is 3600 seconds
Memory confinement is 16384 MBytes
Number of cores is 1
Run identifier is r151-ebro-149443454600369
=====================================================================

--------------------
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 TriangularGrid-PT-5046-ReachabilityFireability-0
FORMULA_NAME TriangularGrid-PT-5046-ReachabilityFireability-1
FORMULA_NAME TriangularGrid-PT-5046-ReachabilityFireability-10
FORMULA_NAME TriangularGrid-PT-5046-ReachabilityFireability-11
FORMULA_NAME TriangularGrid-PT-5046-ReachabilityFireability-12
FORMULA_NAME TriangularGrid-PT-5046-ReachabilityFireability-13
FORMULA_NAME TriangularGrid-PT-5046-ReachabilityFireability-14
FORMULA_NAME TriangularGrid-PT-5046-ReachabilityFireability-15
FORMULA_NAME TriangularGrid-PT-5046-ReachabilityFireability-2
FORMULA_NAME TriangularGrid-PT-5046-ReachabilityFireability-3
FORMULA_NAME TriangularGrid-PT-5046-ReachabilityFireability-4
FORMULA_NAME TriangularGrid-PT-5046-ReachabilityFireability-5
FORMULA_NAME TriangularGrid-PT-5046-ReachabilityFireability-6
FORMULA_NAME TriangularGrid-PT-5046-ReachabilityFireability-7
FORMULA_NAME TriangularGrid-PT-5046-ReachabilityFireability-8
FORMULA_NAME TriangularGrid-PT-5046-ReachabilityFireability-9

=== Now, execution of the tool begins

BK_START 1496690875899

timeout --kill-after=10s --signal=SIGINT 1m for testing only

Marcie rev. 8852M (built: crohr on 2017-05-03)
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=ReachabilityFireability.xml --memory=6

parse successfull
net created successfully

Net: TriangularGrid_PT_5046
(NrP: 280 NrTr: 240 NrArc: 960)

parse formulas
formulas created successfully
place and transition orderings generation:0m 0.012sec

net check time: 0m 0.001sec

init dd package: 0m 2.165sec

parse successfull
net created successfully

Net: TriangularGrid_PT_5046
(NrP: 280 NrTr: 240 NrArc: 960)

parse formulas
formulas created successfully
place and transition orderings generation:0m 0.014sec

net check time: 0m 0.001sec

init dd package: 0m 7.181sec


RS generation: 12m54.468sec


-> last computed set: #nodes 189491 (1.9e+05) #states 1,431,039,188,131,436,523,037,825,427,314,304,039 (36)


CANNOT_COMPUTE


BK_STOP 1496691693594

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

check for maximal unmarked siphon
ok
check for constant places
ok
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

ptnet_zbdd.cc:255: Boundedness exception: net is not 1-bounded!

check for maximal unmarked siphon
ok
check for constant places
ok
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


initing FirstDep: 0m 0.002sec

193847 74624 172617std::bad_alloc

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="S_TriangularGrid-PT-5046"
export BK_EXAMINATION="ReachabilityFireability"
export BK_TOOL="marcie"
export BK_RESULT_DIR="/tmp/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/S_TriangularGrid-PT-5046.tgz
mv S_TriangularGrid-PT-5046 execution

# this is for BenchKit: explicit launching of the test

cd execution
echo "====================================================================="
echo " Generated by BenchKit 2-3253"
echo " Executing tool marcie"
echo " Input is S_TriangularGrid-PT-5046, examination is ReachabilityFireability"
echo " Time confinement is $BK_TIME_CONFINEMENT seconds"
echo " Memory confinement is 16384 MBytes"
echo " Number of cores is 1"
echo " Run identifier is r151-ebro-149443454600369"
echo "====================================================================="
echo
echo "--------------------"
echo "content from stdout:"
echo
echo "=== Data for post analysis generated by BenchKit (invocation template)"
echo
if [ "ReachabilityFireability" = "UpperBounds" ] ; then
echo "The expected result is a vector of positive values"
echo NUM_VECTOR
elif [ "ReachabilityFireability" != "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 "ReachabilityFireability.txt" ] ; then
echo "here is the order used to build the result vector(from text file)"
for x in $(grep Property ReachabilityFireability.txt | cut -d ' ' -f 2 | sort -u) ; do
echo "FORMULA_NAME $x"
done
elif [ -f "ReachabilityFireability.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 '' ReachabilityFireability.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 ;