Analysis Comparisons for Code Version 14.05.006

Run Over D3PDs using the MSU analysis code

The DPDPs are stored on the CERN cluster in the directory /rooms/living/ntuples/single_top/TopPhysDPDMaker/14.05.006/ The following samples were included in the analysis:

Signal: 5500, 5502 (note that there is no 5501 sample for v14.05.006)

Background: 5200, 5204, 6280, 6281, 6282, 6283, 7680, 7681, 7682, 7683, 7684, 7685, 7690, 7691, 7692, 7693, 7694, 7695, 7700, 7701, 7702, 7703, 7704, 7705

Unlike v13.0.30, all input files ran without crashing and it was not necessary to comment out any of them in the list files.

The output files from the MSU analysis code are stored in the CERN cluster in the directory /home/root_files/single_top/TopPhysDPDMaker/14.05.006/EarlyData/ The samples in the directory unweighted were processed without an event weight. The samples in the directory weighted were weighted so that the number of events corresponds to a luminosity of 100 pb-1. The weighted samples were used for this analysis.

Merge Signal and Background Files

This comparison was done for the electron chain. Note that "Electron" is replaced by "Muon" in the file names for the muon chain.

The merging was done using the !MergeTrees.C routine located in the macros/TreeManipulation directory in the MSU analysis package and the merged files are in the directory /home/root_files/single_top/TopPhysDPDMaker/14.05.006/EarlyData/merged/.

The 2 signal files were combined into a single signal file called Topology.!SingleTop.1405006.FDR2.Electron.Signal.root. The 24 background files were combined into a signal background file called Topology.!SingleTop.1405006.FDR2.Electron.Background.root.

Division into Training, Validation, and Yield Samples

The merged files were then divided into training, validation, and yield samples, which was achieved by setting the Split flag to 1 in the config file when running !MergeTrees.C. The events were split according to their order in the merged file. For example, the first event was categorized as training, the second as validation, the third as yield, the fourth as training, and so on. Functionality to randomly assign variables to the different categories will be added in the future.

Events with negative weights were excluded from the Training sample to retain compatibility with SPR, which cannot handle negative weights. Validation samples both with and without events with negative weights were made. The files without events having negative weights are signified by the label !NoNeg.

Put Signal and Background Trees into One File

In order to be compatible with the TMVA input requirements, the signal tree from the signal file and the background tree from the background file were placed in one file. This was accomplished by the routine located in the macros/TreeManipulation directory. This routine is run, for example, as
python \
   -S /home/root_files/single_top/TopPhysDPDMaker/14.05.006/EarlyData/merged/Topology.SingleTop.1405006.FDR2.Electron.Signal.root \
   -B /home/root_files/single_top/TopPhysDPDMaker/14.05.006/EarlyData/merged/Topology.SingleTop.1405006.FDR2.Electron.Background.root \
   -t TopTree \
   -o /home/root_files/single_top/TopPhysDPDMaker/14.05.006/EarlyData/CombineSigBkg/Topology.SingleTop.1405006.FDR2.Electron.root \

Variables Used

For comparison purposes, only the following variables were considered for training: HT, Jet1Pt =, =DeltaRJet1Jet2, !WTransverseMass.

Multivariate Programs

The multivariate analysis was done using both TMVA and SPR.

-- PatRyan - 16 Apr 2009
Topic revision: r6 - 16 Oct 2009, TomRockwell
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback