Draft: turning on boundary check in the extrapolation

It has been found out that due to no boundary condition during the extrapolation in hole recovery, there are additional holes (especially in the BMGs) being added on the track where hits are already present in the same layers (and tracks are not crossing the holes). For details see presentation in muon sw meeting.

Here including the standard pull checks where only boundary check in MDT chambers have been addreseed AllPerigeeChecks.pdf

• In general, we see around the same amount of tracks and a bit less of holes as expected. However, these plots are probably too crude since higher hole occupancy was only seen in some of the chambers. I will try to make some validation plots only targeting those chambers.

Here I set all the boundary check to true (in all systems not just MDT) AllPerigeeChecks_allboundaryCondOn.pdf

• In this case we observe a few percent (~3%) increase in number of tracks. This increase seem quite flat over the number of the inner/middle/outer hits, whereas in case of the holes we have more cases with 0 holes.