-
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: provenance metadata for 2015 MC #68
Comments
NB that for Run1, the datasets are in AODSIM format, but for Run2 they will be in MiniAODSIM, which is an additional step in the production chain, which was not present during Run1. |
Because of the features in 2015 MC production, some McM entries do not have the input data field filled although it is available in DAS. The script in https://github.com/cernopendata/data-curation/tree/master/cms-YYYY-simulated-datasets can be used for all further provenance extractions. The query logic (parent relationship from DAS), should not be modified for 2015, but can be done for UL afterwards. To test:
To do:
|
Extraction done by @OsamaMomani OK, but provenance not found for three datasets. Manual search through DAS and MCM gives the following:
➡️ Leave out the invalid one, and build the provenance of the two others by hand. |
These 3 datasets affect three steps in the following records
|
McM queries are empty for these output datasets. |
The missing 5 configs are in The records are in
|
The 5 files are already in the target location, for example:
|
(from #65)
Run2 legacy metadata of 2016-2018 will be extracted from the ultra-legacy production, see https://github.com/cernopendata/data-curation/tree/master/cms-run2-ultra-legacy-production.
Run1 metadata has been extracted with
2015 is a separate production and the script may need to be modified.
Run2 Fall15 MiniAOD v2 campaign (76X version 2)
dataset=/*/*RunIIFall15MiniAODv2-PU25nsData2015v1*/*
Size: 227.4TB
7114 datasets
Check if the 2015 MC extraction works with the ultra-legacy script, or if the previous Run1 scripts should be used.
Run the script and prepare the records.
The text was updated successfully, but these errors were encountered: