-
Notifications
You must be signed in to change notification settings - Fork 5
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
Refactored rviz launch file #28
base: rolling
Are you sure you want to change the base?
Conversation
AdarshKaran
commented
Feb 27, 2025
- Refactored the rviz_launch file to use opaque function
- Added additional launch argument to change the output type (screen, log) of RViz node
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.
LGTM! I see your idea of making it generic for all the robots. This means that we also have to add the rviz_launch.py to the navigation_neo.launch.py. By that way, we just have to add a single argument to our navigation.launch.py across the robots.
By default, use_rviz should be set to true on the navigation launch.
Did you have something else in mind?
README.md
Outdated
### **[Date: 2025-02-27]** | ||
|
||
- Refactored the rviz_launch file to use opaque function | ||
- Added additional launch argument to change the output type (screen, log) of RViz node |
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.
changelog will be generated by the bloom. Just make sure, your commits are descriptive.
|
…e necessary launch argument, removed changelog