Reoptimisation of Charm HLT2 selections for 2025

There some lines which potentially can be problematic due to their large bandwidth (BW) or rate. The idea will be to retune those lines/selections in benefit of the WG bandwidth consumption. For the different authors, if you want please comment directly on possible cause what could be done to improve (reduce rate/bandwidth) the selection.

Please also take a look at your line in the overlap matrix, and check how many lines overlap with your line. Is it possible to reduce/remove it?

Line	Problem	Module	Author	Possible cause
First 10 Charm lines with largest BW
Hlt2Charm_HccppToLcpPpKmPip_RSWSDecision	Line with largest BW: 200 Hz + 0.4 MB event size	hexaquarks	@ipolyako	Uses combiner without any DOCA, could add it help with event size and duplication?
Hlt2Charm_Lb0ToLcpPimPimPip_LcpToPpPimPipDecision	Large BW: 270 Hz + 0.32 MB event size	cbaryon_to_sl	@msaur @ziyiw	Cuts sound reasonable. Probably due to large combinatorics with 6 particle final state
Hlt2Charm_HcppToPpPpKs_LL_RSWSDecision	Large rate: 722 Hz	hexaquarks	@ipolyako	It looks like only an invariant mass cut is applied in the Hcpp builder - can more cuts be applied?
Hlt2Charm_HcpToPpPpKsPim_LL_RSWSDecision	Large rate: 593 Hz	hexaquarks	@ipolyako	Only an invariant mass cut is applied - a simple DOCA + quality vertex could help reduce rate, since it's a 4-track vertex
Hlt2Charm_Lb0ToLcpPim_LcpToPEta_EtaToPipPimGDecision	Large rate: 955 Hz	cbaryon_to_ph0_btag	@yangjie	Neutrals are probably the problem here. I would ask author if cuts can be tightened
Hlt2Charm_DstpToD0Pip_D0ToKmPip_LowBiasDecision	Large rate: 2000 Hz	d0_to_hh	@fhblanc @gpunzi @mimorell @nkleijne @smaccoli @tpajero	This is not trivial, as the line is important for some analyses and has a significant signal rate
Hlt2Charm_B0bToDpPipPimPim_DpToKpKmPipDecision	Large event size: 0.5 MB	cmeson_to_sl_btag	@yangjie	Selections look reasonable. There's a 6 particle final state and this probably causes overlap with other lines. Can selections be tightened?
Hlt2Charm_XimToL0Pim_VeloMatch_SPDecision	Large rate: 1380 Hz	hyperons	@mstahl @ziyiw	Looks quite "exotic", I think selections can be tightened with small effort
Hlt2Charm_HcspToPpPpKmKs_LL_RSWSDecision	Large BW: 390 Hz + 215 kB event size	hexaquarks	@ipolyako	Combiner has only mass cuts again. Ask for additional cuts to reduce rate and overlap?
Hlt2Charm_Lb0ToLcpPimPimPip_LcpToPpKmPipDecision	Large even size: 0.64 MB	cbaryon_to_sl	@msaur @ziyiw	A 6 particle final state again- probably large duplication. Can cuts be tightened?
Hlt2Charm_DspToKsKp_LL_ADetDecision	Large rate: 1230 Hz	detection_asymmetry_lines	@ldufour @smaccoli	Specific line for ADet measurement - can it be prescaled?
Comment: hexaquarks module needs to be revised in general - several lines in the first 10 and others are present as well
Other problematic lines
Hlt2Charm_XibmToXic0PipPimPim_Xic0ToXimPip_LLLDecision	Huge event size: 1.5/2 MB	cbaryon_to_sl	@msaur @ziyiw	Not sure if the BW is actually this large. Exclusive rate is zero and rate value suggests very low statistics passing selections. Could it be an artifact of the test?
Hlt2Charm_ObmToOc0PipPimPim_Oc0ToXimPip_LLLDecision	Huge event size: 1.5/2 MB	cbaryon_to_sl	@msaur @ziyiw	Not sure if the BW is actually this large. Exclusive rate is zero and rate value suggests very low statistics passing selections. Could it be an artifact of the test?
Hlt2Charm_HccppToDpPpPpKm_RSWSDecision	Huge event size: 1.5/2 MB	hexaquarks	@ipolyako	Not sure if the BW is actually this large. Exclusive rate is zero and rate value suggests very low statistics passing selections. Could it be an artifact of the test?
Hlt2Charm_ObmToOc0PipPimPim_Oc0ToOmPip_LLLDecision	Huge event size: 1.5/2 MB	cbaryon_to_sl	@msaur @ziyiw	Not sure if the BW is actually this large. Exclusive rate is zero and rate value suggests very low statistics passing selections. Could it be an artifact of the test?
Hlt2Charm_XibmToXic0PipPimPim_Xic0ToL0PimPip_LLDecision	Huge event size: 1.5/2 MB	cbaryon_to_sl	@msaur @ziyiw	Not sure if the BW is actually this large. Exclusive rate is zero and rate value suggests very low statistics passing selections. Could it be an artifact of the test?
Other lines with the same configurations are present (0 exclusive rate and huge event size) - to be checked
Hlt2Charm_DpDspToKmPipPipDecision	Huge rate: 8350 Hz	d_to_hhh	@fsouzade @polye @smaccoli	Not clear. Cuts looks tuned, can these be tuned? I think cross-checking this with authors is the best solution
Hlt2Charm_DpDspToKmKpPipDecision	Huge rate: 4900 Hz	d_to_hhh	@fsouzade @polye @smaccoli	Not clear. Cuts looks tuned, can these be tuned? I think cross-checking this with authors is the best solution
Hlt2Charm_DstpToD0Pip_D0ToPimPipGDecision	Huge rate: 1230 Hz	d0_to_hhgamma	@jbrodzic	Neutrals?
Hlt2Charm_PspToPpPipPim_RSWSDecision	Huge rate: 3530 Hz	hexaquarks	@ipolyako	No cuts again
Hlt2Charm_Dst0ToD0EmEp_D0ToKmPip_SSDecision	Huge rate: 1330 Hz	dst_to_dee	@cacochat	SS is used to model the combinatorial background, the thing is it has large combinatorics, some tighter cuts could be applied

FYI: @tpajero @fbetti