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

Introduction

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

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

Statistics on the executions
  ITS-Tools.L LTSMin Both tools   ITS-Tools.L LTSMin
All computed OK 59 401 216   Smallest Memory Footprint
ITS-Tools.L = LTSMin 2 Times tool wins 60 765
ITS-Tools.L > LTSMin 116   Shortest Execution Time
ITS-Tools.L < LTSMin 31 Times tool wins 301 524
Do not compete 0 181 0
Error detected 0 0 0  
Cannot Compute + Time-out 523 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.L computed more values than LTSMin, denote cases where ITS-Tools.L 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.L wins when points are below the diagonal, LTSMin wins when points are above the diagonal.

memory chart time chart

ITS-Tools.L versus Tapaal

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

Statistics on the executions
  ITS-Tools.L Tapaal Both tools   ITS-Tools.L Tapaal
All computed OK 1 511 224   Smallest Memory Footprint
ITS-Tools.L = Tapaal 4 Times tool wins 139 796
ITS-Tools.L > Tapaal 89   Shortest Execution Time
ITS-Tools.L < Tapaal 106 Times tool wins 182 753
Do not compete 0 0 0
Error detected 0 0 0  
Cannot Compute + Time-out 511 1 12


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

memory chart time chart

ITS-Tools.L versus LoLA

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

Statistics on the executions
  ITS-Tools.L LoLA Both tools   ITS-Tools.L LoLA
All computed OK 11 483 174   Smallest Memory Footprint
ITS-Tools.L = LoLA 2 Times tool wins 98 809
ITS-Tools.L > LoLA 133   Shortest Execution Time
ITS-Tools.L < LoLA 104 Times tool wins 252 655
Do not compete 0 0 0
Error detected 0 5 0  
Cannot Compute + Time-out 484 7 39


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

memory chart time chart

ITS-Tools.L versus M4M.full

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

Statistics on the executions
  ITS-Tools.L M4M.full Both tools   ITS-Tools.L M4M.full
All computed OK 222 326 61   Smallest Memory Footprint
ITS-Tools.L = M4M.full 1 Times tool wins 243 507
ITS-Tools.L > M4M.full 125   Shortest Execution Time
ITS-Tools.L < M4M.full 15 Times tool wins 369 381
Do not compete 0 0 0
Error detected 0 4 0  
Cannot Compute + Time-out 326 218 197


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

memory chart time chart

ITS-Tools.L versus M4M.struct

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

Statistics on the executions
  ITS-Tools.L M4M.struct Both tools   ITS-Tools.L M4M.struct
All computed OK 217 215 85   Smallest Memory Footprint
ITS-Tools.L = M4M.struct 15 Times tool wins 235 404
ITS-Tools.L > M4M.struct 95   Shortest Execution Time
ITS-Tools.L < M4M.struct 12 Times tool wins 379 260
Do not compete 0 0 0
Error detected 0 3 0  
Cannot Compute + Time-out 216 215 307


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

memory chart time chart

ITS-Tools.L versus ITS-Tools

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

Statistics on the executions
  ITS-Tools.L ITS-Tools Both tools   ITS-Tools.L ITS-Tools
All computed OK 3 24 308   Smallest Memory Footprint
ITS-Tools.L = ITS-Tools 91 Times tool wins 207 241
ITS-Tools.L > ITS-Tools 5   Shortest Execution Time
ITS-Tools.L < ITS-Tools 17 Times tool wins 217 231
Do not compete 0 0 0
Error detected 0 0 0  
Cannot Compute + Time-out 24 3 499


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

memory chart time chart

ITS-Tools.L versus GreatSPN

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

Statistics on the executions
  ITS-Tools.L GreatSPN Both tools   ITS-Tools.L GreatSPN
All computed OK 136 37 245   Smallest Memory Footprint
ITS-Tools.L = GreatSPN 4 Times tool wins 136 325
ITS-Tools.L > GreatSPN 2   Shortest Execution Time
ITS-Tools.L < GreatSPN 37 Times tool wins 208 253
Do not compete 0 0 0
Error detected 0 0 0  
Cannot Compute + Time-out 37 136 486


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

memory chart time chart

ITS-Tools.L versus Irma.full

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

Statistics on the executions
  ITS-Tools.L Irma.full Both tools   ITS-Tools.L Irma.full
All computed OK 218 344 132   Smallest Memory Footprint
ITS-Tools.L = Irma.full 9 Times tool wins 237 531
ITS-Tools.L > Irma.full 46   Shortest Execution Time
ITS-Tools.L < Irma.full 19 Times tool wins 343 425
Do not compete 0 0 0
Error detected 0 0 0  
Cannot Compute + Time-out 344 218 179


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

memory chart time chart

ITS-Tools.L versus Irma.struct

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

Statistics on the executions
  ITS-Tools.L Irma.struct Both tools   ITS-Tools.L Irma.struct
All computed OK 217 343 133   Smallest Memory Footprint
ITS-Tools.L = Irma.struct 9 Times tool wins 234 533
ITS-Tools.L > Irma.struct 46   Shortest Execution Time
ITS-Tools.L < Irma.struct 19 Times tool wins 342 425
Do not compete 0 0 0
Error detected 0 0 0  
Cannot Compute + Time-out 343 217 180


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

memory chart time chart