fond
Model Checking Contest @ Petri Nets 2017
7th edition, Zaragoza, Spain, June 27, 2017
ITS-Tools compared to other tools («Stripped» models, ReachabilityCardinality)
Last Updated
June 27, 2017

Introduction

This page presents how Tapaal do cope efficiently with the ReachabilityCardinality 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' 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 versus LTSMin

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

Statistics on the execution
  Tapaal LTSMin Both tools   Tapaal LTSMin
Computed OK 0 0 313   Smallest Memory Footprint
Do not compete 0 0 120 Times tool wins 275 38
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 0 0 0 Times tool wins 139 174


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 versus LoLA

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

Statistics on the execution
  Tapaal LoLA Both tools   Tapaal LoLA
Computed OK 0 110 313   Smallest Memory Footprint
Do not compete 120 0 0 Times tool wins 108 315
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 0 10 0 Times tool wins 37 386


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 versus ITS-Tools

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

Statistics on the execution
  Tapaal ITS-Tools Both tools   Tapaal ITS-Tools
Computed OK 74 84 239   Smallest Memory Footprint
Do not compete 120 0 0 Times tool wins 267 130
Error detected 0 17 0   Shortest Execution Time
Cannot Compute + Time-out 0 93 0 Times tool wins 179 218


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 versus MARCIE

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

Statistics on the execution
  Tapaal MARCIE Both tools   Tapaal MARCIE
Computed OK 168 30 145   Smallest Memory Footprint
Do not compete 120 0 0 Times tool wins 297 46
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 0 258 0 Times tool wins 232 111


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 versus GreatSPN

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

Statistics on the execution
  Tapaal GreatSPN Both tools   Tapaal GreatSPN
Computed OK 242 21 71   Smallest Memory Footprint
Do not compete 120 0 0 Times tool wins 302 32
Error detected 0 2 0   Shortest Execution Time
Cannot Compute + Time-out 0 339 0 Times tool wins 269 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