Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create records for the 2011 jet validation example #1191

Open
katilp opened this issue Oct 7, 2016 · 3 comments
Open

Create records for the 2011 jet validation example #1191

katilp opened this issue Oct 7, 2016 · 3 comments

Comments

@katilp
Copy link
Member

katilp commented Oct 7, 2016

Create records for the jet validation example in collection http://opendata.cern.ch/search?p=Run2011A%20collection%3ACMS-Validation-Utilities
It is done in two steps

Step 1: https://github.com/cms-opendata-validation/2011-jet-inclusivecrosssection-ntupleproduction-optimized

Step 2: https://github.com/cms-opendata-validation/2011-jet-inclusivecrosssection-analysis

@tiborsimko should we have this in two records (in a similar way as the di/four lepton ntuple production (http://opendata.cern.ch/record/233) and analysis (http://opendata.cern.ch/record/234) steps currently) or should we start to anticipate something more "analysis preservation" -like here?

The data should be uploaded in a separate record, see (#1192)

@katilp
Copy link
Member Author

katilp commented Oct 24, 2017

@zenaiev Provide entries under the different titles for the software record (get inspiration from http://opendata.cern.ch/record/462 or http://opendata.cern.ch/record/233 but note that the header names with "data" are wrong and will be changed see #1537) for the code in

https://github.com/cms-opendata-validation/2011-jet-inclusivecrosssection-ntupleproduction-optimized

Current visible fields are (taken into account #1537)
If you feel that these titles do not match the contents or are not enough, we can still change them.
Title:
Authors:
Description:
Use with:
System details:
Related items:
How can you use this code:
Issues and limitations:

@zenaiev
Copy link

zenaiev commented Oct 24, 2017

Proposed requested entries:

Title:
Software to preprocess the CMS 2011 Jet dataset and produce ROOT ntuples for further physics analysis

Authors:
..., Oleksandr Zenaiev, ... (what are other authors? I contributed only to performance optimisation)

Description:
This code to produce ROOT ntuples of the Jet dataset is set up at Research level, i.e. it requires university-student-level programming experience. Minimal acquaintance with Linux and the ROOT analysis package (https://root.cern.ch/) as well as a basic text editor is needed.

Use with:
Use this with 2011 Jet primary dataset (see detailed instructions in readme files and code): http://opendata.cern.ch/record/16, http://opendata.cern.ch/record/17, http://opendata.cern.ch/record/25

System Details:
Use this code with the CMS Open Data VM environment http://opendata.cern.ch/record/249
Software release: CMSSW_5_3_32

Related items:
The output of the code are ROOT ntuples described in readme file.

How can you use this code:
If you do not have the CERN Virtual Machine for 2011 CMS data installed, follow the instructions in step 1 at http://opendata.cern.ch/VM/CMS/2011. Then install and run the Demo (demo analyzer) program following the instructions at http://opendata.cern.ch/VM/CMS/2011#testvalidate2011. To run the analysis, follow the instructions in readme file.

Issues and limitations:
??? (perhaps original authors of the code should be asked)

@ArtemisLav ArtemisLav self-assigned this May 24, 2018
@ArtemisLav
Copy link
Member

@katilp is this going to be one or two records after all? If it's going to be two, I just need the metadata for the second record. And should they link back to #1192 somehow?

Also, WRT the github repos, if you tag them with a release tag, we could just grab the tarball and show it on the record, if you like.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants