-
-
Notifications
You must be signed in to change notification settings - Fork 622
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
Crash loading bag with 2 topics of nav_msgs/Odometry #42
Comments
Thanks for reporting, I will take a look ASAP |
There is something very weird related to the message with prefix /ihmc Apparently the definition is incomplete. It looks like the message was created by hand and not from The other message instead is just fine. Which process is publishing the the valkyrie/output/robot_pose? |
To be more specific. This is the truncated definition of the ihmc message
Whilst this it the correct one from /floating_base_pose
|
It is published by the IHMC Valkyrie Controller we are using in the Space Robotics Challenge. Installation instructions are here: https://bitbucket.org/osrf/srcsim/wiki/system_setup |
As I said, the message seems to be corrupted and there is nothing I can do about it (a part from hard coding a solution for you). I have tried to use rqt_plot and it is not able to extract the fields either. |
My suggestion is to ask the people a IHMC if they know why that message definition was truncated. |
Yeah, certainly looks like that. Thanks for the help! |
For the records. There is a solution to solve this problem. I just tested it and it works; You can hard code the message definition inside the plugin doing this: #include <nav_msgs/Odometry.h>
DataLoadROS::DataLoadROS()
{
_extensions.push_back( "bag");
RosIntrospectionFactory::get().registerMessage(
ros::message_traits::DataType<nav_msgs::Odometry>::value(),
ros::message_traits::MD5Sum<nav_msgs::Odometry>::value(),
ros::message_traits::DataType<nav_msgs::Odometry>::value(),
ros::message_traits::Definition<nav_msgs::Odometry>::value() );
} |
Awesome, next time you come by PAL I'll invite you to a beer! |
YES, the standard committee believes this might be narrowing and clang 12 throws this error: > error: non-constant-expression cannot be narrowed from type 'uint8_t' (aka 'unsigned char') to 'double' in initializer list [-Wc++11-narrowing]
The short one (named Error_opening.bag) crashes after selecting both topics inside the rosbag with the error:
The same happened when I tried the ROS Topic Streamer on those two topics at the same time.
The other bag is fine.
bags.zip
The text was updated successfully, but these errors were encountered: