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

reverse the order in which HEXPLIT and topo-clustering take place #1481

Open
sebouh137 opened this issue Jun 3, 2024 · 0 comments
Open

reverse the order in which HEXPLIT and topo-clustering take place #1481

sebouh137 opened this issue Jun 3, 2024 · 0 comments

Comments

@sebouh137
Copy link
Contributor

Is your feature request related to a problem? Please describe.
The topo clustering finds many "clusters" that belong to only on single real hit when it is being run on subcell hits from the output of the HEXPLIT algorithm. This happens because a single isolated hit will be divided into 12 subcell hits. The affected detectors are the foward HCAL insert (CALI) and the SiPM-on-tile ZDC.

Describe the solution you'd like

  • Swap the order in which these two algorithms are run. Do this for both detectors
  • Modify the expected input/output structure of HEXPLIT so that it can either run on all hits in a collection, or only on hits that belong to protoclusters in a collection of protoclusters (and produce a new protocluster collection in which each protocluster contains subcell hits instead of normal hits)
  • Choose topo-cluster geometric parameters that are appropriate for hit-level instead of subcell-hit-level. Do this for both detectors

Describe alternatives you've considered
N/A

Additional context
N/A

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

No branches or pull requests

1 participant