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

Providede additional raw sweeplidar and is not a rigid transformation with existing sweeplidar 3D points #84

Open
TWJianNuo opened this issue Nov 20, 2020 · 4 comments

Comments

@TWJianNuo
Copy link

Hi! I wish to compute a rigid affine transformation between additional provided raw sweeplidar and existing sweeplidar. However, not matter I use moorse-puesodo inverse to compute or use ICP algorithmn to compute, I can not acqurie a feasible affine transformation between the two.

In visualization, I find they are in correspondence but exists distorion in existing sweeplidar. May I know what additional operation you apply to transfer the raw sweeplidar to current sweeplidar points?

@dkoguciuk
Copy link

I was just going to describe the exact same problem.

I've downloaded raw data given the link here: #67
I've read the raw point cloud in lidar coordinate frame like shown here: #77

Then, I've tried to estimate rigid transformation from the world/ego frame to raw lidar frame, and this is the result:

Screenshot from 2020-11-25 16-50-23

@nisseknudsen , you know anything about it? Or maybe you could provide the transformation from ego frame to lidar frame, so we won't have to reverse engineer it?

@xpchuan-95
Copy link
Contributor

I was just going to describe the exact same problem.

I've downloaded raw data given the link here: #67
I've read the raw point cloud in lidar coordinate frame like shown here: #77

Then, I've tried to estimate rigid transformation from the world/ego frame to raw lidar frame, and this is the result:

Screenshot from 2020-11-25 16-50-23

@nisseknudsen , you know anything about it? Or maybe you could provide the transformation from ego frame to lidar frame, so we won't have to reverse engineer it?

I think transform between raw pointcloud and pandaset-pointcloud is not a rigid transformation because of motion compensation used.

@dkoguciuk
Copy link

@xpchuan-95 , sure, I am ok with motion compensation :) I would be even more ok if the rigid transformation from ego frame to lidar frame would be provided by PandaSet authors :)

@jlbslbs
Copy link

jlbslbs commented Feb 24, 2021

I would like to have the transformation from ego frame to the sensor frames as well! @xpchuan-95

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

4 participants