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 3 and Version 4 of SubmittingAnalyses


Ignore:
Timestamp:
Dec 5, 2017, 12:55:47 PM (2 years ago)
Author:
Andy Buckley
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SubmittingAnalyses

    v3 v4  
    11== Submitting an analysis to Rivet ==
    22
    3 === Analyses from LHC experiments ===
     3=== Analyses from LHC (and other) experiments ===
    44
    5 Rivet plugins tested and validated by the experimental groups of ATLAS, CMS and LHCb should now be
    6 copied to the rivet downloads/contrib directly by the responsibles of the experiments.
     5Our 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.
    76
    8 We have a machinery in place that detects new files in that folder
    9 and alert us to take action.
     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!''
    108
    11 We would like to ask you to scp a single tarball for each new analysis to
     9Rivet 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.
     10
     11We 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.
     12
     13We would like to ask you to scp a single .tar.gz tarball for each new analysis to
    1214
    1315    login.hepforge.org:/hepforge/downloads/rivet/contrib
     
    1618
    1719    the analysis files (.cc, .info, .plot, . yoda)
    18     a rivet html with your validation plots
     20    a rivet-plots HTML directory with your validation plots
    1921
    20 For the latter, it would be ideal if the labels in these plots would allow us to identify
    21 the corresponding line in the corresponding publication. In cases where this is
    22 not possible any more, e.g. deleted MC samples, a clear identification of the
    23 MC used in the validation and maybe a run card will be very helpful.
     22For 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.
     23
     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!'''
     25
    2426
    2527=== General submission ===