HIAllPhysics primary dataset in RECO format from the 2.76 TeV Pb-Pb run of 2010 (/HIAllPhysics/HIRun2010-ZS-v2/RECO)
/HIAllPhysics/HIRun2010-ZS-v2/RECO, CMS collaboration
Cite as: CMS collaboration (2020). HIAllPhysics primary dataset in RECO format from the 2.76 TeV Pb-Pb run of 2010 (/HIAllPhysics/HIRun2010-ZS-v2/RECO). CERN Open Data Portal. DOI:10.7483/OPENDATA.305G.POEC
Dataset Collision Heavy-ion physics CMS 2.76TeV PbPb CERN-LHC
Description
HIAllPhysics primary dataset from the 2.76 TeV Pb-Pb run of 2010.
The list of validated runs, which must be applied to all analyses, either with the full validation or for an analysis requiring only muons, can be found in
Dataset characteristics
75482193 events. 28954 files. 151.0 TiB in total.System details
GR_R_39X_V6B::AllCMSSW_3_9_2_patch5
Recommended container image for analyses is available in the following locations (see guide):
docker.io/cmsopendata/cmssw_3_9_2_patch5-slc5_amd64_gcc434:latestgitlab-registry.cern.ch/cms-cloud/cmssw-docker-opendata/cmssw_3_9_2_patch5-slc5_amd64_gcc434:latest
How were these data selected?
During the heavy-ion run, events were directed to this primary dataset through several different HLT trigger paths, which can be studied and selected with the example usage code linked below. The possible HLT trigger paths in this dataset (the list may be incomplete):
HLT_HIBptxXOR
HLT_HICentralityVeto
HLT_HIDoublePhoton5_CEP_L1R
HLT_HIJet35U
HLT_HIJet50U
HLT_HIJet75U
HLT_HIJet90U
HLT_HIL1Algo_BptxXOR_BSC_OR
HLT_HIL1DoubleMuOpen
HLT_HIL1SingleMu3
HLT_HIL1SingleMu5
HLT_HIL1SingleMu7
HLT_HIL2DoubleMu0
HLT_HIL2DoubleMu3
HLT_HIL2Mu20
HLT_HIL2Mu3
HLT_HIL2Mu5Tight
HLT_HIMinBiasBSC
HLT_HIMinBiasBSC_OR
HLT_HIMinBiasHF
HLT_HIMinBiasHfOrBSC
HLT_HIMinBiasHf_OR
HLT_HIMinBiasPixel_SingleTrack
HLT_HIMinBiasZDCPixel_SingleTrack
HLT_HIMinBiasZDC_Calo
HLT_HIMinBiasZDC_Calo_PlusOrMinus
HLT_HIMinBiasZDC_Scint
HLT_HIPhoton15
HLT_HIPhoton20
HLT_HIPhoton30
HLT_HIRandom
HLT_HIStoppedHSCP35
HLT_HIUpcEcal
HLT_HIUpcMu
HLT_HIZeroBias
HLT_HIZeroBiasPixel_SingleTrack
HLT_HIZeroBiasXOR
How were these data validated?
During data taking all the runs recorded by CMS are certified as good for physics analysis if all subdetectors, trigger, lumi and physics objects (tracking, electron, muon, photon, jet and MET) show the expected performance. Certification is based first on the offline shifters evaluation and later on the feedback provided by detector and Physics Object Group experts. Based on the above information, which is stored in a specific database called Run Registry, the Data Quality Monitoring group verifies the consistency of the certification and prepares a json file of certified runs to be used for physics analysis. For each reprocessing of the raw data, the above mentioned steps are repeated. For more information see:
CMS data quality monitoring: Systems and experiences
The CMS Data Quality Monitoring software experience and future improvements
The CMS data quality monitoring software: experience and future prospects
How can you use these data?
You can access these data through the CMS Open Data container or the CMS Virtual Machine. See the instructions for setting up one of the two alternative environments and getting started with CMS heavy-ion data data in
Running CMS analysis code using Docker
Files and indexes
Disclaimer
These open data are released under the Creative Commons Zero v1.0 Universal license.
Neither the experiment(s) ( CMS ) nor CERN endorse any works, scientific or otherwise, produced using these data.
This release has a unique DOI that you are requested to cite in any applications or publications.
