# Introduction

This page presents how Tapaal do cope efficiently with the StateSpace examination face to the other participating tools. In this page, we consider «Known» 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 Tapaal' 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).

# Tapaal versus GreatSPN

Some statistics are displayed below, based on 2458 runs (1229 for Tapaal and 1229 for GreatSPN, so there are 1229 plots on each of the two charts). Each execution was allowed 1 hour and 16 GByte of memory. Then performance charts comparing Tapaal to GreatSPN are shown (you may click on one graph to enlarge it).

Statistics on the executions | ||||||

Tapaal | GreatSPN | Both tools | Tapaal | GreatSPN | ||

All computed OK | 5 | 493 | 0 | Smallest Memory Footprint | ||

Tapaal = GreatSPN | — | — | 2 | Times tool wins | 129 | 618 |

Tapaal > GreatSPN | — | — | 0 | Shortest Execution Time | ||

Tapaal < GreatSPN | — | — | 247 | Times tool wins | 113 | 634 |

Do not compete | 0 | 0 | 0 | |||

Error detected | 9 | 0 | 0 | |||

Cannot Compute + Time-out | 485 | 6 | 481 |

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 Tapaal
computed more values than GreatSPN,
denote cases where Tapaal
computed less values than GreatSPN,
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.

Tapaal wins when points are below the diagonal, GreatSPN wins when points are above the diagonal.

# Tapaal versus ITS-Tools

Some statistics are displayed below, based on 2458 runs (1229 for Tapaal and 1229 for ITS-Tools, so there are 1229 plots on each of the two charts). Each execution was allowed 1 hour and 16 GByte of memory. Then performance charts comparing Tapaal to ITS-Tools are shown (you may click on one graph to enlarge it).

Statistics on the executions | ||||||

Tapaal | ITS-Tools | Both tools | Tapaal | ITS-Tools | ||

All computed OK | 8 | 487 | 0 | Smallest Memory Footprint | ||

Tapaal = ITS-Tools | — | — | 246 | Times tool wins | 210 | 531 |

Tapaal > ITS-Tools | — | — | 0 | Shortest Execution Time | ||

Tapaal < ITS-Tools | — | — | 0 | Times tool wins | 167 | 574 |

Do not compete | 0 | 0 | 0 | |||

Error detected | 9 | 0 | 0 | |||

Cannot Compute + Time-out | 478 | 8 | 488 |

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 Tapaal
computed more values than ITS-Tools,
denote cases where Tapaal
computed less values than ITS-Tools,
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.

Tapaal wins when points are below the diagonal, ITS-Tools wins when points are above the diagonal.

# Tapaal versus tedd

Some statistics are displayed below, based on 2458 runs (1229 for Tapaal and 1229 for tedd, so there are 1229 plots on each of the two charts). Each execution was allowed 1 hour and 16 GByte of memory. Then performance charts comparing Tapaal to tedd are shown (you may click on one graph to enlarge it).

Statistics on the executions | ||||||

Tapaal | tedd | Both tools | Tapaal | tedd | ||

All computed OK | 7 | 570 | 0 | Smallest Memory Footprint | ||

Tapaal = tedd | — | — | 0 | Times tool wins | 228 | 596 |

Tapaal > tedd | — | — | 0 | Shortest Execution Time | ||

Tapaal < tedd | — | — | 247 | Times tool wins | 155 | 669 |

Do not compete | 0 | 0 | 0 | |||

Error detected | 9 | 0 | 0 | |||

Cannot Compute + Time-out | 561 | 7 | 405 |

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 Tapaal
computed more values than tedd,
denote cases where Tapaal
computed less values than tedd,
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.

Tapaal wins when points are below the diagonal, tedd wins when points are above the diagonal.

# Tapaal versus 2020-gold

Some statistics are displayed below, based on 2458 runs (1229 for Tapaal and 1229 for 2020-gold, so there are 1229 plots on each of the two charts). Each execution was allowed 1 hour and 16 GByte of memory. Then performance charts comparing Tapaal to 2020-gold are shown (you may click on one graph to enlarge it).

Statistics on the executions | ||||||

Tapaal | 2020-gold | Both tools | Tapaal | 2020-gold | ||

All computed OK | 7 | 556 | 0 | Smallest Memory Footprint | ||

Tapaal = 2020-gold | — | — | 0 | Times tool wins | 234 | 576 |

Tapaal > 2020-gold | — | — | 0 | Shortest Execution Time | ||

Tapaal < 2020-gold | — | — | 247 | Times tool wins | 158 | 652 |

Do not compete | 0 | 0 | 0 | |||

Error detected | 9 | 0 | 0 | |||

Cannot Compute + Time-out | 547 | 7 | 419 |

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 Tapaal
computed more values than 2020-gold,
denote cases where Tapaal
computed less values than 2020-gold,
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.

Tapaal wins when points are below the diagonal, 2020-gold wins when points are above the diagonal.

# Tapaal versus BVT-2021

Some statistics are displayed below, based on 2458 runs (1229 for Tapaal and 1229 for BVT-2021, so there are 1229 plots on each of the two charts). Each execution was allowed 1 hour and 16 GByte of memory. Then performance charts comparing Tapaal to BVT-2021 are shown (you may click on one graph to enlarge it).

Important: here, Tapaal is compared to BVT-2021. It is a good way to check how Tapaal compete in terms of resource consomption with the best tools (even virtual). When Tapaal is best, the corresponding plots are on the diagonal of the scatter plots chart.

Statistics on the executions | ||||||

Tapaal | BVT-2021 | Both tools | Tapaal | BVT-2021 | ||

All computed OK | 0 | 617 | 0 | Smallest Memory Footprint | ||

Tapaal = BVT-2021 | — | — | 6 | Times tool wins | 0 | 871 |

Tapaal > BVT-2021 | — | — | 0 | Shortest Execution Time | ||

Tapaal < BVT-2021 | — | — | 248 | Times tool wins | 0 | 871 |

Do not compete | 0 | 358 | 0 | |||

Error detected | 9 | 0 | 0 | |||

Cannot Compute + Time-out | 966 | 0 | 0 |

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 Tapaal
computed more values than BVT-2021,
denote cases where Tapaal
computed less values than BVT-2021,
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.

Tapaal wins when points are below the diagonal, BVT-2021 wins when points are above the diagonal.