| 2013-08-26 20:22:36 |
Mathias Grund Sørensen |
description |
The following stats are incorrectly reported by the engine (wrt. TAPAAL):
- The number "max tokens" does not always correctly report the maximum number of tokens in any considered marking. See the first attached net+query. With -k 2, the engine reports max tokens: 0, which makes the result conclusive, whereas it should report more than 2 making the result inconclusive.
- With EG/AF and queries containing deadlocks, the stats are all 0 if the query is satisfied by the first marking, making the result undistinguishable from the over-approximation results (see second attached net+query). The initial marking should be counted in the stats as explored as well. |
The following stats are incorrectly reported by the engine (wrt. TAPAAL):
- The number "max tokens" does not always correctly report the maximum number of tokens in any considered marking. See the first attached net+query. With -k 2, the engine reports max tokens: 0, which makes the result conclusive, whereas it should report more than 2 making the result inconclusive.
- With queries containing deadlocks, the stats are all 0 if the query is satisfied by the first marking, making the result undistinguishable from the over-approximation results (see second attached net+query). The initial marking should be counted in the stats as explored as well. |
|
