-
Notifications
You must be signed in to change notification settings - Fork 148
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
Comments
@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 Current visible fields are (taken into account #1537) |
Proposed requested entries: Title: Authors: Description: Use with: System Details: Related items: How can you use this code: Issues and limitations: |
@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. |
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)
The text was updated successfully, but these errors were encountered: