This Page is written as a basic guide to operating the SABRE South Development DAQ. It is mostly being prepared for the SABRE North group at LNGS and is a summary to the other pages on this wiki. As such some places use specific locations and install names for the LNGS install. If you are not using this install either change the global paths or use the relative ones.
| Table of Contents |
|---|
Starting the DAQ Process
To start the background DAQ process run the following command (check path)
...
Note: there may be mulitple warnings about “Identical process variable names in multiple servers” if you have run the DAQ multiple times during one PC power cycle. I (Bill) do not believe that these are of concern absent other errors (but this maybe be corrected by the codes author)
Starting the GUI
Starting the GUI (Graphical User Interface) is quite straight forward. Run the following command:
...
Then using the file browser open the path /home/sabredaq/Software/sabrecss and select sabre.bob
If the display is ever unresponsive or does not update when the daq status changes, right click and select Re-load display.
The GUI should now match with the DAQ instance.
Setting up the run
The system should load the DAQ information from the prior runs on startup. However this might not always work. So you should make sure to use the following settings…
Thresholds
note despite the thresholds seeming like they are relative to baseline. They are absolute thresholds relative to the DC Offset in adc. So for a negative pulse:
...
Note for the V1730 1 mv ~=8 adc.
Unit Conventions
There are a range of different units.
Coincidence windos - in trigger clock cycles (for the V1730 the trigger clock cycle is 8ns)
Event length/ - number of samples
Starting/Monitoring/Stopping the run
Helpful Hint: Make sure the DAQ is Writing if you are trying to acquire the data. It looks almost identical if the DAQ is running but not writing.
To start/stop the run on the GUI just click start/stop. Note the system may take some time to respond.
...
You can also monitor the instantaneous rate (number of events in 1 second), data rate (MB/s, not cannot support decimals so will say 0 instead of 0.5). More useful maybe the total number of events, total file size, and runtime.
Useful command line commands
So the command caget gets the current value of a variable. camonitor continuously monitors a variable. caput allows you to change a variable. If you want to know the name of a variable hold the mouse over the graphical interface.
...