OK for the PVs, but we need a better solution for dealing with
SVs. Currently these are smeared with the same parameterisation
for PVs, assuming 4 tracks. Not clear if we need to split RapidVertex
into two classes (derived from common parent), use a flag in
RapidVertex to distinguish the cases, or have a separate
RapidVtxSmear class that can be configured differently for each case.
OK for the PVs, but we need a better solution for dealing with SVs. Currently these are smeared with the same parameterisation for PVs, assuming 4 tracks. Not clear if we need to split RapidVertex into two classes (derived from common parent), use a flag in RapidVertex to distinguish the cases, or have a separate RapidVtxSmear class that can be configured differently for each case.