#791: Output timer tree as XML --------------------------+------------------------------------------------- Reporter: hinder | Owner: eschnett Type: enhancement | Status: reviewed_ok Priority: minor | Milestone: ET_2012_05 Component: Carpet | Version: Resolution: | Keywords: --------------------------+-------------------------------------------------
Comment (by hinder):
I see the following potential tasks:
1. Change the XML schema (quick); 2. Modify the history patch to only store historical values if enabled by a parameter (quick); 3. Possibly add iteration information to the timers (not clear what to do); 4. Possibly limit the amount of history stored by storing it only every so many iterations (depends on 3); 5. Output the XML file regularly, not just in shutdown (should be OK); 6. Send all the timer values to the root processor and merge them into one XML file (hard); 7. Add reductions of the timer values to the XML file (depends on 6).
What aspect of this should be implemented by ET_2012_05? I won't have time to do all of this before the freeze, and development work is supposed to happen at the start of a release cycle, not the end. I can probably do 1 and 2 before the freeze. In the release notes, we could indicate that this is a new feature which is still under development, and some aspects of it might change.