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

Cross-Calorimeter Topocluster Algorithm #1561

Open
ruse-traveler opened this issue Aug 8, 2024 · 0 comments
Open

Cross-Calorimeter Topocluster Algorithm #1561

ruse-traveler opened this issue Aug 8, 2024 · 0 comments
Assignees

Comments

@ruse-traveler
Copy link
Contributor

Is your feature request related to a problem? Please describe.

Currently we have two algorithms used for forming topoclusters:

  • ImagingTopoCluster, which combines hits based on proximity across multiple layers of a calorimeter; and
  • EnergyPositionClusterMerger, which combines the positions of one set of clusters with the energies of another.

However, we don't have an algorithm which generically takes two collections (or possibly more) of clusters and merges them into topoclusters. Such functionality would be useful when one needs to combine clusters from multiple calorimeters, such as in Particle Flow or when considering observables like E_{T}^{miss}.

Describe the solution you'd like

This could be implemented as an algorithm which takes as input two collections of protoclusters and outputs a single collection of protoclusters (the topoclusters). The initial implementation could match clusters based simply on proximity, but could be refined later to take advantage of the segmentation of some calorimeters.

This would mean that the relevant parameters for the algorithm would be

  • The weights associated with each input collection of clusters,
  • And some sort of tolerance for matching.

Describe alternatives you've considered

There are a couple of alternative approaches one could imagine, for example:

  • This could be something that is left up to analyzers after the fact, or
  • This functionality could be reserved for another type of algorithm downstream (e.g. a more explicitly "particle flow" algorithm).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

No branches or pull requests

2 participants