Minimal timer output?

[donnaaboise]

Originally reported by: Donna Calhoun (Bitbucket: donnaaboise, GitHub: donnaaboise)

---

It would be nice to have the option of limiting the timing output to a few key (exclusive) timers :

Walltime 
Advance
Ghost fill
Ghost comm

Or even, just

AMR Tasks
Communication 
Advance 
Walltime  

Something like report-timing=<N>, where N=0 is no reporting (already implemented), N=1 is minimal and N=2 more input, etc.

Right now, the timers are really long, and may not be of interest to the typical user.

---

• Bitbucket: https://bitbucket.org/donnaaboise/forestclaw/issue/112

[donnaaboise]

Original comment by Donna Calhoun (Bitbucket: donnaaboise, GitHub: donnaaboise):

---

Yes - this would work!

[donnaaboise]

Original comment by Carsten Burstedde (Bitbucket: cburstedde, GitHub: cburstedde):

---

What about giving each timer a priority (integers), and when printing you can specify >= priority to log?

[cburstedde]

Check out the enhanced API in libsc's sc_statistics.h, branch feature-stats-prio. Comments?

[donnaaboise]

We now have this capability.