[Rivet] MC Predictions in Rivet

[Andy Buckley]

Sounds good! We also need to seriously address the issue of how to
re-sync everything from HepData... which was always the plan, but has
drifted problematically far apart.

Andy

On 4 September 2017 at 16:03, Christian Gutschow <chris.g at cern.ch> wrote:
> Hi Andy,
>
> ATLAS have been putting SM predictions on HEPData for many years now, see
> e.g. this example from a 2012 search:
>
> https://hepdata.net/record/ins1125961
>
> or this unfolded measurement from earlier this year:
>
> https://www.hepdata.net/record/78366
>
> I’m fairly sure I’ve seen CMS do the same. Perhaps we can sort out necessary
> developments on the YODA side at the upcoming workshop...
>
> Cheers,
> Chris
>
> On 4 Sep 2017, at 15:12, Andy Buckley <andy.buckley at cern.ch> wrote:
>
> Hi David,
>
> Yes, we're definitely happy with that. The much bigger battle to be
> fought is on the experiment side. If this info starts appearing in
> HepData, we will support it -- perhaps via a special /MC path prefix,
> if we can't figure out a better way: we have the IsRef annotation for
> ref data, but still need to convert the dict returned by default YODA
> read() to a multimap or similar, to allow multiple data objects with
> the same path.
>
> Andy
>
> On 1 September 2017 at 14:42, Yallup, David <david.yallup.15 at ucl.ac.uk>
> wrote:
>
> Hi Riveteers,
>
>
> I think this is something that I've mentioned before, but I was thinking
> about having the possibility to package the experiments MC predictions
> with the rivet routines, basically just including a second scatter
> alongside each of the /REF/ data scatters, /MC/ or something along those
> lines
>
> The reasoning from my PoV is mostly that this would be useful is in
> limit setting/ results reinterpretation, but I think there's also a good
> case that the experiments MC is getting increasingly more
> complicated/time consuming to reproduce as the calculations get more
> complicated. I don't know however if people think this would actually be
> helpful for more "standard" uses of Rivet, MC Development/Tuning etc?
>
>
> Anyway really the work in rivet for this would be minimal and I guess it
> would be mostly about pushing the Experiments and the HepData entries to
> provide this. I wanted to raise this to the list to see if this sounds
> like a useful, 'rivet-ey'  and probably most importantly feasible idea
> to pursue.
>
>
> Cheers,
> David
>
> _______________________________________________
> Rivet mailing list
> Rivet at projects.hepforge.org
> https://www.hepforge.org/lists/listinfo/rivet
>
>
>
>
> --
> Dr Andy Buckley, Lecturer / Royal Society University Research Fellow
> Particle Physics Expt Group, University of Glasgow
> _______________________________________________
> Rivet mailing list
> Rivet at projects.hepforge.org
> https://www.hepforge.org/lists/listinfo/rivet
>
>
>
>
>
>
>
>  —
>
>  Dr. Christian Gütschow
>
>  Department of Physics and Astronomy
>  University College London
>  Gower Street
>  London WC1E 6BT
>
>  > D10 Physics Building
>  > +44 (0)20 7679 3775
>  > chris.g at cern.ch
>
>
>
>



-- 
Dr Andy Buckley, Lecturer / Royal Society University Research Fellow
Particle Physics Expt Group, University of Glasgow