-
Notifications
You must be signed in to change notification settings - Fork 204
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
Migrate to Noetic and Gazebo11 #247
Conversation
…nd removed tf_prefix
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.
It looks good so far! Could you also update the Never mind, this seems to be ready already.docker/Dockerfile
to use Ubuntu 20.04, Gazebo 11 and ROS Noetic?
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.
I confirm that it worked for me in Noetic inside Docker!
PR to update VRX to Noetic/Gazebo11 with Melodic/Gazebo9 compatibility
Mesh Updates
Empty fields in
*.dae
have been pruned. In Gazebo11, signifying an empty field in a following forward slash format, ie.<librarynotes/>
, would result in an error with RViz.tf_prefix
The global
namespace
variable is used in favor of the deprecatedtf_prefix
, apart from usage as a parameter in therobot_localization
node.RViz Examples
RViz examples are now confirmed to work with new config files in both Gazebo9 and 11
To Test
Run
roslaunch vrx_gazebo vrx.launch
, in another terminal tabroslaunch wamv_gazebo localization_example.launch
, and finallyroslaunch wamv_gazebo rviz_vrx.launch
in another tab.The resulting RViz window should look like the following: