Introduction
This page presents how GreatSPN do cope efficiently with the QuasiLiveness examination face to the other participating tools. In this page, we consider «Surprise» models.
The next sections will show chart comparing performances in terms of both memory and execution time.The x-axis corresponds to the challenging tool where the y-axes represents GreatSPN' performances. Thus, points below the diagonal of a chart denote comparisons favorables to the tool while others 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).
GreatSPN versus Tapaal
Some statistics are displayed below, based on 422 runs (211 for GreatSPN and 211 for Tapaal, so there are 211 plots on each of the two charts). Each execution was allowed 1 hour and 16 GByte of memory. Then performance charts comparing GreatSPN to Tapaal are shown (you may click on one graph to enlarge it).
| Statistics on the executions | ||||||
| GreatSPN | Tapaal | Both tools | GreatSPN | Tapaal | ||
| All computed OK | 23 | 27 | 105 | Smallest Memory Footprint | ||
| GreatSPN = Tapaal | — | — | 0 | Times tool wins | 95 | 60 |
| GreatSPN > Tapaal | — | — | 0 | Shortest Execution Time | ||
| GreatSPN < Tapaal | — | — | 0 | Times tool wins | 71 | 84 |
| Do not compete | 0 | 0 | 0 | |||
| Error detected | 0 | 0 | 0 | |||
| Cannot Compute + Time-out | 27 | 23 | 56 | |||
On the chart below, 
denote cases where
the two tools did computed all results without error,
denote cases where the two tool did computed the
same number of values (but not al values in the examination),
denote cases where GreatSPN
computed more values than Tapaal,
denote cases where GreatSPN
computed less values than Tapaal,
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.
GreatSPN wins when points are below the diagonal, Tapaal wins when points are above the diagonal.
GreatSPN versus smart
Some statistics are displayed below, based on 422 runs (211 for GreatSPN and 211 for smart, so there are 211 plots on each of the two charts). Each execution was allowed 1 hour and 16 GByte of memory. Then performance charts comparing GreatSPN to smart are shown (you may click on one graph to enlarge it).
| Statistics on the executions | ||||||
| GreatSPN | smart | Both tools | GreatSPN | smart | ||
| All computed OK | 26 | 0 | 102 | Smallest Memory Footprint | ||
| GreatSPN = smart | — | — | 0 | Times tool wins | 128 | 0 |
| GreatSPN > smart | — | — | 0 | Shortest Execution Time | ||
| GreatSPN < smart | — | — | 0 | Times tool wins | 116 | 12 |
| Do not compete | 0 | 20 | 0 | |||
| Error detected | 0 | 0 | 0 | |||
| Cannot Compute + Time-out | 14 | 20 | 69 | |||
On the chart below, denote cases where
the two tools did computed all results without error,
denote cases where the two tool did computed the
same number of values (but not al values in the examination),
denote cases where GreatSPN
computed more values than smart,
denote cases where GreatSPN
computed less values than smart,
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.
GreatSPN wins when points are below the diagonal, smart wins when points are above the diagonal.
