Application Workflow

This guide helps you get familiar with the application workflow which includes following:

  1. Launch Graph Composer

  2. Sync extensions from NVIDIA Cloud repository

  3. Create simple application using Graph Composer

  4. Run application

  5. Create container image for the application

We will start by first setting up the system and explain the basic layout of the Composer on Ubuntu 20.04 x86_64. Then, we will load, understand, and run a simple application. This will provide an understanding of how the Composer works. Finally, we will create a simple application without writing a single line of code. Graph development is currently supported only on x86. Graph Composer package for arm64 can be used to deploy or execute graph on Jetson.

Installation step installs all tools in the /opt/nvidia/graph-composer directory with links to tools in /usr/bin directory. You can access the tools without switching to the installation directory. After installation, check if the installation was successful using the following commands in a terminal:

registry --help

Registry Help Command

container_builder --help

Container Builder Help Command

If you still don’t see the components, check the FAQ section.

Launch Graph Composer

There are two options to launch Composer:

  1. Native workstation:

Launch Composer from native workstation using following command:

  1. DeepStream SDK devel container image:

Launch Composer from DeepStream SDK devel container image, installation on local system is not required for it:

docker pull
xhost +
docker run -it --entrypoint /bin/bash --gpus all --rm --network=host -e DISPLAY=${DISPLAY} -v /tmp/.X11-unix/:/tmp/.X11-unix --privileged -v /var/run/docker.sock:/var/run/docker.sock


When using the Composer from the devel container image, users could have a problem browsing the “/” folder from the file browser, in this case they can just type the file path directly or copy and paste it.

Graph Composer Default Window

Sync Extensions

Before any graph can be executed or container built, extensions from NGC public repo must be synced. Follow the steps below to sync the extensions:

  1. Be sure no graph is opened. If there is an graph being opened, it must be closed to make the registry menu usable.

Graph Composer Close Graphs
  1. Open the Registry menu from the menubar at the top and click on Sync Repo

Graph Composer Registry Menu
  1. Select ngc-public from the drop-down list and click on Sync

Graph Composer Select Repo
  1. The composer reports the current status using a progress bar.

Graph Composer Sync Progress
  1. Once the extension sync is complete, the composer displays a success message.

Graph Composer Sync Success
  1. On clicking ‘OK’, the composer automatically refreshes component list. You can see the refreshed list in the component list window on the right.

Graph Composer Default View

Create a Graph

Now, let’s create a simple graph and run it. For this example we will create a simple Ping Graph using components present in the Sample Extension and Standard Extension. In this Ping Graph, we simply send a message from one entity to another periodically for certain number of counts. It uses the following components:

  1. Transmitter:
    • DoubleBufferTransmitter - This is a queue which is holds a message being transmitted.

    • PingTx - This component creates and publishes a message every time it’s executed.

    • PeriodicSchedulingTerm - Scheduling Terms determine when to execute an entity in this case Transmitter. PeriodicSchedulingTerm is used to execute entities periodically.

    • CountSchedulingTerm - CountSchedulingTerm is used to stop the execution after a certain count. If you want to keep it running then skip adding this component.

  2. Receiver:
    • DoubleBufferReceiver - This is a queue which hold the messages sent by other components.

    • PingRx - This component receives a message on DoubleBufferReceiver every time it’s executed.

    • MessageAvailableSchedulingTerm - This Scheduling Term determines if a new message has arrived and only then PingRx codelet is ticked.

  3. Scheduler:
    • GreedyScheduler - Scheduler determines the order in which components are executed. GreedyScheduler is a simple single-threaded scheduler which executes components one after another.

    • RealtimeClock - A clock used by Scheduler to track time.

Follow the steps:

  1. Add PingTx, PingRx and GreedyScheduler by dragging and dropping them from the components panel the graph window.

  2. Add the rest of the components such as CountSchedulingTerm, PeriodicSchedulingTerm and MessageAvailableSchedulingTerm by dragging and dropping into the respective entity node.

  3. Now, right click on the signal in PingTx and click Create DoubleBufferTransmitter. Follow the same steps for PingRx’s signal and GreedyScheduler’s clock.

We can create a graph by simply dragging and dropping components from the Component Panel and add more components to it.

Adding a Component to the Graph

After adding the components your graph will look like the image below:

Create Ping Graph

Now we make connections between components. For instance, you will have to connect a DoubleBufferTransmitter to a DoubleBufferReceiver to pass messages between them. PingTx/clock needs to be linked to GreedyScheduler/RealtimeClock. These connections are made by creating an edge between the components as shown below:

Connecting the Components

Finally, we have to set the required parameters for the components:

  • In PingRx/MessageAvailableSchedulingTerm: set min_size to 1

  • In PingTx/CountSchedulingTerm: set count to 5

  • In PingTx/PeriodicSchedulingTerm: set recess_period to 5

Setting properties

Now you can save the graph using File -> Save Graph (as). This will create a yaml file with all the components and the connections.

  name: MyGraph
- extension: TestHelperExtension
  uuid: 1b99ffeb-c250-4ced-8117-62ac05969a50
  version: 2.1.0
- extension: StandardExtension
  uuid: 8ec2d5d6-b5df-48bf-8dee-0252606fdd7e
  version: 2.1.0
- name: ping_tx0
    signal: double_buffer_transmitter4
  type: nvidia::gxf::test::PingTx
- name: double_buffer_transmitter4
  type: nvidia::gxf::DoubleBufferTransmitter
- name: periodic_scheduling_term7
    recess_period: '5'
  type: nvidia::gxf::PeriodicSchedulingTerm
- name: count_scheduling_term8
    count: 5
  type: nvidia::gxf::CountSchedulingTerm
name: PingTx
    x: 267.5172119140625
    y: 217.01148986816406
- name: ping_rx1
    signal: double_buffer_receiver3
  type: nvidia::gxf::test::PingRx
- name: double_buffer_receiver3
  type: nvidia::gxf::DoubleBufferReceiver
- name: message_available_scheduling_term9
    min_size: 1
    receiver: double_buffer_receiver3
  type: nvidia::gxf::MessageAvailableSchedulingTerm
name: PingRx
    x: 756.0440673828125
    y: 145.01800537109375
- name: greedy_scheduler2
    clock: realtime_clock6
  type: nvidia::gxf::GreedyScheduler
- name: realtime_clock6
  type: nvidia::gxf::RealtimeClock
name: GreedyScheduler
    x: 579.9171752929688
    y: 422.7069396972656
- name: connection5
    source: PingTx/double_buffer_transmitter4
    target: PingRx/double_buffer_receiver3
  type: nvidia::gxf::Connection
name: node0

Run Graph from Graph Composer

You can deploy the graph using one of the following methods:

Run scenarios

Local System

To run a graph click on the Play button from the toolbar. This will open a dialog where you can choose a graph file and the target config file /opt/nvidia/graph-composer/config/target_x86_64.yaml.

Once all the details are filled, click on Run. This will execute the graph and you can see the output in an external terminal.

local run

Remote System

For executing the graph on a remote system, add remote system’s ip address and password.

Click on Run. This will execute the graph on the remote system and the output can be seen in the console.

remote run

Run Graph from Command line

Execute Graph using commandline ( script)

The script provided with the graph composer helps with graph execution and provides added functionality.

Complete usage reference:

    Usage: /opt/nvidia/graph-composer/ [options] <graph-file> [additional graph files]

  -d, --graph-target "<graph-target-file>"    [Required] Graph target config file
  -s, --subgraphs <subgraph1>,<subgraph2>,... [Optional] Paths of subgraphs used by the application, comma-separated list
      --resources <graph-resources-file>      [Optional] Graph resources file
  -f, --fresh-manifest                        [Optional] Re-install graph and generate a new manifest file
  -g, --with-gdb                              [Optional] Execute the graph under gdb
  -m, --use-manifest <existing-manifest>      [Optional] Use an existing manifest file
  -r, --remove-install-dir                    [Optional] Remove graph installation directory during exit
  -t, --target <username@host>                [Optional] Target to execute the graph on. SSH will be used
      --target-env-vars "<env-vars>"          [Optional] Separated list of environment variables to be set before running on target


To execute graphs on a remote target: * Graph Composer package must already be installed on the target * It is recommended that a password-less login method be used for SSH

  • To execute a graph locally, run:

    /opt/nvidia/graph-composer/ <graph-file> -d <graph-target>

    For example, on dGPU host, run:

    /opt/nvidia/graph-composer/ <graph-file> -d /opt/nvidia/graph-composer/config/target_x86_64.yaml

To execute on a remote Jetson target, run:

/opt/nvidia/graph-composer/ <graph-file> -d /opt/nvidia/graph-composer/config/target_aarch64.yaml \
-t <username@host> --target-env-vars "DISPLAY=:0"


If a graph has resources associated with it described in a resources YAML file, an additional argument --resources <resources.yaml> can be passed to the script. The resources would be copied to the remote target before graph execution


When executing a graph that uses subgraphs, you must pass additional argument -s <subgraph1>,<subgraph2>,... containing paths to the subgraph files. You must not pass the subgraphs as graph file arguments without an option.


To run the graph on the remote machine, install the following packages:

  1. openssh-client

  2. sshfs

Use ssh-keygen to generate an ssh key pair. Copy key to target using ssh-copy-id ${TARGET}

Create Container Image from Graph Composer

Container image can be created for Ubuntu 20.04 x86_64 or Jetson but creation is supported only on Ubuntu 20.04 x86_64. Following scenarios are supported for it.

Container Image scenarios

Local System

For creating a container on the local system, choose the container builder config file and target config file.

Click on Build Image. This will create the container image on the local system.


Remote System

For creating a container on the remote system, choose the container builder config file and target config file.

Also add remote system’s ip address and password. Click on Build Image. This will create the container image on the remote system.

This feature is only available on Windows platform.


DeepStream Application

Previous application was simple demonstrating application workflow. Similar workflow can be used to create, load and run DeepStream applications using GXF. It requires that DeepStream 6.2 and reference graphs packages are installed on the system with all the dependencies.

  1. Open the File menu from the menubar at the top and click on Open Graph to launch the file browser. You may alternatively use the Ctrl + O key combination.

Graph Composer File Menu
  1. Browse to a valid graph file, select it and click on Okay to open the graph.

Graph Composer Open Graph
  1. Composer should now show the application graph.

Graph Composer Test1 Graph
  1. To load component parameters from a separate file, right-click on the graph and select Load parameters from the context menu to launch the file browser.

Graph Composer Load Parameters Menu
  1. Browse to an appropriate parameters file for the currently open and visible graph, select it and click on Okay to load parameter values from the file.

Graph Composer Load Parameters

Rest of the steps to run the application or build container image are same as demonstrated earlier.