-
Notifications
You must be signed in to change notification settings - Fork 17
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
rosbag example? #1
Comments
I have submitted a new launch file on the master branch to support the Ouster lidar. Also, you can use the repository at https://github.com/YWL0720/FAST_LIO. This repository has added interfaces for saving maps and pose files. It can save point clouds and poses in the map folder. Just copy the saved maps and poses to the working directory of fast_localization for use. Currently, the bag file I use for testing is quite large and uploading it is somewhat troublesome. I will update with a smaller bag file later for testing purposes. |
thanks for the quick reply. I have a question though, I have a map of an area that was generated by another method (we can assume it is GT), and a rosbag of my own ouster lidar scans going through that same area. Are you suggesting that when generating the map used in the localization process, we must first acquire a set of pose files for that map? If so, does that mean I cannot use this repo for localization on my GT map? |
In FAST-LOCALIZATION, the prior map is composed of a set of point cloud frames combined through their corresponding poses. When initializing and loading the map, ScanContext is used to compute the descriptors for each point cloud frame. During localization initialization, descriptors for the initial point cloud are also computed and matched with the global map to complete the initialization of global localization. If the prior map does not meet the aforementioned conditions, the automatic initialization function of FAST-LOCALIZATION will not work properly. |
Hey i use your version of fast_lio, i also set bool save to true but when i run fast_lio i have no pcd and pose.json files |
The pcd and pose.json files will be saved in YOUR_WORKSPACE/src/FAST_LIO/map/ |
That's my carelessness, you also need to add "save_pcd: true" in the yaml file which you use, just like https://github.com/YWL0720/FAST_LIO/blob/704b1d2305300189fe043081254a916cfa2bdd62/config/mid360.yaml#L25 |
terminate called after throwing an instance of 'pcl::IOException' |
Which type of Lidar are you using? |
I am using Ouster |
Try to add |
I have submitted the new code. |
Hey i just tried but still the error. |
Because I have been busy with other things in the past few days, I apologize for the late reply. Thank you for providing the dataset. I have submitted the latest code, and have successfully tested the map saving and relocalization functions on my local machine. However, given the unique nature of ScanContext, it is more suitable for use on mobile robots or devices where the LiDAR is mounted horizontally. I noticed that the LiDAR in your dataset is not placed horizontally, which may negatively affect the relocalization results. |
@YWL0720 |
The error ”pcl::IOException: [pcl::PCDWriter::writeASCII] Number of points different than width * height!“ arises because, during the conversion of the point cloud from ROS's sensor_msgs/PointCloud2 format to pcl format, the 'width' and 'height' attributes are not assigned. This prevents the use of pcl's point cloud saving interface. To resolve this, simply manually assign values to these two attributes based on the number of points in the point cloud before saving it. |
Hey can i load map of 1st bag then i play 2nd bag(both recorded in the same place) |
of course you can. |
I have 2 rosbags record the same place, but the odometry is parallel and the distance between 2 odometry is about 5 to 10m. |
Hi, many thanks for this awesome repo. I was wondering whether you can provide a rosbag for an example to run the repo? Additionally any plans for supporting ouster lidar, or what is needed to add ouster support?
The text was updated successfully, but these errors were encountered: