-
Notifications
You must be signed in to change notification settings - Fork 765
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
Gazebo plugin for logging #23
Conversation
At this stage it only supports logging of the ground truth
pose_msg_.pose.orientation.y = pose_.rot.y; | ||
pose_msg_.pose.orientation.z = pose_.rot.z; | ||
|
||
bag_.write("ground_truth_pose", ros::Time::now(), pose_msg_); |
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'd say we should use gazebo time (simulation time)?
All the logging as mentioned in issue #20 is supported apart from in_collision, the generic_pose_sensor, services and parameters. I guess we can add those once we have them. |
namespace_ = _sdf->GetElement("robotNamespace")->Get<std::string>(); | ||
else | ||
gzerr << "[gazebo_bag_plugin] Please specify a robotNamespace.\n"; | ||
node_handle_ = new ros::NodeHandle(namespace_); |
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 don't know about gazebo namespaces, but are they always the same as the ros namespaces? shouldn't we take the ros namespaces here?
some comments otherwise this lgtm. |
Resolved Conflicts: mav_description/urdf/multirotor_base.urdf.xacro mav_gazebo_plugins/CMakeLists.txt
Depend on cv_bridge instead of opencv
At this stage it only supports logging of the ground truth pose, but it can be tested :)