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

Introduction

This page presents how Tapaal(SEQ) do cope efficiently with the CTLFireability 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(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 2378 runs (1189 for Tapaal(SEQ) and 1189 for ITS-Tools, so there are 1189 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 422 114 395   Smallest Memory Footprint
Do not compete 337 0 0 Times tool wins 589 342
Error detected 1 1 6   Shortest Execution Time
Cannot Compute + Time-out 2 647 26 Times tool wins 561 370


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 2378 runs (1189 for Tapaal(SEQ) and 1189 for LoLa, so there are 1189 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 32 817   Smallest Memory Footprint
Do not compete 0 0 337 Times tool wins 467 382
Error detected 7 0 0   Shortest Execution Time
Cannot Compute + Time-out 26 1 2 Times tool wins 124 725


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 2378 runs (1189 for Tapaal(SEQ) and 1189 for LTSMin, so there are 1189 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 35 817   Smallest Memory Footprint
Do not compete 0 0 337 Times tool wins 644 208
Error detected 7 0 0   Shortest Execution Time
Cannot Compute + Time-out 28 0 0 Times tool wins 230 622


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 2378 runs (1189 for Tapaal(SEQ) and 1189 for Tapaal(PAR), so there are 1189 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 537 2 280   Smallest Memory Footprint
Do not compete 0 0 337 Times tool wins 655 164
Error detected 7 0 0   Shortest Execution Time
Cannot Compute + Time-out 2 544 26 Times tool wins 550 269


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 2378 runs (1189 for Tapaal(SEQ) and 1189 for Marcie, so there are 1189 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 395 101 422   Smallest Memory Footprint
Do not compete 337 0 0 Times tool wins 604 314
Error detected 7 0 0   Shortest Execution Time
Cannot Compute + Time-out 4 642 24 Times tool wins 541 377


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