key4hep / key4hep/CLDConfig

Pandora sometimes misses obvious-looking track cluster associations

Open
#43 12 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
0
Forks
21
PR merge metrics
No merged PRs in 30d

Description

`PandoraPFOs` (clusters + associated tracks)

![image](https://github.com/user-attachments/assets/8f40ba15-c8f5-488a-a0fc-a5ade744adc6)

`PandoraPFOs` + all `SiTracks`

![image](https://github.com/user-attachments/assets/df7e22e3-604c-42ff-aed8-ab44d788bd81)

TODO:

- [ ] Check if this looks the same for `SiTracks_Refitted`

json and podio-dump output for the event
[pi+.10000.REC.edm4hep.json](https://github.com/user-attachments/files/16246366/pi%2B.10000.REC.edm4hep.json)
[pi+.10000.REC.dump.txt](https://github.com/user-attachments/files/16246367/pi%2B.10000.REC.dump.txt)

Contributor guide

Open the contributing guide

Research direction

Start with the attached pi+.10000.REC.edm4hep.json and pi+.10000.REC.dump.txt, comparing the PandoraPFOs associations with the SiTracks collection. Check whether the same behavior occurs for SiTracks_Refitted; done means the missed association is reproduced and its cause or required correction is documented.

Written by the indexing model from the issue text.

Assessment

Domain
data
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.