Draft: Parameters for online processing of mCBM 2025 data (at least February ones)

Starter: single folder with examples of 2025 specific files and example of files not modified for 2025

TODO per group:

1. Find assignee
2. Ask @p.-a.loizeau to make them developer of mcbm/cbmroot_parameter if not already the case
3. Commit missing files, add more in checklist if needed (ask @p.-a.loizeau with filename)

   git clone git@git.cbm.gsi.de:mcbm/cbmroot_parameter.git cbmroot_parameter_mcbm2025  # if you prefer ssh key login
   # or git clone https://git.cbm.gsi.de/mcbm/cbmroot_parameter.git cbmroot_parameter_mcbm2025 # <= if you prefer https login
   cd cbmroot_parameter_mcbm2025
   git checkout mcbm_2025_online
   # if new commits visible in the MR:
   git fetch origin
   git rebase origin/mcbm_2025_online
   # Add your own files
   git add XXXXXX
   git commit -m"Descriptive message"
   git push

4. Tick the box(es) (or ask @p.-a.loizeau if not possible due to rights)

DEADLINE: 11-12/02/2025

Progress tracking (based on the existing files from past years):

• BMON
  • Assigned?
  • BmonReadout.yaml
  • More files needed? (e.g. Reco or Calibration?)
• STS
  • Assigned?
  • StsReadout.yaml
  • StsChannelMaskSet.yaml
  • StsWalkMap.yaml
  • StsHitfinder.yaml
  • More files needed? (e.g. Reco or Calibration?)
• TOF
  • Assigned?
  • TofReadout.yaml
  • TofCalibratePar.yaml
  • TofHitfinderPar.yaml
  • More files needed? (e.g. Reco or Calibration?)
• TRD-1D
  • Assigned?
  • TrdHitfinderPar.yaml
  • TrdReadoutSetup.yaml
  • More files needed? (e.g. Reco or Calibration?)
• TRD-2D
  • Assigned?
  • TrdReadout2DSetup.yaml
  • TrdHitfinder2DPar.yaml
  • More files needed? (e.g. Reco or Calibration?)
• RICH-NCAL-FSD-PASTA
  • Assigned?
  • More files needed? for now all hard-coded in classes to the best of @p.-a.loizeau knowledge
• Event Building
  • Assigned?
  • EventbuildConfig.yaml
  • More files needed? (e.g. Reco or Calibration?)
• Reco
  • Assigned?
  • RecoParams.yaml
  • LandauWidthTable.txt ?
  • More files needed? (e.g. Reco or Calibration?)
• Tracking
  • Assigned?
  • TrackingChainConfig.yaml
  • ca_params_online.yaml
  • mcbm_beam_2025_02_silver_XXXXXX.ca.par ?
  • mcbm_beam_2025_02_silver.kf.setup
  • More files needed? (e.g. Reco or Calibration?)

Ping (sorry, based on names I know): @a.toia. @n.herrmann, @a.bercuci, @s.zharko, @v.friese, @p.kaehler, @c.pauly

Important:

1. please do NOT create other branches in the mCBM fork or use this branch to base you analysis, this is only meant to be used for the MR and is NOT an mCBM fork as we did in previous years (if this happen I will cleanup the fork or re-assign this MR to whomever wants it)
2. I will rebase the mCBM fork/branch only periodically and in a coordinated way in order to minimize the required work, probably with and announcement during a Beamtime meeting to make sure everybody refresh their copy