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

/visual_slam/status is incorrect ?

Open
#147 1 comment 2 reactions 1 assignee View on GitHub

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

Since Feb 21, 2024.

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

Description

Hello,

I am seeing this message on the launch console .
[component_container-1] [WARN] [1707351289.041480251] [visual_slam_node]: Visual tracking is lost
but the vo_state field in the status message remains 1.
Is there some parameter I should set to enable the status reporting ?
Parameters in the visual slam launch file are.

                'denoise_input_images': True,
                'rectified_images': True,
                'enable_debug_mode': False,
                'debug_dump_path': '/tmp/cuvslam',
                'enable_slam_visualization': True,
                'enable_landmarks_view': True,
                'enable_observations_view': True,
                'enable_localization_n_mapping':True,
                'publish_odom_to_base_tf' : True,
                'publish_map_to_odom_tf': True,
                'map_frame': 'map',
                'odom_frame': 'odom',
                'base_frame': 'base_link',
                'input_imu_frame': 'IMU_1',
                'input_base_frame': 'base_link',
                'image_qos': 'SERVICES_DEFAULT',
                'input_left_camera_frame': 'rs_top_infra1_frame',
                'input_right_camera_frame': 'rs_top_infra2_frame',
                'enable_imu_fusion': False,
                'gyro_noise_density': 8.6e-05  ,
                'gyro_random_walk':2.2e-06,
                'accel_noise_density': 1.4e-03,
                'accel_random_walk':8.0e-05,
                'calibration_frequency': 200.0,
                'img_jitter_threshold_ms': 100.00

Sandeep

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.