Fix customiseTrackingNtuple.extendedContent to correctly pick up OOT particles

[slava77]

It looks like I introduced a bug in #48881 in the extendedContent diffs
The code changes there were intentionally meant to pick up out-of-time pileup, but one component was missing.

This PR is a fix (tested on a somewhat random PU200 setup)

• the symptoms without a fix is a crash with std::exception was thrown. unordered_map::at, which can happen after a few events.

@bdanzi @VourMa I think you mentioned some setup not working with the extendedContent possibly related to this; I can't recall if you found another work-around.

[cmsbuild]

cms-bot internal usage

[cmsbuild]

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-51461/50151

[cmsbuild]

A new Pull Request was created by @slava77 for master.

It involves the following packages:

• Validation/RecoTrack (dqm)

@cmsbuild, @ctarricone, @gabrielmscampos, @rseidita can you please review it and eventually sign? Thanks.
@GiacomoSguazzoni, @VinInn, @VourMa, @dgulhan, @elusian, @felicepantaleo, @mmasciov, @mmusich, @mtosi, @rovere, @wmtford this is something you requested to watch as well.
@ftenchini, @mandrenguyen, @sextonkennedy you are the release manager for this.

cms-bot commands are listed here

[slava77]

@cmsbuild please test

[cmsbuild]

+1

Size: This PR adds an extra 24KB to repository
Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-df965d/54653/summary.html
COMMIT: cd14772
CMSSW: CMSSW_20_1_X_2026-07-09-1100/el9_amd64_gcc13
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/51461/54653/install.sh to create a dev area with all the needed externals and cmssw changes.

The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:

• @artlbv [Phase-2 L1T] Move TauNNIdHW to the externally-built NNPuppiTauModel package #51263
• @SegmentLinking [LST standalone] Bump CUDA compute capability to 8.0 #51339
• @silviodonato Add scouting to Phase-2 HLT menu #51424
• @felicepantaleo DPGAnalysis/HGCalNanoAOD: fix candidate extra table inputs #51433
• @chrishanw Fix: parameters in ElectronSeedFitter #51451
• @bsunanda Phase2-hgx368F Protect RecHitTools in RecoLocalCalo/HGCalRecAlgos for HFNose detIDs #51456
• @Martin-Grunewald Remove customizeHLTFor51053 function call in HLT #51457

You can see more details here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-df965d/54653/git-recent-commits.json
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-df965d/54653/git-merge-result

Comparison Summary

Summary:

• You potentially removed 1 lines from the logs
• Reco comparison results: 19 differences found in the comparisons
• DQMHistoTests: Total files compared: 47
• DQMHistoTests: Total histograms compared: 3792433
• DQMHistoTests: Total failures: 1626
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 3790789
• DQMHistoTests: Total skipped: 18
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.0 KiB( 46 files compared)
• Checked 203 log files, 173 edm output root files, 47 DQM output files
• TriggerResults: no differences found

Max Memory Comparisons exceeding threshold

@cms-sw/core-l2 , I found 1 workflow step(s) with memory usage exceeding the error threshold:

Expand to see workflows ...

• Error: Workflow 34634.0_TTbar_14TeV+Run4D121PU step2 max memory diff 33.3 exceeds +/- 30.0 MiB

[gabrielmscampos]

Are the differences in the DQM comparison (in the HLT/ bit) along the expectation?

[mmusich]

Are the differences in the DQM comparison (in the HLT/ bit) along the expectation?

I think these are coming from the other commits that got merged together:

The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:

[gabrielmscampos]

+dqm

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @mandrenguyen, @ftenchini, @sextonkennedy (and backports should be raised in the release meeting by the corresponding L2)

[mandrenguyen]

+1