Merged
Conversation
Member
|
Hi Zachary, do we expect this change to affect any past production in case we need to reproduce results? |
Member
|
Zach may confirm, but AFAIK, StRefMultCorr is only used at the analysis level, not in production. It is important that we should update PWGs about this change so the analysers should update their analysis. |
marrbnl
approved these changes
Apr 26, 2023
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
There were two edits made to the params file. One was to change the refMultCorr value below which the trigger efficiency gets applied from 100 to 150. The second was to update one of the trigger efficiency parameters to 0 to indicate there is no Vz-dependent trigger efficiency applied.