Test full search mode of Velo Tracking ("overlap" tracks)
Add a test for the full search mode of Velo Tracking (finds all hits in the overlapping regions). See the discussion at !2364 (comment 4271553)
@graven: Very good to see those checks! Now, is it possible to turn those checks into a test which is run as part of the nightly builds? (e.g. just a counter in some algorithm which for a given sample prints out the number of overlap hits encountered -- or if one requires tracks to have overlap hits, how many tracks are selected i.e. what is the fraction of tracks like the one on slide 4 -- or ... ) That way any regression gets spotted as soon as it happens as opposed to when someone will explicitly look at some later stage -- which will make it easier to spot the cause, and push the burden of checking to the person who modified the code, when they modified it, as opposed to eg. you after the code you use has been updated to a new release some time after the change was made, and you then have to figure out what happened when... so adding such monitoring now will reduce the work to be done in future.
@bimitres: I think it is possible to turn these checks in a test. For the overlap residuals I have a monitor that I need to merge after I commit the changes I made within the last weeks, some counter of the number of these tracks can be added there and we need to set that up to run somewhere.