/BTau/Run2010A-Apr21ReReco-v1/AOD, CMS collaboration
Cite as: CMS collaboration (2019). BTau primary dataset in AOD format from RunA of 2010 (/BTau/Run2010A-Apr21ReReco-v1/AOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.OPKV.OXG0
BTau primary dataset in AOD format from RunA of 2010
This dataset contains all runs directed to it from 2010 RunA. The selection to BTau primary dataset was separated from JetMETTau primary dataset starting from run number 141950. The list of validated runs, which must be applied to all analyses, can be found in
Events stored in this primary dataset were selected because of presence of more than one isolated tau in the event, or because of presence of low-energy muons from b-quark decay.
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:
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:
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: