Skip to content
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

Use driver nodelet in the rtabmap_slam launch file #10

Closed
skalldri opened this issue Jun 21, 2019 · 0 comments · Fixed by #11
Closed

Use driver nodelet in the rtabmap_slam launch file #10

skalldri opened this issue Jun 21, 2019 · 0 comments · Fixed by #11
Assignees
Labels
enhancement New feature or request triage approved The Issue has been reviewed and approved for development by the Azure Kinect ROS Driver Team

Comments

@skalldri
Copy link
Contributor

Is your feature request related to a problem? Please describe.
The rtabmap_slam launch file starts a new node of the Azure Kinect ROS Driver, but uses nodelets for the image_proc post-processing steps. It would be significantly more memory efficient to use the pointer-passing mechanics enabled through nodelets.

Describe the solution you'd like
Use the nodelet version of the ROS driver in the rtabmap_slam launch file.

Describe alternatives you've considered
None.

Additional context
None.

@skalldri skalldri added enhancement New feature or request triage needed The Issue still needs to be reviewed by the Azure Kinect ROS Driver Team labels Jun 21, 2019
@skalldri skalldri self-assigned this Jun 21, 2019
@skalldri skalldri added triage approved The Issue has been reviewed and approved for development by the Azure Kinect ROS Driver Team and removed triage needed The Issue still needs to be reviewed by the Azure Kinect ROS Driver Team labels Jun 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request triage approved The Issue has been reviewed and approved for development by the Azure Kinect ROS Driver Team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant