Hi Dave, On Dienstag, 4. März 2014, Dave Steele wrote: > The current precise definition is a bit obtuse in this context - DDPO > sorts these strings, for use in a tooltip, in a particular order > relative to each other, vs. alphabetical for all others. It's a bit > presumptuous to say that in the README now, since DDPO does no such > thing yet. > > The purpose here was to give a hint on a scheme for entering values. > The summary doesn't enforce a model, except for the reserved > 'overall'. > > To work with my current DDPO code, I could add something like "By > convention, the values [...] are expected here, though other values > can be used". > > The real answer is that the "special meaning" is not yet defined. It > is dependent on how you want to use summaries. Last month, I would > have said that the 'special' values were required, at a minimum, to > populate the piuparts distribution table in DDPO. They dropped those > tables for other metrics in February, to reclaim space. > > The current concept, defined by my DDPO patches, is that you have the > ability to control the distributions reported by the DDPO tool tip > from piuparts.conf, with the special sorting for the special > reporting-sections. > > Another concept would be to limit DDPO to the special sections.This > would let you use other values to report other summary breakdowns to > other contexts. The 'overall' concept would need to be reworked a bit > here. > > Which do you prefer?
the first & thanks for your explainations! (Some (all?) of those should be included in the coming patches... :) cheers, Holger
signature.asc
Description: This is a digitally signed message part.