Skip to content
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

Merged

Conversation

diguida
Copy link
Contributor

@diguida diguida commented May 13, 2015

Adding new AlCaReco definition for HCal iterative phi symmetry calibration.
Only python files were added or modified, no new producers added.
Originally in #8286

@mmusich
Copy link
Contributor

mmusich commented May 13, 2015

@nilina @kodolova
something you might want to watch as well

@diguida
Copy link
Contributor Author

diguida commented May 13, 2015

@abdoulline this is something you might want to watch as well.

@cmsbuild
Copy link
Contributor

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
Configuration/EventContent
Configuration/StandardSequences

@diguida, @cerminar, @cmsbuild, @franzoni, @nclopezo, @mmusich, @davidlange6 can you please review it and eventually sign? Thanks.
@ghellwig, @Martin-Grunewald, @makortel, @GiacomoSguazzoni, @rovere, @VinInn, @appeltel, @cerati, @dgulhan this is something you requested to watch as well.
You can sign-off by replying to this message having '+1' in the first line of your reply.
You can reject by replying to this message having '-1' in the first line of your reply.
If you are a L2 or a release manager you can ask for tests by saying 'please test' in the first line of a comment.
@nclopezo you are the release manager for this.
You can merge this pull request by typing 'merge' in the first line of your comment.

@diguida
Copy link
Contributor Author

diguida commented May 13, 2015

please test

@cmsbuild
Copy link
Contributor

The tests are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

@davidlange6
Copy link
Contributor

+1

davidlange6 added a commit that referenced this pull request May 20, 2015
Correction for HCAL iterative phi symmetry calibration AlCaReco
@davidlange6 davidlange6 merged commit b371d1a into cms-sw:CMSSW_7_5_X May 20, 2015
@nilina
Copy link
Contributor

nilina commented May 22, 2015

@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?
Do we have the limits in quantity of the PD where we want to run this AlCaReco?
Thank you!

@diguida
Copy link
Contributor Author

diguida commented Jun 2, 2015

@nilina Sorry for late reply.
HLT Rates and Paths are taken care by TSG. Our contact @jmduarte will be glad to help you figure out these quantities.
For first collisions, please refer to the latest announcement here.

Let me know if you need further assistance.

@jmduarte
Copy link
Member

jmduarte commented Jun 2, 2015

Actually, to clarify, the PDs are

HcalNZS
Commissioning
SingleMu
ZeroBias1
ZeroBias2
ZeroBias3
ZeroBias4
ZeroBias5
ZeroBias6
ZeroBias7
ZeroBias8

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:
SingleEG5 ~ 39 Hz
SingleEG20 ~ 37 Hz
SingleJet36 ~ 30 Hz
SingleJet68 ~ 2 Hz

Commissioning and SingleMu:
SingleMuOpen ~ 2.5 Hz
SingleMu3p5 ~ 52 Hz

ZeroBiasN:
ZeroBiasN ~ 125 Hz

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants