Behavior tree node for extracting pose from path - Githubissues

ros-navigation / navigation2

ROS 2 Navigation Framework and System

https://nav2.org/

Other

2.31k stars 1.2k forks source link

Behavior tree node for extracting pose from path #4516

Closed MarcM0 closed 3 days ago

MarcM0 commented 4 days ago

Basic Info

Info	Please fill out this column
Ticket(s) this addresses	https://github.com/open-navigation/opennav_coverage/issues/64
Primary OS tested on	(Ubuntu)
Robotic platform tested on	(gazebo simulation of turtlebot)
Does this PR contain AI generated software?	(No)

Description of contribution in a few bullet points

Description of documentation updates required from your changes

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

mergify[bot] commented 4 days ago

This pull request is in conflict. Could you fix it @MarcM0?

mergify[bot] commented 4 days ago

@MarcM0, your PR has failed to build. Please check CI outputs and resolve issues. You may need to rebase or pull in main due to API changes (or your contribution genuinely fails).

mergify[bot] commented 4 days ago

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

mergify[bot] commented 4 days ago

This pull request is in conflict. Could you fix it @MarcM0?

mergify[bot] commented 4 days ago

@MarcM0, your PR has failed to build. Please check CI outputs and resolve issues. You may need to rebase or pull in main due to API changes (or your contribution genuinely fails).

mergify[bot] commented 4 days ago

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

mergify[bot] commented 3 days ago

This pull request is in conflict. Could you fix it @MarcM0?

mergify[bot] commented 3 days ago

@MarcM0, your PR has failed to build. Please check CI outputs and resolve issues. You may need to rebase or pull in main due to API changes (or your contribution genuinely fails).

SteveMacenski commented 3 days ago

@MarcM0 you will need to fix the PR, it now touches 10k+ lines

mergify[bot] commented 3 days ago

@MarcM0, your PR has failed to build. Please check CI outputs and resolve issues. You may need to rebase or pull in main due to API changes (or your contribution genuinely fails).

MarcM0 commented 3 days ago

moving to pull request based off of main branch