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

Introduction

This page presents how ITS-Tools do cope efficiently with the StateSpace 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 ITS-Tools' 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).

ITS-Tools versus LTSMin

Some statistics are displayed below, based on 866 runs (433 for ITS-Tools 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 ITS-Tools to LTSMin are shown (you may click on one graph to enlarge it).

Statistics on the execution
  ITS-Tools LTSMin Both tools   ITS-Tools LTSMin
Computed OK 59 10 105   Smallest Memory Footprint
Do not compete 0 120 0 Times tool wins 144 30
Error detected 1 0 0   Shortest Execution Time
Cannot Compute + Time-out 97 27 171 Times tool wins 124 50


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

ITS-Tools versus LoLA

Some statistics are displayed below, based on 866 runs (433 for ITS-Tools 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 ITS-Tools to LoLA are shown (you may click on one graph to enlarge it).

Statistics on the execution
  ITS-Tools LoLA Both tools   ITS-Tools LoLA
Computed OK 164 0 0   Smallest Memory Footprint
Do not compete 0 423 0 Times tool wins 164 0
Error detected 1 0 0   Shortest Execution Time
Cannot Compute + Time-out 258 0 10 Times tool wins 164 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

ITS-Tools versus Tapaal

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

Statistics on the execution
  ITS-Tools Tapaal Both tools   ITS-Tools Tapaal
Computed OK 98 6 66   Smallest Memory Footprint
Do not compete 0 120 0 Times tool wins 112 58
Error detected 1 0 0   Shortest Execution Time
Cannot Compute + Time-out 93 66 175 Times tool wins 119 51


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

ITS-Tools versus MARCIE

Some statistics are displayed below, based on 866 runs (433 for ITS-Tools 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 ITS-Tools to MARCIE are shown (you may click on one graph to enlarge it).

Statistics on the execution
  ITS-Tools MARCIE Both tools   ITS-Tools MARCIE
Computed OK 20 28 144   Smallest Memory Footprint
Do not compete 0 0 0 Times tool wins 159 33
Error detected 1 2 0   Shortest Execution Time
Cannot Compute + Time-out 27 18 241 Times tool wins 98 94


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

ITS-Tools versus GreatSPN

Some statistics are displayed below, based on 866 runs (433 for ITS-Tools 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 ITS-Tools to GreatSPN are shown (you may click on one graph to enlarge it).

Statistics on the execution
  ITS-Tools GreatSPN Both tools   ITS-Tools GreatSPN
Computed OK 23 63 141   Smallest Memory Footprint
Do not compete 0 0 0 Times tool wins 42 185
Error detected 1 0 0   Shortest Execution Time
Cannot Compute + Time-out 62 23 206 Times tool wins 65 162


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

ITS-Tools versus smart

Some statistics are displayed below, based on 866 runs (433 for ITS-Tools and 433 for smart, 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 ITS-Tools to smart are shown (you may click on one graph to enlarge it).

Statistics on the execution
  ITS-Tools smart Both tools   ITS-Tools smart
Computed OK 90 28 74   Smallest Memory Footprint
Do not compete 0 120 0 Times tool wins 94 98
Error detected 1 21 0   Shortest Execution Time
Cannot Compute + Time-out 115 37 153 Times tool wins 110 82


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

ITS-Tools versus TINA.tedd

Some statistics are displayed below, based on 866 runs (433 for ITS-Tools and 433 for TINA.tedd, 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 ITS-Tools to TINA.tedd are shown (you may click on one graph to enlarge it).

Statistics on the execution
  ITS-Tools TINA.tedd Both tools   ITS-Tools TINA.tedd
Computed OK 13 31 151   Smallest Memory Footprint
Do not compete 0 0 0 Times tool wins 161 34
Error detected 1 0 0   Shortest Execution Time
Cannot Compute + Time-out 30 13 238 Times tool wins 60 135


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

ITS-Tools versus TINA.sift

Some statistics are displayed below, based on 866 runs (433 for ITS-Tools and 433 for TINA.sift, 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 ITS-Tools to TINA.sift are shown (you may click on one graph to enlarge it).

Statistics on the execution
  ITS-Tools TINA.sift Both tools   ITS-Tools TINA.sift
Computed OK 86 7 78   Smallest Memory Footprint
Do not compete 0 0 0 Times tool wins 107 64
Error detected 1 2 0   Shortest Execution Time
Cannot Compute + Time-out 6 84 262 Times tool wins 104 67


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