Skip to content
Snippets Groups Projects
  1. Jun 30, 2020
  2. Jun 26, 2020
  3. Jun 18, 2020
  4. Jun 11, 2020
    • scott snyder's avatar
      InDetTrigAmbiguitySolver: Complain about misconfigured MT jobs. · b1b0e669
      scott snyder authored
      The thread-safety checker was not properly checking calls to virtual functions.
      When that is fixed, we get a warning about the call to
      IPRDtoTrackMapExchange::setPRDtoTrackMap.
      
      This is indeed not thread safe, and is supposed to be used only for
      backwards compatibility with run 2.
      
      To resolve this, split out the non-thread-safe part into a separate function.
      We suppress the thread-safety checker warning in the call to it,
      but we also explicitly check and fail the job if we're running
      such a run 2 configuration with more than one thread.
      b1b0e669
  5. Jun 01, 2020
  6. May 28, 2020
  7. May 27, 2020
  8. May 15, 2020
  9. Apr 11, 2020
  10. Apr 09, 2020
  11. Mar 27, 2020
  12. Mar 25, 2020
  13. Mar 04, 2020
  14. Feb 26, 2020
  15. Feb 20, 2020
  16. Jan 10, 2020
  17. Dec 24, 2019
  18. Dec 10, 2019
  19. Nov 25, 2019
  20. Nov 20, 2019
    • Goetz Gaycken's avatar
      Made member functions of TRT extension and segment finder tools constant. · 0077ab07
      Goetz Gaycken authored
      - Moved mutable members into EventData struct or replaced them by local variables
        which are passed through.
      - Made member functions constant.
      - Removed remaining magnetic field init callback. Field mode now adjusted per event.
      - Removed most stream operators to dump tools. The dump methods which provide the
        actual functionality are still available.
      0077ab07
  21. Nov 18, 2019
    • Goetz Gaycken's avatar
      Migrate ambiguity processor from PRD_Association tool to PRD-to-track maps. · 598c55c8
      Goetz Gaycken authored and Walter Lampl's avatar Walter Lampl committed
      - Use a PRD-to-track map rather than the PRD_AssociationTool which conains a PRD-to-track map
        internally. This is needed to resolve ATLASRECTS-5005.
      - Made all methods const.
      - The score processor does not create track copies anymore, thus PRD-to-track maps stay valid for
        scored tracks.
      - The ambiguity processors now use a helper class which manages the new and original tracks i.e.
        tracks with mixed ownership, and creates track copies only for the final track collection if
        necessary.
      - Moved debug ntuple code of simple ambiguity processor to a new derived class, to improve the
        readability.
      598c55c8
  22. Oct 25, 2019
  23. Oct 17, 2019
  24. Oct 07, 2019
  25. Sep 17, 2019
  26. Sep 16, 2019
    • Goetz Gaycken's avatar
      Minimal modification for single threaded PRD to track association with MT scheduler. · aa6a90d1
      Goetz Gaycken authored
      The association map is stored in storegate for cases in which the PRD association
      is shared across multiple algorithms. The PRD_AssociationTool is still used for the
      cases in which the PRD association is shared between multiple tools but which are
      all related to a single algorithm instance. Thus, the PRD_AssociationTool still has
      to be public for tha latter cases. The current configuration does not ensure
      that tool instances are confined to single algorithms. Thus, in case of more than
      one thread, different algorithms may still operate concurrently on the same internal
      association map, which can be mitigated by configuration changes (to be done).
      aa6a90d1
  27. Sep 10, 2019
  28. Sep 04, 2019
  29. Sep 02, 2019
  30. Aug 30, 2019
  31. Aug 27, 2019
  32. Aug 02, 2019
  33. Jul 02, 2019
  34. Jun 04, 2019
  35. Jun 03, 2019
  36. May 31, 2019
Loading