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

/visual_slam/status is incorrect ? #147

Open
sandeepdutta opened this issue Feb 8, 2024 · 1 comment
Open

/visual_slam/status is incorrect ? #147

sandeepdutta opened this issue Feb 8, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@sandeepdutta
Copy link

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

@dakejahl
Copy link

dakejahl commented Feb 9, 2024

+1 for this. I also would expect the vo_state to report when the IMU is being fused or not. I need to be able to differentiate between a VIO and VO solution.

@swapnesh-wani-nvidia swapnesh-wani-nvidia self-assigned this Feb 21, 2024
@swapnesh-wani-nvidia swapnesh-wani-nvidia added the enhancement New feature or request label Feb 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants