You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The benchmarks for reachability queries have two problems, making them hard to use for measuring improvements or regressions for practical use of them.
Firstly it uses IO like the other benchmarks, see #132
Secondly it currently uses very small and similar samples, making it hard to measure the effectiveness of for example implementing a heuristic.
Our group found a possibly useful link for some XML data specifically for benchmarking reachability that should be able to be read by ECDAR https://www.labri.fr/perso/herbrete/tchecker/
The text was updated successfully, but these errors were encountered:
The benchmarks for reachability queries have two problems, making them hard to use for measuring improvements or regressions for practical use of them.
Firstly it uses IO like the other benchmarks, see #132
Secondly it currently uses very small and similar samples, making it hard to measure the effectiveness of for example implementing a heuristic.
Our group found a possibly useful link for some XML data specifically for benchmarking reachability that should be able to be read by ECDAR
https://www.labri.fr/perso/herbrete/tchecker/
The text was updated successfully, but these errors were encountered: