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

I need help with adjusting yaml file parameters. #356

Open
lidarmansiwon opened this issue Sep 19, 2024 · 3 comments
Open

I need help with adjusting yaml file parameters. #356

lidarmansiwon opened this issue Sep 19, 2024 · 3 comments
Labels

Comments

@lidarmansiwon
Copy link

Hi, I am using fast_lio with ouster in humble. I am using ouster pointcloud and built-in imu, but it is showing poor mapping results. What exactly do these parameters mean, how to use them, and are there any recommended parameters for outdoor use? How should I adjust them?

/**:
ros__parameters:
feature_extract_enable: false
point_filter_num: 3
max_iteration: 3
filter_size_surf: 0.5
filter_size_map: 0.5
cube_side_length: 1000.0
runtime_pos_log_enable: false
map_file_path: "./test.pcd"

 And additionally, even if we use the internal imu of ouster, do we need to calibrate the two through an external algorithm?
 Please help me,,
Copy link

stale bot commented Oct 19, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Oct 19, 2024
@juliangaal
Copy link

you're performance issues are likely due to changes in the ouster ros2 tf tree. os_imu now points in the opposite direction of os_lidar, therefore, you need to update the IMU->Lidar transformation parameters according to the output of

ros2 run tf2_ros tf2_echo os_imu os_lidar

I already did exactly this, and more, in #365

@stale stale bot removed the stale label Oct 30, 2024
Copy link

stale bot commented Nov 27, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants