We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Checklist for the 2016 data release. This is to start the preparations.
See also the volume estimates in
https://indico.cern.ch/event/1029215/contributions/4324588/attachments/2234005/3786244/DPOA_news_27_04_2021.pdf#page=5, and
https://indico.cern.ch/event/1192611/contributions/5013791/attachments/2512351/4318700/CERN_ODWG_CMS_Sept_2022.pdf
collision dataset list, see CMS: 2016 collision dataset list #155
MC data, see CMS: 2016 MC list #156
approval
dataset for pileup
pileup profile description in /docs/cms-guide-pileup-simulation (http://opendata.cern.ch/docs/cms-guide-pileup-simulation)
/docs/cms-guide-pileup-simulation
produce PFNano for a part of collision data ("derived data")
build records for PFNano derived data (see CMS - create a script for derived data records #212 )
categorize MC, see CMS: 2016 MC categories #157
check resources
transfer, see CMS: 2016 dataset transfer #188
container cmssw_10_6_30-slc7_amd64_gcc700
new VM (see CMS: add records for the updated VM opendata.cern.ch#3537)
Global tags to /cvmfs
build records for the condition data (see CMS: add records to 2016 condition data and unify titles for all condition data records opendata.cern.ch#3538)
json files for validated runs, see CMS: create 2016 validated run record opendata.cern.ch#3446
build a trigger menu table as in http://opendata.cern.ch/record/1700, in the collision record script (create_hlt_trigger_information_record.py), see cms-2016-collision-datasets: create initial directory #177
data-taking configurations
/eos/opendata/cms/configuration-files/2016
dataset short description for the records
trigger listings for PD, in the collision record script (create_hlt_trigger_listings.py), see cms-2016-collision-datasets: create initial directory #177
MC provenance and configurations files, in the simulated record script, see cms-2016-simulated-datasets: updates done #207
luminosity , see CMS: create 2016 luminosity record opendata.cern.ch#3448
usage examples & documentation, see CMS running documentation to-do list for 2023-2024. opendata.cern.ch#3452
/docs/cms-virtual-machine-2016
/docs/cms-getting-started-2016
/docs/cms-guide-docker
docs/about-cms
docs/cms-guide-for-condition-database
The text was updated successfully, but these errors were encountered:
katilp
No branches or pull requests
Checklist for the 2016 data release. This is to start the preparations.
See also the volume estimates in
https://indico.cern.ch/event/1029215/contributions/4324588/attachments/2234005/3786244/DPOA_news_27_04_2021.pdf#page=5, and
https://indico.cern.ch/event/1192611/contributions/5013791/attachments/2512351/4318700/CERN_ODWG_CMS_Sept_2022.pdf
collision dataset list, see CMS: 2016 collision dataset list #155
MC data, see CMS: 2016 MC list #156
approval
dataset for pileup
pileup profile description in
/docs/cms-guide-pileup-simulation
(http://opendata.cern.ch/docs/cms-guide-pileup-simulation)produce PFNano for a part of collision data ("derived data")
build records for PFNano derived data (see CMS - create a script for derived data records #212 )
categorize MC, see CMS: 2016 MC categories #157
check resources
transfer, see CMS: 2016 dataset transfer #188
container cmssw_10_6_30-slc7_amd64_gcc700
new VM (see CMS: add records for the updated VM opendata.cern.ch#3537)
Global tags to /cvmfs
build records for the condition data (see CMS: add records to 2016 condition data and unify titles for all condition data records opendata.cern.ch#3538)
json files for validated runs, see CMS: create 2016 validated run record opendata.cern.ch#3446
build a trigger menu table as in http://opendata.cern.ch/record/1700, in the collision record script (create_hlt_trigger_information_record.py), see cms-2016-collision-datasets: create initial directory #177
data-taking configurations
/eos/opendata/cms/configuration-files/2016
dataset short description for the records
trigger listings for PD, in the collision record script (create_hlt_trigger_listings.py), see cms-2016-collision-datasets: create initial directory #177
MC provenance and configurations files, in the simulated record script, see cms-2016-simulated-datasets: updates done #207
luminosity , see CMS: create 2016 luminosity record opendata.cern.ch#3448
usage examples & documentation, see CMS running documentation to-do list for 2023-2024. opendata.cern.ch#3452
/docs/cms-virtual-machine-2016
?/docs/cms-getting-started-2016
for NanoAOD/docs/cms-guide-docker
docs/about-cms
docs/cms-guide-for-condition-database
The text was updated successfully, but these errors were encountered: