fond
Model Checking Contest 2019
9th edition, Prague, Czech Republic, April 7, 2019 (TOOLympics)
ITS-Tools.M compared to other tools («Known» models, UpperBounds)
Last Updated
Apr 15, 2019

Introduction

This page presents how ITS-Tools.M do cope efficiently with the UpperBounds examination face to the other participating tools. In this page, we consider «Known» models.

The next sections will show chart comparing performances in terms of both memory and execution time.The x-axis corresponds to the challenging tool where the y-axes represents ITS-Tools.M' performances. Thus, points below the diagonal of a chart denote comparisons favorables to the tool while others 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.M versus ITS-Tools

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

Statistics on the executions
  ITS-Tools.M ITS-Tools Both tools   ITS-Tools.M ITS-Tools
All computed OK 51 11 483   Smallest Memory Footprint
ITS-Tools.M = ITS-Tools 0 Times tool wins 163 386
ITS-Tools.M > ITS-Tools 1   Shortest Execution Time
ITS-Tools.M < ITS-Tools 3 Times tool wins 191 358
Do not compete 0 0 0
Error detected 1 0 0  
Cannot Compute + Time-out 11 52 417


On the chart below, denote cases where the two tools did computed all results without error, denote cases where the two tool did computed the same number of values (but not al values in the examination), denote cases where ITS-Tools.M computed more values than ITS-Tools, denote cases where ITS-Tools.M computed less values than ITS-Tools, 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.

ITS-Tools.M wins when points are below the diagonal, ITS-Tools wins when points are above the diagonal.

memory chart time chart

ITS-Tools.M versus LoLA

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

Statistics on the executions
  ITS-Tools.M LoLA Both tools   ITS-Tools.M LoLA
All computed OK 9 380 448   Smallest Memory Footprint
ITS-Tools.M = LoLA 0 Times tool wins 423 495
ITS-Tools.M > LoLA 78   Shortest Execution Time
ITS-Tools.M < LoLA 3 Times tool wins 227 691
Do not compete 0 0 0
Error detected 1 0 0  
Cannot Compute + Time-out 379 9 50


On the chart below, denote cases where the two tools did computed all results without error, denote cases where the two tool did computed the same number of values (but not al values in the examination), denote cases where ITS-Tools.M computed more values than LoLA, denote cases where ITS-Tools.M computed less values than LoLA, 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.

ITS-Tools.M wins when points are below the diagonal, LoLA wins when points are above the diagonal.

memory chart time chart

ITS-Tools.M versus LTSMin

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

Statistics on the executions
  ITS-Tools.M LTSMin Both tools   ITS-Tools.M LTSMin
All computed OK 76 326 363   Smallest Memory Footprint
ITS-Tools.M = LTSMin 0 Times tool wins 118 747
ITS-Tools.M > LTSMin 96   Shortest Execution Time
ITS-Tools.M < LTSMin 3 Times tool wins 259 606
Do not compete 0 180 0
Error detected 1 0 0  
Cannot Compute + Time-out 429 0 0


On the chart below, denote cases where the two tools did computed all results without error, denote cases where the two tool did computed the same number of values (but not al values in the examination), denote cases where ITS-Tools.M computed more values than LTSMin, denote cases where ITS-Tools.M computed less values than LTSMin, 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.

ITS-Tools.M wins when points are below the diagonal, LTSMin wins when points are above the diagonal.

memory chart time chart

ITS-Tools.M versus Tapaal

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

Statistics on the executions
  ITS-Tools.M Tapaal Both tools   ITS-Tools.M Tapaal
All computed OK 0 412 495   Smallest Memory Footprint
ITS-Tools.M = Tapaal 0 Times tool wins 48 903
ITS-Tools.M > Tapaal 40   Shortest Execution Time
ITS-Tools.M < Tapaal 3 Times tool wins 196 755
Do not compete 0 0 0
Error detected 1 0 0  
Cannot Compute + Time-out 411 0 18


On the chart below, denote cases where the two tools did computed all results without error, denote cases where the two tool did computed the same number of values (but not al values in the examination), denote cases where ITS-Tools.M computed more values than Tapaal, denote cases where ITS-Tools.M computed less values than Tapaal, 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.

ITS-Tools.M wins when points are below the diagonal, Tapaal wins when points are above the diagonal.

memory chart time chart

ITS-Tools.M versus enPAC

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

Statistics on the executions
  ITS-Tools.M enPAC Both tools   ITS-Tools.M enPAC
All computed OK 538 0 0   Smallest Memory Footprint
ITS-Tools.M = enPAC 0 Times tool wins 538 0
ITS-Tools.M > enPAC 0   Shortest Execution Time
ITS-Tools.M < enPAC 0 Times tool wins 538 0
Do not compete 0 0 0
Error detected 1 0 0  
Cannot Compute + Time-out 0 539 429


On the chart below, denote cases where the two tools did computed all results without error, denote cases where the two tool did computed the same number of values (but not al values in the examination), denote cases where ITS-Tools.M computed more values than enPAC, denote cases where ITS-Tools.M computed less values than enPAC, 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.

ITS-Tools.M wins when points are below the diagonal, enPAC wins when points are above the diagonal.

memory chart time chart

ITS-Tools.M versus GreatSPN

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

Statistics on the executions
  ITS-Tools.M GreatSPN Both tools   ITS-Tools.M GreatSPN
All computed OK 65 79 473   Smallest Memory Footprint
ITS-Tools.M = GreatSPN 0 Times tool wins 105 512
ITS-Tools.M > GreatSPN 0   Shortest Execution Time
ITS-Tools.M < GreatSPN 0 Times tool wins 101 516
Do not compete 0 0 0
Error detected 1 0 0  
Cannot Compute + Time-out 78 65 351


On the chart below, denote cases where the two tools did computed all results without error, denote cases where the two tool did computed the same number of values (but not al values in the examination), denote cases where ITS-Tools.M computed more values than GreatSPN, denote cases where ITS-Tools.M computed less values than GreatSPN, 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.

ITS-Tools.M wins when points are below the diagonal, GreatSPN wins when points are above the diagonal.

memory chart time chart

ITS-Tools.M versus smart

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

Statistics on the executions
  ITS-Tools.M smart Both tools   ITS-Tools.M smart
All computed OK 215 19 320   Smallest Memory Footprint
ITS-Tools.M = smart 0 Times tool wins 250 308
ITS-Tools.M > smart 3   Shortest Execution Time
ITS-Tools.M < smart 0 Times tool wins 362 196
Do not compete 0 180 0
Error detected 1 0 0  
Cannot Compute + Time-out 123 140 306


On the chart below, denote cases where the two tools did computed all results without error, denote cases where the two tool did computed the same number of values (but not al values in the examination), denote cases where ITS-Tools.M computed more values than smart, denote cases where ITS-Tools.M computed less values than smart, 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.

ITS-Tools.M wins when points are below the diagonal, smart wins when points are above the diagonal.

memory chart time chart

ITS-Tools.M versus 2018-Gold

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

Statistics on the executions
  ITS-Tools.M 2018-Gold Both tools   ITS-Tools.M 2018-Gold
All computed OK 16 366 410   Smallest Memory Footprint
ITS-Tools.M = 2018-Gold 0 Times tool wins 74 830
ITS-Tools.M > 2018-Gold 109   Shortest Execution Time
ITS-Tools.M < 2018-Gold 3 Times tool wins 126 778
Do not compete 0 0 0
Error detected 1 0 0  
Cannot Compute + Time-out 365 16 64


On the chart below, denote cases where the two tools did computed all results without error, denote cases where the two tool did computed the same number of values (but not al values in the examination), denote cases where ITS-Tools.M computed more values than 2018-Gold, denote cases where ITS-Tools.M computed less values than 2018-Gold, 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.

ITS-Tools.M wins when points are below the diagonal, 2018-Gold wins when points are above the diagonal.

memory chart time chart