-
Notifications
You must be signed in to change notification settings - Fork 103
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
Axis definitions #9
Comments
For anyone who's interested in transformation, can update the line as below if wanna convert KITTI format. |
Thank you so much for pointing this out. I am also doing the kitti format conversion. Is there anything else I should pay attention to? Edit: I found that the center provided by get-box in the two SDK is different, so I replaced it. |
So do your experiments show that the LiDAR axis definition in lyft data is "x-back, y-right, z-up"? @bmankirLinker |
That transformation definition makes the https://github.com/nutonomy/nuscenes-devkit/blob/master/python-sdk/nuscenes/scripts/export_kitti.py#L153 assertion pass. However after converting the PCD and GTs accordingly, GT and the image don't match. And also training with |
Oh, I can comment an assertion without modifying the axis definition, which seems to get the correct visualization, use the render module in the script. @bmankirLinker |
Maybe some functions are not affected by its axis definition, but we are indeed encountered bugs when inferencing orientations of objects by using some models adapted from NuScenes/KITTI. BTW, @joinssmith do you know the clear definition of LiDAR in Lyft dataset? |
@Tai-Wang Sorry, I don't know. |
@joinssmith so you've used the same transformation as in NuScenes, but also updated z of cuboid GT based on definition? |
All right, hope an update...Thanks all the same~ |
Just found out:
here |
I can confirm two things:
|
@joinssmith
Could you please tell me what exactly is different in them? |
@pyaf Sorry for my belated clarification. I ignored the transformation of the coordinate system at that time, and in fact the BOX given is the same. I'm sorry very much. |
@joinssmith there's nothing to be sorry about :) The thing is if we could swap x and y axes, we'd be able to fix this issue. |
I'm trying to transform the dataset to KITTI format, but I think the
export_to_KITTI
file is not updated so I've made some modifications but the axis transformation part is more complicated.Are the axis definition is the same as in NuScenes, such that for KITTI transformation we can apply
kitti_to_nu_lidar = Quaternion(axis=(0, 0, 1), angle=np.pi / 2)
?The text was updated successfully, but these errors were encountered: