Skip to content

WIP:Adding luminositytool for likelihood calculation.

Debottam Bakshi Gupta requested to merge dbakshig/athena:LHcalculation into master

This WIP is to investigate the likelihood for electron in Run 3 currently (also discussed in jira: https://its.cern.ch/jira/browse/ATR-18927). My motivation is to make a comparison between Run 2 and Run 3 likelihood selection output.

Run 2:
HLT_e5_lhloose_idperf                active: 20     run :20     PS: 20     raw: 20     accepted after PS and PT:20 rerun: 0
HLT_e5_lhloose_nod0                  active: 20     run :20     PS: 20     raw: 9      accepted after PS and PT:9  rerun: 0
HLT_e5_lhloose_nod0_idperf           active: 20     run :20     PS: 20     raw: 20     accepted after PS and PT:20 rerun: 0
chain: HLT_e5_lhmedium_nod0          active: 20     run :20     PS: 20     raw: 8      accepted after PS and PT:8  rerun: 0
HLT_e5_lhtight_idperf                active: 20     run :20     PS: 20     raw: 20     accepted after PS and PT:20 rerun: 0
HLT_e5_lhtight_nod0                  active: 20     run :20     PS: 20     raw: 7      accepted after PS and PT:7  rerun: 0
Run 3:
Chain name                   L1,      AfterPS,  step1     step2     step3     step4      Output
HLT_e5_lhloose_L1EM3          20        20        20        19        19        10         10
HLT_e5_lhmedium_L1EM3         20        20        20        19        19        0           0
HLT_e5_lhtight_L1EM3          20        20        20        19        19        0           0

In both cases the sample were used /eos/home-d/dbakshig/data17_13TeV.00339070.physics_Main/data17_13TeV.00339070.physics_Main.merge.DRAW_EGZ.f887_m1831._0152.1

Run 2 uses luminosity tool to use mu in the calculation of likelihood ratio so I tried similar in Run 3 https://gitlab.cern.ch/dbakshig/athena/-/blob/LHcalculation/Trigger/TrigHypothesis/TrigEgammaHypo/src/TrigEgammaPrecisionElectronHypoToolInc.cxx#L167 but I am always getting 0 for average mu do I need to add any flag to get correct average mu value? adding @fernando , @thrynova , @christos , @tamartin

Merge request reports

Loading