Jet primary dataset sample in RAW format from RunA of 2011 (from /Jet/Run2011A-v1/RAW)
/Jet/Run2011A-v1/RAW, CMS collaboration
Cite as: CMS collaboration (2019). Jet primary dataset sample in RAW format from RunA of 2011 (from /Jet/Run2011A-v1/RAW). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.DRTR.53Q8
Dataset Collision CMS 7TeV pp CERN-LHC
Description
A sample from Jet primary dataset in RAW format from RunA of 2011. Run range [163589,165121].
This dataset contains selected runs from 2011 RunA. The list of validated lumi sections, which must be applied to all analyses on events reconstructed from these data, can be found in
CMS list of validated runs Cert_160404-180252_7TeV_ReRecoNov08_Collisions11_JSON.txt
Dataset characteristics
2177197 events. 139 files. 405.8 GiB in total.System details
FT_53_LV5_AN1CMSSW_5_3_32
Recommended container image for analyses is available in the following locations (see guide):
docker.io/cmsopendata/cmssw_5_3_32-slc6_amd64_gcc472:latestgitlab-registry.cern.ch/cms-cloud/cmssw-docker-opendata/cmssw_5_3_32-slc6_amd64_gcc472:latest
How were these data selected?
Events stored in this primary dataset were selected because of the presence of at least one high-energy jet in the event.
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_DiJetAve100U
HLT_DiJetAve110
HLT_DiJetAve140U
HLT_DiJetAve150
HLT_DiJetAve15U
HLT_DiJetAve180U
HLT_DiJetAve190
HLT_DiJetAve240
HLT_DiJetAve30
HLT_DiJetAve300
HLT_DiJetAve300U
HLT_DiJetAve30U
HLT_DiJetAve370
HLT_DiJetAve50U
HLT_DiJetAve60
HLT_DiJetAve70U
HLT_DiJetAve80
HLT_Jet110
HLT_Jet150
HLT_Jet190
HLT_Jet240
HLT_Jet240_CentralJet30_BTagIP
HLT_Jet240_L1FastJet
HLT_Jet270_CentralJet30_BTagIP
HLT_Jet30
HLT_Jet300
HLT_Jet300_L1FastJet
HLT_Jet30_L1FastJet
HLT_Jet370
HLT_Jet370_L1FastJet
HLT_Jet370_NoJetID
HLT_Jet60
HLT_Jet60_L1FastJet
HLT_Jet80
HLT_Jet800
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?
These data are in RAW format and not directly usable in analysis. The reconstructed data reprocessed from these RAW data are included in the data of this record. The reconstruction step can be repeated with the configuration file below and the resulting AOD has been confirmed to be identical with the original one with comparison code available in Validation code to plot basic physics objects from AOD
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.
