-
Notifications
You must be signed in to change notification settings - Fork 22
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
CMS - create a script for derived data records #212
Comments
Can refer to this script from cms-2012-event-display-files as a starting point for new script for derived datasets, taking into account the following notes:
|
For the number of events, you can use the following (if running where ROOT is available) NanoAODRun1 and PFNano:
In the older versions, the event number might appear as a "long" integer, e.g. 563709L, in that case, POET:The POET output has a different structure, and there are two versions of it:
The number of events is the same in both cases. |
Further details for the three types of derived data : POETFiles under These are the files used in the 2022 workshop lesson For each dataset, we have:
e.g.
Finally, no reason to leave out the merged file, we can as well have it in the record.
NanoAODRun1FIles under These are the files used in the 2022 workshop For each dataset we have
So all files go in a single derived
For titles and format, see cernopendata/opendata.cern.ch#3349 (comment) PFNanoFiles to be moved For each dataset, files are under The derived
|
The file types of the "normal" collision and simulated data will be nanoaod and nanoaodsim, respectively. |
The recids for the production code are
|
CMS 2016 release will include several "derived data" records structurally similar to e.g. https://opendata.cern.ch/record/12341
They will be:
We should have a script template to create such records, that can be run in similar way as those for collision or MC records.
For the provenance, they will link to the parent dataset and the SW that was used to produce them (e.g. Run1 Nano: cernopendata/opendata.cern.ch#3281). Both will be available as CODP records. So need for extended provenance listing as it is already available in the parent dataset record.
For the variable description, these records can link to listings of this type.
This html files (one per type of production) should be hosted on the OD portal.
In the scripts, all metadata variables should be collected to the start of the script, for the ease of reuse.
The text was updated successfully, but these errors were encountered: