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

Introduction

This page presents how Tapaal(PAR) do cope efficiently with the UpperBounds 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 7 34 9   Smallest Memory Footprint
Do not compete 9 0 0 Times tool wins 12 38
Error detected 1 3 0   Shortest Execution Time
Cannot Compute + Time-out 37 17 76 Times tool wins 14 36


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 0 113 16   Smallest Memory Footprint
Do not compete 0 0 9 Times tool wins 6 123
Error detected 1 0 0   Shortest Execution Time
Cannot Compute + Time-out 113 1 0 Times tool wins 7 122


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 60 16   Smallest Memory Footprint
Do not compete 9 0 0 Times tool wins 16 60
Error detected 0 0 1   Shortest Execution Time
Cannot Compute + Time-out 54 3 59 Times tool wins 11 65


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 22 16   Smallest Memory Footprint
Do not compete 0 0 9 Times tool wins 0 38
Error detected 1 0 0   Shortest Execution Time
Cannot Compute + Time-out 22 1 91 Times tool wins 8 30


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 16 16   Smallest Memory Footprint
Do not compete 0 0 9 Times tool wins 3 29
Error detected 0 0 1   Shortest Execution Time
Cannot Compute + Time-out 16 0 97 Times tool wins 14 18


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 ydd-pt

Some statistics are displayed below, based on 278 runs (139 for Tapaal(PAR) and 139 for ydd-pt, 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 ydd-pt are shown (you may click on one graph to enlarge it).

Statistics on the execution
  Tapaal(PAR) ydd-pt Both tools   Tapaal(PAR) ydd-pt
Computed OK 16 0 0   Smallest Memory Footprint
Do not compete 9 0 0 Times tool wins 16 0
Error detected 1 0 0   Shortest Execution Time
Cannot Compute + Time-out 0 26 113 Times tool wins 16 0


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