/DoubleMuParked/Run2012B-22Jan2013-v1/AOD, CMS collaboration
Cite as: CMS collaboration (2017). DoubleMuParked primary dataset in AOD format from Run of 2012 (/DoubleMuParked/Run2012B-22Jan2013-v1/AOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.YLIC.86ZZ
DoubleMuParked primary dataset in AOD format from RunB of 2012. Run period from run number 193833 to 196531.
This dataset contains all runs from 2012 RunB. 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 the presence of at least two high-energy muons in the event.
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_53_V18::All
Configuration file for RECO step reco_2012B_DoubleMuParked
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:
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 in
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.