Skip to content
Snippets Groups Projects
Select Git revision
20 results
Search by author
  • Any Author
0 authors
  1. Mar 24, 2018
  3. Mar 12, 2018
    • Will Leight's avatar
      Fix for ATR-16605, round two · a8b711ed
      Will Leight authored 
      As discussed in !2959, a bug in the extrapolator was in rare cases causing thousands of scatterers to be added to a track.
Thanks to Peter Kluit, we believe that we have now tracked this down to a bug in the STEP_Propagator.
The propagator was getting stuck in a volume and iterating forward in steps of 1-10 um, adding a scatterer each time.
At the time, we implemented a "fix" that simply aborted the track-finding when more than 1000 scatterers were found on a track.
Now, the underlying issue should finally be resolved.
It appears that the problem was occurring when the propagator found two solutions from the starting surface, the first of which was trivial and the second of which gave a negative distance estimate.
In this case, the propagator would automatically flip direction, bringing it back almost to the starting point, where it would add a scatterer.
Then the process would repeat thousands of times, until it got far enough away from the start position that there was no second solution, or one with a postive distance estimate.
By identifying these cases and rejecting their negative-distance second solutions, this problem is avoided.
Given the rarity of this problem, FT0 tests naturally show no violation, results are available at /afs/cern.ch/work/w/wleight/public/MuonSW/tooManyScatterers/RunTier0Tests.log


Former-commit-id: 0c1c0d3b0c6bd977208a58a2fc9c9062d4516c7c
      a8b711ed
  5. Mar 01, 2018
    • Vincent Pascuzzi's avatar
      Fix use of smart pointers in `Trk::RectangularSegmentation' · e60b7752
      Vincent Pascuzzi authored 
      The previous commit to this class incorrectly used smart pointers,
specifically, their ownership was not released. Moreover, the wrapped
objects were initialised incorrectly, leading to the same
`Trk::PlaneSurface' being duplicated, filling the vector with the same
surface.

Although it appears the owning objects free memory, we play it safe by
keeping the smart pointers here, as opposed to resorting back to raw
ones.


Former-commit-id: d79f604018172cc9533a35c453d05a589554a346
      e60b7752
  7. Feb 20, 2018
  9. Feb 09, 2018
  11. Jan 09, 2018
  13. Dec 21, 2017
  15. Dec 12, 2017
  17. Dec 10, 2017
  19. Dec 07, 2017
  21. Nov 30, 2017
  23. Nov 24, 2017
  25. Nov 20, 2017
  27. Nov 17, 2017
  29. Nov 13, 2017
  31. Nov 10, 2017