Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

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.

Starting the DAQ Process

To start the background DAQ process run the following command (check path)

/home/sabredaq/devdaq/bin/linux-x86_64/devDaq /home/sabredaq/devdaq/iocBoot/iocdevDaq/dmdaq.cmd

Or alternatively run this command in the devdaq directory.

./bin/linux-x86_64/devDaq iocBoot/iocdevDaq/dmdaq.cmd

This starts the process in the background. You can check it is running with the command

caget DM-DAQ:status

This should return:

DM-DAQ:status       standbye

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:

/home/sabredaq/Software/Phoebus/phoebus-4.6.6/phoebus.sh

or in the phoebus-4.x.x directory just run the phoebus.sh executable.

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:

Absolute Threshold = DC Offset - Threshold [adc] (For positive pulses use a + in place of the -)

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.

There is monitoring for each channel which shows the most recent waveforms and a histogram of charge. However the charge histogram does not seem to work well for the V1730 with raw firmware.

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.

Check the Daq status

caget DM-DAQ:status

Start/ stop the run

caput DM-DAQ:start start
caput DM-DAQ:start stop

Monitor the event rate

camonitor $(DAQ):triggerRate
  • No labels