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
I'm using floam with a simulation point cloud sensor which I've recorded in a rosbag.
there seems to be a limitation in the scanned area that is preventing the the map from completing.
I'm not sure what the max_dis parameter in the launch file represents , but I've tried increasing it so that maybe it gives me more space but anything above 110 causes odometry to drift in weird ways.
I'm using floam with a simulation point cloud sensor which I've recorded in a rosbag.
there seems to be a limitation in the scanned area that is preventing the the map from completing.
I'm not sure what the max_dis parameter in the launch file represents , but I've tried increasing it so that maybe it gives me more space but anything above 110 causes odometry to drift in weird ways.
I've attached a video visualising my problem. point cloud data from rosbag is on the left , floam map is on the right
https://user-images.githubusercontent.com/85008571/234699612-91cfc016-39f3-4193-b7da-025b71458b8f.mp4
Terminal also contains the following messages:
[ INFO] [1682541798.383235440, 1681512504.042436629]: time stamp unaligned with path final, pls check your data --> laser mapping node
not enough correct pointsnot enough correct pointsnot enough correct pointsnot enough correct points
The text was updated successfully, but these errors were encountered: