Update home authored by Andreas Gad's avatar Andreas Gad
......@@ -69,8 +69,7 @@ In the __FAQ__ you can learn how to start __DAQC__. So let's assume you have sta
Notice, that even though you can access it from anywhere on the CERN network, you need the credentials to be able to change anything.
The web frontend will show you something like the following:
![daqc](uploads/8faaeea12352f74cf5de7118c169b597/daqc.png)
![Screenshot_from_2020-07-01_11-10-22](uploads/e5b49739ea3c2ffc421979c280f511c8/Screenshot_from_2020-07-01_11-10-22.png)
1. __VME computers*__ (__RIO2__, __RIO7__): This box shows you whether the VME computers are online, i.e. if they can be reached from __Bumblebee__.
2. __Readout*__: This box shows the status of the readout, i.e. the event builder on __Bumblebee__ and the two `drasi` instances running on the two VME-computers. The `2/2` means that both nodes are running. The event builder broadcasts the data such that we can attach onto it and save it to a file.
3. __Relay__: The relay is a `ucesb` instance that attaches to the event builder's data stream and fans it out to several data streams. This also validates the data, i.e. if it crashes, the data may be corrupt. The relay provides data to, among others, the online analysis. So if the relay dies, so does the online analysis. The relay is *NOT* responsible for the data taking or recording, and is thus non-essential.
......
......