System State

Studio provides a system state module to command nodes into a runtime context, and alert you when any errors are encountered on the system.

The system state module provides an interface to command nodes into the three runtime contexts—standby, record or replay. System state observes the runtime hosts and nodes on the bus. Based on the runtime context it reports the current status of all nodes.

System state with background data

Opening system state

System state can be accessed at any time in Studio. Start Studio from the application icon, or the command:

$ polysync-core-studio

The system state module is launched from the icon.

Studio landing page - system state icon

System state explained

Observed errors are reported on the left half of the window. Hosts and nodes are shown in the system overview section on the right half along with their current runtime status (not to be confused with runtime state).

System state with one manger node and no errors

There are five possible node statuses:

  • Hardware - Orange
  • Standby - Green
  • Replay - Blue
  • Error - Red
  • Unavailable - Grey

Hardware - orange

In this state, the PolySync runtime is referencing the system SDF in the location:

~/.local/share/polysync/config/psync.sdf.

Note that the system SDF is modified using the SDF Configurator.

Enter this state by pressing the button.

Standby - green

This is the default runtime state when Studio starts. Nodes are ready to be instructed to start under the hardware context, or load a log session for replay.

Enter this state by pressing the button.

Replay - blue

The node is actively replaying data. The active replay session is displayed in the control bar, and selected using the logfile manager playlist.

In this state, the PolySync runtime is referencing the replay SDF in the location:

~/.local/share/polysync/rnr_logs/<current_replay_session_id>/psync.sdf.

Enter this state by selecting a logfile session from the Studio logfile manager playlist—here’s a walkthrough of replaying a logfile session through the logfile manager.

Error - red

The node is reporting an error which requires intervention in order to resolve.

The nodes fault stack can be traced using Studio’s console, or by directly looking at the text file ~/.local/share/polysync/polysync.log. By default the file is located in ~/.local/share/polysync/polysync.log.

Unavailable - grey

The node has been defined in the SDF, but is not detectable within the PolySync runtime.

Typically this means the node was not spawned, or that it has not published data to the bus yet, typically indicating the process died shortly after being spawned.

The nodes fault stack can be traced using Studio’s console, or by directly looking at the text file ~/.local/share/polysync/polysync.log. By default the file is located in ~/.local/share/polysync/polysync.log.