Control & monitor the local readout application as any other GEM application
Description
Currently, the local readout application must be manually launched and killed if recording local data is of any interest. In practice, this creates issues for the user because of the data storage location, the start/stop sequences,... While the local readout feature is not implemented as xDAQ application (and it is desirable to keep it that way), automatic control & monitoring is desired.
The proposed solution consists of converting the local readout application into a server, running at all times on the local readout machines, and a "bridge" xDAQ application. A significant advantage is the possibility to produce different configurations for the bridge application (e.g. one server for the whole system, one server per end-cap,...) while keeping the server configuration simple and stable. The end user (e.g. DOC) could switch from one local readout configuration to another without any sort of problem.
This issue is open to track of all tasks and progresses made in that direction.