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

Introduction

This page presents how Marcie do cope efficiently with the ReachabilityDeadlock 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 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 1050 runs (525 for Marcie 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 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 29 24 216   Smallest Memory Footprint
Do not compete 0 0 0 Times tool wins 35 234
Error detected 0 6 0   Shortest Execution Time
Cannot Compute + Time-out 26 25 254 Times tool wins 94 175


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 1050 runs (525 for Marcie 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 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 48 164 197   Smallest Memory Footprint
Do not compete 0 164 0 Times tool wins 61 348
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 280 0 0 Times tool wins 67 342


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 1050 runs (525 for Marcie and 525 for LTSMin, 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 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 104 42 141   Smallest Memory Footprint
Do not compete 0 164 0 Times tool wins 189 98
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 158 56 122 Times tool wins 189 98


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 1050 runs (525 for Marcie 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 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 164 25 81   Smallest Memory Footprint
Do not compete 0 164 0 Times tool wins 164 106
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 141 116 139 Times tool wins 185 85


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 1050 runs (525 for Marcie 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 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 53 147 192   Smallest Memory Footprint
Do not compete 0 164 0 Times tool wins 53 339
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 263 5 17 Times tool wins 127 265


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 1050 runs (525 for Marcie 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 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 105 112 140   Smallest Memory Footprint
Do not compete 0 164 0 Times tool wins 105 252
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 228 57 52 Times tool wins 118 239


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 1050 runs (525 for Marcie 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 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 112 111 133   Smallest Memory Footprint
Do not compete 0 164 0 Times tool wins 116 240
Error detected 0 0 0   Shortest Execution Time
Cannot Compute + Time-out 227 64 53 Times tool wins 146 210


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