AllPhysics2760 primary dataset in RECO format from the 2.76 TeV proton-proton run of 2011 (/AllPhysics2760/Run2011A-16Jul2011-v1/RECO)
/AllPhysics2760/Run2011A-16Jul2011-v1/RECO, CMS collaboration
Cite as: CMS collaboration (2020). AllPhysics2760 primary dataset in RECO format from the 2.76 TeV proton-proton run of 2011 (/AllPhysics2760/Run2011A-16Jul2011-v1/RECO). CERN Open Data Portal. DOI:10.7483/OPENDATA.V439.NXZC
Dataset Collision Heavy-ion physics CMS 2.76TeV pp CERN-LHC
Description
AllPhysics2760 primary dataset from the 2.76 TeV proton-proton run of 2011. These proton-proton data are at the same centre-of-mass energy and have a similar trigger menu to those in Pb-Pb collisions.
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
56168211 events. 1491 files. 6.0 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.
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_Jet20
HLT_Jet40
HLT_L1BscMinBiasORBptxPlusANDMinus
HLT_L1DoubleForJet32_EtaOpp
HLT_L1DoubleForJet8_EtaOpp
HLT_Mu0
HLT_Photon10_CaloIdVL
HLT_Photon15_CaloIdVL
HLT_PixelTracks_Multiplicity50_Loose
HLT_PixelTracks_Multiplicity60_Loose
HLT_PixelTracks_Multiplicity70_Loose
HLT_ZeroBiasPixel_SingleTrack
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
The open data are released under the Creative Commons CC0 waiver. Neither the experiment(s) ( CMS ) nor CERN endorse any works, scientific or otherwise, produced using these data. All releases will have a unique DOI that you are requested to cite in any applications or publications.
