Feature Request: Output runtime statistics to CSV / pipe
Note: This request is based off of the implementation of v1.0.0. See #37 for dev progress
This could be toggled with a command line option e.g. --output-status /path/to/file. The output should/could be semicolon separated, making it easy to graph.
A usage example could be to output the waiting list size and passed list size to an output pipe with a plotting program receiving the data, you could graph the current state of the system.
Statistics may include:
Waiting list size
Passed list size
Count of encountered hash-collissions
How much memory is used (Could be limited with a cli option: --max-ram 16GiB report with OOM <stats>)
Estimate of how far the search is (upper bound could be pre-calculated)
Set a --max-time 30minutes that is simply checked during search. Report with DNF <stats>
This could be implemented as part of the traceable_multimap<T> class. There would have to be done some preliminary work on how to easily inject command-line options into the forward reachability search class
Feature Request: Output runtime statistics to CSV / pipe
Note: This request is based off of the implementation of v1.0.0. See #37 for dev progress
This could be toggled with a command line option e.g.
--output-status /path/to/file. The output should/could be semicolon separated, making it easy to graph.A usage example could be to output the waiting list size and passed list size to an output pipe with a plotting program receiving the data, you could graph the current state of the system.
Statistics may include:
--max-ram 16GiBreport withOOM <stats>)--max-time 30minutesthat is simply checked during search. Report withDNF <stats>This could be implemented as part of the
traceable_multimap<T>class. There would have to be done some preliminary work on how to easily inject command-line options into the forward reachability search class