Repository navigation
Add Risk-aware Planner community plugin (v0.1.0) - #6
Merged
Merged
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.
Summary
Register
p20_risk_aware_planneras aLocalPlanningStrategy, pinned to v0.1.0. This changes only plugins.yaml.The plugin builds a fixed source-to-goal state lattice, performs rolling risk-constrained shortest-path search while preserving the committed edge remainder, and optionally smooths the new suffix with OSQP. Existing controllers and world bridges are unchanged. Enhanced visualization and demo launchers are separate companions. Motion and smoothing default to disabled.
Verification and compatibility
_perception_step(sensors)interface). No planner-only test failed. Full companion-demo support is claimed only for 0.5.3; limitations are documented in the release and dependency notes.Research/demo risk scores are not calibrated probabilities; physical vehicle motion is not validated. Please review the listing and compatibility scope. No AVLite-core changes are requested.