fond
Model Checking Contest @ Petri Nets 2015
Bruxelles, Belgium, June 23, 2015
LoLA2.0 compared to other tools («Known» models, ReachabilityFireabilitySimple)
Last Updated
August 19, 2015

Introduction

This page presents how LoLA2.0 do cope efficiently with the ReachabilityFireabilitySimple examination face to the other participating tools. In this page, we consider «Known» models.

The next sections will show chart comparing performances in termsof both memory and execution time.The x-axis corresponds to the challenging tool where the y-axes represents LoLA2.0' performances. Thus, points below the diagonal of a chart denote comparisons favorables to the tool whileothers 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).

LoLA2.0 versus Cunf

Some statistics are displayed below, based on 808 runs (404 for LoLA2.0 and 404 for Cunf, so there are 404 plots on each of the two charts). Each execution was allowed 1 hour and 16 GByte of memory. Then performance charts comparing LoLA2.0 to Cunf are shown (you may click on one graph to enlarge it).

Statistics on the execution
  LoLA2.0 Cunf Both tools   LoLA2.0 Cunf
Computed OK 190 0 75   Smallest Memory Footprint
Do not compete 0 140 137 Times tool wins 211 54
Error detected 2 1 0   Shortest Execution Time
Cannot Compute + Time-out 0 51 0 Times tool wins 200 65


On the chart below, denote cases where the two tools did computed a result, denote the cases where at least one tool did not competed, denote the cases where at least one tool did a mistake and denote the cases where at least one tool stated it could not compute a result or timed-out.

memory chart time chart

LoLA2.0 versus GreatSPN-Meddly

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

Statistics on the execution
  LoLA2.0 GreatSPN-Meddly Both tools   LoLA2.0 GreatSPN-Meddly
Computed OK 208 0 57   Smallest Memory Footprint
Do not compete 23 0 114 Times tool wins 264 1
Error detected 1 82 1   Shortest Execution Time
Cannot Compute + Time-out 0 150 0 Times tool wins 263 2


On the chart below, denote cases where the two tools did computed a result, denote the cases where at least one tool did not competed, denote the cases where at least one tool did a mistake and denote the cases where at least one tool stated it could not compute a result or timed-out.

memory chart time chart

LoLA2.0 versus ITS-Tools

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

Statistics on the execution
  LoLA2.0 ITS-Tools Both tools   LoLA2.0 ITS-Tools
Computed OK 91 46 174   Smallest Memory Footprint
Do not compete 137 0 0 Times tool wins 264 47
Error detected 2 7 0   Shortest Execution Time
Cannot Compute + Time-out 0 177 0 Times tool wins 257 54


On the chart below, denote cases where the two tools did computed a result, denote the cases where at least one tool did not competed, denote the cases where at least one tool did a mistake and denote the cases where at least one tool stated it could not compute a result or timed-out.

memory chart time chart

LoLA2.0 versus LTSMin

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

Statistics on the execution
  LoLA2.0 LTSMin Both tools   LoLA2.0 LTSMin
Computed OK 8 2 257   Smallest Memory Footprint
Do not compete 137 0 0 Times tool wins 246 21
Error detected 2 6 0   Shortest Execution Time
Cannot Compute + Time-out 0 139 0 Times tool wins 244 23


On the chart below, denote cases where the two tools did computed a result, denote the cases where at least one tool did not competed, denote the cases where at least one tool did a mistake and denote the cases where at least one tool stated it could not compute a result or timed-out.

memory chart time chart

LoLA2.0 versus Marcie

Some statistics are displayed below, based on 808 runs (404 for LoLA2.0 and 404 for Marcie, so there are 404 plots on each of the two charts). Each execution was allowed 1 hour and 16 GByte of memory. Then performance charts comparing LoLA2.0 to Marcie are shown (you may click on one graph to enlarge it).

Statistics on the execution
  LoLA2.0 Marcie Both tools   LoLA2.0 Marcie
Computed OK 134 37 131   Smallest Memory Footprint
Do not compete 137 0 0 Times tool wins 265 37
Error detected 2 0 0   Shortest Execution Time
Cannot Compute + Time-out 0 236 0 Times tool wins 257 45


On the chart below, denote cases where the two tools did computed a result, denote the cases where at least one tool did not competed, denote the cases where at least one tool did a mistake and denote the cases where at least one tool stated it could not compute a result or timed-out.

memory chart time chart

LoLA2.0 versus TAPAAL(MC)

Some statistics are displayed below, based on 808 runs (404 for LoLA2.0 and 404 for TAPAAL(MC), so there are 404 plots on each of the two charts). Each execution was allowed 1 hour and 16 GByte of memory. Then performance charts comparing LoLA2.0 to TAPAAL(MC) are shown (you may click on one graph to enlarge it).

Statistics on the execution
  LoLA2.0 TAPAAL(MC) Both tools   LoLA2.0 TAPAAL(MC)
Computed OK 29 2 236   Smallest Memory Footprint
Do not compete 0 0 137 Times tool wins 254 13
Error detected 2 1 0   Shortest Execution Time
Cannot Compute + Time-out 0 28 0 Times tool wins 238 29


On the chart below, denote cases where the two tools did computed a result, denote the cases where at least one tool did not competed, denote the cases where at least one tool did a mistake and denote the cases where at least one tool stated it could not compute a result or timed-out.

memory chart time chart

LoLA2.0 versus TAPAAL(SEQ)

Some statistics are displayed below, based on 808 runs (404 for LoLA2.0 and 404 for TAPAAL(SEQ), so there are 404 plots on each of the two charts). Each execution was allowed 1 hour and 16 GByte of memory. Then performance charts comparing LoLA2.0 to TAPAAL(SEQ) are shown (you may click on one graph to enlarge it).

Statistics on the execution
  LoLA2.0 TAPAAL(SEQ) Both tools   LoLA2.0 TAPAAL(SEQ)
Computed OK 6 2 259   Smallest Memory Footprint
Do not compete 0 0 137 Times tool wins 183 84
Error detected 2 0 0   Shortest Execution Time
Cannot Compute + Time-out 0 6 0 Times tool wins 248 19


On the chart below, denote cases where the two tools did computed a result, denote the cases where at least one tool did not competed, denote the cases where at least one tool did a mistake and denote the cases where at least one tool stated it could not compute a result or timed-out.

memory chart time chart

LoLA2.0 versus TAPAAL-OTF(PAR)

Some statistics are displayed below, based on 808 runs (404 for LoLA2.0 and 404 for TAPAAL-OTF(PAR), so there are 404 plots on each of the two charts). Each execution was allowed 1 hour and 16 GByte of memory. Then performance charts comparing LoLA2.0 to TAPAAL-OTF(PAR) are shown (you may click on one graph to enlarge it).

Statistics on the execution
  LoLA2.0 TAPAAL-OTF(PAR) Both tools   LoLA2.0 TAPAAL-OTF(PAR)
Computed OK 143 0 122   Smallest Memory Footprint
Do not compete 0 0 137 Times tool wins 235 30
Error detected 2 7 0   Shortest Execution Time
Cannot Compute + Time-out 0 138 0 Times tool wins 261 4


On the chart below, denote cases where the two tools did computed a result, denote the cases where at least one tool did not competed, denote the cases where at least one tool did a mistake and denote the cases where at least one tool stated it could not compute a result or timed-out.

memory chart time chart

LoLA2.0 versus TAPAAL-OTF(SEQ)

Some statistics are displayed below, based on 808 runs (404 for LoLA2.0 and 404 for TAPAAL-OTF(SEQ), so there are 404 plots on each of the two charts). Each execution was allowed 1 hour and 16 GByte of memory. Then performance charts comparing LoLA2.0 to TAPAAL-OTF(SEQ) are shown (you may click on one graph to enlarge it).

Statistics on the execution
  LoLA2.0 TAPAAL-OTF(SEQ) Both tools   LoLA2.0 TAPAAL-OTF(SEQ)
Computed OK 117 0 148   Smallest Memory Footprint
Do not compete 0 0 137 Times tool wins 254 11
Error detected 2 0 0   Shortest Execution Time
Cannot Compute + Time-out 0 119 0 Times tool wins 251 14


On the chart below, denote cases where the two tools did computed a result, denote the cases where at least one tool did not competed, denote the cases where at least one tool did a mistake and denote the cases where at least one tool stated it could not compute a result or timed-out.

memory chart time chart