From 625258c5ed40b43ca62db0dce62a7093efe65063 Mon Sep 17 00:00:00 2001 From: Mattia Faggin Date: Wed, 2 Jul 2025 11:04:12 +0200 Subject: [PATCH 1/2] Add reference to track tuner vs. phi. --- docs/basics-usage/HelperTasks.md | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-) diff --git a/docs/basics-usage/HelperTasks.md b/docs/basics-usage/HelperTasks.md index f0983345..9a22606c 100644 --- a/docs/basics-usage/HelperTasks.md +++ b/docs/basics-usage/HelperTasks.md @@ -754,7 +754,7 @@ The overall table flow is illustrated here: -### TrackTuner +## The TrackTuner class The `TrackTuner` class ([Common/Tools/TrackTuner.h](https://github.com/AliceO2Group/O2Physics/blob/master/Common/Tools/TrackTuner.h)) allows to smear the reconstructed track parameters. Such tool is primarely conceived to smear the parameters of tracks reconstructed in MC simulations according to the discrepancy between data and MC of the dcaXY and dcaZ. ```note @@ -780,7 +780,7 @@ This object can be configured through the `Configurable trackTunerP * `bool isInputFileFromCCDB`: the `pathInputFile/nameInputFile` is searched in CCDB if this flag is `true`, otherwise in the local file system (debug purposes) * `bool usePvRefitCorrections`: if this flag is `true`, the track smearing is performed using mean, resolution and pulls parametrizations vs. pt of dcaXY, dcaZ calculated w.r.t. primary collision vertex refitted w/o the current track, if this was originally a PV contributor ```note -In pp collisions, one should use `usePvRefitCorrections == true` +In pp collisions, there is a difference between `usePvRefitCorrections == true` and `usePvRefitCorrections == false`. In the former case, the parametrizations are obtained after refitting the primary vertex by removing from its fit the probe track, if it was originally a contributor. This is not relevant in Pb-Pb collisions. ``` * `std::string pathFileQoverPt`: path to browse to find the correction file for the `q/pt` smearing @@ -799,15 +799,18 @@ The string `trackTunerParams` must follow the format: `=|< The dcaXY, dcaZ parametrization currently available are the following: -* proxy for pp @ 13.6 TeV: [trackTuner_DataLHC23fPass1_McLHC23k4b_run535085.root](http://alice-ccdb.cern.ch/browse/Users/m/mfaggin/test/inputsTrackTuner/pp2023) - Data: LHC23f apass1, run 535085. - MC: LHC23k4b, run 535085. - Slides [here](https://docs.google.com/presentation/d/1_bsxzgB1DdVu-mxRwhpZ-U65c4J9iL2IH8xUEP3tv4Q/edit?usp=sharing). -* [NEW] proxy for pp @ 13.6 TeV: [trackTuner_DataLHC23hPass4_McLHC23k4g.root](http://alice-ccdb.cern.ch/browse/Users/m/mfaggin/test/inputsTrackTuner/pp2023/pass4/correct_names) +* proxy for pp @ 13.6 TeV: [trackTuner_DataLHC23hPass4_McLHC23k4g.root](http://alice-ccdb.cern.ch/browse/Users/m/mfaggin/test/inputsTrackTuner/pp2023/pass4/correct_names) Data: LHC23h apass4. MC: LHC23k4g. Slides [here](https://docs.google.com/presentation/d/10d1fE7Dh7OukTNgwwOhS8JQCEqzWZ3yjYZmpjntTDWw/edit?usp=sharing). +* proxy for pp @ 13.6 TeV in 24 phi intervals: [trackTuner_DataLHC23pass4ThinSmall_McLHC23k4gSmall.root](http://alice-ccdb.cern.ch/browse/Users/m/mfaggin/test/inputsTrackTuner/pp2023/pass4/vsPhi) + Data: LHC23_pass4_thin_small, runs 535613, 535621, 535623, 535624, 535627, 535644, 535645, 535711, 535716, 535721, 535725 + MC: LHC24k4g_small, runs 535613, 535621, 535623, 535624, 535627, 535644, 535645, 535711, 535716, 535721, 535722, 535725 + Slides [here](https://docs.google.com/presentation/d/1JL8nHY7yJ-PhCqTNTJq8y3dHm5XLe3Nd4bT27yjp97U/edit?usp=sharing) * proxy for Pb-Pb @ 5.36 TeV: [trackTuner_DataLHC22sPass5_McLHC22l1b2_run529397.root](http://alice-ccdb.cern.ch/browse/Users/m/mfaggin/test/inputsTrackTuner/PbPb2022) Data: LHC22s apass5, run 529397. MC: LHC22l1b2, run 529397. Slides [here](https://docs.google.com/presentation/d/1sIXWMckaPZJir3gNLeDnB2TorNJrjXKcGJvyTvz5V8s/edit?usp=sharing). +* proxy for PbPb @ 5.36 TeV in 24 phi intervals: [trackTuner_DataLHC24zzh_apass4_McLHC24e2_MCflat13.root](http://alice-ccdb.cern.ch/browse/Users/m/mfaggin/test/inputsTrackTuner/PbPb2023/apass4/vsPhi) + Data: LHC23zzh_apass4 + MC: LHC24e2 From 42ebbdb339d0358f1680fdc93193b0eb0066bcff Mon Sep 17 00:00:00 2001 From: Mattia Faggin Date: Thu, 3 Jul 2025 11:53:02 +0200 Subject: [PATCH 2/2] Add nPhiBins. --- docs/basics-usage/HelperTasks.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/basics-usage/HelperTasks.md b/docs/basics-usage/HelperTasks.md index 9a22606c..f511b050 100644 --- a/docs/basics-usage/HelperTasks.md +++ b/docs/basics-usage/HelperTasks.md @@ -788,7 +788,8 @@ This is not relevant in Pb-Pb collisions. * `bool updateCurvature`: flag to enable the update of the track curvature, i.e. `q/pt`, at the particle production point * `bool updateCurvatureIU`: flag to enable the update of the track curvature, i.e. `q/pt`, at the innermost update (IU) point * `float oneOverPtMC` (MC) and `float oneOverPtData` (data): the ratio `oneOverPtData/oneOverPtMC` defines the scaling factor to the `q/pt` residual to smear the track pt -* `fillTrackTunerTable`: flag to enable the filling of a new table containing for each track the smeared `q/pt` at the IU point +* `bool fillTrackTunerTable`: flag to enable the filling of a new table containing for each track the smeared `q/pt` at the IU point +* `int nPhiBins`: number of phi intervals in which the parametrizations are provided. The currently-supported cases are `nPhiBins=0` (phi integrated) and `nPhiBins=24` (24 phi bins) ```note * The `TrackTuner` allows also to smear the `q/pt` if only one between `updateCurvature` and `updateCurvatureIU` is `true`