/TTJets_FullLeptMGDecays_8TeV-madgraph/Summer12_DR53X-PU_RD1_START53_V7N-v1/AODSIM, CMS collaboration
Cite as: CMS collaboration (2017). Simulated dataset TTJets_FullLeptMGDecays_8TeV-madgraph in AODSIM format for 2012 collision data. CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.IXH4.KIR9
Dataset Simulated Standard Model Physics Top physics CMS 8TeV pp CERN-LHC
Simulated dataset TTJets_FullLeptMGDecays_8TeV-madgraph in AODSIM format for 2012 collision data.
See the description of the simulated dataset names in: About CMS simulated dataset names.
These simulated datasets correspond to the collision data collected by the CMS experiment in 2012.
docker.io/cmsopendata/cmssw_5_3_32-slc6_amd64_gcc472:latest
gitlab-registry.cern.ch/cms-cloud/cmssw-docker-opendata/cmssw_5_3_32-slc6_amd64_gcc472:latest
These data were generated in several steps (see also CMS Monte Carlo production overview):
Step
Release: CMSSW_5_2_6_patch1
Output dataset: /TTJets_FullLeptMGDecays_8TeV-madgraph/Summer12-START52_V9-v1/GEN
Step SIM
Release: CMSSW_5_2_6_patch1
Global Tag: START52_V9::All
Configuration file
for SIM
(link)
Output dataset: /TTJets_FullLeptMGDecays_8TeV-madgraph/Summer12-START52_V9-v1/GEN-SIM
Step RECO HLT
Release: CMSSW_5_3_10_patch1
Configuration file
for RECO
(link)
Configuration file
for HLT
(link)
Output dataset: /TTJets_FullLeptMGDecays_8TeV-madgraph/Summer12_DR53X-PU_RD1_START53_V7N-v1/AODSIM
To make these simulated data comparable with the collision data, pile-up events are added to the simulated event in this step.
The pile-up dataset is:
/MinBias_TuneZ2star_8TeV-pythia6/Summer12-START50_V13-v3/GEN-SIM
The generation and simulation of simulated Monte Carlo data has been validated through general CMS validation procedures.
You can access these data through the CMS Virtual Machine. See the instructions for setting up the Virtual Machine and getting started in
The open data are released under the Creative Commons CC0 waiver. Neither the experiment(s) ( 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.