Skip to content
Snippets Groups Projects

Most recent common geometries and parameters for mCBM 2024-05 + related fixes

Merged Pierre-Alain Loizeau requested to merge p.-a.loizeau/cbmroot:mcbm2024_geo_pars_nh into master
2 unresolved threads
  • Bring latest (at least last communicated) parameters for mCBM 2024 through hashes update (both "legacy" and "online")
  • Use new calib file with different name in the mCBM 2024 "legacy" macros
  • Add code changes which where needed/used to regenerate the online YAMl parameters matching the "legacy" changes

@s.zharko Two things:

  1. This steals some of the fixes you had prepared in !1862 (closed), we will have to see how easily it works during rebase (may have some conflicts which are not auto-solved)
  2. I did not regenerate the CA parameters following the recent mCBM geometry changes as the mCBM team seems focused on an analysis which does not use the "online event building + reco + tracking". We will nonetheless probably still need it if the "Data Challenge with mCBM 2024 data" is confirmed for next month

=> Most probably we will need to revive !1862 (closed) in the coming 2-3 weeks with @v.friese help

Of interest to: @a.bercuci @a.senger @a.toia @sturm @d.emschermann @d.gutierrezmenendez @d.ramirez@gsi.de @n.herrmann @y.h.leung (by alphab order, may have missed some)

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
117 117 if (uRunId >= 812) cCalId = "831.100.4.0";
118 118 if (uRunId >= 1588) cCalId = "1588.50.6.0";
119 119 if (uRunId >= 2160) cCalId = "2160.50.4.0";
120 if (uRunId >= 2352) cCalId = "2391.5.000";
120 if (uRunId >= 2352) cCalId = "2391_1";
121 121 if (uRunId >= 2700) cCalId = "2912.1";
122 if (uRunId >= 2900) cCalId = "3026_2"; // From nh through MR 1937
  • mentioned in merge request !1973 (merged)

  • Please register or sign in to reply
    Loading