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

VTR3 Extractor Comparison #229

Merged
merged 12 commits into from
Jan 18, 2025
Merged

VTR3 Extractor Comparison #229

merged 12 commits into from
Jan 18, 2025

Conversation

ElliotP-K
Copy link

@ElliotP-K ElliotP-K commented Dec 17, 2024

  • Added all extractors corresponding to the extractor comparison paper
  • Added ICP failure/skip frame conditions:
    • STEAM solver fails unexpectedly
    • Difference in estimated velocity between frames is not reasonable (translational, rotational, combined)
    • Comment if I should add this code to the odometry_icp_module under the vtr_radar_lidar directory as well
  • Added point-cloud visualization utility for extractors. Merging this code with the new gyro update, I see there are also flags for "save_raw_point_cloud" and "save_radar_images". My addition specifically outputs the point cloud overlaid onto the current radar scan in cartesian form. LMK if this feature should be removed because of redundancy.
  • See radar_topometric_localization PR for testing details

Copy link
Contributor

@a-krawciw a-krawciw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The PR overall looks good.

I think that the sanity checks on velocity before accepting a new frame can be added to lidar as well, however, I haven't actually encountered a scenario when they would be activated.

The existing image saving features apply only to each vertex not every frame. Additionally, we are already including support for online and offline modes already. I think you should leave it as is and include both.

@lisusdaniil lisusdaniil merged commit ad26d33 into main Jan 18, 2025
1 check passed
@lisusdaniil lisusdaniil deleted the vtr3_extractor_comp branch January 18, 2025 17:30
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

Successfully merging this pull request may close these issues.

3 participants