Skip to content

add route planning BT nodes to nav2_tree_nodes.xml (backport #5534)#5820

Merged
SteveMacenski merged 1 commit intokiltedfrom
mergify/bp/kilted/pr-5534
Dec 29, 2025
Merged

add route planning BT nodes to nav2_tree_nodes.xml (backport #5534)#5820
SteveMacenski merged 1 commit intokiltedfrom
mergify/bp/kilted/pr-5534

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify bot commented Dec 26, 2025

Basic Info

Info Please fill out this column
Ticket(s) this addresses
Primary OS tested on Ubuntu
Robotic platform tested on not applicable, groot2 1.6.1
Does this PR contain AI generated software? No
Was this PR description generated by AI software? No

Description of contribution in a few bullet points

  • add bt nodes GetCurrentPose, ConcatenatePaths, WouldARouteRecoveryHelp, ArePosesNear to nav2_tree_nodes.xml, descriptions taken from corresponding C++ classes

Description of documentation updates required from your changes

none

Description of how this change was tested

opened navigate_on_route_graph_w_recovery.xml in groot2, no warnings of undefined BT nodes are observed anymore


Future work that may be required in bullet points

  • Some autogeneration of this description from the C++ classes would be nice, i guess

For Maintainers:

  • Check that any new parameters added are updated in docs.nav2.org
  • Check that any significant change is added to the migration guide
  • Check that any new features OR changes to existing behaviors are reflected in the tuning guide
  • Check that any new functions have Doxygen added
  • Check that any new features have test coverage
  • Check that any new plugins is added to the plugins page
  • If BT Node, Additionally: add to BT's XML index of nodes for groot, BT package's readme table, and BT library lists
  • Should this be backported to current distributions? If so, tag with backport-*.

This is an automatic backport of pull request #5534 done by [Mergify](https://mergify.com).

…p, ArePosesNear to nav2_tree_nodes.xml (#5534)

Signed-off-by: Jonas Otto <jonas.otto@ipa.fraunhofer.de>
(cherry picked from commit 547820f)
@mergify
Copy link
Copy Markdown
Contributor Author

mergify bot commented Dec 26, 2025

@mergify[bot], all pull requests must be targeted towards the main development branch.
Once merged into main, it is possible to backport to @kilted, but it must be in main
to have these changes reflected into new distributions.

@mini-1235
Copy link
Copy Markdown
Collaborator

Some of these nodes are not backported to Jazzy yet, so I didn't add the backport-jazzy label

@SteveMacenski SteveMacenski merged commit 791d07e into kilted Dec 29, 2025
7 of 10 checks passed
@mergify mergify bot deleted the mergify/bp/kilted/pr-5534 branch December 29, 2025 02:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants