[Rivet] Many empty bins in refdata for JADE_OPAL_2000...

Holger Schulz holger.schulz at physik.hu-berlin.de
Tue Jun 22 22:17:53 BST 2010


On 22/06/10 22:23, Frank Siegert wrote:
> Holger Schulz, Saturday 19 June 2010:
>    
>>> Thanks for volunteering, but if there are no serious drawbacks of
>>> the zeros, I would suggest not to, because
>>>
>>> 1) We shouldn't deviate from Hepdata without need.
>>> 2) (Existing) AIDA files from the existing Rivet versions can't be
>>> plotted together with new ones then because the binning has
>>> changed. 3) Some of the bins without reference data might still be
>>> filled by (different) Monte-Carlo runs and thus might be useful
>>> for comparison.
>>>        
>> Ok, then lets leave it as it is.  :)
>>      
> Seems like Andy went ahead and changed this in r2501.
> (I just learned it the hard way when my existing and new aida files
> weren't plotting anymore due to binning conflicts)
> It's a little bit annoying, but I guess even if just for my point 1)
> above, we can't avoid it.
>    
I am in favour for consistency. Maybe the refdata is going to be
updated in HepData as well. I don't see a good reason for having
empty bins in the ref-data. In other cases, like the ALPEH_1996,
there are bin missing which should be zero bins as well, following
the logic of the curent Hepdata version of the JAD_OPAL refdata.
Maybe the zero bins are a relict of a conversion tool.

> Btw... I didn't get a rivet-svn notification email for that one
> changeset, all others around it did arrive. Was that just a hiccup of
> the server?
>    
I also didn't get that svn message.

Holger
> Frank
> _______________________________________________
> Rivet mailing list
> Rivet at projects.hepforge.org
> http://www.hepforge.org/lists/listinfo/rivet
>    



More information about the Rivet mailing list