[Rivet] Presentation of Event Shapes results

Sergo Jindariani sergo at fnal.gov
Fri Jun 3 15:30:12 BST 2011


Dear Peter,

  I apologize for delay in my reply.  The data points for individual  
thrust and thrust minor distributions are not included in our PRD   
publication, but
are public in the sense that they were approved by CDF collaboration.  
In the publication we only provide data points for the weighted  
difference of
thrust and thrust minor at given leading jet energy requirement, i.e.:
D=alpha<tau>+beta<T_min>

Currently, data points are saved in the form of ROOT ntuples which I  
could certainly provide.  I'm not familiar with HEPDATA format, however
if there are easy conversion tools , I would be happy to try them.

Regards,
  -Sergo

On May 30, 2011, at 11:39 AM, Peter Skands wrote:

> Dear Sergo and Andrey,
>
> The measurement of event shapes by CDF is extremely nice (corrected  
> to the hadron level, exactly as is ideal for MC comparisons) and we  
> would very much like to be able to use it directly as an input to  
> constrain and tune Monte Carlo models in the future, for instance to  
> make sure that no future tuning revision destroys the good agreement  
> with Tune A that you observe, and also to check all the tuning  
> efforts that are now underway for LHC, which sometimes blatantly  
> ignore constraints from previous experiments; that's not always  
> because they don't want to include them, but because they are not  
> able to. To make sure the data is preserved in the most useful and  
> accessible form, I wanted to ask successive stages of questions to  
> you:
>
>  A) Are the data *points* public, or just the plots?
>
>  B) If the points are public, are they in HEPDATA?
>
>  C) If they are in HEPDATA, is there a corresponding Rivet analysis  
> that is (or could be) incorporated in the official Rivet releases,  
> so everyone can make direct comparisons? (I am cc'ing the Rivet  
> authors who I am sure would be very interested to have this analysis  
> included. I know manpower is an issue for both you and for the Rivet  
> people (and also for MC authors), but from my perspective Rivet does  
> seem to be emerging as a key ingredient in data preservation, so I  
> am hoping it is not impossible.)
>
> Cheers,
> Peter Skands



More information about the Rivet mailing list