Introduction
This page presents how LTSMin do cope efficiently with the StateSpace 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 LoLA
Some statistics are displayed below, based on 866 runs (433 for LTSMin and 433 for LoLA, so there are 433 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 | 115 | 0 | 0 | Smallest Memory Footprint | ||
| Do not compete | 10 | 313 | 110 | Times tool wins | 115 | 0 |
| Error detected | 0 | 0 | 0 | Shortest Execution Time | ||
| Cannot Compute + Time-out | 198 | 10 | 0 | Times tool wins | 115 | 0 |
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
Some statistics are displayed below, based on 866 runs (433 for LTSMin and 433 for Tapaal, so there are 433 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 are shown (you may click on one graph to enlarge it).
| Statistics on the execution | ||||||
| LTSMin | Tapaal | Both tools | LTSMin | Tapaal | ||
| Computed OK | 48 | 5 | 67 | Smallest Memory Footprint | ||
| Do not compete | 0 | 0 | 120 | Times tool wins | 59 | 61 |
| Error detected | 0 | 0 | 0 | Shortest Execution Time | ||
| Cannot Compute + Time-out | 5 | 48 | 193 | Times tool wins | 69 | 51 |
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 ITS-Tools
Some statistics are displayed below, based on 866 runs (433 for LTSMin and 433 for ITS-Tools, so there are 433 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 | 10 | 59 | 105 | Smallest Memory Footprint | ||
| Do not compete | 120 | 0 | 0 | Times tool wins | 30 | 144 |
| Error detected | 0 | 1 | 0 | Shortest Execution Time | ||
| Cannot Compute + Time-out | 27 | 97 | 171 | Times tool wins | 50 | 124 |
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 MARCIE
Some statistics are displayed below, based on 866 runs (433 for LTSMin and 433 for MARCIE, so there are 433 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 | 10 | 67 | 105 | Smallest Memory Footprint | ||
| Do not compete | 120 | 0 | 0 | Times tool wins | 55 | 127 |
| Error detected | 0 | 2 | 0 | Shortest Execution Time | ||
| Cannot Compute + Time-out | 38 | 99 | 160 | Times tool wins | 68 | 114 |
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 GreatSPN
Some statistics are displayed below, based on 866 runs (433 for LTSMin and 433 for GreatSPN, so there are 433 plots on each of the two charts). Each execution was allowed 1 hour and 16 GByte of memory. Then performance charts comparing LTSMin to GreatSPN are shown (you may click on one graph to enlarge it).
| Statistics on the execution | ||||||
| LTSMin | GreatSPN | Both tools | LTSMin | GreatSPN | ||
| Computed OK | 11 | 100 | 104 | Smallest Memory Footprint | ||
| Do not compete | 120 | 0 | 0 | Times tool wins | 30 | 185 |
| Error detected | 0 | 0 | 0 | Shortest Execution Time | ||
| Cannot Compute + Time-out | 60 | 91 | 138 | Times tool wins | 43 | 172 |
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 smart
Some statistics are displayed below, based on 866 runs (433 for LTSMin and 433 for smart, so there are 433 plots on each of the two charts). Each execution was allowed 1 hour and 16 GByte of memory. Then performance charts comparing LTSMin to smart are shown (you may click on one graph to enlarge it).
| Statistics on the execution | ||||||
| LTSMin | smart | Both tools | LTSMin | smart | ||
| Computed OK | 44 | 31 | 71 | Smallest Memory Footprint | ||
| Do not compete | 0 | 0 | 120 | Times tool wins | 44 | 102 |
| Error detected | 0 | 21 | 0 | Shortest Execution Time | ||
| Cannot Compute + Time-out | 31 | 23 | 167 | Times tool wins | 63 | 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.
LTSMin versus TINA.tedd
Some statistics are displayed below, based on 866 runs (433 for LTSMin and 433 for TINA.tedd, so there are 433 plots on each of the two charts). Each execution was allowed 1 hour and 16 GByte of memory. Then performance charts comparing LTSMin to TINA.tedd are shown (you may click on one graph to enlarge it).
| Statistics on the execution | ||||||
| LTSMin | TINA.tedd | Both tools | LTSMin | TINA.tedd | ||
| Computed OK | 7 | 74 | 108 | Smallest Memory Footprint | ||
| Do not compete | 120 | 0 | 0 | Times tool wins | 51 | 138 |
| Error detected | 0 | 0 | 0 | Shortest Execution Time | ||
| Cannot Compute + Time-out | 43 | 96 | 155 | Times tool wins | 41 | 148 |
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 TINA.sift
Some statistics are displayed below, based on 866 runs (433 for LTSMin and 433 for TINA.sift, so there are 433 plots on each of the two charts). Each execution was allowed 1 hour and 16 GByte of memory. Then performance charts comparing LTSMin to TINA.sift are shown (you may click on one graph to enlarge it).
| Statistics on the execution | ||||||
| LTSMin | TINA.sift | Both tools | LTSMin | TINA.sift | ||
| Computed OK | 56 | 26 | 59 | Smallest Memory Footprint | ||
| Do not compete | 120 | 0 | 0 | Times tool wins | 68 | 73 |
| Error detected | 0 | 2 | 0 | Shortest Execution Time | ||
| Cannot Compute + Time-out | 4 | 152 | 194 | Times tool wins | 72 | 69 |
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.
