Ashwin Varghese Kuruttukulam

Yes there is params to enabling clearing the map, except a sphere in the nvblox map about a frame using the parameters: `map_clearing_radius_m` `map_clearing_frame_id` `clear_outside_radius_rate_hz` Details are here: https://nvidia-isaac-ros.github.io/repositories_and_packages/isaac_ros_nvblox/isaac_ros_nvblox/api/parameters.html Code...

We cannot directly cap the memory usage by number of bytes. But @alexmillane or @remostei can elaborate on how to estimate the memory usage based on the nvblox configuration.

The current version of the library does **not** provide a covariance estimate as an output.@jaiveersinghNV can you mark this as a feature request?

Can you please post a short rosbag and launch file that can be used to reproduce this issue?

It looks like the FOV is computed to be 106 from the FlatScan msg. Can you please post the FlatScan msg for this error comes up? Note: `min_scan_fov_degrees` parameter here:...

If you can provide a small rosbag + map(.png+.yaml) and launch file, I can try to reproduce this on my end. Then I look into it this issue further.

Once the isaac_ros_occupancy_grid_localizer node has been launched, we do not have a feature to change the map it uses to localize against. But one solution for your use case would...

For some reason your xml launch file doesn't seem to load the map image from the path in the map_yaml file. ``` [component_container_mt-1] 2024-07-13 12:42:15.505 ERROR gems/image/io.cpp@480: Unrecognized image file...

Has this been implemented or is there any work in progress?

Hi, Thanks for your `ros2_tracing` contributions and your efforts to help integrate the live tracing feature. I’m exploring the use of this tool as part of a live monitoring system...