Skip to content
Snippets Groups Projects
  1. May 17, 2024
  2. May 15, 2024
  3. May 14, 2024
    • Scott Snyder's avatar
      FPGATrackSimHough: Fix cppcheck 2.14 warnings. · 89d1b3ed
      Scott Snyder authored and Tadej Novak's avatar Tadej Novak committed
      FPGATrackSimHough: Fix cppcheck 2.14 warnings.
      
      Copying values in range-for.
      Prefer returning const references to members rather than copies.
      Prefer to pass strings/containers by const reference rather than value.
      Redundant map lookup.
      89d1b3ed
  4. May 12, 2024
  5. May 10, 2024
  6. May 02, 2024
  7. Apr 30, 2024
  8. Apr 26, 2024
  9. Apr 23, 2024
  10. Apr 22, 2024
  11. Apr 20, 2024
    • Vakhtang Tsulaia's avatar
      Fixed clang warnings · 5f10c0d1
      Vakhtang Tsulaia authored
      - ActsDataPreparation/PixelClusteringTool: Unused function
      - ActsEventCnv/ActsToTrkConvertorAlg: Unused lambda capture
      - ActsTrackReconstruction/TrackFindingAlg: Reference cannot be bound to dereferenced null
      pointer in well-defined C++ code
      - FPGATrackSimHough/FPGATrackSimHough1DShiftTool: Unused static functions
      - ISF_Event/ISFTruthIncident: Delete called on non-final class that has virtual functions
      but non-virtual destructor
      5f10c0d1
  12. Apr 19, 2024
  13. Apr 18, 2024
  14. Apr 17, 2024
    • Thomas Strebler's avatar
      Clean up legacy EFTracking FPGA configs · 799a020c
      Thomas Strebler authored and Petar Bokan's avatar Petar Bokan committed
      Clean up legacy EFTracking FPGA configs
      799a020c
    • Jahred Adelman's avatar
      EFTracking/FPGATrackSim: port spacepoint-based fitting, updated Hough... · 9f6c3724
      Jahred Adelman authored and Adam Edward Barton's avatar Adam Edward Barton committed
      EFTracking/FPGATrackSim: port spacepoint-based fitting, updated Hough transforms, related changes from HTTSim (Part 1)
      
      FPGATrackSim: make track fit constants spacepoint aware
      
      Ported over from HTTSim. Since a spacepoint is formed from two strip hits
      from two layers, we keep two copies for bookkeeping purposes. At the moment
      that then means that in the fit, there are two versions of the spacepoint's
      phi coordinate-- and the z/eta coordinate is never used. This commit changes
      that so we dynamically select whether the spacepoint's coordinate is phi
      or z/eta based on whether it is in an inner or outer strip layer.
      
      This nicely avoids having to remove duplicate spacepoints, and also avoids
      having to rework a fundamental assumption of the code, which is that strip
      hits are only ever "one" dimension. Since we don't remove duplicates or
      change the number of layers it also makes it easy to mix and match strip
      hits with spacepoints; a track could (conceivably) have two strip hits
      in two layers that are one spacepoint OR two strip hits from which a
      spacepoint couldn't be formed.
      9f6c3724
    • Ioannis Maznas's avatar
      reactivate truth info in RDO analysis · 58a30da4
      Ioannis Maznas authored
      58a30da4
  15. Apr 09, 2024
  16. Apr 02, 2024
  17. Apr 01, 2024
  18. Mar 29, 2024
  19. Mar 27, 2024
  20. Mar 23, 2024
  21. Mar 17, 2024
  22. Mar 15, 2024
Loading