Skip to content

Stop Turbo-only Calo objects being used in TISTOS decisions

Olli Lupton requested to merge olupton-tistos-fix into master

See https://its.cern.ch/jira/browse/LHCBPS-1746 for background.

It seems that a change in the Hlt2/SelReports structure broke a workaround in HltSelReportsDecoder that stopped Turbo-only objects (in this case CaloCluster objects associated with charged particles) from being seen by the TISTOS machinery.

The workaround broke because the structure changed from:

  • Particle
    • CaloCluster

to

  • Particle
    • CaloHypo
      • CaloCluster

in 2016 (and later) data.

I checked this has the desired affect when TISTOSing Hlt2 decisions, but haven't checked for any impact on Tesla (but I don't see why there would be any problem...). I suggest running it in the nightlies now, but it should be more thoroughly tested before being merged.

The original bug affects user analysis and stripping lines that include TOS filters...I wasn't sure which branch I should target.

Merge request reports