fond
Model Checking Contest @ Petri Nets 2016
6th edition, Toruń, Poland, June 21, 2016
ITS-Tools compared to other tools («Surprise» models, ReachabilityDeadlock)
Last Updated
June 30, 2016

Introduction

This page presents how Tapaal(PAR) do cope efficiently with the ReachabilityDeadlock examination face to the other participating tools. In this page, we consider «Surprise» 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(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(PAR) versus ITS-Tools

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

Statistics on the execution
  Tapaal(PAR) ITS-Tools Both tools   Tapaal(PAR) ITS-Tools
Computed OK 12 29 16   Smallest Memory Footprint
Do not compete 9 0 0 Times tool wins 25 32
Error detected 0 1 0   Shortest Execution Time
Cannot Compute + Time-out 27 18 75 Times tool wins 25 32


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

memory chart time chart

Tapaal(PAR) versus LoLa

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

Statistics on the execution
  Tapaal(PAR) LoLa Both tools   Tapaal(PAR) LoLa
Computed OK 1 102 27   Smallest Memory Footprint
Do not compete 0 0 9 Times tool wins 10 120
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 102 1 0 Times tool wins 1 129


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

memory chart time chart

Tapaal(PAR) versus LTSMin

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

Statistics on the execution
  Tapaal(PAR) LTSMin Both tools   Tapaal(PAR) LTSMin
Computed OK 4 51 24   Smallest Memory Footprint
Do not compete 0 0 9 Times tool wins 27 52
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 51 4 51 Times tool wins 22 57


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

memory chart time chart

Tapaal(PAR) versus Marcie

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

Statistics on the execution
  Tapaal(PAR) Marcie Both tools   Tapaal(PAR) Marcie
Computed OK 0 41 28   Smallest Memory Footprint
Do not compete 9 0 0 Times tool wins 28 41
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 38 6 64 Times tool wins 23 46


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

memory chart time chart

Tapaal(PAR) versus PeCan

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

Statistics on the execution
  Tapaal(PAR) PeCan Both tools   Tapaal(PAR) PeCan
Computed OK 3 71 25   Smallest Memory Footprint
Do not compete 0 0 9 Times tool wins 22 77
Error detected 0 13 0   Shortest Execution Time
Cannot Compute + Time-out 81 0 21 Times tool wins 14 85


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

memory chart time chart

Tapaal(PAR) versus Tapaal(EXP)

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

Statistics on the execution
  Tapaal(PAR) Tapaal(EXP) Both tools   Tapaal(PAR) Tapaal(EXP)
Computed OK 0 80 28   Smallest Memory Footprint
Do not compete 0 0 9 Times tool wins 0 108
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 80 0 22 Times tool wins 1 107


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

memory chart time chart

Tapaal(PAR) versus Tapaal(SEQ)

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

Statistics on the execution
  Tapaal(PAR) Tapaal(SEQ) Both tools   Tapaal(PAR) Tapaal(SEQ)
Computed OK 0 74 28   Smallest Memory Footprint
Do not compete 0 0 9 Times tool wins 0 102
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 74 0 28 Times tool wins 0 102


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

memory chart time chart