Introduction

This page presents how LTSMin 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 terms of 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 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).

LTSMin versus Tapaal

Some statistics are displayed below, based on 1616 runs (808 for LTSMin and 808 for Tapaal, so there are 808 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).

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

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

LTSMin versus LoLA

Some statistics are displayed below, based on 1616 runs (808 for LTSMin and 808 for LoLA, so there are 808 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).

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 LTSMin computed more values than LoLA, denote cases where LTSMin computed less values than LoLA, 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 wins when points are below the diagonal, LoLA wins when points are above the diagonal.

LTSMin versus M4M.full

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

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 LTSMin computed more values than M4M.full, denote cases where LTSMin computed less values than M4M.full, 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 wins when points are below the diagonal, M4M.full wins when points are above the diagonal.

LTSMin versus M4M.struct

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

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 LTSMin computed more values than M4M.struct, denote cases where LTSMin computed less values than M4M.struct, 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 wins when points are below the diagonal, M4M.struct wins when points are above the diagonal.

LTSMin versus ITS-Tools

Some statistics are displayed below, based on 1616 runs (808 for LTSMin and 808 for ITS-Tools, so there are 808 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).

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

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

LTSMin versus ITS-Tools.L

Some statistics are displayed below, based on 1616 runs (808 for LTSMin and 808 for ITS-Tools.L, so there are 808 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.L are shown (you may click on one graph to enlarge it).

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 LTSMin computed more values than ITS-Tools.L, denote cases where LTSMin computed less values than ITS-Tools.L, 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 wins when points are below the diagonal, ITS-Tools.L wins when points are above the diagonal.

LTSMin versus GreatSPN

Some statistics are displayed below, based on 1616 runs (808 for LTSMin and 808 for GreatSPN, so there are 808 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).

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

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

LTSMin versus Irma.full

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

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 LTSMin computed more values than Irma.full, denote cases where LTSMin computed less values than Irma.full, 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 wins when points are below the diagonal, Irma.full wins when points are above the diagonal.

LTSMin versus Irma.struct

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

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 LTSMin computed more values than Irma.struct, denote cases where LTSMin computed less values than Irma.struct, 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 wins when points are below the diagonal, Irma.struct wins when points are above the diagonal.