Tracking Utility Functions

23.10. Tracking Utility Functions#

tracking.__init__.add_tracking_reconstruction(path, components=None, pruneTracks=False, skipGeometryAdding=False, mcTrackFinding=False, trackFitHypotheses=None, reco_tracks='RecoTracks', prune_temporary_tracks=True, fit_tracks=True, use_second_cdc_hits=False, skipHitPreparerAdding=False, svd_standalone_mode='VXDTF2', use_svd_to_cdc_ckf=True, use_ecl_to_cdc_ckf=False, add_cdcTrack_QI=True, add_vxdTrack_QI=False, add_recoTrack_QI=False, pxd_filtering_offline=False, create_intercepts_for_pxd_ckf=False, append_full_grid_cdc_eventt0=True, v0_finding=True, flip_recoTrack=True, skip_full_grid_cdc_eventt0_if_svd_time_present=True)[source]#

This function adds the standard tracking reconstruction modules to a path:

  1. first we find tracks using the CDC hits only, see CDC Track Finding

  2. CDC tracks are extrapolated to SVD and SVD hits are attached, see CDC to SVD SpacePoint CKF

  3. remaining SVD hits are used to find SVD tracks, see SVD Track Finding

  4. CDC standalone tracks which don’t have SVD hits attached to them from the CDC to SVD CKF are combined with SVD standalone tracks found in the previous step using the CDC to SVD Seed CKF

  5. SVD tracks are extrapolated to CDC to attach CDC hits, see SVD to CDC CKF

  6. SVD and CDC tracks are merged and fitted, see Track Fitting

  7. merged SVD+CDC tracks are extrapolated to PXD to attach PXD hits, see SVD to PXD CKF

    Note

    PXD hits are not available on HLT. At the end of the tracking chain on HLT we have the PXD Region Of Interest Finding, that consists of extrapolating the tracks on the PXD sensors and defining regions in which we expect to find the hit. Only fired pixels inside these regions reach Event Builder 2.

  8. after all the tracks from the IP are found, we look for special classes of tracks, in particular we search for displaced vertices to reconstruct K-short, Lambda and photon-conversions, see V0 Finding.

  9. If the reconstruction uses PXD, we finally look for tracks with a wrong charge, flip and refit them to fix the charge, see Flip&Refit.

