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

Introduction

This page presents how TAPAAL(MC) 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(MC)' 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(MC) versus Cunf

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

Statistics on the execution
  TAPAAL(MC) Cunf Both tools   TAPAAL(MC) Cunf
Computed OK 261 28 127   Smallest Memory Footprint
Do not compete 0 351 301 Times tool wins 286 130
Error detected 0 4 0   Shortest Execution Time
Cannot Compute + Time-out 164 42 76 Times tool wins 310 106


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(MC) versus GreatSPN-Meddly

Some statistics are displayed below, based on 1858 runs (929 for TAPAAL(MC) 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(MC) to GreatSPN-Meddly are shown (you may click on one graph to enlarge it).

Statistics on the execution
  TAPAAL(MC) GreatSPN-Meddly Both tools   TAPAAL(MC) GreatSPN-Meddly
Computed OK 131 66 257   Smallest Memory Footprint
Do not compete 73 0 228 Times tool wins 347 107
Error detected 0 2 0   Shortest Execution Time
Cannot Compute + Time-out 67 203 173 Times tool wins 349 105


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(MC) versus LoLA2.0

Some statistics are displayed below, based on 1858 runs (929 for TAPAAL(MC) 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(MC) to LoLA2.0 are shown (you may click on one graph to enlarge it).

Statistics on the execution
  TAPAAL(MC) LoLA2.0 Both tools   TAPAAL(MC) LoLA2.0
Computed OK 12 187 376   Smallest Memory Footprint
Do not compete 0 0 301 Times tool wins 136 439
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 187 12 53 Times tool wins 203 372


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(MC) versus LTSMin

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

Statistics on the execution
  TAPAAL(MC) LTSMin Both tools   TAPAAL(MC) LTSMin
Computed OK 107 77 281   Smallest Memory Footprint
Do not compete 301 0 0 Times tool wins 373 92
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 77 408 163 Times tool wins 358 107


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(MC) versus Marcie

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

Statistics on the execution
  TAPAAL(MC) Marcie Both tools   TAPAAL(MC) Marcie
Computed OK 166 184 222   Smallest Memory Footprint
Do not compete 301 0 0 Times tool wins 388 184
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 106 389 134 Times tool wins 365 207


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(MC) versus TAPAAL(SEQ)

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

Statistics on the execution
  TAPAAL(MC) TAPAAL(SEQ) Both tools   TAPAAL(MC) TAPAAL(SEQ)
Computed OK 0 234 388   Smallest Memory Footprint
Do not compete 0 0 301 Times tool wins 36 586
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 234 0 6 Times tool wins 94 528


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(MC) versus TAPAAL-OTF(PAR)

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

Statistics on the execution
  TAPAAL(MC) TAPAAL-OTF(PAR) Both tools   TAPAAL(MC) TAPAAL-OTF(PAR)
Computed OK 150 45 238   Smallest Memory Footprint
Do not compete 0 0 301 Times tool wins 286 147
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 45 150 195 Times tool wins 368 65


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(MC) versus TAPAAL-OTF(SEQ)

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

Statistics on the execution
  TAPAAL(MC) TAPAAL-OTF(SEQ) Both tools   TAPAAL(MC) TAPAAL-OTF(SEQ)
Computed OK 15 129 373   Smallest Memory Footprint
Do not compete 0 0 301 Times tool wins 314 203
Error detected 0 23 0   Shortest Execution Time
Cannot Compute + Time-out 145 8 95 Times tool wins 326 191


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