NVIDIA-ISAAC-ROS / NVIDIA-ISAAC-ROS/isaac_ros_visual_slam

RVIZ VIO and SLAM paths seperate

Open
#142 3 comments 0 reactions 1 assignee View on GitHub

@swapnesh-wani-nvidia is already working on this.

Since Jan 29, 2024.

verify to close
Dominant language
C++
Stars
1.5k
Forks
206
PR merge metrics
No merged PRs in 30d

Description

Hi,

I have been using your SLAM software and I have been having some issues. First the VIO and SLAM paths in RVIZ seperate and get extremely far apart. Is this normal?

Secondly it's not at all clear what features being track actually means, is there is a way to display the features detected ontop of the image pairs so we can diagnose potential problems with tracking and see where tracking fails?

Third the information on frames is pretty confusing, to clarify what is the difference between base_frame and input_base_frame and base_link? My assumption was input_base_frame transforms the base_link to the left_camera_frame but the wording is very confusing.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.