Aitheon Core works with nodes. Some of these nodes are made to simplify the interface and contain other nodes. These are sub-graphs.
A sub-graph is an element of the entire system that connects with other elements - sub-graphs andnodes. We may think about sub-graphs as folders on a computer that we can connect with other folders and files - nodes. Sub-graphs may contain other sub-graphs and nodes.
Use sub-graphs to organize your services and automations on the graph table visually. Build services, add nodes to them, connect them for your business purposes.
Each service you have already activated will be a Service Sub-graph in Core (1).
These sub-graphs have ready-to-use settings (2) and a service nodeinside that allows you to make immediate automation connections.
There are several sub-types of this Service sub-graph type for specific services. For example, inside the Smart Infrastructure Service Sub-graph, there are such sub-graphs (after its sub-services):
Infrastructure Sub-graph(created automatically when you add infrastructure to Smart Infrastructure Service)
Floor Sub-graph (created automatically inside the Infrastructure Sub-graph when you add a floor to the Infrastructure)
Station Sub-graph (created when you add a station)
Controller Sub-graph (created for your devices, added to a particular station, as an example)
2. Also, you can make your own sub-graph, and it will have a corresponding common subtitle:
Above the sub-graph there is a status line. It displays statuses of the nodes inside the sub-graph.
An empty sub-graph has an EMPTY status (1).
A green dot with a number shows how many nodes inside the sub-graph are working (2), a yellow dot shows the number of stopped nodes, and an empty dot is the number of empty sub-graphs inside the current sub-graph.
You can set up settings for a sub-graph.
Click three dots at the top-right corner of your sub-graph.
Now you can go to Settings or Remove your sub-graph. Notice that you can remove only non-Service sub-graphs.
You can add as many inputs and outputs as you need (1). Give a good name for your input or outputsince it's easier to understand all the flows when inputs and outputs explain themselves.
The Multiple option (2) allows you to put multiple inputs of defined type in one place.
The Placement option defines where an input or output point locates on the sub-graph (3). If you choose Center, you will get two points of your input or output, both on the left and right sides.
Normally inputs are on the left side, while outputs are on the right side. But if needed you can make it your way for clearer connections appearance.
Select a proper Socketfor the input or output message (4).
You can delete an input or output if you don't need it anymore (5).
Double click on a sub-graph to open it. If you open a new sub-graph, it will be empty, but Service Sub-graphscontain ready-to-use nodes and settings.
There is one node named Communications Service Node(1) inside our service sub-graph Communications.
We can see what kinds of inputsmay go into the Item Manager sub-graph (2) and what outputs we may receive from it (3).
If a sub-graph (or a node) has to take or send some more possible messages (inputs and outputs), Create input and Create output options appear (4). You may use them at once, just connecting with needed input and output sockets - socket type will be AnyData.
Between these inputs and outputs, some computing work takes place. In this particular sub-graph, this work is done by one node. To configure this node, press three dots at its top-right corner (5).
Use TOOLBOX to add other nodes, sub-graphs, and other elements (6).
You may watch the ongoing log for this sub-graph with SHOW RUN INFO(7) and stop or run this sub-graph.
At the top-left corner (8) you can see the path to this part of Core and come back at a higher level.