Repository navigation
Conversation
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.
Reference issue
No matching issue or PR found in searches for arm goal costs and
safe_goal_costs.What does this implement/fix?
Arm RRT* goal selection minimizes only the stored cost of each nearby vertex, omitting the final connection to the goal. A cheaper partial path can therefore produce a more expensive complete path than another collision-free candidate.
Rank safe candidates by
calc_new_cost(vertex, goal_node), which adds the Euclidean joint-space length of the final edge. This matches the complete-path objective already used by the two-dimensional RRT* implementation. Retain collision checks, connection-radius filtering and first-candidate handling for equal total costs.Additional information
Python 3.13.15 with project-pinned dependencies: 7 tests pass, including the existing seven-joint arm planning test. Six new cases build actual parent branches with costs calculated from their edges, compare complete costs with the extracted course length, and cover native-DH collision filtering, no safe candidate, out-of-radius vertices and equal complete costs. Two competing-branch regressions fail on upstream. An independent reviewer reran all seven tests successfully. Repository Ruff and patch whitespace checks pass; the complete project suite was not run.
CheckList