Controller UI - PoC

[cc-a]

This umbrella issue covers the various strands of work required for a simple proof of concept for the Controller UI.

Background:

The below concept diagram describes the relationship between the relevant parts of the DUNE system:

The DAQ (data acquisition) processes are the actual component of the DUNE system responsible for collecting data from the underlying hardware and recording it into data files. These DAQ processes can be in various states. These states are represented as a finite state machine (covered in detail in the drunc wiki).

The function of the controller processes is essentially to manage the state of the DAQ processes. Controllers are arranged in a hierarchy such that there is a root controller which can be used to control the state of the whole system and various sub controllers that manage the state of a set of DAQ processes. For instance here the hierarchy of processes that is booted by the full test session data:

(Anything not labelled as a controller is a DAQ process).

UI Pages

The current reference we are working from is a wireframe diagram provided by the DUNE team.

This proposes 3 pages that are covered in their own issues:

• Controller overview page - PoC #164
• Controller Log Page - PoC #166
• Controller App Tree Page - PoC #167