IFT: Sprucing Lines for Ξ and Ω in SMOG2

Hi @nskidmor @abertoli these are lines that we would like to include (if possible) in the 2023 sprucing campaign for the pp reference run data that we will take later this month (not for the 2023 campaigns you have already prepared).

@lakolk @kmattiol (cc @nskidmor):

in general in LHCb the throughput is the number of events per second Hlt2 or Spruce can process, see: https://lhcbpr-hlt.web.cern.ch/PerfTests/UpgradeThroughput/

could it be that the % above are the retentions ? i.e. the fraction of the input file events saved by that line ?

does the proposed lines depends on any Hlt2 line writing to the FULL stream not yet in master ?
does these lines have ZERO rate, because of a vertex cut for example, in pp simulated events ?
for the final green light we will need an estimate of the bandwidth from pAr simulated events as @kmattiol gave us in the past

let me point out that what I read in these two places:

https://gitlab.cern.ch/lhcb/Moore/-/blob/lakolk_spruce_smog_omega_xi/Hlt/Hlt2Conf/python/Hlt2Conf/lines/ift/spruce_ift_smog2_omegas.py#L32-L33

_MASSWINDOW_LAMBDA0 = [(1115.683 - 25) * MeV, (1115.683 + 25) * MeV]
_MASSWINDOW_OMEGA = [(1672 - 25) * MeV, (1672 + 25) * MeV]

https://gitlab.cern.ch/lhcb/Moore/-/blob/lakolk_spruce_smog_omega_xi/Hlt/Hlt2Conf/python/Hlt2Conf/lines/ift/spruce_ift_smog2_xis.py#L32-L33

_MASSWINDOW_LAMBDA0 = [(1115.683 - 25) * MeV, (1115.683 + 25) * MeV]
_MASSWINDOW_XI = [(1321.71 - 25) * MeV, (1321.71 + 25) * MeV]

is by far not ideal: please let's avoid hardwired mass values in the code

in B2OC we have been doing so for some time but now we are using, for example, F.PDG_MASS("D_s+")

so 1115.683 is F.PDG_MASS("Lambda_0") and so on

approved this merge request

unapproved this merge request

let me add that we do not really care if docs failed and in addition to the comment above I do not have anything else, this is why I approved/unapproved

if I leave it approved and accidental merge (by misclick) may happen so better avoid ...

changed title from Sprucing Lines for Ξ and Ω in SMOG2 to IFT: Sprucing Lines for Ξ and Ω in SMOG2

Looks ready to me!

resolved all threads

added ci-test-triggered label

[2023-09-08 10:20] Validation started with lhcb-master-mr#9166

resolved all threads

assigned to @nskidmor

changed the description

@lakolk @oboenteg @kmattiol (cc @kmattiol), let me try to summarize the different therads above and tell me if I am wrong and where:

the hlt2 lines these sprucing line depend on are already merged into master
the retentions on pAr are in the description, I am assuming these retentions have been obtained using a Moore/Hlt2 version that contains the Hlt2 lines of the point above
largest retention is 0.1 % (or 0.1 = 10 % ?)
there is no real rush at the moment to get this in master, about 1 week left
the 1 week left is still not sufficient to fix the hardwired masses ? you could fix them in this MR / in the Spruce first and then later propagate to the Hlt2
if retention are < 0.1 % then we do not absolutely need the GB/sec

mentioned in issue #659 (closed)

added 1 commit

38066342 - replaced hardcoded masses with thor functors

Compare with previous version

added 1 commit

7d8859de - Fixed formatting

Compare with previous version

approved this merge request

resolved all threads

changed the description

merged

mentioned in commit 933d84ee

Line	Retention
SpruceIFT_SMOG2Xi2Lambda0pi_lllDecisionWithOutput	(0.1020211 +- 0.00627576)%
SpruceIFT_SMOG2Xi2Lambda0pi_ddlDecisionWithOutput	(0.05796653 +- 0.00473158)%
SpruceIFT_SMOG2Xi2Lambda0pi_dddDecisionWithOutput	(0.05719365 +- 0.00469994)%
SpruceIFT_SMOG2Omega2Lambda0K_lllDecisionWithOutput	(0.08347181 +- 0.00567717)%
SpruceIFT_SMOG2Omega2Lambda0K_ddlDecisionWithOutput	(0.03671214 +- 0.00376589)%
SpruceIFT_SMOG2Omega2Lambda0K_dddDecisionWithOutput	(0.02859682 +- 0.00332384)%

IFT: Sprucing Lines for Ξ and Ω in SMOG2

Merge request reports

Activity