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

iVox parameters hardcoded? #134

Open
themightyoarfish opened this issue Dec 5, 2024 · 2 comments
Open

iVox parameters hardcoded? #134

themightyoarfish opened this issue Dec 5, 2024 · 2 comments

Comments

@themightyoarfish
Copy link

Should this line not use the params passed to the constructor? If yes, they also look to be in the wrong order according to the parameter names in the iVox constructor.

@themightyoarfish
Copy link
Author

I had applied this diff here, but this completely breaks the fusion of the ouster sample data

diff --git a/src/vlcal/preprocess/dynamic_point_cloud_integrator.cpp b/src/vlcal/preprocess/dynamic_point_cloud_integrator.cpp
index 1e4f32e..b7d3763 100644
--- a/src/vlcal/preprocess/dynamic_point_cloud_integrator.cpp
+++ b/src/vlcal/preprocess/dynamic_point_cloud_integrator.cpp
@@ -35,7 +35,7 @@ DynamicPointCloudIntegrator::DynamicPointCloudIntegrator(const DynamicPointCloud
   last_T_odom_lidar_begin = gtsam::Pose3();
   last_T_odom_lidar_end = gtsam::Pose3();

-  target_ivox.reset(new iVox(1.0, 0.05, 100));
+  target_ivox.reset(new iVox(params.voxel_resolution, params.min_distance, 100));

What am I missing here?

@koide3
Copy link
Owner

koide3 commented Dec 29, 2024

It's my bad. Here params.voxel_resolution is the voxel resolution for final downsampling (e.g., 0.05) while the first argument for iVox is the voxel resolution for data association (e.g., 1.0).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants