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

Introduction

This page presents how ITS-Tools.M do cope efficiently with the StateSpace examination face to the other participating tools. In this page, we consider «All» 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 2036 runs (1018 for ITS-Tools.M and 1018 for ITS-Tools, so there are 1018 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 36 90 0   Smallest Memory Footprint
ITS-Tools.M = ITS-Tools 422 Times tool wins 156 392
ITS-Tools.M > ITS-Tools 0   Shortest Execution Time
ITS-Tools.M < ITS-Tools 0 Times tool wins 185 363
Do not compete 0 0 0
Error detected 0 0 0  
Cannot Compute + Time-out 90 36 470


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 LTSMin

Some statistics are displayed below, based on 2036 runs (1018 for ITS-Tools.M and 1018 for LTSMin, so there are 1018 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 129 39 0   Smallest Memory Footprint
ITS-Tools.M = LTSMin 329 Times tool wins 150 347
ITS-Tools.M > LTSMin 0   Shortest Execution Time
ITS-Tools.M < LTSMin 0 Times tool wins 206 291
Do not compete 0 193 0
Error detected 0 0 0  
Cannot Compute + Time-out 165 62 395


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 2036 runs (1018 for ITS-Tools.M and 1018 for Tapaal, so there are 1018 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 260 22 0   Smallest Memory Footprint
ITS-Tools.M = Tapaal 198 Times tool wins 303 177
ITS-Tools.M > Tapaal 0   Shortest Execution Time
ITS-Tools.M < Tapaal 0 Times tool wins 323 157
Do not compete 0 0 0
Error detected 0 0 0  
Cannot Compute + Time-out 22 260 538


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 2036 runs (1018 for ITS-Tools.M and 1018 for enPAC, so there are 1018 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 395 6 0   Smallest Memory Footprint
ITS-Tools.M = enPAC 0 Times tool wins 424 40
ITS-Tools.M > enPAC 63   Shortest Execution Time
ITS-Tools.M < enPAC 0 Times tool wins 424 40
Do not compete 0 193 0
Error detected 0 22 0  
Cannot Compute + Time-out 138 312 422


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 2036 runs (1018 for ITS-Tools.M and 1018 for GreatSPN, so there are 1018 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 22 163 0   Smallest Memory Footprint
ITS-Tools.M = GreatSPN 5 Times tool wins 76 545
ITS-Tools.M > GreatSPN 0   Shortest Execution Time
ITS-Tools.M < GreatSPN 431 Times tool wins 54 567
Do not compete 0 0 0
Error detected 0 0 0  
Cannot Compute + Time-out 163 22 397


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 2036 runs (1018 for ITS-Tools.M and 1018 for smart, so there are 1018 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 170 19 0   Smallest Memory Footprint
ITS-Tools.M = smart 2 Times tool wins 223 254
ITS-Tools.M > smart 0   Shortest Execution Time
ITS-Tools.M < smart 286 Times tool wins 338 139
Do not compete 0 193 0
Error detected 0 0 0  
Cannot Compute + Time-out 145 103 415


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 TINA.tedd

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

Statistics on the executions
  ITS-Tools.M TINA.tedd Both tools   ITS-Tools.M TINA.tedd
All computed OK 9 214 0   Smallest Memory Footprint
ITS-Tools.M = TINA.tedd 0 Times tool wins 426 246
ITS-Tools.M > TINA.tedd 0   Shortest Execution Time
ITS-Tools.M < TINA.tedd 449 Times tool wins 117 555
Do not compete 0 0 0
Error detected 0 0 0  
Cannot Compute + Time-out 214 9 346


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 TINA.tedd, denote cases where ITS-Tools.M computed less values than TINA.tedd, 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, TINA.tedd wins when points are above the diagonal.

memory chart time chart

ITS-Tools.M versus 2018-Gold

Some statistics are displayed below, based on 2036 runs (1018 for ITS-Tools.M and 1018 for 2018-Gold, so there are 1018 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 22 155 0   Smallest Memory Footprint
ITS-Tools.M = 2018-Gold 7 Times tool wins 81 504
ITS-Tools.M > 2018-Gold 0   Shortest Execution Time
ITS-Tools.M < 2018-Gold 401 Times tool wins 59 526
Do not compete 0 0 0
Error detected 0 0 0  
Cannot Compute + Time-out 155 22 382


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