JetMETTauMonitor primary dataset in AOD format from RunB of 2010 (/JetMETTauMonitor/Run2010B-Apr21ReReco-v1/AOD)
/JetMETTauMonitor/Run2010B-Apr21ReReco-v1/AOD, CMS collaboration
Cite as: CMS collaboration (2014). JetMETTauMonitor primary dataset in AOD format from RunB of 2010 (/JetMETTauMonitor/Run2010B-Apr21ReReco-v1/AOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.WV7H.T2B8
Dataset Collision CMS 7TeV pp CERN-LHC
Description
JetMETTauMonitor primary dataset in AOD format from RunB of 2010
The list of validated runs, which must be applied to all analyses, can be found in
CMS list of validated runs Cert_136033-149442_7TeV_Apr21ReReco_Collisions10_JSON_v2.txt
Dataset characteristics
10178530 events. 668 files. 1008.4 GiB in total.System details
FT_R_42_V10A::AllCMSSW_4_2_8
Recommended container image for analyses is available in the following locations (see guide):
docker.io/cmsopendata/cmssw_4_2_8-slc5_amd64_gcc434:latestgitlab-registry.cern.ch/cms-cloud/cmssw-docker-opendata/cmssw_4_2_8-slc5_amd64_gcc434:latest
How were these data selected?
Dedicated primary dataset detector monitoring. Events stored in this primary dataset were selected because of presence of a low-energy central jet in the event, tau jets or high missing transverse energy.
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_2_1_patch1
Global tag: FT_R_42_V10A::All
The configuration file for RECO step can be generated with the cmsDriver command line script in the corresponding CMSSW release area:
cmsDriver.py reco -s RAW2DIGI,L1Reco,RECO --data --conditions FT_R_42_V10A::All --eventcontent AOD --no_exec --python reco_cmsdriver2010.py
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_HT50U
HLT_L1ETT140
HLT_L1Jet10U
HLT_L1Jet10U_NoBPTX
HLT_L1Jet6U
HLT_L1Jet6U_NoBPTX
HLT_L1MET20
HLT_L1SingleCenJet
HLT_L1SingleCenJet_NoBPTX
HLT_L1SingleForJet
HLT_L1SingleForJet_NoBPTX
HLT_L1SingleTauJet
HLT_L1SingleTauJet_NoBPTX
HLT_MET45
HLT_QuadJet15U
HLT_R010U_MR50U
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 Virtual Machine. See the instructions for setting up the Virtual Machine and getting started in
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.
