Introduction
This page presents how LTSMin do cope efficiently with the ReachabilityDeadlock examination face to the other participating tools. In this page, we consider «Stripped» 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 | 51 | 106 | 134 | Smallest Memory Footprint | ||
| Do not compete | 164 | 0 | 0 | Times tool wins | 70 | 221 |
| Error detected | 0 | 6 | 0 | Shortest Execution Time | ||
| Cannot Compute + Time-out | 50 | 153 | 126 | Times tool wins | 108 | 183 |
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.
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 | 1 | 175 | 184 | Smallest Memory Footprint | ||
| Do not compete | 0 | 0 | 164 | Times tool wins | 24 | 336 |
| Error detected | 0 | 0 | 0 | Shortest Execution Time | ||
| Cannot Compute + Time-out | 175 | 1 | 1 | Times tool wins | 37 | 323 |
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.
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 | 89 | 10 | 96 | Smallest Memory Footprint | ||
| Do not compete | 0 | 0 | 164 | Times tool wins | 104 | 91 |
| Error detected | 0 | 0 | 0 | Shortest Execution Time | ||
| Cannot Compute + Time-out | 10 | 89 | 166 | Times tool wins | 123 | 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.
_ReachabilityDeadlock.png)
_ReachabilityDeadlock.png)
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 | 44 | 102 | 141 | Smallest Memory Footprint | ||
| Do not compete | 164 | 0 | 0 | Times tool wins | 100 | 187 |
| Error detected | 0 | 0 | 0 | Shortest Execution Time | ||
| Cannot Compute + Time-out | 56 | 162 | 120 | Times tool wins | 99 | 188 |
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.
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 | 11 | 164 | 174 | Smallest Memory Footprint | ||
| Do not compete | 0 | 0 | 164 | Times tool wins | 37 | 312 |
| Error detected | 0 | 0 | 0 | Shortest Execution Time | ||
| Cannot Compute + Time-out | 164 | 11 | 12 | Times tool wins | 83 | 266 |
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.
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 | 26 | 93 | 159 | Smallest Memory Footprint | ||
| Do not compete | 0 | 0 | 164 | Times tool wins | 27 | 251 |
| Error detected | 0 | 0 | 0 | Shortest Execution Time | ||
| Cannot Compute + Time-out | 93 | 26 | 83 | Times tool wins | 32 | 246 |
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.
_ReachabilityDeadlock.png)
_ReachabilityDeadlock.png)
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 | 30 | 87 | 155 | Smallest Memory Footprint | ||
| Do not compete | 0 | 0 | 164 | Times tool wins | 38 | 234 |
| Error detected | 0 | 0 | 0 | Shortest Execution Time | ||
| Cannot Compute + Time-out | 87 | 30 | 89 | Times tool wins | 65 | 207 |
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.
_ReachabilityDeadlock.png)
_ReachabilityDeadlock.png)