Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • VTK VTK
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 740
    • Issues 740
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 197
    • Merge requests 197
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • VTK
  • VTKVTK
  • Issues
  • #8983
Closed
Open
Created May 06, 2009 by Kitware Robot@kwrobotOwner

ICP should have a "too far way" threshold

This issue was created automatically from an original Mantis Issue. Further discussion may take place here.


The current implementation of ICP requires ALL of the source points to match to the target. This is ok if one set is a strict subset of the other, because you can simply match the subset to the entire set. However, if the polydata which contains the subset also has many other points, the transform gets pulled to the center of the entire dataset rather than staying near the original location. The idea is that some points are "too far" to be considered in the transform at all, so they do not affect the cost function. This is always a problem when matching a model to a LIDAR scan.

Assignee
Assign to
Time tracking