Introduction

This page presents how M4M.struct 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 M4M.struct' 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).

M4M.struct versus LTSMin

Some statistics are displayed below, based on 1616 runs (808 for M4M.struct and 808 for LTSMin, 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 M4M.struct to LTSMin 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 M4M.struct computed more values than LTSMin, denote cases where M4M.struct computed less values than LTSMin, 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.

M4M.struct wins when points are below the diagonal, LTSMin wins when points are above the diagonal.

M4M.struct versus Tapaal

Some statistics are displayed below, based on 1616 runs (808 for M4M.struct 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 M4M.struct 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 M4M.struct computed more values than Tapaal, denote cases where M4M.struct 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.

M4M.struct wins when points are below the diagonal, Tapaal wins when points are above the diagonal.

M4M.struct versus LoLA

Some statistics are displayed below, based on 1616 runs (808 for M4M.struct 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 M4M.struct 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 M4M.struct computed more values than LoLA, denote cases where M4M.struct 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.

M4M.struct wins when points are below the diagonal, LoLA wins when points are above the diagonal.

M4M.struct versus M4M.full

Some statistics are displayed below, based on 1616 runs (808 for M4M.struct 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 M4M.struct 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 M4M.struct computed more values than M4M.full, denote cases where M4M.struct 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.

M4M.struct wins when points are below the diagonal, M4M.full wins when points are above the diagonal.

M4M.struct versus ITS-Tools

Some statistics are displayed below, based on 1616 runs (808 for M4M.struct 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 M4M.struct 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 M4M.struct computed more values than ITS-Tools, denote cases where M4M.struct 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.

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

M4M.struct versus ITS-Tools.L

Some statistics are displayed below, based on 1616 runs (808 for M4M.struct 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 M4M.struct 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 M4M.struct computed more values than ITS-Tools.L, denote cases where M4M.struct 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.

M4M.struct wins when points are below the diagonal, ITS-Tools.L wins when points are above the diagonal.

M4M.struct versus GreatSPN

Some statistics are displayed below, based on 1616 runs (808 for M4M.struct 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 M4M.struct 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 M4M.struct computed more values than GreatSPN, denote cases where M4M.struct 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.

M4M.struct wins when points are below the diagonal, GreatSPN wins when points are above the diagonal.

M4M.struct versus Irma.full

Some statistics are displayed below, based on 1616 runs (808 for M4M.struct 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 M4M.struct 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 M4M.struct computed more values than Irma.full, denote cases where M4M.struct 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.

M4M.struct wins when points are below the diagonal, Irma.full wins when points are above the diagonal.

M4M.struct versus Irma.struct

Some statistics are displayed below, based on 1616 runs (808 for M4M.struct 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 M4M.struct 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 M4M.struct computed more values than Irma.struct, denote cases where M4M.struct 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.

M4M.struct wins when points are below the diagonal, Irma.struct wins when points are above the diagonal.