You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to Ouster's description from their official website (page 22 - 23) the points are with respect to a "LIDAR Coordinate Frame" {L}, where the positive x direction points from the center towards the socket, and z points upwards as below.
So if one uses the raw pointcloud data, I assume that the extrinsics should have been set as
@BritskNguyen
It occurs to me that the points in Gen1 and Gen2 lidar might be different. See my replay at #94.
After some troubleshooting I think this is indeed the explanation. To recap: gen1 ouster outputs pointcloud in the frame {L} in the figure above. So if we want to use LIO-SAM with gen1 ouster, we should invert the x and y coordinates of each point. It effectively converts the pointcloud to the {S} frame above, which coincides with gen2 ouster and Velodyne.
Dear Author,
According to Ouster's description from their official website (page 22 - 23) the points are with respect to a "LIDAR Coordinate Frame" {L}, where the positive x direction points from the center towards the socket, and z points upwards as below.
So if one uses the raw pointcloud data, I assume that the extrinsics should have been set as
However the extrinsic params you use seem to be with respect to the "Sensor Coordinate Frame" in the Figure above.
So my question is whether you have done the transform of the pointcloud from the "LIDAR Coordinate Frame" to "Sensor Coordinate Frame" already?
The text was updated successfully, but these errors were encountered: