Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • Corryvreckan Corryvreckan
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 37
    • Issues 37
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 19
    • Merge requests 19
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Corryvreckan
  • CorryvreckanCorryvreckan
  • Merge requests
  • !523

Tracking4D: Use local coordinates for cluster association

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged David Bacher requested to merge cms-it-tb/corryvreckan:fixTracking4D into master May 25, 2022
  • Overview 5
  • Commits 4
  • Changes 8

Tracking4D currently uses global coordinates to calculate the distance between cluster and track but the spatial cuts are assumed in local coordinates (spatial_cut_rel reuses the detector resolution which is local). This leads to wrong cuts if one of the telescope planes is rotated around the z-axis. The association should be done in local coordinates only, which is also how it is done in the DUTAssociation module.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: fixTracking4D