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

Introduction

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

Some statistics are displayed below, based on 1050 runs (525 for Tapaal(SEQ) and 525 for ITS-Tools, so there are 525 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 ITS-Tools are shown (you may click on one graph to enlarge it).

Statistics on the execution
  Tapaal(SEQ) ITS-Tools Both tools   Tapaal(SEQ) ITS-Tools
Computed OK 218 1 130   Smallest Memory Footprint
Do not compete 164 0 0 Times tool wins 273 76
Error detected 0 0 2   Shortest Execution Time
Cannot Compute + Time-out 1 382 10 Times tool wins 258 91


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

Some statistics are displayed below, based on 1050 runs (525 for Tapaal(SEQ) and 525 for LoLa, so there are 525 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 LoLa are shown (you may click on one graph to enlarge it).

Statistics on the execution
  Tapaal(SEQ) LoLa Both tools   Tapaal(SEQ) LoLa
Computed OK 0 13 348   Smallest Memory Footprint
Do not compete 0 0 164 Times tool wins 184 177
Error detected 2 0 0   Shortest Execution Time
Cannot Compute + Time-out 11 0 0 Times tool wins 49 312


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

Some statistics are displayed below, based on 1050 runs (525 for Tapaal(SEQ) and 525 for LTSMin, so there are 525 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 0 13 348   Smallest Memory Footprint
Do not compete 0 0 164 Times tool wins 262 99
Error detected 2 0 0   Shortest Execution Time
Cannot Compute + Time-out 11 0 0 Times tool wins 124 237


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

Some statistics are displayed below, based on 1050 runs (525 for Tapaal(SEQ) and 525 for Tapaal(PAR), so there are 525 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(PAR) are shown (you may click on one graph to enlarge it).

Statistics on the execution
  Tapaal(SEQ) Tapaal(PAR) Both tools   Tapaal(SEQ) Tapaal(PAR)
Computed OK 226 1 122   Smallest Memory Footprint
Do not compete 0 0 164 Times tool wins 264 85
Error detected 2 0 0   Shortest Execution Time
Cannot Compute + Time-out 1 228 10 Times tool wins 237 112


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

Some statistics are displayed below, based on 1050 runs (525 for Tapaal(SEQ) and 525 for Marcie, so there are 525 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 172 36 176   Smallest Memory Footprint
Do not compete 164 0 0 Times tool wins 278 106
Error detected 2 0 0   Shortest Execution Time
Cannot Compute + Time-out 1 303 10 Times tool wins 242 142


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