Location:
QTracker_main/src/models/multi_track_finder.py in dev branch
Problem:
The current multi-track finder does not remove or suppress hits belonging to already identified tracks. Without this, repeated runs can produce identical or confused track proposals.
Naively zeroing out hits is insufficient due to:
- Error propagation
- Overlapping tracks
- Shared detector elements
Proposed Solution:
Implement soft subtraction based on detector-wise softmax scores.
Algorithm:
For each detector in an event:
- Identify the detector element ID predicted to be a signal hit for the current track.
- Retrieve the highest softmax probability for that detector.
- Subtract this probability from the corresponding hit value.
Example:
- Detector: I
- Event: J
- Element ID: K
- Predicted signal hit softmax: 0.9
- Original hit value: 1.0
- Updated hit value: 1.0 - 0.9 = 0.1
Safety Constraint:
- Enforce a lower bound of zero to avoid negative values:
new_value = max(0.0, original_value - softmax_value)
This handles cases where overlapping mu+ and mu- tracks share the same detector element.
Location:
QTracker_main/src/models/multi_track_finder.pyindevbranchProblem:
The current multi-track finder does not remove or suppress hits belonging to already identified tracks. Without this, repeated runs can produce identical or confused track proposals.
Naively zeroing out hits is insufficient due to:
Proposed Solution:
Implement soft subtraction based on detector-wise softmax scores.
Algorithm:
For each detector in an event:
Example:
Safety Constraint:
new_value = max(0.0, original_value - softmax_value)
This handles cases where overlapping mu+ and mu- tracks share the same detector element.