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

Introduction

This page presents how LTSMin do cope efficiently with the ReachabilityFireabilitySimple examination face to the other participating tools. In this page, we consider «Surprise» 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 Cunf

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

Statistics on the execution
  LTSMin Cunf Both tools   LTSMin Cunf
Computed OK 85 0 9   Smallest Memory Footprint
Do not compete 0 98 0 Times tool wins 85 9
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 27 14 0 Times tool wins 87 7


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 GreatSPN-Meddly

Some statistics are displayed below, based on 242 runs (121 for LTSMin and 121 for GreatSPN-Meddly, so there are 121 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 79 0 15   Smallest Memory Footprint
Do not compete 0 0 0 Times tool wins 83 11
Error detected 0 23 0   Shortest Execution Time
Cannot Compute + Time-out 0 56 27 Times tool wins 88 6


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 242 runs (121 for LTSMin and 121 for ITS-Tools, so there are 121 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 25 24 69   Smallest Memory Footprint
Do not compete 0 0 0 Times tool wins 65 53
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 24 25 3 Times tool wins 76 42


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 242 runs (121 for LTSMin and 121 for LoLA2.0, so there are 121 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 1 0 93   Smallest Memory Footprint
Do not compete 0 27 0 Times tool wins 4 90
Error detected 0 1 0   Shortest Execution Time
Cannot Compute + Time-out 27 0 0 Times tool wins 12 82


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 242 runs (121 for LTSMin and 121 for Marcie, so there are 121 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 36 14 58   Smallest Memory Footprint
Do not compete 0 0 0 Times tool wins 74 34
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 14 36 13 Times tool wins 83 25


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 242 runs (121 for LTSMin and 121 for TAPAAL(MC), so there are 121 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 4 0 90   Smallest Memory Footprint
Do not compete 0 27 0 Times tool wins 38 56
Error detected 0 1 0   Shortest Execution Time
Cannot Compute + Time-out 27 3 0 Times tool wins 28 66


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 242 runs (121 for LTSMin and 121 for TAPAAL(SEQ), so there are 121 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 0 94   Smallest Memory Footprint
Do not compete 0 27 0 Times tool wins 22 72
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 27 0 0 Times tool wins 39 55


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 242 runs (121 for LTSMin and 121 for TAPAAL-OTF(PAR), so there are 121 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 36 0 58   Smallest Memory Footprint
Do not compete 0 27 0 Times tool wins 36 58
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 27 36 0 Times tool wins 46 48


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 242 runs (121 for LTSMin and 121 for TAPAAL-OTF(SEQ), so there are 121 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 28 0 66   Smallest Memory Footprint
Do not compete 0 27 0 Times tool wins 36 58
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 27 28 0 Times tool wins 45 49


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