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

Introduction

This page presents how LTSMin do cope efficiently with the ReachabilityCardinality 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 LoLA

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

Statistics on the execution
  LTSMin LoLA Both tools   LTSMin LoLA
Computed OK 0 16 137   Smallest Memory Footprint
Do not compete 16 0 0 Times tool wins 9 144
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 0 0 0 Times tool wins 4 149


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

LTSMin versus Tapaal

Some statistics are displayed below, based on 306 runs (153 for LTSMin and 153 for Tapaal, so there are 153 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 are shown (you may click on one graph to enlarge it).

Statistics on the execution
  LTSMin Tapaal Both tools   LTSMin Tapaal
Computed OK 0 0 137   Smallest Memory Footprint
Do not compete 0 0 16 Times tool wins 22 115
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 0 0 0 Times tool wins 42 95


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

LTSMin versus ITS-Tools

Some statistics are displayed below, based on 306 runs (153 for LTSMin and 153 for ITS-Tools, so there are 153 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 29 8 108   Smallest Memory Footprint
Do not compete 16 0 0 Times tool wins 50 95
Error detected 0 11 0   Shortest Execution Time
Cannot Compute + Time-out 0 26 0 Times tool wins 68 77


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

LTSMin versus MARCIE

Some statistics are displayed below, based on 306 runs (153 for LTSMin and 153 for MARCIE, so there are 153 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 84 3 53   Smallest Memory Footprint
Do not compete 16 0 0 Times tool wins 106 34
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 0 97 0 Times tool wins 129 11


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

LTSMin versus GreatSPN

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

Statistics on the execution
  LTSMin GreatSPN Both tools   LTSMin GreatSPN
Computed OK 99 7 38   Smallest Memory Footprint
Do not compete 16 0 0 Times tool wins 104 40
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 0 108 0 Times tool wins 116 28


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