-
Notifications
You must be signed in to change notification settings - Fork 219
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
Pose with wrong direction #20
Comments
I am having the same issue. I simply added the negative sign in LaserOdometry2D::PoseUpdate(). |
Really helpful, thanks! |
Hi, I have the same problem, but when tried to make this solution, the problem got worse, now the odom is calculated in the reverse direction Can you please help me with this one. |
The above solution works but could the repository developers let us know if this a proper solution or is there something we should know about the way the algorithm expects the scan data to solve this problem. @JGMonroy @jgoppert @famoreno @mertsaadet |
I have a similar problem, but might be different. During initialization the
retrieved = false; is returned.
Maybe for some, ensuring we keep trying to get the TF, would solve the problem!? |
Hi there I'm using rf2o for the navigation stack. I rotated my lidar 90 degrees around z direction, and flipped upside down, and it scans only half range, from -180 to 0 degree.
There I got a problem: tf goes to mirrored direction( x axis)...i.e. when I move robot to right, the tf goes to left..
The tf setup seems to be correct because I run the same tf for hector slam to create a map, and no problem with the pose direction.
I'm new in ROS, could anyone advise how to solve it?
The text was updated successfully, but these errors were encountered: