fond
Model Checking Contest @ Petri Nets 2015
Bruxelles, Belgium, June 23, 2015
TAPAAL-OTF(PAR) compared to other tools («Known» models, ReachabilityBounds)
Last Updated
August 19, 2015

Introduction

This page presents how TAPAAL-OTF(PAR) do cope efficiently with the ReachabilityBounds examination face to the other participating tools. In this page, we consider «Known» models.

The next sections will show chart comparing performances in termsof both memory and execution time.The x-axis corresponds to the challenging tool where the y-axes represents TAPAAL-OTF(PAR)' performances. Thus, points below the diagonal of a chart denote comparisons favorables to the tool whileothers corresponds to situations where the challenging tool performs better.

You might also find plots out of the range that denote the case were at least one tool could not answer appropriately (error, time-out, could not compute or did not competed).

TAPAAL-OTF(PAR) versus GreatSPN-Meddly

Some statistics are displayed below, based on 808 runs (404 for TAPAAL-OTF(PAR) and 404 for GreatSPN-Meddly, so there are 404 plots on each of the two charts). Each execution was allowed 1 hour and 16 GByte of memory. Then performance charts comparing TAPAAL-OTF(PAR) to GreatSPN-Meddly are shown (you may click on one graph to enlarge it).

Statistics on the execution
  TAPAAL-OTF(PAR) GreatSPN-Meddly Both tools   TAPAAL-OTF(PAR) GreatSPN-Meddly
Computed OK 26 44 51   Smallest Memory Footprint
Do not compete 23 0 114 Times tool wins 48 73
Error detected 11 54 0   Shortest Execution Time
Cannot Compute + Time-out 77 39 102 Times tool wins 49 72


On the chart below, denote cases where the two tools did computed a result, denote the cases where at least one tool did not competed, denote the cases where at least one tool did a mistake and denote the cases where at least one tool stated it could not compute a result or timed-out.

memory chart time chart

TAPAAL-OTF(PAR) versus LoLA2.0

Some statistics are displayed below, based on 808 runs (404 for TAPAAL-OTF(PAR) and 404 for LoLA2.0, so there are 404 plots on each of the two charts). Each execution was allowed 1 hour and 16 GByte of memory. Then performance charts comparing TAPAAL-OTF(PAR) to LoLA2.0 are shown (you may click on one graph to enlarge it).

Statistics on the execution
  TAPAAL-OTF(PAR) LoLA2.0 Both tools   TAPAAL-OTF(PAR) LoLA2.0
Computed OK 0 187 77   Smallest Memory Footprint
Do not compete 0 0 137 Times tool wins 14 250
Error detected 11 3 0   Shortest Execution Time
Cannot Compute + Time-out 179 0 0 Times tool wins 7 257


On the chart below, denote cases where the two tools did computed a result, denote the cases where at least one tool did not competed, denote the cases where at least one tool did a mistake and denote the cases where at least one tool stated it could not compute a result or timed-out.

memory chart time chart

TAPAAL-OTF(PAR) versus LTSMin

Some statistics are displayed below, based on 808 runs (404 for TAPAAL-OTF(PAR) and 404 for LTSMin, so there are 404 plots on each of the two charts). Each execution was allowed 1 hour and 16 GByte of memory. Then performance charts comparing TAPAAL-OTF(PAR) to LTSMin are shown (you may click on one graph to enlarge it).

Statistics on the execution
  TAPAAL-OTF(PAR) LTSMin Both tools   TAPAAL-OTF(PAR) LTSMin
Computed OK 77 0 0   Smallest Memory Footprint
Do not compete 137 266 0 Times tool wins 77 0
Error detected 11 0 0   Shortest Execution Time
Cannot Compute + Time-out 178 137 1 Times tool wins 77 0


On the chart below, denote cases where the two tools did computed a result, denote the cases where at least one tool did not competed, denote the cases where at least one tool did a mistake and denote the cases where at least one tool stated it could not compute a result or timed-out.

memory chart time chart

TAPAAL-OTF(PAR) versus Marcie

Some statistics are displayed below, based on 808 runs (404 for TAPAAL-OTF(PAR) and 404 for Marcie, so there are 404 plots on each of the two charts). Each execution was allowed 1 hour and 16 GByte of memory. Then performance charts comparing TAPAAL-OTF(PAR) to Marcie are shown (you may click on one graph to enlarge it).

Statistics on the execution
  TAPAAL-OTF(PAR) Marcie Both tools   TAPAAL-OTF(PAR) Marcie
Computed OK 18 104 59   Smallest Memory Footprint
Do not compete 137 0 0 Times tool wins 62 119
Error detected 11 12 0   Shortest Execution Time
Cannot Compute + Time-out 65 115 114 Times tool wins 45 136


On the chart below, denote cases where the two tools did computed a result, denote the cases where at least one tool did not competed, denote the cases where at least one tool did a mistake and denote the cases where at least one tool stated it could not compute a result or timed-out.

memory chart time chart

TAPAAL-OTF(PAR) versus TAPAAL(MC)

Some statistics are displayed below, based on 808 runs (404 for TAPAAL-OTF(PAR) and 404 for TAPAAL(MC), so there are 404 plots on each of the two charts). Each execution was allowed 1 hour and 16 GByte of memory. Then performance charts comparing TAPAAL-OTF(PAR) to TAPAAL(MC) are shown (you may click on one graph to enlarge it).

Statistics on the execution
  TAPAAL-OTF(PAR) TAPAAL(MC) Both tools   TAPAAL-OTF(PAR) TAPAAL(MC)
Computed OK 12 94 65   Smallest Memory Footprint
Do not compete 0 0 137 Times tool wins 44 127
Error detected 11 0 0   Shortest Execution Time
Cannot Compute + Time-out 94 23 85 Times tool wins 33 138


On the chart below, denote cases where the two tools did computed a result, denote the cases where at least one tool did not competed, denote the cases where at least one tool did a mistake and denote the cases where at least one tool stated it could not compute a result or timed-out.

memory chart time chart

TAPAAL-OTF(PAR) versus TAPAAL(SEQ)

Some statistics are displayed below, based on 808 runs (404 for TAPAAL-OTF(PAR) and 404 for TAPAAL(SEQ), so there are 404 plots on each of the two charts). Each execution was allowed 1 hour and 16 GByte of memory. Then performance charts comparing TAPAAL-OTF(PAR) to TAPAAL(SEQ) are shown (you may click on one graph to enlarge it).

Statistics on the execution
  TAPAAL-OTF(PAR) TAPAAL(SEQ) Both tools   TAPAAL-OTF(PAR) TAPAAL(SEQ)
Computed OK 0 185 77   Smallest Memory Footprint
Do not compete 0 0 137 Times tool wins 25 237
Error detected 11 0 0   Shortest Execution Time
Cannot Compute + Time-out 174 0 5 Times tool wins 41 221


On the chart below, denote cases where the two tools did computed a result, denote the cases where at least one tool did not competed, denote the cases where at least one tool did a mistake and denote the cases where at least one tool stated it could not compute a result or timed-out.

memory chart time chart

TAPAAL-OTF(PAR) versus TAPAAL-OTF(SEQ)

Some statistics are displayed below, based on 808 runs (404 for TAPAAL-OTF(PAR) and 404 for TAPAAL-OTF(SEQ), so there are 404 plots on each of the two charts). Each execution was allowed 1 hour and 16 GByte of memory. Then performance charts comparing TAPAAL-OTF(PAR) to TAPAAL-OTF(SEQ) are shown (you may click on one graph to enlarge it).

Statistics on the execution
  TAPAAL-OTF(PAR) TAPAAL-OTF(SEQ) Both tools   TAPAAL-OTF(PAR) TAPAAL-OTF(SEQ)
Computed OK 0 0 77   Smallest Memory Footprint
Do not compete 0 0 137 Times tool wins 66 11
Error detected 0 0 11   Shortest Execution Time
Cannot Compute + Time-out 0 0 179 Times tool wins 13 64


On the chart below, denote cases where the two tools did computed a result, denote the cases where at least one tool did not competed, denote the cases where at least one tool did a mistake and denote the cases where at least one tool stated it could not compute a result or timed-out.

memory chart time chart