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

Introduction

This page presents how Marcie do cope efficiently with the ReachabilityFireability 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 22 12 51   Smallest Memory Footprint
Do not compete 0 0 0 Times tool wins 24 61
Error detected 1 2 0   Shortest Execution Time
Cannot Compute + Time-out 13 22 52 Times tool wins 36 49


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 62 67   Smallest Memory Footprint
Do not compete 0 9 0 Times tool wins 12 123
Error detected 1 0 0   Shortest Execution Time
Cannot Compute + Time-out 65 1 0 Times tool wins 22 113


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 63 67   Smallest Memory Footprint
Do not compete 0 9 0 Times tool wins 58 78
Error detected 1 0 0   Shortest Execution Time
Cannot Compute + Time-out 65 0 0 Times tool wins 27 109


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 8 46 65   Smallest Memory Footprint
Do not compete 0 9 0 Times tool wins 14 105
Error detected 1 0 0   Shortest Execution Time
Cannot Compute + Time-out 48 2 17 Times tool wins 47 72


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 63 21 10   Smallest Memory Footprint
Do not compete 0 9 0 Times tool wins 63 31
Error detected 1 43 0   Shortest Execution Time
Cannot Compute + Time-out 33 24 32 Times tool wins 70 24


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 61 67   Smallest Memory Footprint
Do not compete 0 9 0 Times tool wins 18 116
Error detected 0 0 1   Shortest Execution Time
Cannot Compute + Time-out 64 0 1 Times tool wins 34 100


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 7 51 66   Smallest Memory Footprint
Do not compete 0 9 0 Times tool wins 24 100
Error detected 1 0 0   Shortest Execution Time
Cannot Compute + Time-out 53 1 12 Times tool wins 41 83


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