HIMinBiasUPC primary dataset in RECO format from the 2.76 TeV Pb-Pb run of 2011 (/HIMinBiasUPC/HIRun2011-12Jun2013-v1/RECO)
/HIMinBiasUPC/HIRun2011-12Jun2013-v1/RECO, CMS collaboration
Cite as: CMS collaboration (2020). HIMinBiasUPC primary dataset in RECO format from the 2.76 TeV Pb-Pb run of 2011 (/HIMinBiasUPC/HIRun2011-12Jun2013-v1/RECO). CERN Open Data Portal. DOI:10.7483/OPENDATA.U18S.LSSA
Dataset Collision Heavy-ion physics CMS 2.76TeV PbPb CERN-LHC
Description
HIMinBiasUPC 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
Dataset characteristics
29913768 events. 3191 files. 10.5 TiB in total.System details
GR_R_44_V15::AllCMSSW_4_4_7
Recommended container image for analyses is available in the following locations (see guide):
docker.io/cmsopendata/cmssw_4_4_7-slc5_amd64_gcc434:latestgitlab-registry.cern.ch/cms-cloud/cmssw-docker-opendata/cmssw_4_4_7-slc5_amd64_gcc434:latest
How were these data selected?
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_HIMinBiasUPC
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_HIBptxXOR
HLT_HICentral10
HLT_HICentralityVeto
HLT_HIL1Algo_BptxXOR_BSC_OR
HLT_HIL1CaloMonitor
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_PlusOrMinusPixel_SingleTrack
HLT_HIPhysics
HLT_HIRandom
HLT_HIUCC010
HLT_HIUCC015HLT_HIUPCNeuEG2Pixel_SingleTrack
HLT_HIUPCNeuEG5Pixel_SingleTrack
HLT_HIUPCNeuHcalHfEG2Pixel_SingleTrack
HLT_HIUPCNeuHcalHfEG5Pixel_SingleTrack
HLT_HIUPCNeuHcalHfMuPixel_SingleTrack
HLT_HIUPCNeuMuPixel_SingleTrack
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
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.
