fond
Model Checking Contest @ Petri Nets 2016
6th edition, Toruń, Poland, June 21, 2016
ITS-Tools compared to other tools («Known» models, ReachabilityFireability)
Last Updated
June 30, 2016

Introduction

This page presents how LTSMin do cope efficiently with the ReachabilityFireability 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 ITS-Tools

Some statistics are displayed below, based on 1050 runs (525 for LTSMin and 525 for ITS-Tools, so there are 525 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 148 64 213   Smallest Memory Footprint
Do not compete 164 0 0 Times tool wins 177 248
Error detected 0 14 0   Shortest Execution Time
Cannot Compute + Time-out 0 234 0 Times tool wins 196 229


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 LoLa

Some statistics are displayed below, based on 1050 runs (525 for LTSMin and 525 for LoLa, so there are 525 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 0 361   Smallest Memory Footprint
Do not compete 0 0 164 Times tool wins 42 319
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 0 0 0 Times tool wins 31 330


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(PAR)

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

Statistics on the execution
  LTSMin Tapaal(PAR) Both tools   LTSMin Tapaal(PAR)
Computed OK 70 0 291   Smallest Memory Footprint
Do not compete 0 0 164 Times tool wins 118 243
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 0 70 0 Times tool wins 200 161


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 1050 runs (525 for LTSMin and 525 for Marcie, so there are 525 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 175 48 186   Smallest Memory Footprint
Do not compete 164 0 0 Times tool wins 247 162
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 0 291 0 Times tool wins 277 132


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 PeCan

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

Statistics on the execution
  LTSMin PeCan Both tools   LTSMin PeCan
Computed OK 224 0 137   Smallest Memory Footprint
Do not compete 0 0 164 Times tool wins 233 128
Error detected 0 120 0   Shortest Execution Time
Cannot Compute + Time-out 0 104 0 Times tool wins 246 115


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(EXP)

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

Statistics on the execution
  LTSMin Tapaal(EXP) Both tools   LTSMin Tapaal(EXP)
Computed OK 2 0 359   Smallest Memory Footprint
Do not compete 0 0 164 Times tool wins 34 327
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 0 2 0 Times tool wins 182 179


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(SEQ)

Some statistics are displayed below, based on 1050 runs (525 for LTSMin and 525 for Tapaal(SEQ), so there are 525 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 42 0 319   Smallest Memory Footprint
Do not compete 0 0 164 Times tool wins 108 253
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 0 42 0 Times tool wins 195 166


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