-
Notifications
You must be signed in to change notification settings - Fork 262
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
About the Imu data #48
Comments
In the KITTI paper:
|
This is fine. It is the correct coordinate system to export. Your second comment refers to gps vs rest. |
@geoeo sorry, do you mean the original assignment is right? how to explain my fist comment? |
I see your point. I think it should be x,y,z as well. Practically however, I tried a motion integration with both and it didnt make any difference. But for completeness it should be x,y,z |
@geoeo and for my second comment, in the paper it refers both gps and IMU:
|
Hi, can I ask you how you got the same trajectory with motion integration using both xyz and flu? |
Hi, I pay attention to that in kitti2bag.py, imu message is assigned as
But in the definition of kitti raw_data:
That is the absolute values, but IMU measures the relative acceleration and angular rate in its coordinate. Why doesn't use the following values?
The text was updated successfully, but these errors were encountered: