Getting Timings

[trey0]

Getting Timings

[trey0]

You got it. The 'zmdp benchmark' command is similar to 'zmdp solve' but periodically interrupts the solver to report statistics such as number of updates performed, elapsed time, policy performance in simulation, and upper and lower bounds on the quality of the policy.

The elapsed time reported by 'zmdp benchmark' excludes time spent in loading in data and initializing bounds in order to focus on the iterative updates that are the main difference between different solver algorithms. It would be easy to log extra timing information by tweaking TestDriver.cc.

The debugLevel parameter isn't really connected to timing. It's more for debugging any weird behavior and understanding the internals of the algorithms.