fond
Model Checking Contest @ Petri Nets 2015
Bruxelles, Belgium, June 23, 2015
TAPAAL-OTF(PAR)%20compared%20to%20other%20tools%20(%C2%ABKnown%C2%BB%20models,%20ReachabilityCardinality)
Last Updated
August 19, 2015

Introduction

This page presents how TAPAAL-OTF(PAR) do cope efficiently with the ReachabilityCardinality 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 10 30 53   Smallest Memory Footprint
Do not compete 23 0 114 Times tool wins 41 52
Error detected 24 48 0   Shortest Execution Time
Cannot Compute + Time-out 66 45 114 Times tool wins 46 47


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 ITS-Tools

Some statistics are displayed below, based on 808 runs (404 for TAPAAL-OTF(PAR) and 404 for ITS-Tools, 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 ITS-Tools are shown (you may click on one graph to enlarge it).

Statistics on the execution
  TAPAAL-OTF(PAR) ITS-Tools Both tools   TAPAAL-OTF(PAR) ITS-Tools
Computed OK 48 209 15   Smallest Memory Footprint
Do not compete 137 0 0 Times tool wins 55 217
Error detected 17 118 7   Shortest Execution Time
Cannot Compute + Time-out 158 33 22 Times tool wins 55 217


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 188 63   Smallest Memory Footprint
Do not compete 0 0 137 Times tool wins 9 242
Error detected 18 10 6   Shortest Execution Time
Cannot Compute + Time-out 180 0 0 Times tool wins 1 250


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 54 140 9   Smallest Memory Footprint
Do not compete 137 0 0 Times tool wins 62 141
Error detected 13 104 11   Shortest Execution Time
Cannot Compute + Time-out 177 137 3 Times tool wins 59 144


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 19 29 44   Smallest Memory Footprint
Do not compete 137 0 0 Times tool wins 55 37
Error detected 24 36 0   Shortest Execution Time
Cannot Compute + Time-out 20 135 160 Times tool wins 47 45


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 0 173 63   Smallest Memory Footprint
Do not compete 0 0 137 Times tool wins 30 206
Error detected 23 3 1   Shortest Execution Time
Cannot Compute + Time-out 153 0 27 Times tool wins 17 219


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 197 63   Smallest Memory Footprint
Do not compete 0 0 137 Times tool wins 13 247
Error detected 23 1 1   Shortest Execution Time
Cannot Compute + Time-out 175 0 5 Times tool wins 21 239


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 76 63   Smallest Memory Footprint
Do not compete 0 0 137 Times tool wins 36 103
Error detected 24 0 0   Shortest Execution Time
Cannot Compute + Time-out 52 0 128 Times tool wins 11 128


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