Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
G GeoTrees
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 4
    • Issues 4
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • NOCSurfaceProcesses
  • GeoTrees
  • Issues
  • #3

Closed
Open
Created Oct 04, 2024 by Joseph Siddons@josiddOwner

Potential Infinite Loop in KDTree

If max_depth is set to inf, and two (or more) Records have the same lon and lat, they cannot be split and will infinitely be assigned to the child_left node. max_depth = inf is the standard form for a KDTree as each leaf should have only a single Record.

The previous approach of splitting the array in the middle would not lead to an infinite loop, however it this means that the child_left and child_right nodes can have Records with the same variable value. This could impact performance when querying, and make it more difficult to delete Records from the Tree.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking