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
Add AlCaNano
and inherit AlCaPhiSymEcal_Nano
from it
#37854
Conversation
assign alca |
type ecal |
@cmsbuild , please test |
urgent
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-37854/29788
|
New categories assigned: alca @yuanchao,@francescobrivio,@malbouis,@tvami you have been requested to review this Pull request/Issue and eventually sign? Thanks |
A new Pull Request was created by @tvami (Tamas Vami) for master. It involves the following packages:
@perrotta, @malbouis, @yuanchao, @tvami, @qliphy, @davidlange6, @fabiocos, @francescobrivio can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-8d5197/24517/summary.html Comparison SummarySummary:
|
+alca
|
+1
|
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will be automatically merged. |
PR description:
Follow-up to dmwm/T0#4664 (comment)
Inheriting from the
AlCa
scenario does not allow us to costumize the RECO stepwhile inheriting from the
pp
scenario forces to use the DQM step. This apparently cannot be switched off in the T0 config. So now I introduceAlCaNano
and inheritAlCaPhiSymEcal_Nano
from it.PR validation:
if this PR is a backport please specify the original PR and why you need to backport that PR:
Backport to
12_3_X
will be submitted after T0 replay with the12_4_0_pre4