|
[Rivet] Profile histograms in Rivet 2James Robinson james.robinson at cern.chTue Oct 7 17:43:06 BST 2014
Dear David, Yes, that's true. In fact, I'm only really bothering with the ROOT output running for easier visual debugging. I guess I can just use the Rivet plotting scripts instead for the moment. It might be something that's worth looking into at some point, but it's not critical. Thanks, James On 7 October 2014 18:39, David Bjergaard <david.bjergaard at gmail.com> wrote: > Hi James, > > (Shooting from the hip). It looks like it wouldn't be too hard (reading > the Profile1D.h interface) to roll your own YODA->ROOT converter. > > Do you know where the code that handles Rivet->Root conversion? If this > is athena software then I suppose this issue gets punted downstream? > Andy can better comment on what happens if ProfileBin1D::mean() is > called with no entries (in my experience it should throw an exception). > In that case it may be that this behavior has changed causing the athena > code to fail. > > Dave > > James Robinson <james.robinson at cern.ch> writes: > > > Dear David and Andy, > > > > Sorry about this, but I'm having another problem with my analysis' > > Rivet routine. One of the histograms is a Profile1DPtr and, although > > the .yoda output gives sensible numbers, the .root file has a TProfile > > for which all bins are 0. > > > > Obviously this isn't a problem in Rivet per se, but I guess it might > > be a problem with the athena Rivet_i interface. The only thing I can > > think of that might be weird about this histogram is that some bins > > have no entries (so a naive call to ProfileBin1D::mean() might fail). > > > > Any ideas about this one? > > > > Thanks, > > James > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://www.hepforge.org/lists-archive/rivet/attachments/20141007/133245aa/attachment.html>
More information about the Rivet mailing list |