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

Introduction

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

Some statistics are displayed below, based on 866 runs (433 for LTSMin and 433 for LoLA, 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 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 1 111 312   Smallest Memory Footprint
Do not compete 120 0 0 Times tool wins 125 299
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 0 10 0 Times tool wins 57 367


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 866 runs (433 for LTSMin 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 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 5 0 308   Smallest Memory Footprint
Do not compete 0 0 120 Times tool wins 107 206
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 0 5 0 Times tool wins 216 97


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 866 runs (433 for LTSMin 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 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 200 29 113   Smallest Memory Footprint
Do not compete 120 0 0 Times tool wins 214 128
Error detected 0 1 0   Shortest Execution Time
Cannot Compute + Time-out 0 290 0 Times tool wins 248 94


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 866 runs (433 for LTSMin 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 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 177 26 136   Smallest Memory Footprint
Do not compete 120 0 0 Times tool wins 210 129
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 0 271 0 Times tool wins 249 90


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 866 runs (433 for LTSMin 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 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 242 22 71   Smallest Memory Footprint
Do not compete 120 0 0 Times tool wins 242 93
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 0 340 0 Times tool wins 249 86


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