-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AMRNAV-4736 support launching as composable node #4
Conversation
RCLCPP_ERROR_STREAM(this->get_logger(),"Failed to start IMU"); | ||
} | ||
|
||
RCLCPP_INFO(this->get_logger(),"K4A Started"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this logic was in the k4a_ros_bridge_node
, which manually created the executor in some main function. This is not supported in composable nodes. So I moved everything here and stopped building that node. In general, the new way should be fine also for launching in non-composable way.
@@ -40,13 +41,10 @@ find_package(diagnostic_msgs REQUIRED) | |||
########### | |||
|
|||
|
|||
## Declare a C++ executable | |||
add_executable(${PROJECT_NAME}_node | |||
src/k4a_ros_bridge_node.cpp |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see comment below for reason to remove this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you create a ticket to upstream this? Probably will need some changes to upstream
good point, here it is https://lvserv01.logivations.com/browse/AMRNAV-4745 |
Support launching as ComposableNode for IPC, and also zero-copy for the pointclouds.
Did not test whether this breaks normal launching, that should still be done before upstreaming
Inspired from realsense repo: