[Rivet] Rivet analysis for a D0 W+jets publication

Andy Buckley andy.buckley at cern.ch
Wed Dec 14 14:38:33 GMT 2016


On 14/12/16 12:40, Darren Price wrote:
> Hi Andy,
>
> Thanks for the prod!
>
> Holger, thanks for your help -- answers to your questions (as best I
> can) inline below:

And replies from me on a couple of them:

>>>     The tarball contains references to inspire 913084 whilst the paper
>>>     is inspire 1221252.
>
> Ah ,this is because the W+jets measurements spanned two papers:
> http://inspirehep.net/record/913084
> and
> http://inspirehep.net/record/1221252
>
> The second does not supersede the first, rather adds additional
> observables, so both are covered by this one rivet routine (I don't
> know if this causes problems or not?)
> The first paper covers integrated fiducial cross-sections in n-jets
> bins, and differential distributions in the nth jet pT in W+njet
> inclusive events.
> The second paper adds a variety of additional distributions.

The simplest -- and preferable, I think -- thing is to split them. So 
far we have sometimes done it the other ways around, i.e. one paper = > 
1 analysis code, but I think never this.

I know it's a bit inconvenient, but retaining a mostly 1-to-1, sometimes 
1-to-N, mapping between papers and analyses will play better with e.g. 
data-link ties between Inspire, HepData, Rivet, etc.. And will allow us 
to pull down ref data updates from HepData in a simple & uniform fashion.

On a smaller level, our metadata format only allows a single Inspire ID 
to be indicated in a given analysis, but if the other reasons were 
compelling we could extend that. But two orthogonal analysis codes can 
anyway be easily run at the same time, so I'm not sure there's a good 
case given the potential downsides.

Slightly connected, is the reference data that you supplied direct from 
the analysis, or is it a merged output from HepData for the two papers?

[...]

>>>     The corresponding .info file is missing.
>
> Sorry for my ignorance: what would normally go into this? Perhaps I
> can reconstruct the necessary information for you?

I've attached an example from the last D0 paper. This might explain some 
of my comments above, too!

Cheers,
Andy

-- 
Dr Andy Buckley, Lecturer / Royal Society University Research Fellow
Particle Physics Expt Group, University of Glasgow
-------------- next part --------------
A non-text attachment was scrubbed...
Name: D0_2015_I1324946.info
Type: application/x-info
Size: 1707 bytes
Desc: not available
URL: <https://www.hepforge.org/lists-archive/rivet/attachments/20161214/fbdf918a/attachment.info>


More information about the Rivet mailing list