Skip to content

Conversation

@yrh012
Copy link
Contributor

@yrh012 yrh012 commented Dec 12, 2025

Description

This PR solves the issue by developing a new that explains in details how to interface Isaac Sim with AICA core using omnigraphs and ROS2 control

Review guidelines

Estimated Time of Review: 10 minutes

Checklist before merging:

  • Confirm that the relevant changelog(s) are up-to-date in case of any user-facing changes

@yrh012 yrh012 self-assigned this Dec 12, 2025

# Interface with Isaac Sim using OmniGraph and ROS 2

This guide walks you through the steps required to set up **NVIDIA Isaac Sim** so it can interface with **AICA Core**
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

General question here, the ROS 2 Bridge is something specific to Omnigraph or not? Is it also a thing outside Omnigraph?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

great question, there are multiple ways of interacting with Isaac Sim and using the ROS 2 Bridge, Omnigraph is only one way, for example, there is also the python SDK that allows connecting to ROS as shown here

@SprGrf
Copy link
Contributor

SprGrf commented Dec 18, 2025

Just FYI, switching to v4 doc version switches to the AICA Studio tour. And what's worse is that returning to v5 does not return you to the actual guide, but the v5 version of tour. Maybe it's something known, just letting you know.

@domire8
Copy link
Member

domire8 commented Dec 18, 2025

Just FYI, switching to v4 doc version switches to the AICA Studio tour.

interesting, that's probably something we haven't tested yet but ideally this would redirect to the list of examples

This command opens the Isaac Sim launcher. In the launcher:

- Set ROS Bridge Extension to `isaacsim.ros2.bridge`
- Set Use Internal ROS2 Libraries to `jazzy`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ROS2 or ROS 2? I would expect the first, since it's also how it appears in the picture, but the latter has been used so far in the document.

Copy link
Member

@domire8 domire8 Dec 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's ROS 2 with a space officially, https://www.ros.org/imgs/ROSBrandGuide.pdf

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Over here, I am referencing what exactly is written in the image, do you prefer to ROS 2 as it is officially named?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not a strong preference. Initially I didn't see the image this is why I commented in the first place.

yrh012 and others added 2 commits December 18, 2025 17:01
Co-authored-by: Spyros Garyfallidis <spyros@aica.tech>
Co-authored-by: Vaios Papaspyros <8146703+bpapaspyros@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants