• Help
  •    
  • About
    • CERN Open Data
    • ALICE
    • ATLAS
    • CMS
    • LHCb
    • OPERA
    • Glossary

AllPhysics2760 (JetHI) primary dataset in RECO format from the 2.76 TeV proton-proton run of 2011 (/AllPhysics2760/Nov2011_HI-SD_JetHI-276TeV_ppRereco/RECO)

/AllPhysics2760/Nov2011_HI-SD_JetHI-276TeV_ppRereco/RECO, CMS collaboration

Cite as: CMS collaboration (2020). AllPhysics2760 (JetHI) primary dataset in RECO format from the 2.76 TeV proton-proton run of 2011 (/AllPhysics2760/Nov2011_HI-SD_JetHI-276TeV_ppRereco/RECO). CERN Open Data Portal. DOI:10.7483/OPENDATA.PBQN.WK8M

Dataset Collision Heavy-ion physics CMS 2.76TeV CERN-LHC


Description

AllPhysics2760 (JetHI) 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

Validated runs, full validation

Validated runs, muons only

Dataset characteristics

2375982 events. 67 files. 275.1 GB in total.

System details

GR_R_44_V15::All
CMSSW_4_4_7

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
This dataset is derived from /AllPhysics2760/Run2011A-v1/RAW. All trigger paths for that dataset are listed under /AllPhysics2760/Run2011A-16Jul2011-v1/RECO.

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

How to install the CMS Virtual Machine

Usage example for CMS 2011 heavy-ion data

File Indexes

{{$ctrlTbl.files = $ctrl.index_files.files; ""}} {{$ctrlTbl.totalItems = $ctrl.index_files.total; ""}}
Filename
Size
{{ file.key }}
{{ file.size | bytes }}
List Files Download Download Preview
Filename
Size
{{ file.key }}
{{ file.size | bytes }}
List Files Download Download Preview

Files

{{$ctrlTbl.files = $ctrl.files.files; ""}} {{$ctrlTbl.totalItems = $ctrl.files.total; ""}}
Filename
Size
{{ file.key }}
{{ file.size | bytes }}
List Files Download Download Preview
Filename
Size
{{ file.key }}
{{ file.size | bytes }}
List Files Download Download Preview

Disclaimer

The open data are released under the Creative Commons CC0 waiver. Neither 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.

  • © CERN, 2014–2021 ·
  • Terms of Use ·
  • Privacy Policy ·
  • Help ·
  • GitHub ·
  • Twitter ·
  • Email