Make plots of timing, ncalls, and allocations data

docs/src/developing.md

@@ -82,7 +82,20 @@ $ h5dump -d /timing_data/global_timer_string my_output_file.moments.h5
 ```
 
 More detailed timing information is saved for each MPI rank into subgroups
-`rank<i>` of the `timing_data` group in the output file.
+`rank<i>` of the `timing_data` group in the output file. This information can
+be plotted using [`makie_post_processing.timing_data`](@ref). The plots contain
+many curves. Filtering out the ones you are not interested in (using the
+`include_patterns`, `exclude_patterns`, and/or `ranks` arguments) can help, but
+it still may be useful to have interactive plots which show the label and MPI
+rank when you hover over a curve. For example
+```julia
+julia> using makie_post_processing, GLMakie
+julia> ri = get_run_info("runs/my_example_run/")
+julia> timing_data(ri; interactive_figs=:times);
+```
+Here `using GLMakie` selects the `Makie` backend that provides interactive
+plots, and the `interactive_figs` argument specifies that `timing_data()`
+should make an interactive plot (in this case for the execution times).
 
 Lower level timing data, for example timing MPI and linear-algebra calls, can
 be enabled by activating 'debug timing'. This can be done by re-defining the

makie_post_processing/makie_post_processing/Project.toml

@@ -9,7 +9,9 @@ Combinatorics = "861a8166-3701-5b0c-9a16-15d98fcdc6aa"
 LaTeXStrings = "b964fa9f-0449-5b57-a5c2-d3ea65f4040f"
 LsqFit = "2fda8390-95c7-5789-9bda-21331edee243"
 MPI = "da04e1cc-30fd-572f-bb4f-1f8673147195"
+Makie = "ee78f7c6-11fb-53f2-987a-cfe4a2b5a57a"
 NaNMath = "77ba4419-2d1f-58cd-9bb1-8ffee604a2e3"
 OrderedCollections = "bac558e1-5e72-5ebc-8fee-abe8a469f55d"
+StatsBase = "2913bbd2-ae8a-5f71-8c99-4fb6c76f3a91"
 TOML = "fa267f1f-6049-4f14-aa54-33bafae1ed76"
 moment_kinetics = "b5ff72cc-06fc-4161-ad14-dba1c22ed34e"