QEE Hlt2 and Sprucing lines for ZMuMu without MuID

To facilitate background studies, adding in two Hlt2 lines (and two passthrough-Spruceing lines) investigating Z->mumu decays where one or both muons do not require IS_MUON.

Minor affectations of the builder structure for the existing lines of:
Hlt2QEE_ZToMuMu
Hlt2QEE_DiMuonSameSign
SpruceQEE_ZToMuMu
SpruceQEE_DiMuonSameSign

New Lines are:
Hlt2QEE_ZToMuMu_SingleNoMuID
Hlt2QEE_ZToMuMu_DoubleNoMuID
SpruceQEE_ZToMuMu_SingleNoMuID
SpruceQEE_ZToMuMu_DoubleNoMuID

Efficiencies on 5k Z->mumu MC: (Denominator CanRecoChildren, =Muons{eta in LHCb Acceptance + Charged Long tracks})

Line:	 Hlt2QEE_ZToMuMuDecision                       	 Efficiency:	 0.885 +/- 0.012
Line:	 Hlt2QEE_ZToMuMu_DoubleNoMuIDDecision          	 Efficiency:	 0.959 +/- 0.008
Line:	 Hlt2QEE_ZToMuMu_SingleNoMuIDDecision          	 Efficiency:	 0.919 +/- 0.011

Rates on 25k hlt1-filtered MinBias:

Line:	 Hlt2QEE_ZToMuMuDecision               	 Incl: 0.0 +/- 0.0 kHz,	Excl: 0.0 +/- 0.0 kHz
Line:	 Hlt2QEE_ZToMuMu_DoubleNoMuIDDecision  	 Incl: 0.0 +/- 0.0 kHz,	Excl: 0.0 +/- 0.0 kHz
Line:	 Hlt2QEE_ZToMuMu_SingleNoMuIDDecision  	 Incl: 0.0 +/- 0.0 kHz,	Excl: 0.0 +/- 0.0 kHz

Sprucing Retention on 1k Z->mumu MC: (Should be passthrough currently, just checking)

Chain:   Hlt2QEE_ZToMuMu              -> SpruceQEE_ZToMuMu                Events: 1000->260->260  Retention: 1.000
Chain:   Hlt2QEE_ZToMuMu_SingleNoMuID -> SpruceQEE_ZToMuMu_SingleNoMuID   Events: 1000->281->281  Retention: 1.000
Chain:   Hlt2QEE_ZToMuMu_DoubleNoMuID -> SpruceQEE_ZToMuMu_DoubleNoMuID   Events: 1000->304->304  Retention: 1.000

ToDo:

• Hlt2 Efficiencies
• Hlt2 Rates
• Spruce Retention

added DPA-WP1 RTA qee labels

assigned to @lugrazet

changed the description

marked the checklist item Hlt2 Efficiencies as completed

marked the checklist item Spruce Retention as completed

To verify retention is actually selecting exactly the same events instead of 'no selection' or some issue with how we are testing it, increased the muon_pt cut required on the sprucing lines from 3 GeV to 15 GeV and verified that the retention dropped, which it did as follows.

Chain:   Hlt2QEE_ZToMuMu              -> SpruceQEE_ZToMuMu                Events: 1000->260->251  Retention: 0.965
Chain:   Hlt2QEE_ZToMuMu_SingleNoMuID -> SpruceQEE_ZToMuMu_SingleNoMuID   Events: 1000->281->268  Retention: 0.954
Chain:   Hlt2QEE_ZToMuMu_DoubleNoMuID -> SpruceQEE_ZToMuMu_DoubleNoMuID   Events: 1000->304->280  Retention: 0.924

changed the description

added 60 commits

• e3e0b2ac...8202607a - 58 commits from branch master
• 5c723cb0 - Initial draft of Hlt2+Spruce MuID lines
• d10459ca - Minor function naming changed

Compare with previous version

Re: Rates, we expect not to be able to see the Z lines in even 50k of Hlt1-filtered MinBias (see: !1989 (comment 6324135)), however we can be confident that the builders are working as expected via the fact that the efficiency for the Z->mumu line matches that calculated previously (0.889 +/- 0.027 on a slightly different amount of data) (see: !1989 (comment 6324192))

marked the checklist item Hlt2 Rates as completed

Hi @dzuliani, as QEE's co-subconvener for Trigger, offline processing and jets, would you like to give this MR a quick once-over before I move to asking the WorkPackages with this? I have discussed the necessity for these lines with @rjhunter offline a few times, but he is on holiday and I don't see a need to postpone these.

I think the behaviour of these lines and the implementation are working as expected and quite simple.

Hi @mvesteri, here's the Z NoMuID lines we discussed, hopefully the description is clear enough, would you like to make any comments before I pass it onto the shifter?

added 1 commit

• d50a6e3b - prescales added

Compare with previous version

resolved all threads

approved this merge request

marked this merge request as ready

Hi @frodrigu, I've run these new lines past my WG (QEE) and RTA WP3, could we get a ci-test?