...
The original concept of QTracker was proposed to be modular such that each independent part could work to achieve a particular part and could if needed work as a stand-alone function/class. As an example The Event Filter could help anyone filter events for their analysis of help filter OM/OR events if it is made to be used that way. This also make each module easier to test directly and turn into something useful. We should at least try this with two of the QTracker models. The Track Finder also fits into this category if its coupled with a Tracker Filter.
The Event Filter Track Finder should be followed by a Track Filter. After track candidates are found they should be filter out based on a quality metric as well as by seeing if the track hit patterns actual match that of something coming from the target. This may be two distinct cuts, one from the final track quality metric and one from a target-dump classifier (could go together in if metric is part of classifier training). There is certainly some major overlap of target and dump hits that make this part challenging, but this can be iterated as well. One Perhaps one filter before reconstruction and one filter after which also used uses the final 3-momentum and vertex information which has a narrowed training space.
...