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

Introduction

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

Some statistics are displayed below, based on 278 runs (139 for LTSMin and 139 for ITS-Tools, so there are 139 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 92 0 38   Smallest Memory Footprint
Do not compete 9 0 0 Times tool wins 99 31
Error detected 0 3 0   Shortest Execution Time
Cannot Compute + Time-out 0 98 0 Times tool wins 119 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 LoLa

Some statistics are displayed below, based on 278 runs (139 for LTSMin and 139 for LoLa, so there are 139 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 0 129   Smallest Memory Footprint
Do not compete 0 0 9 Times tool wins 57 73
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 0 1 0 Times tool wins 49 81


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 278 runs (139 for LTSMin and 139 for Tapaal(PAR), so there are 139 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 90 0 40   Smallest Memory Footprint
Do not compete 0 0 9 Times tool wins 105 25
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 0 90 0 Times tool wins 121 9


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 278 runs (139 for LTSMin and 139 for Marcie, so there are 139 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 63 6 67   Smallest Memory Footprint
Do not compete 9 0 0 Times tool wins 83 53
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 0 66 0 Times tool wins 109 27


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 278 runs (139 for LTSMin and 139 for Tapaal(SEQ), so there are 139 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 0 125   Smallest Memory Footprint
Do not compete 0 0 9 Times tool wins 61 69
Error detected 0 2 0   Shortest Execution Time
Cannot Compute + Time-out 0 3 0 Times tool wins 100 30


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