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

Introduction

This page presents how Tapaal 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 Tapaal' 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).

Tapaal versus LTSMin

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

Statistics on the executions
  Tapaal LTSMin Both tools   Tapaal LTSMin
All computed OK 87 140 233   Smallest Memory Footprint
Tapaal = LTSMin 6 Times tool wins 530 185
Tapaal > LTSMin 216   Shortest Execution Time
Tapaal < LTSMin 33 Times tool wins 322 393
Do not compete 0 180 0
Error detected 2 0 0  
Cannot Compute + Time-out 231 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 Tapaal computed more values than LTSMin, denote cases where Tapaal 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.

Tapaal wins when points are below the diagonal, LTSMin wins when points are above the diagonal.

memory chart time chart

Tapaal versus LoLA

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

Statistics on the executions
  Tapaal LoLA Both tools   Tapaal LoLA
All computed OK 15 181 288   Smallest Memory Footprint
Tapaal = LoLA 10 Times tool wins 126 630
Tapaal > LoLA 75   Shortest Execution Time
Tapaal < LoLA 187 Times tool wins 135 621
Do not compete 0 0 0
Error detected 2 0 0  
Cannot Compute + Time-out 179 15 52


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 Tapaal computed more values than LoLA, denote cases where Tapaal 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.

Tapaal wins when points are below the diagonal, LoLA wins when points are above the diagonal.

memory chart time chart

Tapaal versus M4M.full

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

Statistics on the executions
  Tapaal M4M.full Both tools   Tapaal M4M.full
All computed OK 271 112 166   Smallest Memory Footprint
Tapaal = M4M.full 10 Times tool wins 474 213
Tapaal > M4M.full 81   Shortest Execution Time
Tapaal < M4M.full 47 Times tool wins 414 273
Do not compete 0 0 0
Error detected 2 1 0  
Cannot Compute + Time-out 112 272 119


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 Tapaal computed more values than M4M.full, denote cases where Tapaal 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.

Tapaal wins when points are below the diagonal, M4M.full wins when points are above the diagonal.

memory chart time chart

Tapaal versus M4M.struct

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

Statistics on the executions
  Tapaal M4M.struct Both tools   Tapaal M4M.struct
All computed OK 343 29 174   Smallest Memory Footprint
Tapaal = M4M.struct 0 Times tool wins 523 81
Tapaal > M4M.struct 16   Shortest Execution Time
Tapaal < M4M.struct 42 Times tool wins 466 138
Do not compete 0 0 0
Error detected 2 1 0  
Cannot Compute + Time-out 29 344 202


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 Tapaal computed more values than M4M.struct, denote cases where Tapaal 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.

Tapaal wins when points are below the diagonal, M4M.struct wins when points are above the diagonal.

memory chart time chart

Tapaal versus ITS-Tools

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

Statistics on the executions
  Tapaal ITS-Tools Both tools   Tapaal ITS-Tools
All computed OK 192 72 320   Smallest Memory Footprint
Tapaal = ITS-Tools 0 Times tool wins 567 80
Tapaal > ITS-Tools 1   Shortest Execution Time
Tapaal < ITS-Tools 62 Times tool wins 347 300
Do not compete 0 0 0
Error detected 2 0 0  
Cannot Compute + Time-out 72 194 159


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 Tapaal computed more values than ITS-Tools, denote cases where Tapaal 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.

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

memory chart time chart

Tapaal versus ITS-Tools.L

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

Statistics on the executions
  Tapaal ITS-Tools.L Both tools   Tapaal ITS-Tools.L
All computed OK 218 70 290   Smallest Memory Footprint
Tapaal = ITS-Tools.L 0 Times tool wins 567 78
Tapaal > ITS-Tools.L 10   Shortest Execution Time
Tapaal < ITS-Tools.L 57 Times tool wins 364 281
Do not compete 0 0 0
Error detected 2 0 0  
Cannot Compute + Time-out 70 220 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 Tapaal computed more values than ITS-Tools.L, denote cases where Tapaal 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.

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

memory chart time chart

Tapaal versus GreatSPN

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

Statistics on the executions
  Tapaal GreatSPN Both tools   Tapaal GreatSPN
All computed OK 138 65 333   Smallest Memory Footprint
Tapaal = GreatSPN 0 Times tool wins 405 235
Tapaal > GreatSPN 0   Shortest Execution Time
Tapaal < GreatSPN 104 Times tool wins 227 413
Do not compete 0 0 0
Error detected 2 0 0  
Cannot Compute + Time-out 64 139 167


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 Tapaal computed more values than GreatSPN, denote cases where Tapaal 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.

Tapaal wins when points are below the diagonal, GreatSPN wins when points are above the diagonal.

memory chart time chart

Tapaal versus smart

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

Statistics on the executions
  Tapaal smart Both tools   Tapaal smart
All computed OK 326 31 224   Smallest Memory Footprint
Tapaal = smart 0 Times tool wins 505 101
Tapaal > smart 1   Shortest Execution Time
Tapaal < smart 24 Times tool wins 420 186
Do not compete 0 180 0
Error detected 2 0 0  
Cannot Compute + Time-out 123 240 108


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 Tapaal computed more values than smart, denote cases where Tapaal 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.

Tapaal wins when points are below the diagonal, smart wins when points are above the diagonal.

memory chart time chart

Tapaal versus Irma.full

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

Statistics on the executions
  Tapaal Irma.full Both tools   Tapaal Irma.full
All computed OK 183 160 195   Smallest Memory Footprint
Tapaal = Irma.full 11 Times tool wins 441 294
Tapaal > Irma.full 106   Shortest Execution Time
Tapaal < Irma.full 80 Times tool wins 335 400
Do not compete 0 0 0
Error detected 2 0 0  
Cannot Compute + Time-out 159 184 72


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 Tapaal computed more values than Irma.full, denote cases where Tapaal 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.

Tapaal wins when points are below the diagonal, Irma.full wins when points are above the diagonal.

memory chart time chart

Tapaal versus Irma.struct

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

Statistics on the executions
  Tapaal Irma.struct Both tools   Tapaal Irma.struct
All computed OK 183 160 195   Smallest Memory Footprint
Tapaal = Irma.struct 12 Times tool wins 443 292
Tapaal > Irma.struct 107   Shortest Execution Time
Tapaal < Irma.struct 78 Times tool wins 331 404
Do not compete 0 0 0
Error detected 2 0 0  
Cannot Compute + Time-out 159 184 72


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 Tapaal computed more values than Irma.struct, denote cases where Tapaal 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.

Tapaal wins when points are below the diagonal, Irma.struct wins when points are above the diagonal.

memory chart time chart