We've made it easy for our users to run
timing experiments on SamIam's
If you plan to report empirical timings,
we provide two alternatives:
Batch Tool and Code Bandit.
automatically includes detailed timing
information as part of the results of an approximate or exact MAP query.
It breaks the time to calculate MAP into three mutually exclusive
tasks: (1) model pruning, (2) initialization, and (3) the actual search.
For each of these chunks BatchTool gives the system elapsed time and
a thread profile time, if available.
writes an example Java program that
calculates MAP and reports the same timings as BatchTool.
Short prototype code demonstrates clearly and concisely
how to include such timings in your own Java programs that
call our inference library.