[Rivet] YODA write out

[Chris Pollard]

Hi David, all,

Making this general for any function of 2 histograms (not just division) is
tricky, no?

I think the option someone mentioned a few months ago was to only allow
access to *booked* histograms in finalize(). That way you are guaranteed to
be able to rerun finalize() on the output yoda file(s).

Chris

On Wed, Jan 20, 2016 at 5:03 PM, David Bjergaard <david.bjergaard at gmail.com>
wrote:

> Why can't there be custom 1D booking for ratios that is implemented in the
> software that writes out name_num and name_den? Then users can yodamerge to
> their hearts content.
>
>     David
>
> > On Jan 20, 2016, at 11:56 AM, Holger Schulz <holger.schulz at durham.ac.uk>
> wrote:
> >
> >> On 20/01/16 16:51, David Grellscheid wrote:
> >> Hi Holger,
> >>
> >> Is your question why the result of dividing two histos is a scatter
> rather than a histogram?
> >> It gets hard to define many of the properties that a histogram / bin
> should have after the division.
> >
> > Sorry, I was unprecise.
> >
> > Specifically, what people want to do (for observables that are defined
> as ratios)
> > is to do some yodamerge stuff for the denominator and separately some
> yodamerge
> > stuff for the numerator. For instance adding background and signal
> contributions.
> > That requires output in the form of HISTO1D.
> >
> > I.e. do we have/ can we add a switch which disables the divide call in
> analyses and
> > instead writes out the histo1D guys of the numerator and the denominator
> such
> > that one can do arbitrary histogram manipulation afterwards?
> >
> > Cheers,
> > Holger
> >
> >>   David
> >>
> >>
> >>
> >>> On 20 January 2016 13:47:20 GMT+00:00, Holger Schulz<
> holger.schulz at durham.ac.uk>  wrote:
> >>>> On 20/01/16 13:44, Andy Buckley wrote:
> >>>> Er, it already does. If you call bookHisto1D, a Histo1D will be
> >>>> written out. Do you have a counterexample?
> >>> Ah sorry I forgot one important bit of information and that is the call
> >>>
> >>> of divide in finalize.
> >>>
> >>> Sorry, overworked already ...
> >>>
> >>> Holger
> >>>> A
> >>>>
> >>>> On 20 Jan 2016 13:30, "Holger Schulz"<holger.schulz at durham.ac.uk
> >>>> <mailto:holger.schulz at durham.ac.uk>>  wrote:
> >>>>
> >>>>     Hi,
> >>>>
> >>>>     is there a way to have rivet write out YODA Histo1D at the end of
> >>>>     a run
> >>>>     rather than Scatter2D? (I think the experimental --histo-interval
> >>>>     kind of does
> >>>>     that, right?)
> >>>>
> >>>>     I am asking because of post processing concerns brought forward
> >>> by
> >>>>     some
> >>>>     people at IPPP when using yodamerge.
> >>>>
> >>>>     Cheers,
> >>>>     Holger
> >
> > _______________________________________________
> > Rivet mailing list
> > Rivet at projects.hepforge.org
> > https://www.hepforge.org/lists/listinfo/rivet
> _______________________________________________
> Rivet mailing list
> Rivet at projects.hepforge.org
> https://www.hepforge.org/lists/listinfo/rivet
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.hepforge.org/lists-archive/rivet/attachments/20160120/b2636d6a/attachment.html>