Skip to content

Add an example for UPC events in hadronic Pb-Pb pile-up - #2514

Open
sawenzel wants to merge 1 commit into
AliceO2Group:masterfrom
sawenzel:upc-hadronic-pileup-example
Open

sawenzel wants to merge 1 commit into
AliceO2Group:masterfrom
sawenzel:upc-hadronic-pileup-example

Conversation

@sawenzel

Copy link
Copy Markdown
Contributor

This provides an example script that embeds STARlight UPC events into hadronic Pb-Pb pile-up, anchored to a real run. It is meant as a starting point for PWG-UD studies of how overlapping hadronic collisions affect UPC tracking, vertexing and event selection. It builds on the setup of the "Processes with hadronic background" productions (https://its.cern.ch/jira/browse/O2-6883).

Compared to that setup, the hadronic density is 90% of the real one instead of 50% (r0:e10 instead of r0:e2), and enough background events are simulated that none repeats within a timeframe. The timeframe length is taken from the anchor run instead of being forced to 128 orbits, which with realistic pile-up made TPC digitisation exceed the memory of a GRID slot.

Tested on the GRID for 2023 Pb-Pb runs 544013 (8 kHz) and 544868 (19 kHz). In the AOD, the UPC collisions are identified by generator ID 51. The committed version differs from the tested one only in using the release's own O2DPG configuration and anchorMC.sh's log archive.

Assisted by Claude Code.

This commit provides an example script that embeds STARlight UPC events into hadronic Pb-Pb pile-up, anchored to a real run.

- Every N-th collision (default 10) is a UPC event in its own bunch crossing; the others are Angantyr Pb-Pb collisions.
- The interaction rate and the timeframe length come from the anchor run.
- The number of background events is set so that none repeats within a timeframe.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sawenzel
sawenzel requested a review from jackal1-66 as a code owner October 20, 2026 13:32
@github-actions

Copy link
Copy Markdown

REQUEST FOR PRODUCTION RELEASES:
To request your PR to be included in production software, please add the corresponding labels called "async-" to your PR. Add the labels directly (if you have the permissions) or add a comment of the form (note that labels are separated by a ",")

+async-label <label1>, <label2>, !<label3> ...

This will add <label1> and <label2> and removes <label3>.

The following labels are available
async-2023-pbpb-apass4
async-2023-pp-apass4
async-2024-pp-apass1
async-2022-pp-apass7
async-2024-pp-cpass0
async-2024-PbPb-apass1
async-2024-ppRef-apass1
async-2024-PbPb-apass2
async-2023-PbPb-apass5

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant