Difference: TagAndProbe (1 vs. 25)

Revision 25
10 Mar 2010 - Main.SarahHeim
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Idea of study

  1. Get trigger efficiency plots (p.ex. pT) from Z->ee tag and probe (with single top quark cuts)
Line: 133 to 133
 

3 c) Single Top Root Analysis

what calls what?
  • script
    ./scripts/run_triggerTagProbeEfficiency.sh 1551 topmix electron recon
    calls
Changed:
<
<
  • bin/Trigger/TriggerTagProbeEfficiencyElectron.cpp calls
>
>
  • bin/Trigger/TriggerTagProbeEfficiencyElectron.cpp (instantiates object of class AnalysisMain), calls
 
  • src/Cuts?Weights/TagProbeWeight.cpp
Procedure
  • take text file (table with efficiencies) and plug into src/Cuts/Weights/TagProbeWeight.cpp, compile
Revision 24
12 Jan 2010 - Main.SarahHeim
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Idea of study

  1. Get trigger efficiency plots (p.ex. pT) from Z->ee tag and probe (with single top quark cuts)
Line: 136 to 136
 
  • bin/Trigger/TriggerTagProbeEfficiencyElectron.cpp calls
  • src/Cuts?Weights/TagProbeWeight.cpp
Procedure
Changed:
<
<
  • take text file (table with efficiencies) and plug into src/Cuts?Weights/TagProbeWeight.cpp, compile
>
>
  • take text file (table with efficiencies) and plug into src/Cuts/Weights/TagProbeWeight.cpp, compile
 
  • run ./scripts/run_triggerTagProbeEfficiency.sh 1551 topmix electron recon
  • run macros/trigger/tagProbeEfficiency
    bin/efficiency.x config/kinematic/electron.general.1551.config
Line: 146 to 146
  Procedure:
  • run TagProbe or use sarah10, run Insitu Performance to get efficiency matrix & distributions after trigger
  • run script (databasetext), which calls InsituAccessToolTester to get table of matrix
Changed:
<
<
  • put table into Performance_ClosureTestUgly algo, compile, run again to get weighted distribution
>
>
  • put table into Performance_ClosureTestUgly algo, COMPILE, run again to get weighted distribution
 
  • run macro for plotting/comparing weighted distribution and distribution after trigger (and normalized comparisons)
=> use good naming convention!!! (it must be clear which database comes from which input file to avoid confusion! also try to mark chosen options) => three to four joboptions...
Line: 157 to 157
 
  • run TagProbe or use sarah10, run Insitu Performance to get efficiency matrix for 2D matrix
  • run Insitu Performance to get efficiency matrix for 1D matrix
  • run script (databasetextMultiply), which calls InsituAccessToolMultiply to get table of multiplied matrix (not scaled yet)
Changed:
<
<
  • run Insitu Performance_ClosureTestUgly to get monitoring plots with weighted distribution and after trigger
>
>
  • plug table into Insitu Performance_ClosureTestUgly , COMPILE, then run it to get monitoring plots with weighted distribution and after trigger
 
  • run script makeScaleFactorMultiplication.C to get Scalefactor, plug into table of multiplied matrix

  • should probably do closure test (Performance_ClosureTestUgly to get weighted distribution and after trigger, run macro for plotting/comparing weighted distribution and distribution after trigger (and normalized comparisons))
Revision 23
12 Jan 2010 - Main.SarahHeim
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Idea of study

  1. Get trigger efficiency plots (p.ex. pT) from Z->ee tag and probe (with single top quark cuts)
Line: 111 to 111
 
  • Probe: 15 GeV
  • plotted over reco pT, but required truth matching
Changed:
<
<

3. SingleTopRootAnalysis, MC Trigger Efficiency

>
>

3.a) SingleTopRootAnalysis, MC Trigger Efficiency

 
  • Tight Electrons 10 Gev, Eta< 2.47
  • Jet cuts 30 for first two, then 15
  • Trigger efficiency EF_e20i_loose wrt Tight Electron
Line: 124 to 124
  => not so good (turn on means adding everything up above a certain threshold), better use:
  • macros/trigger/tagProbeEfficiency
    bin/efficiency.x config/kinematic/electron.general.1551.config
Changed:
<
<

4. SingleTopRootAnalysis, Tag and Probe

>
>

3.b) SingleTopRootAnalysis, Tag and Probe

 
  • have to weight events according to efficiency from (1.)
  • ./scripts/run_triggerTagProbeEfficiency.sh 1551 topmix electron recon
  • for comparison plot: root, .L plotHistosSum.C, makePlots(). better: plotHistosRegional.C
  • root: root /rooms/living/ntuples/single_top/TopPhysDPDMaker/MC08_1551/user.top.sgtopD3PD_rel1551.user.RichardHawkings.0108175.topmix_Egamma.AOD.v5_v03/user09.ArnaudLucotte.sgtopD3PD_rel1551.user.RichardHawkings.0108175.topmix_Egamma.AOD.v5_v03._00001.root

Added:
>
>

3 c) Single Top Root Analysis

what calls what?
  • script
    ./scripts/run_triggerTagProbeEfficiency.sh 1551 topmix electron recon
    calls
  • bin/Trigger/TriggerTagProbeEfficiencyElectron.cpp calls
  • src/Cuts?Weights/TagProbeWeight.cpp
Procedure
  • take text file (table with efficiencies) and plug into src/Cuts?Weights/TagProbeWeight.cpp, compile
  • run ./scripts/run_triggerTagProbeEfficiency.sh 1551 topmix electron recon
  • run macros/trigger/tagProbeEfficiency
    bin/efficiency.x config/kinematic/electron.general.1551.config
    (plug in input file, which is outputy file from script above, choose output file names/directory (have to create it)
 

4. Closure Test

Procedure:
  • run TagProbe or use sarah10, run Insitu Performance to get efficiency matrix & distributions after trigger
Revision 22
11 Jan 2010 - Main.SarahHeim
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Idea of study

  1. Get trigger efficiency plots (p.ex. pT) from Z->ee tag and probe (with single top quark cuts)
Line: 127 to 127
 

4. SingleTopRootAnalysis, Tag and Probe

  • have to weight events according to efficiency from (1.)
  • ./scripts/run_triggerTagProbeEfficiency.sh 1551 topmix electron recon
Changed:
<
<
  • for comparison plot: root, .L plotHistosSum.C, makePlots().
>
>
  • for comparison plot: root, .L plotHistosSum.C, makePlots(). better: plotHistosRegional.C
 
  • root: root /rooms/living/ntuples/single_top/TopPhysDPDMaker/MC08_1551/user.top.sgtopD3PD_rel1551.user.RichardHawkings.0108175.topmix_Egamma.AOD.v5_v03/user09.ArnaudLucotte.sgtopD3PD_rel1551.user.RichardHawkings.0108175.topmix_Egamma.AOD.v5_v03._00001.root

4. Closure Test

Changed:
<
<
So far:
>
>
Procedure:
 
  • run TagProbe or use sarah10, run Insitu Performance to get efficiency matrix & distributions after trigger
  • run script (databasetext), which calls InsituAccessToolTester to get table of matrix
  • put table into Performance_ClosureTestUgly algo, compile, run again to get weighted distribution
Line: 140 to 140
  => three to four joboptions... => need to use the same options in both Performance joboptions!!!
Added:
>
>

5. 3D matrix out of 2D and 1D

Procedure:
  • run TagProbe or use sarah10, run Insitu Performance to get efficiency matrix for 2D matrix
  • run Insitu Performance to get efficiency matrix for 1D matrix
  • run script (databasetextMultiply), which calls InsituAccessToolMultiply to get table of multiplied matrix (not scaled yet)
  • run Insitu Performance_ClosureTestUgly to get monitoring plots with weighted distribution and after trigger
  • run script makeScaleFactorMultiplication.C to get Scalefactor, plug into table of multiplied matrix

  • should probably do closure test (Performance_ClosureTestUgly to get weighted distribution and after trigger, run macro for plotting/comparing weighted distribution and distribution after trigger (and normalized comparisons))
 

Issues

  • Think about bias!
  • overlap removal for D3PD? (some objects are identified both as electron and jet)
Revision 21
11 Jan 2010 - Main.SarahHeim
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Idea of study

  1. Get trigger efficiency plots (p.ex. pT) from Z->ee tag and probe (with single top quark cuts)
Line: 24 to 24
 
  • e22i OR e55 OR mu20

2. Cuts and Triggers implemented
Added:
>
>
  • require Event trigger, Tag trigger
 
  • isEM medium (?) not for now
Changed:
<
<
  • pT > 30
>
>
  • pt(probe) > 10, pt(tag) > 20 GeV
 
  • eta < 2.5
Changed:
<
<
  • delta(R) < 0.2
  • no crack (probe)

  • e22i (?)
>
>
  • probe out of cracks
 
  • for v14 & v15 dataset (mc08.106050.PythiaZee_1Lepton.recon.AOD.e347_s462_s520_r808/):
    L1_EM18, L2_e20i_loose, EF_e20i_loose
Revision 20
09 Jan 2010 - Main.SarahHeim
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Idea of study

  1. Get trigger efficiency plots (p.ex. pT) from Z->ee tag and probe (with single top quark cuts)
Line: 135 to 135
 

4. Closure Test

So far:
  • run TagProbe or use sarah10, run Insitu Performance to get efficiency matrix & distributions after trigger
Changed:
<
<
  • run Insitu AccessToolTester and then the script to get table of matrix
>
>
  • run script (databasetext), which calls InsituAccessToolTester to get table of matrix
 
  • put table into Performance_ClosureTestUgly algo, compile, run again to get weighted distribution
  • run macro for plotting/comparing weighted distribution and distribution after trigger (and normalized comparisons)
=> use good naming convention!!! (it must be clear which database comes from which input file to avoid confusion! also try to mark chosen options)
Revision 19
07 Jan 2010 - Main.SarahHeim
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Idea of study

  1. Get trigger efficiency plots (p.ex. pT) from Z->ee tag and probe (with single top quark cuts)
Line: 132 to 132
 
  • for comparison plot: root, .L plotHistosSum.C, makePlots().
  • root: root /rooms/living/ntuples/single_top/TopPhysDPDMaker/MC08_1551/user.top.sgtopD3PD_rel1551.user.RichardHawkings.0108175.topmix_Egamma.AOD.v5_v03/user09.ArnaudLucotte.sgtopD3PD_rel1551.user.RichardHawkings.0108175.topmix_Egamma.AOD.v5_v03._00001.root

Changed:
<
<

>
>

4. Closure Test

So far:
  • run TagProbe or use sarah10, run Insitu Performance to get efficiency matrix & distributions after trigger
  • run Insitu AccessToolTester and then the script to get table of matrix
  • put table into Performance_ClosureTestUgly algo, compile, run again to get weighted distribution
  • run macro for plotting/comparing weighted distribution and distribution after trigger (and normalized comparisons)
=> use good naming convention!!! (it must be clear which database comes from which input file to avoid confusion! also try to mark chosen options) => three to four joboptions... => need to use the same options in both Performance joboptions!!!
 

Issues

  • Think about bias!
Line: 146 to 154
 
  • is turnon curve shape important to be modelled right?
  • Isolated/Unisolated electrons in topmix sample does not really make a difference for higher pT (above turnon curve)

Added:
>
>

Adding new algorithm to InsituEgammaPerformance

Need to go to src/components/InsituEGammaPerformance_entries.cxx and add new algo three times ( in this case)

 

Revision 18
12 Dec 2009 - Main.SarahHeim
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Idea of study

  1. Get trigger efficiency plots (p.ex. pT) from Z->ee tag and probe (with single top quark cuts)
Line: 108 to 108
 

  • GRID commands:
    pathena ElectronID_TagAndProbe_Zee_SelectionGRIDSarah1.py --inDS mc08.106050.PythiaZee_1Lepton.recon.AOD.e347_s462_s520_r808 --outDS user09.SarahHeim.mc08.106050.PythiaZeeTP.InsituDPD.GRIDSarah1a.pool.root
Changed:
<
<
pathena ElectronID_Zee_PerformanceGRIDSarah1.py --inDS user09.SarahHeim.mc08.106050.PythiaZeeTP.InsituDPD.GRIDSarah1a.pool.root --outDS user09.SarahHeim.ZeeTP.ElectronID_Zee_Monitoring_Output.GRIDSarah1a.root --extOutFile EgammaID_Zee_RootDatabase.tp.Sarah1a.root
>
>
pathena ElectronID_Zee_PerformanceGRIDSarah1.py --inDS user09.SarahHeim.mc08.106050.PythiaZeeTP.InsituDPD.GRIDSarah10.pool.root --outDS user09.SarahHeim.ZeeTP.ElectronID_Zee_Monitoring_Output.GRIDSarah1a.root --extOutFile EgammaID_Zee_RootDatabase.tp.Sarah1a.root
 

2. Single Electron => also nice turn-on curve

  • Probe: 15 GeV
  • plotted over reco pT, but required truth matching
Revision 17
07 Dec 2009 - Main.SarahHeim
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Idea of study

  1. Get trigger efficiency plots (p.ex. pT) from Z->ee tag and probe (with single top quark cuts)
Line: 123 to 123
 
  • ./scripts/run_triggerEfficiency.sh 1551 topmix electron recon
  • in macros/trigger/turnon:
    bin/TurnOnBin.x config/v1551/general.1551.config config/v1551/electron.1.config
Changed:
<
<
>
>
=> not so good (turn on means adding everything up above a certain threshold), better use:
  • macros/trigger/tagProbeEfficiency
    bin/efficiency.x config/kinematic/electron.general.1551.config
 

4. SingleTopRootAnalysis, Tag and Probe

  • have to weight events according to efficiency from (1.)
  • ./scripts/run_triggerTagProbeEfficiency.sh 1551 topmix electron recon
  • for comparison plot: root, .L plotHistosSum.C, makePlots().
Added:
>
>
  • root: root /rooms/living/ntuples/single_top/TopPhysDPDMaker/MC08_1551/user.top.sgtopD3PD_rel1551.user.RichardHawkings.0108175.topmix_Egamma.AOD.v5_v03/user09.ArnaudLucotte.sgtopD3PD_rel1551.user.RichardHawkings.0108175.topmix_Egamma.AOD.v5_v03._00001.root
 

Revision 16
01 Dec 2009 - Main.SarahHeim
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Idea of study

  1. Get trigger efficiency plots (p.ex. pT) from Z->ee tag and probe (with single top quark cuts)
Line: 140 to 140
 
  • How does Insitu calculate uncertainties on bins?
  • difference between MCParticles and other Particles in SingleTopRootAnalysis
  • What is TreeEventWeight in comparison to (Output)!EventWeight and GlobalEventWeight ?
Added:
>
>
  • is turnon curve shape important to be modelled right?
  • Isolated/Unisolated electrons in topmix sample does not really make a difference for higher pT (above turnon curve)
 

Revision 15
30 Nov 2009 - Main.SarahHeim
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Idea of study

  1. Get trigger efficiency plots (p.ex. pT) from Z->ee tag and probe (with single top quark cuts)
Line: 49 to 49
 
"In general, what is in the release since 15.5 is safe (ie. you don't even need to check out anything!) If you want to have latest versions of the package, you will have to
Changed:
<
<
chekc out some packages.
>
>
check out some packages.
  To avoid confusions, on this twiki: https://twiki.cern.ch/twiki/bin/view/AtlasProtected/InsituEGammaPerformance#Release_15_5_X
Line: 105 to 105
 
  • turn on curve better for ElectronTight than for ElectronLoose (I guess because of QCD background)

  • good result: TrigEF_wrt_EgammaTight_TP_Pt_Efficiency in user09.SarahHeim.ZeeTP.Monitoring.Grid.s520_r808.root
Added:
>
>

  • GRID commands:
    pathena ElectronID_TagAndProbe_Zee_SelectionGRIDSarah1.py --inDS mc08.106050.PythiaZee_1Lepton.recon.AOD.e347_s462_s520_r808 --outDS user09.SarahHeim.mc08.106050.PythiaZeeTP.InsituDPD.GRIDSarah1a.pool.root
    pathena ElectronID_Zee_PerformanceGRIDSarah1.py --inDS user09.SarahHeim.mc08.106050.PythiaZeeTP.InsituDPD.GRIDSarah1a.pool.root --outDS user09.SarahHeim.ZeeTP.ElectronID_Zee_Monitoring_Output.GRIDSarah1a.root --extOutFile EgammaID_Zee_RootDatabase.tp.Sarah1a.root
 

2. Single Electron => also nice turn-on curve

  • Probe: 15 GeV
  • plotted over reco pT, but required truth matching
Changed:
<
<

3. SingleTopRootAnalysis, MC Trigger Efficiency

>
>

3. SingleTopRootAnalysis, MC Trigger Efficiency

 
  • Tight Electrons 10 Gev, Eta< 2.47
  • Jet cuts 30 for first two, then 15
  • Trigger efficiency EF_e20i_loose wrt Tight Electron
  • reconstructed electron - what about truth info? (like in Single Electron)
  • What is MC electron?

Added:
>
>
  • ./scripts/run_triggerEfficiency.sh 1551 topmix electron recon
  • in macros/trigger/turnon:
    bin/TurnOnBin.x config/v1551/general.1551.config config/v1551/electron.1.config

4. SingleTopRootAnalysis, Tag and Probe

  • have to weight events according to efficiency from (1.)
  • ./scripts/run_triggerTagProbeEfficiency.sh 1551 topmix electron recon
  • for comparison plot: root, .L plotHistosSum.C, makePlots().

 

Issues

  • Think about bias!
Revision 14
24 Nov 2009 - Main.SarahHeim
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Idea of study

  1. Get trigger efficiency plots (p.ex. pT) from Z->ee tag and probe (with single top quark cuts)
Line: 119 to 119
 

Issues

  • Think about bias!
Changed:
<
<
  • overlap removal for D3PD?
>
>
  • overlap removal for D3PD? (some objects are identified both as electron and jet)
 
  • which bins for database, which triggers?
  • should I start with a pure single top sample before using topmix?
  • how would topmix work? -> background removal? channels separate or together?
  • How does Insitu calculate uncertainties on bins?
Changed:
<
<
  • cvs commit: need author rights? (Insufficient Karma???)
>
>
  • difference between MCParticles and other Particles in SingleTopRootAnalysis
  • What is TreeEventWeight in comparison to (Output)!EventWeight and GlobalEventWeight ?
 

Revision 13
23 Nov 2009 - Main.SarahHeim
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Idea of study

  1. Get trigger efficiency plots (p.ex. pT) from Z->ee tag and probe (with single top quark cuts)
Line: 110 to 110
 
  • plotted over reco pT, but required truth matching

3. SingleTopRootAnalysis, MC Trigger Efficiency

Changed:
<
<
  • Tight Electrons 15 Gev, Eta< 2.47
>
>
  • Tight Electrons 10 Gev, Eta< 2.47
 
  • Jet cuts 30 for first two, then 15
  • Trigger efficiency EF_e20i_loose wrt Tight Electron
  • reconstructed electron - what about truth info? (like in Single Electron)
Revision 12
23 Nov 2009 - Main.SarahHeim
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Idea of study

  1. Get trigger efficiency plots (p.ex. pT) from Z->ee tag and probe (with single top quark cuts)
Line: 107 to 107
 
  • good result: TrigEF_wrt_EgammaTight_TP_Pt_Efficiency in user09.SarahHeim.ZeeTP.Monitoring.Grid.s520_r808.root

2. Single Electron => also nice turn-on curve

  • Probe: 15 GeV
Added:
>
>
  • plotted over reco pT, but required truth matching

3. SingleTopRootAnalysis, MC Trigger Efficiency

  • Tight Electrons 15 Gev, Eta< 2.47
  • Jet cuts 30 for first two, then 15
  • Trigger efficiency EF_e20i_loose wrt Tight Electron
  • reconstructed electron - what about truth info? (like in Single Electron)
  • What is MC electron?
 

Issues

Line: 114 to 122
 
  • overlap removal for D3PD?
  • which bins for database, which triggers?
  • should I start with a pure single top sample before using topmix?
Added:
>
>
  • how would topmix work? -> background removal? channels separate or together?
 
  • How does Insitu calculate uncertainties on bins?
Added:
>
>
  • cvs commit: need author rights? (Insufficient Karma???)
 

Revision 11
19 Nov 2009 - Main.SarahHeim
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Idea of study

  1. Get trigger efficiency plots (p.ex. pT) from Z->ee tag and probe (with single top quark cuts)
Revision 10
18 Nov 2009 - Main.SarahHeim
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Idea of study

  1. Get trigger efficiency plots (p.ex. pT) from Z->ee tag and probe (with single top quark cuts)
Line: 31 to 31
 
  • no crack (probe)

  • e22i (?)
Changed:
<
<
  • for v15 dataset (mc08.106050.PythiaZee_1Lepton.recon.AOD.e347_s462_s520_r808/): L1_EM18, L2_e20i_loose, EF_e20i_loose
>
>
  • for v14 & v15 dataset (mc08.106050.PythiaZee_1Lepton.recon.AOD.e347_s462_s520_r808/):
    L1_EM18, L2_e20i_loose, EF_e20i_loose
 

  • background subtraction
Line: 76 to 77
 
  • Single top sample (D3PDs):

2. Top-D3PD study

  • TopMix: /rooms/living/ntuples/single_top/TopPhysDPDMaker/MC08_1451_t53_nooverlap/
Changed:
<
<
  • directories 8175X and 8176X, , where X = 1-3 is electron and X = 4 is
muon (see file /rooms/living/ntuples/list_mc08_v1451_t53_topmix.py. This also lists the original file/directory names from the grid)
>
>
  • directories 8175X and 8176X, , where X = 1-3 is electron and X = 4 is muon (see file /rooms/living/ntuples/list_mc08_v1451_t53_topmix.py. This also lists the original file/directory names from the grid)
 

Accessing the database

I am planning to do this in root, I managed to modify a root program to access the database outside athena (it is in the InsituExample root analysis package). Maybe I will then use the MSU single top package for my further analysis.
Line: 94 to 93
 

Single Electron

  • in Performance: dumpMC= true
  • in Performance: algoEfficiencyPerformance.InputProbesStoregateName = "ElectronIDProbeSingleElectronVsTrueVarContainer"
Added:
>
>
  • useRecoVariables = true (otherwise it plots reco efficiencies over true pT etc)
 

Tests

1. Tag and Probe=> nice turnon-curve for ElectronTight

Line: 103 to 103
 
  • SarahGrid1a (mc08.106050.PythiaZee_1Lepton.recon.AOD.e347_s462_s520_r808)
  • Cut study: Sarah$TagCut_$ProbeCut, to see if/how turn-on curve depends on cuts => does not really depend on Tag cut, above 25 though problems with statistics
  • turn on curve better for ElectronTight than for ElectronLoose (I guess because of QCD background)
Changed:
<
<

2. Single Electron => need more statistics

>
>

  • good result: TrigEF_wrt_EgammaTight_TP_Pt_Efficiency in user09.SarahHeim.ZeeTP.Monitoring.Grid.s520_r808.root

2. Single Electron => also nice turn-on curve

 
  • Probe: 15 GeV

Revision 9
17 Nov 2009 - Main.SarahHeim
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Idea of study

  1. Get trigger efficiency plots (p.ex. pT) from Z->ee tag and probe (with single top quark cuts)
Line: 101 to 101
 
  • mc08.106050.PythiaZee_1Lepton.recon.AOD.e347_s462_s520_r808_tid091523
  • Sarah1a-d (a without background fit, b with background fit, c, d other datasets)
  • SarahGrid1a (mc08.106050.PythiaZee_1Lepton.recon.AOD.e347_s462_s520_r808)
Changed:
<
<
  • Cut study: Sarah$TagCut_$ProbeCut, to see if/how turn-on curve depends on cuts
>
>
  • Cut study: Sarah$TagCut_$ProbeCut, to see if/how turn-on curve depends on cuts => does not really depend on Tag cut, above 25 though problems with statistics
 
  • turn on curve better for ElectronTight than for ElectronLoose (I guess because of QCD background)

2. Single Electron => need more statistics

  • Probe: 15 GeV
Revision 8
17 Nov 2009 - Main.SarahHeim
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Idea of study

  1. Get trigger efficiency plots (p.ex. pT) from Z->ee tag and probe (with single top quark cuts)
Line: 66 to 66
 
  • egammaInterfaces-00-00-55 (only if you use 15.5.X, not needed for 15.6.X)
  • egammaUtils-00-04-29 (only if you use 15.5.X, not needed for 15.6.X"
1523
Added:
>
>

Datasets

1. Insitu (AODs)

 
  • Z->ee: mc08.106050.PythiaZee_1Lepton.recon.AOD.e347_s462_r635/ : this is the v.14 reco (has ~2.5 Mio events)
  • or reco v15: mc08.106050.PythiaZee_1Lepton.recon.AOD.e347_s462_s520_r808/ (5.3 Mio events) => try using this one
Changed:
<
<
=> for first studies subset: mc08.106050.PythiaZee_1Lepton.recon.AOD.e347_s462_s520_r808_tid091523
>
>
=> for first studies subset: mc08.106050.PythiaZee_1Lepton.recon.AOD.e347_s462_s520_r808_tid091523 (407000 events)
 
  • TopMixingSample (D3PDs):
  • Single top sample (D3PDs):
Added:
>
>

2. Top-D3PD study

  • TopMix: /rooms/living/ntuples/single_top/TopPhysDPDMaker/MC08_1451_t53_nooverlap/
  • directories 8175X and 8176X, , where X = 1-3 is electron and X = 4 is
muon (see file /rooms/living/ntuples/list_mc08_v1451_t53_topmix.py. This also lists the original file/directory names from the grid)
 

Accessing the database

I am planning to do this in root, I managed to modify a root program to access the database outside athena (it is in the InsituExample root analysis package). Maybe I will then use the MSU single top package for my further analysis.
Line: 80 to 88
 

Useful links

Changed:
<
<

Tests

>
>

Important Options in Joboptions

 

Tag and Probe

  • Sarah1 :

Single Electron

  • in Performance: dumpMC= true
  • in Performance: algoEfficiencyPerformance.InputProbesStoregateName = "ElectronIDProbeSingleElectronVsTrueVarContainer"
Changed:
<
<

Think about bias

>
>

Tests

1. Tag and Probe=> nice turnon-curve for ElectronTight

  • Tag: 25, Probe 15 GeV
  • mc08.106050.PythiaZee_1Lepton.recon.AOD.e347_s462_s520_r808_tid091523
  • Sarah1a-d (a without background fit, b with background fit, c, d other datasets)
  • SarahGrid1a (mc08.106050.PythiaZee_1Lepton.recon.AOD.e347_s462_s520_r808)
  • Cut study: Sarah$TagCut_$ProbeCut, to see if/how turn-on curve depends on cuts
  • turn on curve better for ElectronTight than for ElectronLoose (I guess because of QCD background)

2. Single Electron => need more statistics

  • Probe: 15 GeV

Issues

  • Think about bias!
  • overlap removal for D3PD?
  • which bins for database, which triggers?
  • should I start with a pure single top sample before using topmix?
  • How does Insitu calculate uncertainties on bins?

 

Revision 7
16 Nov 2009 - Main.SarahHeim
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Idea of study

  1. Get trigger efficiency plots (p.ex. pT) from Z->ee tag and probe (with single top quark cuts)
Line: 74 to 74
 

Accessing the database

I am planning to do this in root, I managed to modify a root program to access the database outside athena (it is in the InsituExample root analysis package). Maybe I will then use the MSU single top package for my further analysis.
Added:
>
>
     ./APReader ElectronID_TP_GRIDSarah1.root ElectronAODCollection TrigEFwrtEgammaLooseTP ZeeTag-and-Probe O.Arnaez mc09Example Opt 

For tests, can also use "ElectronEfficiencyAccessToolTester.py"
 

Useful links

Tests

Added:
>
>

Tag and Probe

 
  • Sarah1 :
Added:
>
>

Single Electron

  • in Performance: dumpMC= true
  • in Performance: algoEfficiencyPerformance.InputProbesStoregateName = "ElectronIDProbeSingleElectronVsTrueVarContainer"
 

Think about bias

Revision 6
13 Nov 2009 - Main.SarahHeim
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Idea of study

  1. Get trigger efficiency plots (p.ex. pT) from Z->ee tag and probe (with single top quark cuts)
Line: 7 to 7
  =>new efficiency plot
  1. see if comparable to MC efficiency, or if different bins are necessary
Deleted:
<
<

Efficiencies

  1. Tag and Probe Efficiency
 

Bins

  • For now: Eta, P_T
  • Possible: Isolation, Phi...
Line: 40 to 36
 
  • background subtraction

Efficiencies

Changed:
<
<
>
>
  • Trigger Efficiencies wrt ElectronLoose, ElectronTight
  1. Tag and Probe: (No of probes that pass cuts and triggers and have a valid tag)/(no of probes that pass cuts and have a valid tag) (Tag is only there to reduce bias)
  2. Single Loop or Mc Truth Efficiency: (No of Electrons that pass cuts and triggers and are true)/(No of Electrons that pass cuts and are true)
 

Software

InsituEGammaPerformance package within athena framework (https://twiki.cern.ch/twiki/bin/view/AtlasProtected/InsituPerformance, https://twiki.cern.ch/twiki/bin/view/AtlasProtected/InsituEGammaPerformance)
Revision 5
12 Nov 2009 - Main.SarahHeim
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Idea of study

  1. Get trigger efficiency plots (p.ex. pT) from Z->ee tag and probe (with single top quark cuts)
Line: 7 to 7
  =>new efficiency plot
  1. see if comparable to MC efficiency, or if different bins are necessary
Added:
>
>

Efficiencies

  1. Tag and Probe Efficiency
 

Bins

  • For now: Eta, P_T
Line: 71 to 74
 
  • Single top sample (D3PDs):

Accessing the database

Changed:
<
<
I am planning to do this in root, I managed to modify a root program to access the database outside athena (it is in the InsituExample root analysis package)
>
>
I am planning to do this in root, I managed to modify a root program to access the database outside athena (it is in the InsituExample root analysis package). Maybe I will then use the MSU single top package for my further analysis.
 

Useful links

Revision 4
12 Nov 2009 - Main.SarahHeim
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Idea of study

  1. Get trigger efficiency plots (p.ex. pT) from Z->ee tag and probe (with single top quark cuts)
Line: 25 to 25
 
  • e22i OR e55 OR mu20

2. Cuts and Triggers implemented
Changed:
<
<
  • isEM medium (?)
>
>
  • isEM medium (?) not for now
 
  • pT > 30
  • eta < 2.5
  • delta(R) < 0.2
Line: 34 to 34
 
  • e22i (?) * for v15 dataset (mc08.106050.PythiaZee_1Lepton.recon.AOD.e347_s462_s520_r808/): L1_EM18, L2_e20i_loose, EF_e20i_loose
Added:
>
>
  • background subtraction

Efficiencies

 

Software

InsituEGammaPerformance package within athena framework (https://twiki.cern.ch/twiki/bin/view/AtlasProtected/InsituPerformance, https://twiki.cern.ch/twiki/bin/view/AtlasProtected/InsituEGammaPerformance)
Line: 59 to 63
 
  • HEAD of InsituTools (InsituTools-00-01-08 )
  • egammaInterfaces-00-00-55 (only if you use 15.5.X, not needed for 15.6.X)
  • egammaUtils-00-04-29 (only if you use 15.5.X, not needed for 15.6.X"
Changed:
<
<

Data sets

>
>
1523
 
  • Z->ee: mc08.106050.PythiaZee_1Lepton.recon.AOD.e347_s462_r635/ : this is the v.14 reco (has ~2.5 Mio events)
  • or reco v15: mc08.106050.PythiaZee_1Lepton.recon.AOD.e347_s462_s520_r808/ (5.3 Mio events) => try using this one
Added:
>
>
=> for first studies subset: mc08.106050.PythiaZee_1Lepton.recon.AOD.e347_s462_s520_r808_tid091523
 
  • TopMixingSample (D3PDs):
  • Single top sample (D3PDs):
Changed:
<
<

Accessing the database

>
>

Accessing the database

  I am planning to do this in root, I managed to modify a root program to access the database outside athena (it is in the InsituExample root analysis package)
Changed:
<
<

Useful links

>
>

Useful links

 
Added:
>
>

Tests

  • Sarah1 :

Think about bias

 

-- SarahHeim - 11 Nov 2009 \ No newline at end of file
Revision 3
12 Nov 2009 - Main.SarahHeim
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Idea of study

  1. Get trigger efficiency plots (p.ex. pT) from Z->ee tag and probe (with single top quark cuts)
Line: 32 to 32
 
  • no crack (probe)

  • e22i (?)
Added:
>
>
* for v15 dataset (mc08.106050.PythiaZee_1Lepton.recon.AOD.e347_s462_s520_r808/): L1_EM18, L2_e20i_loose, EF_e20i_loose
 

Software

InsituEGammaPerformance package within athena framework (https://twiki.cern.ch/twiki/bin/view/AtlasProtected/InsituPerformance, https://twiki.cern.ch/twiki/bin/view/AtlasProtected/InsituEGammaPerformance)
Revision 2
12 Nov 2009 - Main.SarahHeim
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Idea of study

  1. Get trigger efficiency plots (p.ex. pT) from Z->ee tag and probe (with single top quark cuts)
Line: 57 to 58
 
  • egammaUtils-00-04-29 (only if you use 15.5.X, not needed for 15.6.X"

Data sets

Changed:
<
<
  • Z->ee: mc08.106050.PythiaZee_1Lepton.recon.AOD.e347_s462_r635/ : this is
the v.14 reco (has ~2.5 M events)
  • or reco v15: mc08.106050.PythiaZee_1Lepton.recon.AOD.e347_s462_s520_r808/
>
>
  • Z->ee: mc08.106050.PythiaZee_1Lepton.recon.AOD.e347_s462_r635/ : this is the v.14 reco (has ~2.5 Mio events)
  • or reco v15: mc08.106050.PythiaZee_1Lepton.recon.AOD.e347_s462_s520_r808/ (5.3 Mio events) => try using this one
 
  • TopMixingSample (D3PDs):
  • Single top sample (D3PDs):

Accessing the database

I am planning to do this in root, I managed to modify a root program to access the database outside athena (it is in the InsituExample root analysis package)
Added:
>
>

Useful links

 

-- SarahHeim - 11 Nov 2009
 
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