Inconsistency between Pr and v1 VELO tracks
The converter seems to (be able to) change information of a track during conversion, hence introducing inconsistencies: https://gitlab.cern.ch/lhcb/Rec/-/blob/master/Pr/PrConverters/src/fromPrTracksV1Track.cpp#L421
Some PV finding algos use Pr some use v1, input should (always) be consistent. v1 is persisted, TBLV uses Pr as input, not (by construction) consistent with v1.
If this functionality is being used (changing the information), it should be moved to another algorithm, clear to the configurer.