/HIHighPt/HIRun2011-15Apr2013-v1/RECO, CMS collaboration
Cite as: CMS collaboration (2020). HIHighPt primary dataset in RECO format from the 2.76 TeV Pb-Pb run of 2011 (/HIHighPt/HIRun2011-15Apr2013-v1/RECO). CERN Open Data Portal. DOI:10.7483/OPENDATA.M2XV.K3B0
Dataset Collision Heavy-ion physics CMS 2.76TeV PbPb CERN-LHC
HIHighPt primary dataset from the 2.76 TeV Pb-Pb run of 2011.
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
docker.io/cmsopendata/cmssw_4_4_7-slc5_amd64_gcc434:latest
gitlab-registry.cern.ch/cms-cloud/cmssw-docker-opendata/cmssw_4_4_7-slc5_amd64_gcc434:latest
Data taking / HLT
The collision data were assigned to different RAW datasets using the following HLT configuration.
Data processing / RECO
This primary AOD dataset was processed from the RAW dataset by the following step:
Step: RECO
Release: CMSSW_4_4_5_patch1
Global tag: GR_P_V27A::All
Configuration file for RECO step reco_HIRun2011
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_HIDiJet55
HLT_HIDoublePhoton10
HLT_HIDoublePhoton15
HLT_HIDoublePhoton20
HLT_HIFullTrack12_L1Central
HLT_HIFullTrack12_L1Peripheral
HLT_HIFullTrack14_L1Central
HLT_HIFullTrack14_L1Peripheral
HLT_HIFullTrack20_L1Central
HLT_HIFullTrack20_L1Peripheral
HLT_HIFullTrack25_L1Central
HLT_HIFullTrack25_L1Peripheral
HLT_HIJet55
HLT_HIJet65
HLT_HIJet65_Jet55
HLT_HIJet80
HLT_HIJet95
HLT_HIJetE30_NoBPTX
HLT_HIJetE50_NoBPTX3BX_NoHaloHLT_HIMET120
HLT_HIMET200
HLT_HIMET220
HLT_HIPhoton10_Photon15
HLT_HIPhoton15_Photon20
HLT_HISinglePhoton15
HLT_HISinglePhoton20
HLT_HISinglePhoton30
HLT_HISinglePhoton40
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
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
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.