Parameters:

  • path – the path to add the tracking reconstruction modules to

  • components – the list of geometry components in use or None for all components.

  • pruneTracks – if true, delete all hits except the first and the last in the found tracks.

  • skipGeometryAdding – (advanced flag) the tracking modules need the geometry module and will add it, if it is not already present in the path. In a setup with multiple (conditional) paths however, it can not determine, if the geometry is already loaded. This flag can be used o just turn off the geometry adding at all (but you will have to add it on your own then).

  • skipHitPreparerAdding – (advanced flag) if true, do not add the hit preparation (esp. VXD cluster creation modules. This is useful if they have been added before already.

  • mcTrackFinding – if true, use the MC track finders instead of the realistic ones.

  • reco_tracks – name of the StoreArray where the reco tracks should be stored

  • prune_temporary_tracks – if false, store all information of the single CDC and VXD tracks before merging. If true, prune them.

  • fit_tracks – if false, the final track find and the TrackCreator module will no be executed

  • use_second_cdc_hits – if true, the second hit information will be used in the CDC track finding.

  • trackFitHypotheses – which pdg hypothesis to fit. Defaults to [211, 321, 2212].

  • svd_standalone_mode – Which SVD standalone tracking is used. Options are “VXDTF2”, “SVDHough”, “VXDTF2_and_SVDHough”, and “SVDHough_and_VXDTF2”. Defaults to “VXDTF2”

  • use_svd_to_cdc_ckf – if true, add SVD to CDC CKF module.

  • use_ecl_to_cdc_ckf – if true, add ECL to CDC CKF module.

  • add_cdcTrack_QI – if true, add the MVA track quality estimation to the path that sets the quality indicator property of the found CDC standalone tracks

  • add_vxdTrack_QI – if true, add the MVA track quality estimation to the path that sets the quality indicator property of the found VXDTF2 tracks (ATTENTION: Standard triplet QI of VXDTF2 is replaced in this case -> setting this option to ‘True’ will have some influence on the final track collection)

  • add_recoTrack_QI – if true, add the MVA track quality estimation to the path that sets the quality indicator property of all found reco tracks (Both other QIs needed as input.)

  • pxd_filtering_offline – If True, PXD data reduction (ROI filtering) is applied during the track reconstruction. The reconstructed SVD/CDC tracks are used to define the ROIs and reject all PXD clusters outside of these.

  • create_intercepts_for_pxd_ckf – If True, the PXDROIFinder is added to the path to create PXDIntercepts to be used for hit filtering when creating the CKF relations. This independent of the offline PXD digit filtering which is steered by ‘pxd_filtering_offline’. This can be applied for both data and MC.

  • append_full_grid_cdc_eventt0 – If True, the module FullGridChi2TrackTimeExtractor is added to the path and provides the CDC temporary EventT0.

  • v0_finding – if false, the V0Finder module is not executed

  • flip_recoTrack – if true, add the recoTracks flipping function in the postfilter (only if PXD is present)

  • skip_full_grid_cdc_eventt0_if_svd_time_present – if true, and if also append_full_grid_cdc_eventt0 is true, the FullGridChi2TrackTimeExtractor is only executed in the events where no SVD-based EventT0 is found. If false, but append_full_grid_cdc_eventt0 is true, FullGridChi2TrackTimeExtractor will be executed in each event regardless of SVD EventT0 being present. Has no effect if append_full_grid_cdc_eventt0 is false. Default: true

tracking.__init__.add_prefilter_tracking_reconstruction(path, components=None, skipGeometryAdding=False, mcTrackFinding=False, trackFitHypotheses=None, reco_tracks='RecoTracks', prune_temporary_tracks=True, fit_tracks=True, use_second_cdc_hits=False, skipHitPreparerAdding=False, svd_standalone_mode='VXDTF2', use_svd_to_cdc_ckf=True, use_ecl_to_cdc_ckf=False, add_cdcTrack_QI=True, add_vxdTrack_QI=False, add_recoTrack_QI=False, pxd_filtering_offline=False, create_intercepts_for_pxd_ckf=False, append_full_grid_cdc_eventt0=True, skip_full_grid_cdc_eventt0_if_svd_time_present=True)[source]#

This function adds the tracking reconstruction modules required to calculate HLT filter decision to a path.

Parameters:

  • path – The path to add the tracking reconstruction modules to

  • components – the list of geometry components in use or None for all components.

  • skipGeometryAdding – Advances flag: The tracking modules need the geometry module and will add it, if it is not already present in the path. In a setup with multiple (conditional) paths however, it can not determine, if the geometry is already loaded. This flag can be used o just turn off the geometry adding at all (but you will have to add it on your own then).

  • skipHitPreparerAdding – Advanced flag: do not add the hit preparation (esp. VXD cluster creation modules. This is useful if they have been added before already.

  • mcTrackFinding – Use the MC track finders instead of the realistic ones.

  • reco_tracks – Name of the StoreArray where the reco tracks should be stored

  • prune_temporary_tracks – If false, store all information of the single CDC and VXD tracks before merging. If true, prune them.

  • fit_tracks – If false, the final track find and the TrackCreator module will no be executed

  • use_second_cdc_hits – If true, the second hit information will be used in the CDC track finding.

  • trackFitHypotheses – Which pdg hypothesis to fit. Defaults to [211, 321, 2212].

  • svd_standalone_mode – Which SVD standalone tracking is used. Options are “VXDTF2”, “SVDHough”, “VXDTF2_and_SVDHough”, and “SVDHough_and_VXDTF2”. Defaults to “VXDTF2”

  • use_svd_to_cdc_ckf – if true, add SVD to CDC CKF module.

  • use_ecl_to_cdc_ckf – if true, add ECL to CDC CKF module.

  • add_cdcTrack_QI – If true, add the MVA track quality estimation to the path that sets the quality indicator property of the found CDC standalone tracks

  • add_vxdTrack_QI – If true, add the MVA track quality estimation to the path that sets the quality indicator property of the found VXDTF2 tracks (ATTENTION: Standard triplet QI of VXDTF2 is replaced in this case -> setting this option to ‘True’ will have some influence on the final track collection)

  • add_recoTrack_QI – If true, add the MVA track quality estimation to the path that sets the quality indicator property of all found reco tracks (Both other QIs needed as input.)

  • pxd_filtering_offline – If True, PXD data reduction (ROI filtering) is applied during the track reconstruction. The reconstructed SVD/CDC tracks are used to define the ROIs and reject all PXD clusters outside of these.

  • create_intercepts_for_pxd_ckf – If True, the PXDROIFinder is added to the path to create PXDIntercepts to be used for hit filtering when creating the CKF relations. This independent of the offline PXD digit filtering which is steered by ‘pxd_filtering_offline’. This can be applied for both data and MC.

  • append_full_grid_cdc_eventt0 – If True, the module FullGridChi2TrackTimeExtractor is added to the path and provides the CDC temporary EventT0.

  • skip_full_grid_cdc_eventt0_if_svd_time_present – if true, and if also append_full_grid_cdc_eventt0 is true, the FullGridChi2TrackTimeExtractor is only executed in the events where no SVD-based EventT0 is found. If false, but append_full_grid_cdc_eventt0 is true, FullGridChi2TrackTimeExtractor will be executed in each event regardless of SVD EventT0 being present. Has no effect if append_full_grid_cdc_eventt0 is false. Default: true

tracking.__init__.add_postfilter_tracking_reconstruction(path, components=None, pruneTracks=False, reco_tracks='RecoTracks', use_second_cdc_hits=False, prune_temporary_tracks=True, v0_finding=True, flip_recoTrack=True, mcTrackFinding=False, kink_finding=True)[source]#

This function adds the tracking reconstruction modules not required to calculate HLT filter decision to a path.

Parameters:

  • path – The path to add the tracking reconstruction modules to

  • components – the list of geometry components in use or None for all components.

  • pruneTracks – Delete all hits except the first and the last in the found tracks.

  • reco_tracks – Name of the StoreArray where the reco tracks should be stored

  • use_second_cdc_hits – If true, the second hit information will be used in the CDC track finding.

  • prune_temporary_tracks – If false, store all information of the single CDC and VXD tracks before merging. If true, prune them.

  • v0_finding – If false, the V0 module will not be executed

  • flip_recoTrack – if true, add the recoTracks flipping function in the postfilter (only if PXD is present)

  • mcTrackFinding – Use the MC track finders instead of the realistic ones.

Contents