New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NanoAODv6 release preparation #28119
Comments
A new Issue was created by @peruzzim . @davidlange6, @Dr15Jones, @smuzaffar, @fabiocos, @kpedro88 can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
assign xpog |
Branches for a cumulative backport of #28103 and #28122 are also ready: CMSSW_10_2_X...cms-nanoAOD:pr_nanov6_102X and will depend on backports of #28096 (PRs open) and #28118 (PRs not open yet) |
I'm afraid we forgot to update NanoAOD code for the backports of #27184, would like to check with @ahinzmann @lathomas before building _pre10 |
the jet ID is now updated in #28122 |
everything is now merged to build _pre10 from the xpog side |
List of features to be backported to 10_2_X for NanoAODv6:
#28145 depends technically only on #28095 and #28135, but we will need also #28098 to use the intended jet energy corrections. |
Status update:
|
RelVals have run, we can build the 10_2_X release for the NanoAODv6 production campaign. |
For 10_6_X to be used in UL, we need:
I don't understand the role of #28177 - is that just for validation activities i.e. is the title misleading? |
@aspiezia should comment, I agree that the title should be better updated to reflect the Validation nature of that update |
Dear All, I have updated the title to "Tau Validation/DQM: switching deepTau version from v2 to v2p1 for CMSSW10_6_X". |
@peruzzim as discussed, for the record: the integration of #28182 in 10_6_X causes two test workflows to fail (11824 and 11825):
|
relval workflows are fixed in recent 10_6_X integration builds by #28302, that is specific for the 10_6_X configuration and does not need being ported elsewhere |
+xpog I think we can close the NanoAODv6 chapter, as pull requests are merged in all branches:
|
This issue is fully signed and ready to be closed. |
@mariadalfonso @gouskos @fabiocos @peruzzim |
for completeness, this can be fixed if one uses this recipe |
This is to collect and track items for integration in the release for NanoAODv6:
The text was updated successfully, but these errors were encountered: