Skip to content

[15.0.X] Improved Event Content for the TkAlHLT* ALCARECO #48486

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: CMSSW_15_0_X
Choose a base branch
from

Conversation

mmusich
Copy link
Contributor

@mmusich mmusich commented Jul 5, 2025

backport of #48474

PR description:

This PR is a follow-up to PR #46888 which introduced the High Granularity Tracker Alignment Prompt Calibration Loop for HLT alignment conditions. In that PR two new flavours of ALCARECO were introduced TkAlHLTTracks and TkAlHLTTracksZMuMu.
I add in this PR the hltPixelVertices collection to the list of HLT products saved in both ALCARECO flavours.
Then I profit of the existing machinery from AlignmentTracksFromVertexSelector in order to save also all the pixel tracks associated to the hltPixelVertex closest in space to the di-muon decay vertex selected by TkAlHLTTracksZMuMu (not necessarily the hardest in the event).
In this way it would be possible to recompute offline the vertex with different calibration constants and measure the impact of that.
I profit of this PR to introduce in commit 6d243a7 a small bug-fix in order to consume an intermediated collection only when it's needed.

PR validation:

Run successfully the following command :

#!/bin/bash -ex

cmsDriver.py testReAlCaHLT \
	     -s ALCA:TkAlHLTTracks+TkAlHLTTracksZMuMu  \
	     --conditions 150X_dataRun3_HLT_v1 \
	     --scenario pp \
	     --data \
	     --era Run3_2025 \
	     --datatier ALCARECO \
	     --eventcontent ALCARECO \
	     --processName=ReAlCa \
	     -n 10000 \
	     --dasquery='file dataset=/HLTMonitor/Run2025C-Express-v2/FEVTHLTALL site=T2_CH_CERN' \
	     --nThreads 4 >& ReAlCa.log

on 10k input events:

  • 9900 events are selected by ALCA:TkAlHLTTracks. The size of the output file TkAlHLTTracks.root goes form 348M to 362M (i.e. a +4.02% increase)
  • 706 events are selected by ALCA:TkAlHLTTracksZMuMu. The size of the output file TkAlHLTTracksZMuMu.root goes from 4.2M to 7.9M (i.e. a +88% increase -- though the event size per event remains fairly small 11kB/event).

If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:

Verbatim backport of #48474 to CMSSW,_15_0_X for 2025 data-taking operations.

@cmsbuild
Copy link
Contributor

cmsbuild commented Jul 5, 2025

A new Pull Request was created by @mmusich for CMSSW_15_0_X.

It involves the following packages:

  • Alignment/CommonAlignmentProducer (alca)

@atpathak, @cmsbuild, @perrotta can you please review it and eventually sign? Thanks.
@adewit, @missirol, @mmusich, @pakhotin, @rsreds, @tlampen, @tocheng, @yuanchao this is something you requested to watch as well.
@antoniovilela, @mandrenguyen, @rappoccio, @sextonkennedy you are the release manager for this.

cms-bot commands are listed here

@cmsbuild
Copy link
Contributor

cmsbuild commented Jul 5, 2025

cms-bot internal usage

@mmusich
Copy link
Contributor Author

mmusich commented Jul 5, 2025

test parameters:

  • workflow = 1002.5

@mmusich
Copy link
Contributor Author

mmusich commented Jul 5, 2025

@cmsbuild, please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Jul 5, 2025

+1

Size: This PR adds an extra 20KB to repository
Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-f1b6c2/47093/summary.html
COMMIT: 09c3b41
CMSSW: CMSSW_15_0_X_2025-07-05-1100/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/48486/47093/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

  • You potentially added 2 lines to the logs
  • Reco comparison results: 3 differences found in the comparisons
  • DQMHistoTests: Total files compared: 51
  • DQMHistoTests: Total histograms compared: 4010005
  • DQMHistoTests: Total failures: 4
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 4009981
  • DQMHistoTests: Total skipped: 20
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 50 files compared)
  • Checked 223 log files, 189 edm output root files, 51 DQM output files
  • TriggerResults: no differences found

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants