key4hep / key4hep/k4SimDelphes
Handling of `EFlowTrack`, `EFlowPhotons`, `EFlowNeutralHadrons`?
- Dominant language
- C++
- Stars
- 6
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
* Currently these are the names of the `edm4hep::Track` and `edm4hep::Cluster` collections, which can be confusing, because the actual `edm4hep::ReconstructedParticle`s live in the "global" reco particle collection. Additionally the `edm4hep::Cluster`s have no "real" information currently, and serve mainly as a tag.
* Raised by FCC, proposed solution (Valentin, Thomas): Make these collections a subset collection as well and rename the `edm4hep::Track` and `edm4hep::Cluster` collection to reduce confusion.
Contributor guide
Research direction
Start by tracing how the EFlowTrack, EFlowPhotons, EFlowNeutralHadrons, and global reco particle collections are defined and used. Clarify the collection renames and subset-collection behavior with the proposed solution, then verify that the resulting names no longer confuse the Track, Cluster, and ReconstructedParticle data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100