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

Introduction

This page presents how LTSMin do cope efficiently with the ReachabilityCardinality 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 128 62 21   Smallest Memory Footprint
Do not compete 0 114 0 Times tool wins 130 81
Error detected 102 35 13   Shortest Execution Time
Cannot Compute + Time-out 114 133 26 Times tool wins 130 81


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 ITS-Tools

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

Statistics on the execution
  LTSMin ITS-Tools Both tools   LTSMin ITS-Tools
Computed OK 61 136 88   Smallest Memory Footprint
Do not compete 0 0 0 Times tool wins 113 172
Error detected 41 51 74   Shortest Execution Time
Cannot Compute + Time-out 111 26 29 Times tool wins 80 205


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 10 112 139   Smallest Memory Footprint
Do not compete 0 137 0 Times tool wins 33 228
Error detected 109 10 6   Shortest Execution Time
Cannot Compute + Time-out 140 0 0 Times tool wins 35 226


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 137 61 12   Smallest Memory Footprint
Do not compete 0 0 0 Times tool wins 144 66
Error detected 97 18 18   Shortest Execution Time
Cannot Compute + Time-out 30 185 110 Times tool wins 149 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(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 24 111 125   Smallest Memory Footprint
Do not compete 0 137 0 Times tool wins 69 191
Error detected 114 3 1   Shortest Execution Time
Cannot Compute + Time-out 137 24 3 Times tool wins 57 203


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 5 116 144   Smallest Memory Footprint
Do not compete 0 137 0 Times tool wins 35 230
Error detected 114 1 1   Shortest Execution Time
Cannot Compute + Time-out 139 4 1 Times tool wins 69 196


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 140 54 9   Smallest Memory Footprint
Do not compete 0 137 0 Times tool wins 141 62
Error detected 104 13 11   Shortest Execution Time
Cannot Compute + Time-out 137 177 3 Times tool wins 144 59


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 101 91 48   Smallest Memory Footprint
Do not compete 0 137 0 Times tool wins 104 136
Error detected 115 0 0   Shortest Execution Time
Cannot Compute + Time-out 137 125 3 Times tool wins 117 123


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