cuRobo feature mapping + nvblox roadmap — is nvblox being phased out for 3D reconstruction?

Robotics & Edge Computing Robotics - Isaac Isaac ROS
1

Hello community,

I have been extending nvblox with deep feature mapping using NVIDIA RADIO (C-RADIO v3-B) and SigLIP-aligned text queries, building on top of isaac_ros_nvblox. I recently got to a point where I have usable results with a wrist-mounted RealSense mapping a robot workspace and answering open-vocabulary object queries. My goal is to integrate this into the Isaac ROS manipulation reference workflow.

Now that cuRoboV2 was released last week, which already includes native TSDF featurehannel integration with RADIO and text query support, along with direct performance comparisons to nvblox in the release notes. I am trying to decide how to proceed.

My questions:

  1. Is there a planned Isaac ROS wrapper for cuRobo’s reconstruction / feature mapping module, analogous to isaac_ros_cumotion?
  2. Is nvblox expected to remain the recommended 3D reconstruction backend for Isaac ROS, or is cuRobo’s mapper the intended long-term direction?
  3. Are the two intended to coexist for different use cases (e.g. nvblox for occupancy/ESDF, cuRobo for feature-enriched manipulation planning)?

I do not need a firm commitment or timeline even a general signal wether nvblox is in maintenance mode would help me decide where to invest my time further.

Thank you.

Tom

2

Hello @MossProphet,

Thank you for the thoughtful question and for the detailed experimentation.
I’ll address your questions below.

  1. Is there a planned Isaac ROS wrapper for cuRobo’s reconstruction / feature-mapping module, analogous to isaac_ros_cumotion?
    At this time, we do not have any announced Isaac ROS wrapper for cuRobo’s reconstruction or feature-mapping module specifically. However, cuRobo is part of the broader area we are actively evolving in our refactoring efforts.

  2. Is nvblox expected to remain the recommended 3D reconstruction backend for Isaac ROS, or is cuRobo’s mapper the intended long-term direction?
    Today, nvblox remains an important part of the Isaac ROS stack for 3D reconstruction and distance-field generation. We are also continuing to evolve the manipulation stack around cuMotion / cuRobo, so the overall direction is better viewed as an expansion of capabilities rather than a simple one-for-one replacement.

  3. Are the two intended to coexist for different use cases?
    Yes, that is the most accurate way to think about it. In general, nvblox is used for reconstruction / ESDF-style world representation, while cuMotion / cuRobo are focused on motion generation and manipulation workflows. Depending on the application, these components can complement each other rather than compete directly.