Tracking acceptance electrons
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
Check duplicate issues.
-Maybe it's related to issue
Goal
I generated Z-->qq (q=uds) events and it look like many electrons don't have tracks. I plot the percentage of electrons that leave a calo cluster but not a track (using truth tracking). The second plot shows the number per bin. Is this expected?
Operating System and Version
..
compiler
..
The version of the key4hep stack
source /cvmfs/sw.hsf.org/key4hep/setup.sh
Package Version
2025_05_26
Reproducer
I generated 3000 events using the code here:
/eos/experiment/fcc/users/m/mgarciam/mlpf/condor/test/data_generation
the result of the data generation is in /eos/experiment/fcc/users/m/mgarciam/mlpf/condor/test/3
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reproducer at /eos/experiment/fcc/users/m/mgarciam/mlpf/condor/test/data_generation and the generated results in /eos/experiment/fcc/users/m/mgarciam/mlpf/condor/test/3, using the key4hep setup and package version 2025_05_26. Reproduce the electron cluster-versus-track plots and compare the behavior with issue 80. Done means the expected acceptance is established or the responsible configuration or behavior is identified and documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100