B2OC: store isolation variables instead of tracks
Can confirm the info is correctly saved by dumping a random event of
TUBRO stream:
/Event/Turbo/Hlt2B2OC_BuToDstpKK_DstpToD0Pi_D0ToHH
/Event/Turbo/Hlt2B2OC_BuToDstpKK_DstpToD0Pi_D0ToHH/B0_DeltaR_05_NeutralIsolation
/Event/Turbo/Hlt2B2OC_BuToDstpKK_DstpToD0Pi_D0ToHH/B0_DeltaR_05_NeutralIsolation/P2InfoRelations
/Event/Turbo/Hlt2B2OC_BuToDstpKK_DstpToD0Pi_D0ToHH/B0_DeltaR_10_NeutralIsolation
/Event/Turbo/Hlt2B2OC_BuToDstpKK_DstpToD0Pi_D0ToHH/B0_DeltaR_10_NeutralIsolation/P2InfoRelations
/Event/Turbo/Hlt2B2OC_BuToDstpKK_DstpToD0Pi_D0ToHH/B0_DeltaR_05_LongTrackIsolation
/Event/Turbo/Hlt2B2OC_BuToDstpKK_DstpToD0Pi_D0ToHH/B0_DeltaR_05_LongTrackIsolation/P2InfoRelations
/Event/Turbo/Hlt2B2OC_BuToDstpKK_DstpToD0Pi_D0ToHH/B0_DeltaR_10_LongTrackIsolation
/Event/Turbo/Hlt2B2OC_BuToDstpKK_DstpToD0Pi_D0ToHH/B0_DeltaR_10_LongTrackIsolation/P2InfoRelations
/Event/Turbo/Hlt2B2OC_BuToDstpKK_DstpToD0Pi_D0ToHH/B0_DeltaR_15_NeutralIsolation
/Event/Turbo/Hlt2B2OC_BuToDstpKK_DstpToD0Pi_D0ToHH/B0_DeltaR_15_NeutralIsolation/P2InfoRelations
/Event/Turbo/Hlt2B2OC_BuToDstpKK_DstpToD0Pi_D0ToHH/B0_DeltaR_15_LongTrackIsolation
/Event/Turbo/Hlt2B2OC_BuToDstpKK_DstpToD0Pi_D0ToHH/B0_DeltaR_15_LongTrackIsolation/P2InfoRelations
/Event/Turbo/Hlt2B2OC_BuToDstpKK_DstpToD0Pi_D0ToHH/B0_VertexIsolation
/Event/Turbo/Hlt2B2OC_BuToDstpKK_DstpToD0Pi_D0ToHH/B0_VertexIsolation/P2InfoRelations
/Event/Turbo/Hlt2B2OC_BuToDstpKK_DstpToD0Pi_D0ToHH/Particles
FULL stream:
/Event/Spruce/SpruceB2OC_BuToDspGamma_DspToHHH
/Event/Spruce/SpruceB2OC_BuToDspGamma_DspToHHH/B0_VertexIsolation
/Event/Spruce/SpruceB2OC_BuToDspGamma_DspToHHH/B0_VertexIsolation/P2InfoRelations
/Event/Spruce/SpruceB2OC_BuToDspGamma_DspToHHH/B0_DeltaR_15_NeutralIsolation
/Event/Spruce/SpruceB2OC_BuToDspGamma_DspToHHH/B0_DeltaR_15_NeutralIsolation/P2InfoRelations
/Event/Spruce/SpruceB2OC_BuToDspGamma_DspToHHH/B0_DeltaR_15_LongTrackIsolation
/Event/Spruce/SpruceB2OC_BuToDspGamma_DspToHHH/B0_DeltaR_15_LongTrackIsolation/P2InfoRelations
/Event/Spruce/SpruceB2OC_BuToDspGamma_DspToHHH/B0_DeltaR_10_NeutralIsolation
/Event/Spruce/SpruceB2OC_BuToDspGamma_DspToHHH/B0_DeltaR_10_NeutralIsolation/P2InfoRelations
/Event/Spruce/SpruceB2OC_BuToDspGamma_DspToHHH/B0_DeltaR_10_LongTrackIsolation
/Event/Spruce/SpruceB2OC_BuToDspGamma_DspToHHH/B0_DeltaR_10_LongTrackIsolation/P2InfoRelations
/Event/Spruce/SpruceB2OC_BuToDspGamma_DspToHHH/B0_DeltaR_05_NeutralIsolation
/Event/Spruce/SpruceB2OC_BuToDspGamma_DspToHHH/B0_DeltaR_05_NeutralIsolation/P2InfoRelations
/Event/Spruce/SpruceB2OC_BuToDspGamma_DspToHHH/B0_DeltaR_05_LongTrackIsolation
/Event/Spruce/SpruceB2OC_BuToDspGamma_DspToHHH/B0_DeltaR_05_LongTrackIsolation/P2InfoRelations
/Event/Spruce/SpruceB2OC_BuToDspGamma_DspToHHH/Particles
Merge request reports
Activity
assigned to @shunan
added B2OC label
added PR/Moore_hlt2_and_spruce_bandwidth label
added RTA label
Hi @dmendoza and @msaur , in B2OC we'd like to utilise the new implementation to save isolation variables instead of track in our lines. With this I would expect a big drop in average event size and we hope that it can be applied to all B2OC lines (previous implementation only applies to a few lines).
Given the change I'd like to run a bandwidth test here first, the target is temporarily switched to
master
and I can confirm that BW test on this branch went well locally (but the numbers are not comparable I'm afraid).Could you launch a CI test on BW test platform when the resource allows? To have a fair comparison with !4508 (comment 9323862) I think some technical MR need to be included as well: LHCb!4901 (merged), Rec!4233 (merged), !4262 (merged), !4682 (merged), !4691 (merged)
Many thanks!
cc-ing
author @chenjia
- Resolved by Shunan Zhang
Is there any reason why this is not targeting
b2oc-2025-dev
?
- Resolved by Shunan Zhang
added ci-test-triggered label
- [2025-04-04 11:07] Validation started with lhcb-master-mr#13223
Comparisons between old implementation (lhcb-master-mr.13209) and new implementation (lhcb-master-mr.13223):
TLDR: avg event size of turbo to disk decreased by 1 kB, full to disk increased by 0.2 kB.
- old, turbo to disk:
- new, turbo to disk:
- old, full to disk:
- new, full to disk:
I believe these are sensible because:
- Most of lines requring isolation are booked in turbo (mostly gamma lines), so the impact from current B2OC main branch is larger.
- Very few spruce lines required isolation, and with new implementation we added isolation info for all lines, so the average event size goes up.
My conclusion would be
- For turbo, the current B2OC branch is increasing BW so this new implementation is certainly desired.
- For full, the current B2OC branch is decreasing BW and this new implementation won't revert that.
@abertoli @bshi I believe this MR is ready for your review and merge, changing the target to
b2oc-2025-dev
.mentioned in merge request !4508 (merged)
mentioned in commit Boole@489d2a80