We use a rather broad palette of different programs and libraries to make everything work. In order to not have worry to much about the individual parts, we have written __DAQC__, which handles all the different parts and provides a user-friendly interface for control and monitoring. The following list is an extremely brief description of the different components. Most of the time, however, all you need to worry about is __DAQC__, which will be described in next section.
We use a rather broad palette of different programs and libraries to make everything work. In order to not have worry to much about the individual parts, we have written __DAQC__, which handles all the different parts and provides a user-friendly interface for control and monitoring. The following list is an extremely brief description of the different components. Most of the time, however, all you need to worry about is __DAQC__, which will be described in next section.
-`drasi`: The data acquisition (data pump) that handles the data transport aquired from our modules. It allows the use of a so called `f_user.c`, which is a piece of C code that handles the actual readout of the modules. The `f_user.c` is custom made. We run 2 drasi instances: one on each VME computer and an event builder on __Bumblebee__.
-`drasi`: The data acquisition (data pump) that handles the data transport aquired from our modules. It allows the use of a so called `f_user.c`, which is a piece of C code that handles the actual readout of the modules. The `f_user.c` is custom made. We run 2 drasi instances: one on the VME computer and an event builder on __Bumblebee__.
-`nurdlib`: The VME library that knows the data layout of a wide variety of modules and how to do an actual data readout. We use this to perform the tasks of our `f_user.c`.
-`nurdlib`: The VME library that knows the data layout of a wide variety of modules and how to do an actual data readout. We use this to perform the tasks of our `f_user.c`.
-`trlo II`: Firmware for the VOLUM-models. We use this to program our trigger logic.
-`trlo II`: Firmware for the VOLUM-models. We use this to program our trigger logic.
-`ucesb`: Data unpacking software. We use it mainly for two purposes. It is used to attach to the data stream from the event builder and save the data to disk. It is also used to attach to the data stream from the event builder and fan it out to multiple online analysis programs. A major advantage of `ucesb` is that it checks that the data is not corrupt online.
-`ucesb`: Data unpacking software. We use it mainly for two purposes. It is used to attach to the data stream from the event builder and save the data to disk. It is also used to attach to the data stream from the event builder and fan it out to multiple online analysis programs. A major advantage of `ucesb` is that it checks that the data is not corrupt online.
...
@@ -193,7 +193,6 @@ This section will give you the step-by-step guide to how to start up the acqusit
...
@@ -193,7 +193,6 @@ This section will give you the step-by-step guide to how to start up the acqusit
- Go to the correct directory and source the `virtualenv`.
- Go to the correct directory and source the `virtualenv`.
- Run the __DAQC__ command.
- Run the __DAQC__ command.
To detach from the screen session: `Ctrl+A D`.
- __Stop or Restart DAQC__:
- __Stop or Restart DAQC__:
Go to the screen session running __DAQC__ and do a `Ctrl + C`. Be patient, it will take some seconds to power down, do not keep hitting `Ctrl + C`.
Go to the screen session running __DAQC__ and do a `Ctrl + C`. Be patient, it will take some seconds to power down, do not keep hitting `Ctrl + C`.
...
@@ -256,7 +255,7 @@ This section will give you the step-by-step guide to how to start up the acqusit
...
@@ -256,7 +255,7 @@ This section will give you the step-by-step guide to how to start up the acqusit
- __Save the Mesytec settings__:
- __Save the Mesytec settings__:
Go to the MesytecControl. If you are inside a module, exit this with `x`. Now enter `s` and follow the commands.
Go to the MesytecControl. If you are inside a module, exit this with `x`. Now enter `S` and follow the commands.
- __Load the Mesytec settings__:
- __Load the Mesytec settings__:
Go to the MesytecControl. If you are inside a module, exit this with `x`. Now enter `l` and follow the commands.
Go to the MesytecControl. If you are inside a module, exit this with `x`. Now enter `l` and follow the commands.
