Updated JER SFs for 2024, 2025, and 2026#31
Merged
anmalara merged 1 commit intoJul 10, 2026
Conversation
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
2 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.
This PR corresponds to the JERCProtolab MR #118.
It contains updated JER SFs for 2024 and 2025, and new JER SFs for 2026. More information is provided in the PDF files included in
Prompt24to26_V11MV5MV2M_arxiv.tar.gz, which is attached in this indico agenda. The newJER SFfiles are based on the internal2024 V11M,2025 V5M, and2026 V2Mversions of the Helsinki group.The new recommended JER tags are:
Summer24Prompt24_JRV2_MCSummer24Prompt25_JRV2_MCSummer24Prompt26_RunBD_JRV1_MC,Summer24Prompt26_RunC_JRV1_MC(era C is a dedicated lowPU run)(DATA tags also provided for completeness and consistency with previous versions, but are NOT to be used by analyzers).
cc: @ravindkv , @anmalara , @nurfikri89