fond
Model Checking Contest 2018
8th edition, Bratislava, Slovakia, June 26, 2018
ITS-Tools compared to other tools («Known» models, ReachabilityCardinality)
Last Updated
June 26, 2018

Introduction

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

Some statistics are displayed below, based on 1616 runs (808 for ITS-Tools and 808 for LTSMin, so there are 808 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 executions
  ITS-Tools LTSMin Both tools   ITS-Tools LTSMin
All computed OK 137 64 271   Smallest Memory Footprint
ITS-Tools = LTSMin 21 Times tool wins 140 625
ITS-Tools > LTSMin 227   Shortest Execution Time
ITS-Tools < LTSMin 45 Times tool wins 386 379
Do not compete 0 180 0
Error detected 0 0 0  
Cannot Compute + Time-out 107 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 computed more values than LTSMin, denote cases where ITS-Tools 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 wins when points are below the diagonal, LTSMin wins when points are above the diagonal.

memory chart time chart

ITS-Tools versus Tapaal

Some statistics are displayed below, based on 1616 runs (808 for ITS-Tools and 808 for Tapaal, so there are 808 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 executions
  ITS-Tools Tapaal Both tools   ITS-Tools Tapaal
All computed OK 0 104 409   Smallest Memory Footprint
ITS-Tools = Tapaal 6 Times tool wins 6 799
ITS-Tools > Tapaal 22   Shortest Execution Time
ITS-Tools < Tapaal 264 Times tool wins 75 730
Do not compete 0 0 0
Error detected 0 0 0  
Cannot Compute + Time-out 104 0 3


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 computed more values than Tapaal, denote cases where ITS-Tools 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 wins when points are below the diagonal, Tapaal wins when points are above the diagonal.

memory chart time chart

ITS-Tools versus LoLA

Some statistics are displayed below, based on 1616 runs (808 for ITS-Tools and 808 for LoLA, so there are 808 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 executions
  ITS-Tools LoLA Both tools   ITS-Tools LoLA
All computed OK 16 83 342   Smallest Memory Footprint
ITS-Tools = LoLA 3 Times tool wins 46 738
ITS-Tools > LoLA 82   Shortest Execution Time
ITS-Tools < LoLA 258 Times tool wins 223 561
Do not compete 0 0 0
Error detected 0 1 0  
Cannot Compute + Time-out 83 15 24


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 computed more values than LoLA, denote cases where ITS-Tools 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 wins when points are below the diagonal, LoLA wins when points are above the diagonal.

memory chart time chart

ITS-Tools versus M4M.full

Some statistics are displayed below, based on 1616 runs (808 for ITS-Tools and 808 for M4M.full, so there are 808 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 M4M.full are shown (you may click on one graph to enlarge it).

Statistics on the executions
  ITS-Tools M4M.full Both tools   ITS-Tools M4M.full
All computed OK 329 63 203   Smallest Memory Footprint
ITS-Tools = M4M.full 24 Times tool wins 360 404
ITS-Tools > M4M.full 45   Shortest Execution Time
ITS-Tools < M4M.full 100 Times tool wins 510 254
Do not compete 0 0 0
Error detected 0 0 0  
Cannot Compute + Time-out 63 329 44


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 computed more values than M4M.full, denote cases where ITS-Tools computed less values than M4M.full, 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 wins when points are below the diagonal, M4M.full wins when points are above the diagonal.

memory chart time chart

ITS-Tools versus M4M.struct

Some statistics are displayed below, based on 1616 runs (808 for ITS-Tools and 808 for M4M.struct, so there are 808 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 M4M.struct are shown (you may click on one graph to enlarge it).

Statistics on the executions
  ITS-Tools M4M.struct Both tools   ITS-Tools M4M.struct
All computed OK 248 73 218   Smallest Memory Footprint
ITS-Tools = M4M.struct 64 Times tool wins 332 442
ITS-Tools > M4M.struct 66   Shortest Execution Time
ITS-Tools < M4M.struct 105 Times tool wins 446 328
Do not compete 0 0 0
Error detected 0 0 0  
Cannot Compute + Time-out 73 248 34


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 computed more values than M4M.struct, denote cases where ITS-Tools computed less values than M4M.struct, 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 wins when points are below the diagonal, M4M.struct wins when points are above the diagonal.

memory chart time chart

ITS-Tools versus ITS-Tools.L

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

Statistics on the executions
  ITS-Tools ITS-Tools.L Both tools   ITS-Tools ITS-Tools.L
All computed OK 18 21 413   Smallest Memory Footprint
ITS-Tools = ITS-Tools.L 195 Times tool wins 371 351
ITS-Tools > ITS-Tools.L 40   Shortest Execution Time
ITS-Tools < ITS-Tools.L 35 Times tool wins 248 474
Do not compete 0 0 0
Error detected 0 0 0  
Cannot Compute + Time-out 21 18 86


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

memory chart time chart

ITS-Tools versus GreatSPN

Some statistics are displayed below, based on 1616 runs (808 for ITS-Tools and 808 for GreatSPN, so there are 808 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 executions
  ITS-Tools GreatSPN Both tools   ITS-Tools GreatSPN
All computed OK 411 4 256   Smallest Memory Footprint
ITS-Tools = GreatSPN 2 Times tool wins 412 293
ITS-Tools > GreatSPN 20   Shortest Execution Time
ITS-Tools < GreatSPN 12 Times tool wins 536 169
Do not compete 0 0 0
Error detected 0 0 0  
Cannot Compute + Time-out 4 411 103


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 computed more values than GreatSPN, denote cases where ITS-Tools 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 wins when points are below the diagonal, GreatSPN wins when points are above the diagonal.

memory chart time chart

ITS-Tools versus Irma.full

Some statistics are displayed below, based on 1616 runs (808 for ITS-Tools and 808 for Irma.full, so there are 808 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 Irma.full are shown (you may click on one graph to enlarge it).

Statistics on the executions
  ITS-Tools Irma.full Both tools   ITS-Tools Irma.full
All computed OK 223 85 233   Smallest Memory Footprint
ITS-Tools = Irma.full 3 Times tool wins 238 548
ITS-Tools > Irma.full 79   Shortest Execution Time
ITS-Tools < Irma.full 163 Times tool wins 409 377
Do not compete 0 0 0
Error detected 0 0 0  
Cannot Compute + Time-out 85 223 22


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 computed more values than Irma.full, denote cases where ITS-Tools computed less values than Irma.full, 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 wins when points are below the diagonal, Irma.full wins when points are above the diagonal.

memory chart time chart

ITS-Tools versus Irma.struct

Some statistics are displayed below, based on 1616 runs (808 for ITS-Tools and 808 for Irma.struct, so there are 808 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 Irma.struct are shown (you may click on one graph to enlarge it).

Statistics on the executions
  ITS-Tools Irma.struct Both tools   ITS-Tools Irma.struct
All computed OK 220 86 232   Smallest Memory Footprint
ITS-Tools = Irma.struct 5 Times tool wins 240 547
ITS-Tools > Irma.struct 81   Shortest Execution Time
ITS-Tools < Irma.struct 163 Times tool wins 405 382
Do not compete 0 0 0
Error detected 0 0 0  
Cannot Compute + Time-out 86 220 21


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 computed more values than Irma.struct, denote cases where ITS-Tools computed less values than Irma.struct, 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 wins when points are below the diagonal, Irma.struct wins when points are above the diagonal.

memory chart time chart