rivet is hosted by Hepforge, IPPP Durham
close Warning: Can't synchronize with repository "(default)" (Repository path '/hepforge/hg/rivet/public/rivet' does not exist.). Look in the Trac log for more information.

Changes between Version 4 and Version 5 of SubmittingAnalyses


Ignore:
Timestamp:
Dec 5, 2017 1:49:59 PM (11 months ago)
Author:
Andy Buckley
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SubmittingAnalyses

    v4 v5  
    55Our thanks to the LHC experiments who've really got into the swing of submitting Rivet analysis routines directly to us -- this is by far the best way to ensure high-quality analyses that match the experiment analysis procedures.
    66
    7 '''IMPORTANT:''' ''please make sure that your analysis submission uses reference data taken from HepData, e.g. the pre-publication staged version of the experiment data submission to HepData. HepData is the canonical repository for all HEP analysis data, and Rivet needs to stay synchronised with it for future maintainability of our analysis routines: please help us to avoid divergence!''
     7'''IMPORTANT:''' ''please make sure that your analysis submission uses reference data taken from !HepData, e.g. the pre-publication staged version of the experiment data submission to !HepData. This is the canonical repository for all HEP analysis data, and Rivet needs to stay synchronised with it for future maintainability of our analysis routines: please help us to avoid divergence.''
    88
    9 Rivet plugins tested and validated by the experimental groups of ATLAS, CMS and LHCb should now be copied to the rivet downloads/contrib directly by the responsibles of the experiments.
     9Rivet plugins tested and validated by the experimental groups of ALICE, ATLAS, CMS and LHCb should now be copied to the rivet downloads/contrib directly by the responsibles of the experiments.
    1010
    1111We have machinery in place that detects new files in that folder and alert us to take action, but it's also helpful if you drop a short email to rivet@projects.hepforge.org to let us know about the upload.
     
    2222For our ease of integration into the Rivet releases, it's preferred if the analysis files are all in the same base- or sub-directory of the tarball.
    2323
    24 Re. the validation, ideally the labels in these plots should allow us to identify the corresponding line in the corresponding publication. In cases where this is not possible any more, e.g. deleted MC samples, a clear identification of the MC used in the validation and maybe a run card will be very helpful. '''Reproducibility is good!'''
     24Re. the validation, ideally the labels in these plots should allow us to identify the corresponding line in the corresponding publication. In cases where this is not possible any more, e.g. deleted MC samples, a clear identification of the MC used in the validation and maybe a run card will be very helpful. '''Reproducibility is good! '''
    2525
    2626
     
    4141Rivet has a set of code rules under CodingStyleGuide. Mostly these are good guidance for clear code (despite being for a different language the Python style guide is also full of generally good advice for clear, readable, and maintainable code), but some are purely chosen for stylistic consistence with the rest of the Rivet system. Please pay attention to these and don't use a different style that you personally prefer in analyses that you wish to make official.
    4242
    43 As well as the layout, naming conventions, etc., please try to use features of the Rivet library as much as possible. For example did you know that Jet and Particle have their own {{{pT()}}}, {{{eta()}}}, {{{phi()}}}, etc. methods so you don't have to use an intermediate call to {{{momentum()}}}? Please use them. Even better, they have {{{abseta()}}}, {{{absrap()}}}, and {{{abspid()}}} methods so no more need for {{{fabs(p.eta())}}} or {{{abs(p.pid())}}}. There are also many helpful functions like {{{inRange(x, low, high)}}}, {{{sqr()}}} and {{{add_quad()}}} in {{{Rivet/Math/MathUtils.hh}}}.
     43As well as the layout, naming conventions, etc., please try to use features of the Rivet library as much as possible. For example, did you know that
     44
     45* Jet and Particle have their own {{{pT()}}}, {{{eta()}}}, {{{phi()}}}, etc. methods so you don't have to use an intermediate call to {{{momentum()}}}?
     46* Even better, they have {{{abseta()}}}, {{{absrap()}}}, and {{{abspid()}}} methods so no more need for {{{fabs(p.eta())}}} or {{{abs(p.pid())}}}
     47* There are also many helpful functions like {{{inRange(x, low, high)}}}, {{{sqr()}}} and {{{add_quad()}}} in {{{Rivet/Math/MathUtils.hh}}}.
    4448
    4549