fond
Model Checking Contest @ Petri Nets 2017
7th edition, Zaragoza, Spain, June 27, 2017
ITS-Tools compared to other tools («Known» models, StateSpace)
Last Updated
June 27, 2017

Introduction

This page presents how LoLA do cope efficiently with the StateSpace 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 LoLA' 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).

LoLA versus LTSMin

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

Statistics on the execution
  LoLA LTSMin Both tools   LoLA LTSMin
Computed OK 0 115 0   Smallest Memory Footprint
Do not compete 313 9 111 Times tool wins 0 115
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 9 198 0 Times tool wins 0 115


On the chart below, denote cases where the two tools did computed a result without error, 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.

memory chart time chart

LoLA versus Tapaal

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

Statistics on the execution
  LoLA Tapaal Both tools   LoLA Tapaal
Computed OK 0 71 0   Smallest Memory Footprint
Do not compete 313 9 111 Times tool wins 0 71
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 9 242 0 Times tool wins 0 71


On the chart below, denote cases where the two tools did computed a result without error, 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.

memory chart time chart

LoLA versus ITS-Tools

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

Statistics on the execution
  LoLA ITS-Tools Both tools   LoLA ITS-Tools
Computed OK 0 173 0   Smallest Memory Footprint
Do not compete 424 0 0 Times tool wins 0 173
Error detected 0 2 0   Shortest Execution Time
Cannot Compute + Time-out 2 251 7 Times tool wins 0 173


On the chart below, denote cases where the two tools did computed a result without error, 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.

memory chart time chart

LoLA versus MARCIE

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

Statistics on the execution
  LoLA MARCIE Both tools   LoLA MARCIE
Computed OK 0 173 0   Smallest Memory Footprint
Do not compete 424 0 0 Times tool wins 0 173
Error detected 0 2 0   Shortest Execution Time
Cannot Compute + Time-out 0 249 9 Times tool wins 0 173


On the chart below, denote cases where the two tools did computed a result without error, 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.

memory chart time chart

LoLA versus GreatSPN

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

Statistics on the execution
  LoLA GreatSPN Both tools   LoLA GreatSPN
Computed OK 0 207 0   Smallest Memory Footprint
Do not compete 424 0 0 Times tool wins 0 207
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 0 217 9 Times tool wins 0 207


On the chart below, denote cases where the two tools did computed a result without error, 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.

memory chart time chart

LoLA versus smart

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

Statistics on the execution
  LoLA smart Both tools   LoLA smart
Computed OK 0 99 0   Smallest Memory Footprint
Do not compete 313 9 111 Times tool wins 0 99
Error detected 0 23 0   Shortest Execution Time
Cannot Compute + Time-out 9 191 0 Times tool wins 0 99


On the chart below, denote cases where the two tools did computed a result without error, 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.

memory chart time chart

LoLA versus TINA.tedd

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

Statistics on the execution
  LoLA TINA.tedd Both tools   LoLA TINA.tedd
Computed OK 0 194 0   Smallest Memory Footprint
Do not compete 419 4 5 Times tool wins 0 194
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 5 226 4 Times tool wins 0 194


On the chart below, denote cases where the two tools did computed a result without error, 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.

memory chart time chart

LoLA versus TINA.sift

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

Statistics on the execution
  LoLA TINA.sift Both tools   LoLA TINA.sift
Computed OK 0 89 0   Smallest Memory Footprint
Do not compete 419 4 5 Times tool wins 0 89
Error detected 0 2 0   Shortest Execution Time
Cannot Compute + Time-out 5 329 4 Times tool wins 0 89


On the chart below, denote cases where the two tools did computed a result without error, 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.

memory chart time chart