Mcbm kfparticle mr
Merge request reports
Activity
added 23 commits
- 6c6f7be1...2f804a05 - 13 earlier commits
- 1f285293 - test2
- c5f58153 - test4
- 8b407c46 - test 5
- 59a8ab79 - merge request v3
- 36ad458d - Remove file(s) from Git tracking but keep locally
- 01ca1c29 - Remove file(s) from Git tracking but keep locally
- f8144b72 - remove local files
- e64653fa - testv6
- 4fc7b6cf - Permanently delete files
- 97c8bfe3 - Add untracked files
Toggle commit list- Resolved by Pierre-Alain Loizeau
- all the automatically generated files should be removed from the merge request (e.g., gphys.dat, TRhistos.root), as well as backup files (e.g., .run_reco_digievent.C.swp)
- what is the difference between the /macro/beamtime/mcbm2022/mcbm_reco_kf_*.C files? As I see, there are different versions of them. Do the macros have different purposes? If no, please select the latest working one and remove the others from the merge request
added 3 commits
-
97c8bfe3...712d0b65 - 2 commits from branch
computing:master
- 20688674 - Update KFParticleFinder for mCBM Lambda analysis
-
97c8bfe3...712d0b65 - 2 commits from branch
added 1 commit
- 49c8caab - Update KFParticleFinder for mCBM Lambda analysis
- Resolved by Pierre-Alain Loizeau
@y.h.leung The two failing tests are
mcbm_reco_toftr_2022_2391
andmcbm_reco_toftr_digievent_2022_2391
I suspect this is due to your changes in
macro/beamtime/mcbm2022/ini_tof_trks.C
, as all the rest is either unrelated or new files
requested review from @se.gorbunov
added 1 commit
- cfd326b1 - fix to pass CI test + add setter to kfpartcleanalysis
added 1 commit
- cadf24cf - fix to pass CI test + add setter to kfpartcleanalysis
Dear @f.uhlig, @v.friese, @p.-a.loizeau, @se.gorbunov, @s.zharko,
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
mentioned in merge request CbmSoft/cbmroot_parameter!203 (closed)
mentioned in merge request !1942 (merged)
@s.zharko Hi Sergei,
Here is a summary of what the codes are doing: Macro: macro/beamtime/mcbm2024/mcbm_reco_kf_lambda.C This macro takes data digivents as input, performs hit reconstruction, track reconstruction, and KFParticle finder. KFParticle finder is called on L604
The first task is kfParticleFinderPID The macro uses: kfParticleFinderPID->UseTopoPID(); The code is located at reco/KF/CbmKFParticleFinderPID.cxx L663 It calculates the DCA defined by two STS hits L667-708, and pushes back the PID on L727
The next task is CbmKFParticleFinder kfParticleFinder->SetmCBMmode(); sets fmCBM to true. kfParticleFinder->UseOrigin(); uses 0,0,0 as vertex The code is located at reco/KF/CbmKFParticleFinder.cxx At L195, because fmCBM is true, global tracks are used instead of STS tracks From L233-273, the T0 is found by looping over TOF hits. Then the time for each TOF hits is reset by subtracting T0 Some cuts are skipped when using mCBM mode. Because the tracking is still not finalized, there is no need to set such cuts as default The next part is on L358-425, where velocity is calculated according to the time and the length. Then, using the PID, q/p is calculated, and added to the track parameters. The covariance matrix is also updated here L493-494. We skip events with less than 1 proton and 1 pion because you cannot reconstruct lambda from these events L554: Set vertex to 0,0,0 L571-588: The B-field is 0, so we just set to 0. The vChiToPrimVtx is set to 999. This value ensures that for mCBM all tracks will enter reconstruction. There is no proper primary vertex reconstruction so we just set this to a large value
The next task is CbmKFParticleFinderAnalysis This task is to save the lambda candidate information. The lambda_tree is a ttree and is defined in L98-149 L278 is the beginning of the loop for kfparticle. It basically loops over all particles, and when the PDG code is 3122 (lambda), it saves the information, including pT, mass, decay length, etc.
Let me know if you need more information.
Best, Yue Hang
added Analysis label
added mCBM label