Simon Schuett authored 3 weeks ago and Volker Friese committed 3 weeks ago

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%.

 - QA for V0-trigger
 - Masking channels (BMON as example) in digi event-selector

kfp-online: linking ROOT::Hist and ROOT::MathCore, changed the dependency on CbmKFParticle<Online/Offline>Interface to PUBLIC

- using a KFParticle version with no ROOT dependencies

- V0Finder:
  - YAML config
  - cuts on velocity of pion and proton candidates
  - enhanced cut for decay length (0.1 -> 5 cm)

- mcbm_beam_2025_02_14_silver setup is added to the runId map;
- actualisation of CbmOnlineParWrite;
- actualisation of ParFiles.cxx