Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR description:
PR Description
This update introduces several improvements to the FSC digitization and reconstruction workflow:
Dedicated FSC Data Structure
A new header (
FSCstruct.h) defines a dedicated struct where additional FSC-related variables can be stored.Charge Calibration Using Calibration Constants
The total measured charge is now computed using calibration parameters (currently hard-coded for validation; once verified, they will be moved to the conditions database).
Support for 50 ns Bunch-Spacing Reconstruction
The reconstruction now handles 50 ns bunch spacing, properly accounting for signals from neighbouring bunches.
Extended
fscdigiOutputThe fscdigi tree now includes:
Bunch-Spacing Configuration
The default settings of the module are optimized for PbPb data, which use 50 ns bunch spacing.
For datasets with >100 ns spacing (e.g., O-O, p-O, Ne-Ne, or any other HI run with long bunch spacing), you should switch to the full time-interval charge reconstruction.
To do this, update your configuration as follows:
PR validation:
Tested with
CMSSW_15_1_0_patch3and recent HI data (run=399540)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: