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

Introduction

This page presents how TAPAAL-OTF(PAR) do cope efficiently with the ReachabilityDeadlock examination face to the other participating tools. In this page, we consider «All» 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 Cunf

Some statistics are displayed below, based on 1858 runs (929 for TAPAAL-OTF(PAR) and 929 for Cunf, so there are 929 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 Cunf are shown (you may click on one graph to enlarge it).

Statistics on the execution
  TAPAAL-OTF(PAR) Cunf Both tools   TAPAAL-OTF(PAR) Cunf
Computed OK 194 66 89   Smallest Memory Footprint
Do not compete 0 351 301 Times tool wins 209 140
Error detected 0 4 0   Shortest Execution Time
Cannot Compute + Time-out 241 14 104 Times tool wins 212 137


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 GreatSPN-Meddly

Some statistics are displayed below, based on 1858 runs (929 for TAPAAL-OTF(PAR) and 929 for GreatSPN-Meddly, so there are 929 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 84 124 199   Smallest Memory Footprint
Do not compete 73 0 228 Times tool wins 195 212
Error detected 0 2 0   Shortest Execution Time
Cannot Compute + Time-out 125 156 220 Times tool wins 218 189


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 1858 runs (929 for TAPAAL-OTF(PAR) and 929 for LoLA2.0, so there are 929 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 280 283   Smallest Memory Footprint
Do not compete 0 0 301 Times tool wins 93 470
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 280 0 65 Times tool wins 83 480


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 1858 runs (929 for TAPAAL-OTF(PAR) and 929 for LTSMin, so there are 929 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 62 137 221   Smallest Memory Footprint
Do not compete 301 0 0 Times tool wins 259 161
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 137 363 208 Times tool wins 216 204


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 1858 runs (929 for TAPAAL-OTF(PAR) and 929 for Marcie, so there are 929 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 73 196 210   Smallest Memory Footprint
Do not compete 301 0 0 Times tool wins 244 235
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 118 296 227 Times tool wins 205 274


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 1858 runs (929 for TAPAAL-OTF(PAR) and 929 for TAPAAL(MC), so there are 929 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 45 150 238   Smallest Memory Footprint
Do not compete 0 0 301 Times tool wins 147 286
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 150 45 195 Times tool wins 65 368


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 1858 runs (929 for TAPAAL-OTF(PAR) and 929 for TAPAAL(SEQ), so there are 929 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 339 283   Smallest Memory Footprint
Do not compete 0 0 301 Times tool wins 66 556
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 339 0 6 Times tool wins 11 611


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 1858 runs (929 for TAPAAL-OTF(PAR) and 929 for TAPAAL-OTF(SEQ), so there are 929 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 219 283   Smallest Memory Footprint
Do not compete 0 0 301 Times tool wins 166 336
Error detected 0 23 0   Shortest Execution Time
Cannot Compute + Time-out 242 0 103 Times tool wins 71 431


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