[mCBM 2022] Bring mTOF 21k geometry + rrelated/updated parameters + related fixes
- Update geometry and parameters hashes to most recent ones (bring tof 21k + also previously stacked mvd geo creation macros)
Copy the to tof clusterizer initialization for 2022 mCBM in the 2024 mCBM folder to allow different settingsHard-code the TOF calibration filename in the tof clusterizer initialization for 2022- Force the specific filename for run 2391 in the 2022 reco macros and the mTOF clusterizer initialization script (and higher runs in most 2022 macros)
- Remove switch to custom alignment file in 2022 mcbm_event_reco_l1 macro for TOF 21k
@a.bercuci Could you please check quickly (not in all details) that this works also for the event_hreco_L1
macro? it passes the CI tests locally so the macros splitting event and reco should be ok
Merge request reports
Activity
added Geometry Parameters mCBM labels
requested review from @a.bercuci
assigned to @p.-a.loizeau
- Resolved by Alexandru Bercuci
Hi @p.-a.loizeau, Your modification is very abrupt in the ini_tof_clusterizer.C. Additionally you left in mcbm_event_reco_L1.C the line which points to my old alignment in case of v21k_mcbm for tof. I will put here my version which besides being a little softer will also add PV calculation on the 2022 data which I think should be there. Pls consider it. mcbm22.diff
- Resolved by Pierre-Alain Loizeau
There should be also the geometry file "mcbm_beam_2022_05_23_nickel.geo.root" updated for the 21k geometry. IS this not included in the distribution ? If yes it has also to be regenerated (I can provide).
added 1 commit
- 3a415010 - [mCBM 2022] Bring mTOF 21k geometry + rrelated/updated parameters + related fixes
Dear @f.uhlig, @p.-a.loizeau,
you have been identified as code owner of at least one file which was changed with this merge request.
Please check the changes and approve them or request changes.
added CodeOwners label