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

Introduction

This page presents how Marcie 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 Marcie' 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).

Marcie versus ITS-Tools

Some statistics are displayed below, based on 278 runs (139 for Marcie 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 Marcie to ITS-Tools are shown (you may click on one graph to enlarge it).

Statistics on the execution
  Marcie ITS-Tools Both tools   Marcie ITS-Tools
Computed OK 24 12 51   Smallest Memory Footprint
Do not compete 0 0 0 Times tool wins 26 61
Error detected 0 3 0   Shortest Execution Time
Cannot Compute + Time-out 14 23 50 Times tool wins 31 56


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

Marcie versus LoLa

Some statistics are displayed below, based on 278 runs (139 for Marcie 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 Marcie to LoLa are shown (you may click on one graph to enlarge it).

Statistics on the execution
  Marcie LoLa Both tools   Marcie LoLa
Computed OK 6 60 69   Smallest Memory Footprint
Do not compete 0 9 0 Times tool wins 12 123
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 63 0 1 Times tool wins 20 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

Marcie versus LTSMin

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

Statistics on the execution
  Marcie LTSMin Both tools   Marcie LTSMin
Computed OK 6 61 69   Smallest Memory Footprint
Do not compete 0 9 0 Times tool wins 49 87
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 64 0 0 Times tool wins 19 117


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

Marcie versus Tapaal(PAR)

Some statistics are displayed below, based on 278 runs (139 for Marcie 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 Marcie to Tapaal(PAR) are shown (you may click on one graph to enlarge it).

Statistics on the execution
  Marcie Tapaal(PAR) Both tools   Marcie Tapaal(PAR)
Computed OK 9 42 66   Smallest Memory Footprint
Do not compete 0 9 0 Times tool wins 16 101
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 45 3 19 Times tool wins 50 67


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

Marcie versus PeCan

Some statistics are displayed below, based on 278 runs (139 for Marcie and 139 for PeCan, 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 Marcie to PeCan are shown (you may click on one graph to enlarge it).

Statistics on the execution
  Marcie PeCan Both tools   Marcie PeCan
Computed OK 49 22 26   Smallest Memory Footprint
Do not compete 0 9 0 Times tool wins 49 48
Error detected 0 40 0   Shortest Execution Time
Cannot Compute + Time-out 37 15 27 Times tool wins 53 44


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

Marcie versus Tapaal(EXP)

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

Statistics on the execution
  Marcie Tapaal(EXP) Both tools   Marcie Tapaal(EXP)
Computed OK 6 59 69   Smallest Memory Footprint
Do not compete 0 9 0 Times tool wins 34 100
Error detected 0 2 0   Shortest Execution Time
Cannot Compute + Time-out 64 0 0 Times tool wins 45 89


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

Marcie versus Tapaal(SEQ)

Some statistics are displayed below, based on 278 runs (139 for Marcie 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 Marcie to Tapaal(SEQ) are shown (you may click on one graph to enlarge it).

Statistics on the execution
  Marcie Tapaal(SEQ) Both tools   Marcie Tapaal(SEQ)
Computed OK 6 48 69   Smallest Memory Footprint
Do not compete 0 9 0 Times tool wins 31 92
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 51 0 13 Times tool wins 44 79


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