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
Correction for HCAL iterative phi symmetry calibration AlCaReco #9075
Correction for HCAL iterative phi symmetry calibration AlCaReco #9075
Conversation
Hcal iterative Phi Sym Cal was added
HCAL Iterative Phi Sym Cal was added
HCAL Iterative Phi Sym Cal was added
@abdoulline this is something you might want to watch as well. |
A new Pull Request was created by @diguida (Salvatore Di Guida) for CMSSW_7_5_X. Correction for HCAL iterative phi symmetry calibration AlCaReco It involves the following packages: Calibration/HcalAlCaRecoProducers @diguida, @cerminar, @cmsbuild, @franzoni, @nclopezo, @mmusich, @davidlange6 can you please review it and eventually sign? Thanks. |
please test |
The tests are being triggered in jenkins. |
+1 |
Correction for HCAL iterative phi symmetry calibration AlCaReco
@diguida Could you please advise where I can find some information about rates of the HLT paths in the PD? Is there any table on twiki? |
Actually, to clarify, the PDs are HcalNZS These PDs are composed of HLT paths that are essentially L1 pass-throughs. In terms of rates, things are a little uncertain, but these are some of the expected rates for tomorrow's first collisions (lumi 1.5E30/bunch) Commissioning: Commissioning and SingleMu: ZeroBiasN: Note that each ZeroBiasN PD will get ~ 125 Hz I am not sure if there are any Tier0 limitations as to how many PDs an AlCaReco can run in. |
Adding new AlCaReco definition for HCal iterative phi symmetry calibration.
Only python files were added or modified, no new producers added.
Originally in #8286