rest-for-physics / rest-for-physics/tracklib
TRestTrackReconnection not properly identifying end-tracks
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
This issue is created to follow up a problem discussed on the following forum post
http://rest-forum.unizar.es/t/pandaxiii-mc-pipeline-at-development-v2-3/410/15
The problem is that normally TRestTrackReconnectionProcess should shift the order of hits so that the longer edge is suppressed (minimising the total track length). In other words, just re-ordering in the array so that hit_0 and hit_N correspond with the long edge.
Also the reconnection routine, such as breaking tracks and find an optimum reconnection should solve the problem observed on the track observed at the forum post. This last, fixing reconnection through sub-tracks, might just need optimisation of fNSigmas parameter.
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 by reading the linked forum discussion and inspecting TRestTrackReconnectionProcess, including how it orders hits and uses fNSigmas. Reproduce the reported track-reconnection case, then verify that end-tracks are identified with the long edge suppressed and that sub-track reconnection produces the expected result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- data
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100