-
Notifications
You must be signed in to change notification settings - Fork 4
Completing the Algorithm #6
Comments
Ok, 0th order is
However, I shall say that this job is complete wasting of time, since the only information which should be used during fitting is probability of each wire to be signal, because
And I believe that modified RANSAC will work normally with this. |
Perhaps to this effect, we can do a pre-fitting procedure. This is basically a rough fit to make sure we're not returning garbage. This is done in current algorithms. We could be really clever and fit in z as well using the separation of the even-odd peaks. This information should be used somewhere. |
ok, for 0th order, how do I "find peaks"? Using is_max()? And yes, RANSAC looks like a great idea for pre-fitting. I'll have to look into the current fitting techniques. this is what the track fitting is being built on so far I think: hopefully it will play nice with whatever we come up with. |
Iteratively - find a maximum, mark those signal-like wires it 'covers' as 'resolved'. If there are too many 'unresolved' signal-like tracks left - do hough again and find a maximum. |
We must add penalties for gaps in signal track. This will help normalize tracks that are longer by comparing it to tracks that are continuous. |
idea for spiral fitting for RANSAC base fitting function: |
So far, our classifier does an excellent job of separating signal hits from background hits.
On top of this, we need to take each event, and return a collection of wire ID's that correspond to a track. I have a feeling we have all the machinery we need, given the hough transform and clean, final environment.
Doing this to 0th order would mean I can present these results to the collaboration.
The text was updated successfully, but these errors were encountered: