Parameters for online processing of mCBM 2025 data Part 2
Starter: Current master
TODO per group:
- Find assignee
- Ask @p.-a.loizeau to make them
developer
ofmcbm/cbmroot_parameter
if not already the case - 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
- Tick the box(es) (or ask @p.-a.loizeau if not possible due to rights)
DEADLINE: 13/02/2025 evening!!!!
Progress tracking (based on the existing files from past years):
-
BMON -
Assigned? -
BmonReadout.yaml
-
More files needed? (e.g. Reco or Calibration?)
-
-
STS -
Assigned? -
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: @apuntke -
More files needed? (e.g. Reco or Calibration?)
-
-
TRD-2D -
Assigned: @a.bercuci -
TrdHitfinder2DPar.yaml
? -
More files needed? (e.g. Reco or Calibration?)
-
-
RICH-NCAL-FSD -
Assigned? -
More files needed? for now all hard-coded in classes to the best of @p.-a.loizeau knowledge
-
-
PASTA -
Assigned: @bartosz.sobol -
More files needed?
-
-
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: @s.zharko -
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:
- 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)
- 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
Merge request reports
Activity
assigned to @p.-a.loizeau
added CodeOwners label
- Resolved by Pierre-Alain Loizeau
@a.bercuci Could you please confirm that the
TrdHitfinder2DPar.yaml
from last year is enough? or is it part of the files you want to update this evening/night?I made a commit doing a symbolic link to the
mcbm2024_05
for now
mentioned in merge request !223 (closed)
mentioned in merge request !225 (closed)
- Resolved by Pierre-Alain Loizeau
TofReadout.yaml is tickmarked - shall I still update?
added 1 commit
- f8a44b64 - mCBM 2025: Add preliminary TOF calibration for offline
added 1 commit
- 04429bf5 - online: New TOF unpack mapping valid for production, not working for last week commissioning data
added 6 commits
-
bb45d862 - 1 commit from branch
CbmSoft:master
- eb25ce8c - mCBM 2025: symbolic link to 2024 TRD2D HitFinder par file
- abd2325d - mCBM 2025: Add preliminary TOF calibration for offline
- e86ae743 - online: New TOF unpack mapping valid for production, not working for last week commissioning data
- 3a0a2ced - mCBM 2025: Add preliminary alignment from NH for silver setup for offline
- 61b8c67c - online: tracking configs and BMon readout
Toggle commit list-
bb45d862 - 1 commit from branch
After discussion with @a.toia few days ago, assuming that
LandauWidthTable.txt
does not need to be changed ever
@v.friese File that still need some attention and/or confirmation that using a link to the one of last year is ok:
RecoParams.yaml
@s.zharko Files that still need some attention and/or confirmation that using a link to the one of last year is ok:
ca_params_online.yaml
-
mcbm_beam_2025_02_silver_XXXXXX.ca.par
? mcbm_beam_2025_02_silver.kf.setup
Please let me know if I can merge the current state and we do eventual updates to these files in a
Part 3
MR or whether I should wait before mergingadded 6 commits
-
16488256 - 1 commit from branch
CbmSoft:master
- 5056f6c4 - mCBM 2025: symbolic link to 2024 TRD2D HitFinder par file
- a9c3eedd - mCBM 2025: Add preliminary TOF calibration for offline
- 05374f33 - mCBM 2025: Add preliminary alignment from NH for silver setup for offline
- 7dee8e7c - online: tracking configs and BMon readout
- 0334315c - online: New TOF unpack mapping valid for production, maybe not working for...
Toggle commit list-
16488256 - 1 commit from branch
- Resolved by Pierre-Alain Loizeau
Added tracking online and corrected tof v24f digibdf parameters in !227 (merged)
added 7 commits
-
0334315c...33f6e85f - 2 commits from branch
CbmSoft:master
- df4757fa - mCBM 2025: symbolic link to 2024 TRD2D HitFinder par file
- a938fa72 - mCBM 2025: Add preliminary TOF calibration for offline
- e8d6025f - mCBM 2025: Add preliminary alignment from NH for silver setup for offline
- 1f2d2e91 - online: BMon readout
- 9f653faa - online: New TOF unpack mapping valid for production, maybe not working for...
Toggle commit list-
0334315c...33f6e85f - 2 commits from branch
@p.-a.loizeau, I added current TOF and BMON hitfinder parameters here !229 (diffs)