Skip to content
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

Confusion about Odom data #33

Open
FelicxFoster opened this issue Apr 11, 2021 · 5 comments
Open

Confusion about Odom data #33

FelicxFoster opened this issue Apr 11, 2021 · 5 comments

Comments

@FelicxFoster
Copy link

FelicxFoster commented Apr 11, 2021

Hi, @ZacharyTaylor. Thanks for your open source
I got a problem about the Odom message we need to load in the function loadTformFromROSBAG().
Does translation field in geometry_msgs/TransformStamped message in ROS mean the GPS position? like the following picture
odom数据
but in the example.bag you provided, the translation is too samll, such as
example_odom
I use my dataset to calibrate and I got the bad result, and different results on one dataset. Is there something wrong with my data?
Thanks.

@LarryDong
Copy link

Hi I think the TransformStamped should be in "meter", which is 0 at the beginning. Not GPS. You could minus the offset (at the beginning) from you GPS data.

@FelicxFoster
Copy link
Author

@LarryDong Thanks for your reply. I will try. Could you share your dataset? I want to compare the difference of my dataset, which has the bad result for calibration.

@LarryDong
Copy link

@FelicxFoster
Check the data from the author here. #5 (comment)

@FelicxFoster
Copy link
Author

@LarryDong yeah, I have tried the author's data. However, I don't think is a good example, like author said its just he holding the lidar and randomly waving it around. So I hope you could share your data if you have, thanks.

@LarryDong
Copy link

@FelicxFoster
Sorry that I do not have a record.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants