Skip to content

FT0: align trigger definition in Digitizer with data trigger logic#15156

Open
spulawsk wants to merge 1 commit intoAliceO2Group:devfrom
spulawsk:FIX_MC_FT0_Triggers_clean
Open

FT0: align trigger definition in Digitizer with data trigger logic#15156
spulawsk wants to merge 1 commit intoAliceO2Group:devfrom
spulawsk:FIX_MC_FT0_Triggers_clean

Conversation

@spulawsk
Copy link

This PR introduces an updated signal shape model and revised trigger handling in the FT0 digitization.

The signal response used in the FT0 digitizer has been updated to a parametrization based on a sum of two log-normal components. This allows a better description of the detector pulse shape in Monte Carlo simulations and improves the agreement between simulated trigger response and data.

In addition, trigger logic has been adjusted to better reproduce the behaviour of the FT0 trigger chain.

Main changes
Signal model:

  • introduce a new signal shape function based on two log-normal components
  • provide analytical integral of the signal shape for amplitude evaluation
  • keep the previous implementation commented for reference

Trigger tuning
update trigger thresholds in FT0DigParam (mtrg_central_trh, mtrg_semicentral_trh)
introduce a dedicated vertex trigger gate parameter (mTime_trg_vertex_gate)

Digitizer improvements
introduce mapping from channel ID to PM hash using FT0 metadata
accumulate charge per PM using the mapping
improve calculation of central and semicentral triggers based on summed PM charge
add monitoring of summed PM amplitudes (debug logging)

The definition of FT0 triggers in the digitizer is updated to better match the trigger logic used in data processing. In particular, the central, semicentral, and vertex trigger conditions are now computed using PM-summed amplitudes and timing definitions consistent with those used in the FT0 trigger chain.

These changes improve the consistency between MC digitization and the trigger quantities reconstructed from data.

No changes to the data format are introduced.

@github-actions
Copy link
Contributor

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

Development

Successfully merging this pull request may close these issues.

1 participant