Isaac OS Concepts
Isaac OS applications are built on Holoscan SDK 5.0 graphs, which can also exchange data with other graphs and frameworks through external topics. This page introduces the concepts needed to read or write one: operators and messages, graph composition, execution and connections outside the graph.
Operators, ports and messages
An operator is a unit of work. It declares typed input and output ports in
setup(), timing rules in contract(), and processing in compute(). Sources can
produce data without an input; sinks can consume data without an output.
A message carries a payload between connected ports. Isaac OS uses generated FlatBuffers schema types for data such as joint states and commands, and schema payloads containing tensors for images. Holoscan also supports scalar and tensor payloads. See payload types and the Isaac OS message catalog.
A temporal contract states what triggers an operator, which input samples it
uses and what to do when data is missing. For example, OnEach reacts to each
accepted sample on one input, while OnClock drives periodic work. A graph’s
clock supplies its time domain: applications use real time for hardware and
can use synthetic time for simulation. See temporal contracts
and time and clocks.
Application Composition
An application authors a holoscan::Graph. It creates operators and connects their
ports with add_flow(). Each edge has bounded queue storage and a delivery policy:
apply backpressure or drop the oldest sample when full.
A subgraph groups operators for reuse. Holoscan supports reusable Graph
subclasses with exported ports, embedded with embed(). Isaac OS also uses helper
functions that add operator groups to a parent graph, such as the
Unitree simulator subgraph.
See graph composition and reusable graphs.
Compose, compile and run
Composing describes the graph without executing it. holoscan::compile(graph)
checks its connections, timing rules and resource bounds, and returns an immutable
execution plan with diagnostics. Application code checks plan.ok() before
starting the plan with holoscan::run_async(plan).
The returned run session owns the running work. The application can request a stop, wait for completion and inspect the termination status. See compiling a plan and running and stopping.
The plan assigns operators to execution partitions. Callbacks within one partition run serially; different partitions can run concurrently. Several Isaac OS applications place control, camera and inference work in named partitions. The robot control benchmark shows this placement in use.
Connections outside the graph
Ports and edges connect operators inside a graph. Imported and exported topics connect the graph to external publishers and subscribers. Isaac OS uses these boundaries for ROS 2 transport and MCAP recording and replay. See external topics for the SDK contract.
Learn about Holoscan basics
- Your first pipeline walks through a complete application.
- Writing an operator explains the operator interface; the Python guide covers Python authoring.
- Holoscan Modules and the Isaac OS component catalog list reusable components.
- Custom FlatBuffer schemas explains how to define message payloads.