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

Introduction

This page presents how TAPAAL(SEQ) do cope efficiently with the ReachabilityBounds examination face to the other participating tools. In this page, we consider «Stripped» 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(SEQ)' 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(SEQ) versus GreatSPN-Meddly

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

Statistics on the execution
  TAPAAL(SEQ) GreatSPN-Meddly Both tools   TAPAAL(SEQ) GreatSPN-Meddly
Computed OK 166 0 96   Smallest Memory Footprint
Do not compete 23 0 114 Times tool wins 210 52
Error detected 0 53 0   Shortest Execution Time
Cannot Compute + Time-out 0 136 5 Times tool wins 196 66


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

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

Statistics on the execution
  TAPAAL(SEQ) LoLA2.0 Both tools   TAPAAL(SEQ) LoLA2.0
Computed OK 5 0 257   Smallest Memory Footprint
Do not compete 0 0 137 Times tool wins 134 128
Error detected 0 3 0   Shortest Execution Time
Cannot Compute + Time-out 0 2 5 Times tool wins 109 153


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

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

Statistics on the execution
  TAPAAL(SEQ) LTSMin Both tools   TAPAAL(SEQ) LTSMin
Computed OK 262 0 0   Smallest Memory Footprint
Do not compete 137 266 0 Times tool wins 262 0
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 4 137 1 Times tool wins 262 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(SEQ) versus Marcie

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

Statistics on the execution
  TAPAAL(SEQ) Marcie Both tools   TAPAAL(SEQ) Marcie
Computed OK 137 37 125   Smallest Memory Footprint
Do not compete 137 0 0 Times tool wins 230 69
Error detected 0 12 0   Shortest Execution Time
Cannot Compute + Time-out 1 226 4 Times tool wins 183 116


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

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

Statistics on the execution
  TAPAAL(SEQ) TAPAAL(MC) Both tools   TAPAAL(SEQ) TAPAAL(MC)
Computed OK 104 1 158   Smallest Memory Footprint
Do not compete 0 0 137 Times tool wins 254 9
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 1 104 4 Times tool wins 164 99


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

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

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


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

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

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


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