Skip to content

[ATR-22104] Trigger Navigation Links - allow for remapping checks to be optional

Tim Martin requested to merge tamartin/athena:decisionObjectLinkFetching into master

An optimisation as part of trigger navigation slimming and thinning for R3.

As this touches a low level interface, it needs to go in first. The following larger MR will then build on the nightly which includes this change.

At present, each link retrieved from an xAOD::TrigComposite makes a check if there happens to be updated (via dynamic decoration) information to use.

This check requires a SG lock to be briefly enacted.

The check is made a vast number of times when navigating the trigger navigation, whereas it is only needed for links which online originated inside EventViews.

The mayBeRemapped flag is hence only set to true deep in the TDT's features retrieval code when we know that we need to be making the check.

Other changes along for the ride:

  • Inclusion of removeObjectLink & removeObjectCollectionLinks for the slimming code to use.
  • Additional static node name specifiers for the HLT Summary Alg to make use of

Merge request reports