Closed sumedhreddy90 closed 8 months ago
Did you happen to refresh your Isaac ROS Dev container (git pull on isaac_ros_common and run run_dev.sh again)? The error looks like stale VPI which did not have the new threshold parameter for SGM.
admin@jon-jp511-isaac-ros:/workspaces/isaac_ros-dev/src$ cd isaac_ros_common/
admin@jon-jp511-isaac-ros:/workspaces/isaac_ros-dev/src/isaac_ros_common$ ls
docker isaac_ros_bi3d_interfaces isaac_ros_nitros_bridge_interfaces isaac_ros_pointcloud_interfaces isaac_ros_test README.md
isaac_ros_apriltag_interfaces isaac_ros_common isaac_ros_nova_interfaces isaac_ros_tensor_list_interfaces LICENSE scripts
admin@jon-jp511-isaac-ros:/workspaces/isaac_ros-dev/src/isaac_ros_common$ git status
On branch main
Your branch is up to date with 'origin/main'.
nothing to commit, working tree clean
admin@jon-jp511-isaac-ros:/workspaces/isaac_ros-dev/src/isaac_ros_common$ git log
commit 6d3c5c00e0e2b3fc1d75eb4286848d23b05d6dca (HEAD -> main, tag: v2.0.0, origin/main, origin/HEAD)
Merge: 94dfe8d 307f7e5
Author: Jaiveer Singh <[84546269+jaiveersinghNV@users.noreply.github.com](mailto:84546269+jaiveersinghNV@users.noreply.github.com)>
Date: Wed Oct 18 20:00:13 2023 -0700
Merge pull request #97 from NVIDIA-ISAAC-ROS/release-2.0.0
Isaac ROS 2.0.0
commit 307f7e55aac273dd5df281202622e7d8df125e48
Author: Hemal Shah <[hemals@nvidia.com](mailto:hemals@nvidia.com)>
Date: Thu Oct 19 02:19:07 2023 +0000
Isaac ROS 2.0.0
@hemalshahNV yes! isaac_ros_common is on latest pull and container is built with latest isaac_ros_common
I have the same compilation issue after upgrading to IsaacROS 2.0. Did you find any solution to fix it?
Maybe it's worth to mention that I am building the docker image from scratch through run_dev.sh using the latest version of isaac_ros_common, instead of using the Dockerfile.aarch64.ros2_humble precompiled image. Also, I am using Jetpack 5.1.1
@vladmosoiu98 , the Isaac ROS 2.0 release requires VPI 2.3, which was only made available in JetPack 5.1.2. Could you please upgrade JetPack to the latest version and try again?
@sumedhreddy90 , based on the hostname of your device, it looks like your Jetson might also be running on JetPack 5.1.1. If that's an accurate assessment, then upgrading to the latest version of JetPack may fix your issue as well.
@jaiveersinghNV Yes! updating JetPack to 5.1.2 worked.