Skip to content

Generate TPC loopers only in the background transport when embedding - #2524

Draft
sawenzel wants to merge 1 commit into
AliceO2Group:masterfrom
sawenzel:loopers-background-only
Draft

sawenzel wants to merge 1 commit into
AliceO2Group:masterfrom
sawenzel:loopers-background-only

Conversation

@sawenzel

Copy link
Copy Markdown
Contributor

With embedding, the background and the signal transport each covered the whole timeframe with TPC loopers, so the loopers reached the digits twice. This PR proposes to handle that in the workflow: the signal transport gets GenTPCLoopers.loopersVeto=true, and the background alone generates the loopers. Looper settings given for the signal are applied to the background, and a veto given for either transport switches the loopers off in both. In addition, the background loopers now follow -colBkg and no longer take the signal's collision system.

Note that nothing changes without embedding. Replacement patterns (r) are not handled specially, and with --use_bkg_from the loopers are whatever the cached background was produced with.

This is meant as an alternative to AliceO2Group/AliceO2#16015, to be compared before deciding.

Relates to https://its.cern.ch/jira/browse/O2-7272

Assisted by Claude Code.

This avoids the double counting of TPC loopers in embedding productions.

- Background and signal both generated loopers covering the whole timeframe.
- The signal transport now gets GenTPCLoopers.loopersVeto=true.
- GenTPCLoopers settings given with -confKey are applied to the background.
- A veto given for either transport switches loopers off in both.
- The background loopers now use -colBkg as collision system, not -col.

https://its.cern.ch/jira/browse/O2-7272

Co-authored-by: Marco Giacalone <mgiacalo@gmail.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@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