🖥
🖥
🖥
🖥
AugeLab Studio Manual
English
Ask or search…
K
Comment on page

Subsytem

This block can contain other blocks within itself and can output the inputs from the outside by processing them in the subsytem. You can double click to enter Subsytem and you can set up different scenarios here. In general, the purpose of use is to provide a simpler use of the program in large projects.
You can name these blocks by clicking on the text above the subsytem block.
To add input and output to the subsytem, double-click the block and enter inside the block. Add the "subsystem in" and "subsystem out" blocks inside the block. You can name the sockets of these blocks by clicking them. And these sockets receive all data types.
Click the main button on the top tab to exit the block.

Subsystem Node Documentation

The Subsystem node in AugeLab Studio is used to create a subsystem within a data pipeline. It allows you to define a separate node scene that can be used as a subcomponent in your larger workflow.

Node Overview

The Subsystem node acts as a container for a separate node scene called a child scene. It provides a way to encapsulate a group of nodes and their interconnections into a single node, allowing for modular and reusable workflows.

Node Interaction

  1. 1.
    Drag and drop the Subsystem node from the node library onto the canvas in AugeLab Studio.
  2. 2.
    Double-click on the node to open the child scene within a new subwindow.
  3. 3.
    In the child scene, you can create and connect nodes as needed to define the behavior of the subsystem.
  4. 4.
    Close the child scene subwindow to return to the main canvas.
  5. 5.
    Connect the input and output sockets of the Subsystem node to other nodes in your workflow as desired.

Input and Output Sockets

The Subsystem node does not have any input or output sockets of its own. Instead, it serves as a container for the child scene, which may have its own input and output nodes. The input and output connections of the child scene will determine the overall input and output of the Subsystem node.

Implementation Details

The Subsystem node follows these steps to evaluate the child scene:
  1. 1.
    Input Retrieval: The Subsystem node retrieves the input values from its input sockets.
  2. 2.
    Child Scene Evaluation: The Subsystem node runs the child scene and evaluates all the nodes within it.
  3. 3.
    Output Generation: The Subsystem node collects the output values from the child scene's output nodes.
  4. 4.
    The output values are returned by the Subsystem node.

Usage

  1. 1.
    Drag and drop the Subsystem node from the node library onto the canvas in AugeLab Studio.
  2. 2.
    Double-click on the node to open the child scene subwindow.
  3. 3.
    In the child scene, create and connect nodes to define the behavior of the subsystem.
  4. 4.
    Close the child scene subwindow to return to the main canvas.
  5. 5.
    Connect the input sockets of the Subsystem node to provide input values to the child scene.
  6. 6.
    Connect the output sockets of the Subsystem node to other nodes in your workflow to use the output values from the child scene.
  7. 7.
    Run the pipeline or execute the nodes to evaluate the Subsystem node and the child scene.

Notes

  • The Subsystem node is useful for creating reusable components within a data pipeline. It allows you to encapsulate a group of nodes and their interconnections into a single node, promoting modularity and reusability.
  • The child scene within the Subsystem node can have its own input and output nodes, enabling flexible data flow between the subsystem and the main workflow.
  • Opening the child scene subwindow allows you to edit and modify the nodes within the subsystem separately from the main canvas.
  • The Subsystem node evaluates the child scene when the pipeline is executed or when the node is evaluated manually.
  • The Subsystem node is a powerful tool for structuring complex workflows and organizing nodes into logical units.
  • It enhances the capabilities of AugeLab Studio for creating scalable and modular data processing pipelines.