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

Introduction

This page presents how ITS-Tools.L do cope efficiently with the ReachabilityDeadlock 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.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 1616 runs (808 for ITS-Tools.L 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.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 325 17 287   Smallest Memory Footprint
ITS-Tools.L = LTSMin 0 Times tool wins 326 328
ITS-Tools.L > LTSMin 25   Shortest Execution Time
ITS-Tools.L < LTSMin 0 Times tool wins 567 87
Do not compete 0 181 0
Error detected 0 0 0  
Cannot Compute + Time-out 85 212 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.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 1616 runs (808 for ITS-Tools.L 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.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 62 122 575   Smallest Memory Footprint
ITS-Tools.L = Tapaal 0 Times tool wins 72 687
ITS-Tools.L > Tapaal 0   Shortest Execution Time
ITS-Tools.L < Tapaal 0 Times tool wins 119 640
Do not compete 0 0 0
Error detected 0 0 0  
Cannot Compute + Time-out 122 62 49


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 1616 runs (808 for ITS-Tools.L 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.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 115 125 522   Smallest Memory Footprint
ITS-Tools.L = LoLA 0 Times tool wins 115 647
ITS-Tools.L > LoLA 0   Shortest Execution Time
ITS-Tools.L < LoLA 0 Times tool wins 197 565
Do not compete 0 0 0
Error detected 0 0 0  
Cannot Compute + Time-out 125 115 46


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 1616 runs (808 for ITS-Tools.L 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.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 300 129 239   Smallest Memory Footprint
ITS-Tools.L = M4M.full 0 Times tool wins 330 436
ITS-Tools.L > M4M.full 98   Shortest Execution Time
ITS-Tools.L < M4M.full 0 Times tool wins 569 197
Do not compete 0 0 0
Error detected 0 0 0  
Cannot Compute + Time-out 129 300 42


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 1616 runs (808 for ITS-Tools.L 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.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 343 78 216   Smallest Memory Footprint
ITS-Tools.L = M4M.struct 0 Times tool wins 365 350
ITS-Tools.L > M4M.struct 78   Shortest Execution Time
ITS-Tools.L < M4M.struct 0 Times tool wins 566 149
Do not compete 0 0 0
Error detected 0 0 0  
Cannot Compute + Time-out 78 343 93


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 1616 runs (808 for ITS-Tools.L and 808 for ITS-Tools, 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.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 38 10 599   Smallest Memory Footprint
ITS-Tools.L = ITS-Tools 0 Times tool wins 352 295
ITS-Tools.L > ITS-Tools 0   Shortest Execution Time
ITS-Tools.L < ITS-Tools 0 Times tool wins 346 301
Do not compete 0 0 0
Error detected 0 0 0  
Cannot Compute + Time-out 10 38 161


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 1616 runs (808 for ITS-Tools.L 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.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 250 5 387   Smallest Memory Footprint
ITS-Tools.L = GreatSPN 0 Times tool wins 250 392
ITS-Tools.L > GreatSPN 0   Shortest Execution Time
ITS-Tools.L < GreatSPN 0 Times tool wins 427 215
Do not compete 0 0 0
Error detected 0 0 0  
Cannot Compute + Time-out 5 250 166


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 1616 runs (808 for ITS-Tools.L 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.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 234 139 314   Smallest Memory Footprint
ITS-Tools.L = Irma.full 0 Times tool wins 251 525
ITS-Tools.L > Irma.full 89   Shortest Execution Time
ITS-Tools.L < Irma.full 0 Times tool wins 557 219
Do not compete 0 0 0
Error detected 0 0 0  
Cannot Compute + Time-out 139 234 32


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 1616 runs (808 for ITS-Tools.L 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.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 234 140 314   Smallest Memory Footprint
ITS-Tools.L = Irma.struct 0 Times tool wins 251 526
ITS-Tools.L > Irma.struct 89   Shortest Execution Time
ITS-Tools.L < Irma.struct 0 Times tool wins 555 222
Do not compete 0 0 0
Error detected 0 0 0  
Cannot Compute + Time-out 140 234 31


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