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

Change tracker eta boundary for PF linking #4181

Merged

Conversation

mark-grimes
Copy link

Changes the tracker eta boundary used by particle flow from 3.8 to 3.0.

Private correspondence from Michalis Bachtis 05/Jun/2014:

Physics Justification: Nominally inside the tracker coverage we call ECAL clusters photons but outside we do not do it because most of the ECAL contribution comes from charged hadrons without tracker tracks. If you change this 3.8 to 3 we allow photons up to eta 3 but in the HF we make neutral hadrons which are much close to the jets in the HF than photons.

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @mark-grimes (Mark Grimes) for CMSSW_6_2_X_SLHC.

Change tracker eta boundary for PF linking

It involves the following packages:

SLHCUpgradeSimulations/Configuration

@cmsbuild, @civanch, @Degano, @mdhildreth, @nclopezo can you please review it and eventually sign? Thanks.
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.
@fratnikov, @mark-grimes you are the release manager for this.
You can merge this pull request by typing 'merge' in the first line of your comment.

@mark-grimes
Copy link
Author

merge

cmsbuild added a commit that referenced this pull request Jun 10, 2014
Change tracker eta boundary for PF linking
@cmsbuild cmsbuild merged commit 638695c into cms-sw:CMSSW_6_2_X_SLHC Jun 10, 2014
@mark-grimes mark-grimes deleted the changePFLinkingEtaBoundary branch June 16, 2014 07:32
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

2 participants