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

Introduction

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

LTSMin versus GreatSPN-Meddly

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

Statistics on the execution
  LTSMin GreatSPN-Meddly Both tools   LTSMin GreatSPN-Meddly
Computed OK 0 121 0   Smallest Memory Footprint
Do not compete 266 114 0 Times tool wins 0 121
Error detected 0 28 0   Shortest Execution Time
Cannot Compute + Time-out 114 117 24 Times tool wins 0 121


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

LTSMin versus LoLA2.0

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

Statistics on the execution
  LTSMin LoLA2.0 Both tools   LTSMin LoLA2.0
Computed OK 0 267 0   Smallest Memory Footprint
Do not compete 266 137 0 Times tool wins 0 267
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 138 0 0 Times tool wins 0 267


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

LTSMin versus Marcie

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

Statistics on the execution
  LTSMin Marcie Both tools   LTSMin Marcie
Computed OK 0 153 0   Smallest Memory Footprint
Do not compete 266 0 0 Times tool wins 0 153
Error detected 0 23 0   Shortest Execution Time
Cannot Compute + Time-out 36 126 102 Times tool wins 0 153


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

LTSMin versus TAPAAL(MC)

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

Statistics on the execution
  LTSMin TAPAAL(MC) Both tools   LTSMin TAPAAL(MC)
Computed OK 0 80 0   Smallest Memory Footprint
Do not compete 266 137 0 Times tool wins 0 80
Error detected 0 1 0   Shortest Execution Time
Cannot Compute + Time-out 137 185 1 Times tool wins 0 80


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

LTSMin versus TAPAAL(SEQ)

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

Statistics on the execution
  LTSMin TAPAAL(SEQ) Both tools   LTSMin TAPAAL(SEQ)
Computed OK 0 262 0   Smallest Memory Footprint
Do not compete 266 137 0 Times tool wins 0 262
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 137 4 1 Times tool wins 0 262


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

LTSMin versus TAPAAL-OTF(PAR)

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

Statistics on the execution
  LTSMin TAPAAL-OTF(PAR) Both tools   LTSMin TAPAAL-OTF(PAR)
Computed OK 0 61 0   Smallest Memory Footprint
Do not compete 266 137 0 Times tool wins 0 61
Error detected 0 26 0   Shortest Execution Time
Cannot Compute + Time-out 137 179 1 Times tool wins 0 61


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

LTSMin versus TAPAAL-OTF(SEQ)

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

Statistics on the execution
  LTSMin TAPAAL-OTF(SEQ) Both tools   LTSMin TAPAAL-OTF(SEQ)
Computed OK 0 93 0   Smallest Memory Footprint
Do not compete 266 137 0 Times tool wins 0 93
Error detected 0 64 0   Shortest Execution Time
Cannot Compute + Time-out 137 109 1 Times tool wins 0 93


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