Pixel track conf for UPC

added 23.0 HeavyIon Reconstruction Tracking labels

added 1 commit

63b808d1 - removing unnecessary changes

We found some inconsistencies between the configuration use in RUN2 and what is now for Pixel tracks. Max d0, holes and min pt. In this Draft I'm putting them back to the old values. But for some reason no matter the change I made, the min pT we see in the AOD is always cut at 100 MeV (we want 50 MeV), so it not picking what is set in the configuration see: TrackingPassFlags.py#L970

Is there some last moment tracking selection? or some other flag setting the min pt ?

Thanks for any help, Sebastian.

mentioned in merge request !65621 (merged)

added 1 commit

bb04b648 - message

Compare with previous version

marked this merge request as ready

added review-pending-level-1 label

Jenkins please retry a build

resolved all threads

added 1 commit

872929dd - removing comments code

Compare with previous version

This merge request affects 1 package:

Tracking/TrkConfig

This merge request affects 1 file:

Tracking/TrkConfig/python/TrackingPassFlags.py

This merge request affects 1 package:

Tracking/TrkConfig

This merge request affects 1 file:

Tracking/TrkConfig/python/TrackingPassFlags.py

CI Result SUCCESS (hash bb04b648)

	Athena
externals
cmake
make
tests

Full details available on this CI monitor view. Check the JIRA CI status board for known problems
Athena: number of compilation errors 0, warnings 0
For experts only: Jenkins output [CI-MERGE-REQUEST-CC7 77556]

CI Result SUCCESS (hash 872929dd)

	Athena
externals
cmake
make
tests

Full details available on this CI monitor view. Check the JIRA CI status board for known problems
Athena: number of compilation errors 0, warnings 0
For experts only: Jenkins output [CI-MERGE-REQUEST-CC7 77558]