ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
I don't know if I can answer your specific question, but this is a good source for learning about how to calculate the odometry:
http://rossum.sourceforge.net/papers/DiffSteer/
-Jon
2 | No.2 Revision |
I don't know if I can answer your specific question, but this is a good source for learning about how to calculate the odometry:
http://rossum.sourceforge.net/papers/DiffSteer/
-Jon
It seems unlikely to me that that is what the original author intended. It's probably either a bug that doesn't matter in the end, or maybe an artifact of the odometry that supplies data to driver.py.
3 | No.3 Revision |
I don't know if I can answer your specific question, but this is a good source for learning about how to calculate the odometry:
http://rossum.sourceforge.net/papers/DiffSteer/
-Jon
It appears that the global coordinate frame (self.x, self.y and self.th in driver.py) has +y to the left. But the coordinate frame for the change in position (x,y, and th in driver.py) has +y to the right.
It seems unlikely to me that that is what the original author intended. It's probably either a bug that doesn't matter in the end, or maybe an artifact of the odometry that supplies data to driver.py.
4 | No.4 Revision |
I don't know if I can answer your specific question, but this is a good source for learning about how to calculate the odometry:
http://rossum.sourceforge.net/papers/DiffSteer/
-Jon
(EDIT): It appears that the global coordinate frame (self.x, self.y and self.th in driver.py) has +y to the left. But the coordinate frame for the change in position (x,y, and th in driver.py) has +y to the right.
It seems unlikely to me that that is what the original author intended. It's probably either a bug that doesn't matter in the end, or maybe an artifact of the odometry that supplies data to driver.py.