Skip to content
Snippets Groups Projects
Select Git revision
  • 10a8de1d0995d613deec9e5f5a4d99a38177986d
  • master default protected
  • nightly_master
  • online_much_readconf_cleanup protected
  • online_mvd_readconf_cleanup protected
  • jul25_patches
  • cleanup_rich_v25a
  • jul24_patches
  • nov23_patches
  • DC_2404
  • nighly_master
  • DC_Jan24
  • DC_Nov23
  • DC_Oct23
  • feb23_patches
  • L1Algo-dev9
  • dec21_patches protected
  • apr21_patches protected
  • dev_2025_44
  • dev_2025_43
  • dev_2025_42
  • dev_2025_41
  • dev_2025_40
  • dev_2025_39
  • dev_2025_38
  • dev_2025_37
  • dev_2025_36
  • dev_2025_35
  • dev_2025_34
  • dev_2025_33
  • dev_2025_32
  • dev_2025_31
  • dev_2025_30
  • RC_jul25
  • dev_2025_29
  • dev_2025_28
  • dev_2025_27
  • dev_2025_26
38 results

algo

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Simon Schuett authored and Volker Friese committed
    Fix cluster and hit finding in the STS detector when using 32-bit floating-point
    precision. The issue occurs when calculating time differences between digis or
    clusters with large timestamps - 32-bit floats lack sufficient precision for
    representing nanosecond timestamps in the mCBM setup.
    
    Add helper methods GetTimeDiff() that first convert timestamps to int before
    calculating the difference, preserving precision and sign. Replace direct
    floating-point timestamp subtractions throughout the code with calls to these
    helper methods.
    
    This resolves hit count discrepancies between 32-bit and 64-bit float versions,
    reducing the difference from ~2.6% to ~0.04%.
    10a8de1d
    History