Repository navigation
Conversation
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.
Safe-goal searches, path lookahead/distance and obstacle-ahead checks accept generated occupancy/path values. Generated safe goals are the canonical geometry_msgs Point; legacy grid callers retain Vector3 output. Existing BFS/contiguous traversal, clearance thresholds, cached path mask behavior and distance math remain shared.
Parent: #4676. Project: https://linear.app/dimensional/project/message-encoding-refactor-05a3ddb4af3e/overview
After installing this commit, run this offline example:
Validation: 51 source and 51 installed-wheel checks (17 safety/distance and 34 rendering/mask), three unchanged project-fixture safe-goal regressions, strict typing of four production files, applicable hooks, normal main wheel build, full runtime pip check (198 packages). Existing project LFS fixture was SHA256/size verified and safely extracted from cache. The exact snippet above passes against the installed main wheel. No hardware, performance or GitHub CI result is claimed. Global/local planner and controller message ports remain the next consumer layer.