-
Notifications
You must be signed in to change notification settings - Fork 152
change clusterizer and CASeeder to reject zsize==1 clusters #1024
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
base: master
Are you sure you want to change the base?
Conversation
For repository maintainers, please start the CI check manually (feedback)This is an automatic message to assist manually starting CI check for this pull request, commit 921e604743be291ba2820bf23d3cbe1cab4efd2b. sPHENIX software maintainers: please make your input here and start the Build: Note:
Automatically generated by sPHENIX Jenkins continuous integration |
For repository maintainers, please start the CI check manually (feedback)This is an automatic message to assist manually starting CI check for this pull request, commit 6b09d9cd04f65b5dab93a658be9e9200042978b6. sPHENIX software maintainers: please make your input here and start the Build: Note:
Automatically generated by sPHENIX Jenkins continuous integration |
|
Should we add this flag to our reco macros too? Better yet, is it time for us to have a centralized function call for our seeding reconstruction? |
|
First part of the quesion: yes!
Second part, what do you mean by centralized function call?
On 13. Feb 2025, at 18:42, Joseph (Joe) Osborn ***@***.***> wrote:
Should we add this flag to our reco macros too? Better yet, is it time for us to have a centralized function call for our seeding reconstruction?
—
Reply to this email directly, view it on GitHub<#1024 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEALMH7MT3JS4H3HVHVHTNL2PTKQLAVCNFSM6AAAAABTWSQFV6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJXGMYTSNBRGE>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
[osbornjd]osbornjd left a comment (sPHENIX-Collaboration/macros#1024)<#1024 (comment)>
Should we add this flag to our reco macros too? Better yet, is it time for us to have a centralized function call for our seeding reconstruction?
—
Reply to this email directly, view it on GitHub<#1024 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEALMH7MT3JS4H3HVHVHTNL2PTKQLAVCNFSM6AAAAABTWSQFV6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJXGMYTSNBRGE>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
|
For example we are not currently calling the function |
|
Ah, that way, well for me that would be ok. Modulo the changed Michael and David will still come up with... |
|
It does cause a small loss in efficiency at low pT |
For repository maintainers, please start the CI check manually (feedback)This is an automatic message to assist manually starting CI check for this pull request, commit aba70f9b802fd3c5a8e69889b684b1a671840af0. sPHENIX software maintainers: please make your input here and start the Build: Note:
Automatically generated by sPHENIX Jenkins continuous integration |


Set Clusterizer to split common mode noise patterns into zsize = 1 clusters and add machinery to reject them in PHCAseeding