NVIDIA-ISAAC-ROS / NVIDIA-ISAAC-ROS/ros2_benchmark

Does the project still runnable in enviorment with CPU only?

Open
#34 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
141
Forks
19
PR merge metrics
No merged PRs in 30d

Description

I try to follow with Quick Start, but found:

oot@26803bab5599:~/ros_ws/src/ros2_benchmark/assets/datasets/r2b_dataset/r2b_storage# cd $R2B_WS_HOME && \
  colcon build --packages-up-to ros2_benchmark apriltag_ros && \
  source install/setup.bash
Starting >>> cv_bridge
Starting >>> ros2_benchmark_interfaces
Finished <<< cv_bridge [0.76s]                                                                          
Starting >>> apriltag_ros
--- stderr: ros2_benchmark_interfaces                                                                 
CMake Error at /opt/ros/humble/share/ament_cmake_core/cmake/index/ament_index_get_resource.cmake:62 (message):
  ament_index_get_resource() called with not existing resource
  ('isaac_ros_common_cmake_path' 'isaac_ros_common')
Call Stack (most recent call first):
  CMakeLists.txt:72 (ament_index_get_resource)


---
Failed   <<< ros2_benchmark_interfaces [2.69s, exited with code 1]
Aborted  <<< apriltag_ros [2.58s]          

It seems isaac_ros_common must be installed? However, isaac ROS must be installed with CUDA?

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.

Research direction

Start with the Quick Start build command and CMakeLists.txt at line 72, then inspect how the isaac_ros_common resource is expected to be provided. Reproduce the colcon failure in a CPU-only environment and confirm whether the build works without CUDA; done should be a working setup or clear prerequisite documentation.

Written by the indexing model from the issue text.

Assessment

Domain
build-system, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.