Repository navigation
navmap_core: simplify() with a bound that changes from place to place - #46
Open
jmguerreroh wants to merge 1 commit into
Open
jmguerreroh wants to merge 1 commit into
jmguerreroh wants to merge 1 commit into
Conversation
SimplifyParams::max_error_at and max_edge_length_at (optional): the bound at each point, e.g. growing with the distance to a robot, so a map is exact near it and coarse far away. A collapse uses the smaller of the values at its two vertices; a value that is not finite or is negative stands for max_error / max_edge_length.
jmguerreroh
force-pushed
the
navmap-core-simplify-bounds
branch
from
November 17, 2026 14:16
8e91754 to
877935f
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
navmap_core: simplify() with a bound that changes from place to place
Branch base:
rolling. Files:navmap_core(Simplify.hpp/.cppand its tests). Independent ofthe
navmap_toolsbuildings PR; neither needs the other.What
Two optional fields of
SimplifyParams:When set, a collapse is bounded by the smaller of the values at the two vertices of its edge,
instead of
max_error/max_edge_lengtheverywhere. That bound is used wherever the fixed onewas: the deviation of the open edges, the deviation of the surface, the quadric cost and the edge
length. A value that is not finite or is negative stands for the fixed one. Unset, nothing changes.
The use: a map exact near a robot and coarse far from it, e.g. an error that grows with the
distance to the robot.
Why
Planning on such a map against fixed grids, on 2 x 2 km around the Puerta del Sol (Madrid; ground
from the IGN, buildings from the Catastro), 30 routes of 200 to 1500 m, easynav_navmap_planner's
A*, a robot of radius 0.5 m replanning every 30 m on a map rebuilt around it:
The holes (buildings) and the open edges are kept by
simplify()as before, so a coarse far zonekeeps its streets.
Tests
TheErrorCanChangeFromPlaceToPlace: a bumpy terrain with an error of 0 on one half keeps everyvertex of that half and is simplified on the other; a negative value gives the same map as no
max_error_at.TheEdgeLengthCanChangeFromPlaceToPlace: a plane with a short edge length on one half and noneon the other keeps its NavCels small only on the first half.
colcon test --packages-select navmap_coreon this branch: 328 tests (with the linters), nofailures.