-
Notifications
You must be signed in to change notification settings - Fork 0
Running the DAQ
The instructions on this page assume you have followed the instructions on the First Time Server Setup page, or you are using the server that has been already set up for the cosmic stand in the lab. It also assumes that the hgc-python repository has been cloned into the folder ~/cosmic-daq, and that your extern/HGCal-RPi/ directory has been configured (these have already been done for the cosmic stand server).
The first step is to get the DAQ hardware up and running. You should turn the hardware on, and wait a few moments for the Raspberry Pis to boot up. These steps need to be performed when you turn on the hardware, or when the DAQ gets stuck. You only need to follow these instructions once to be able to take as many data-taking runs as desired (assuming things don't get stuck).
Change into the ~/cosmic-daq/extern/HGCal-RPi directory. Run ./reset to get the hardware running.
You should see the following output:
stopping exes
power cycling
setting ipbus ip/mac
starting exes
waiting for ping
checking hexboards
piR10 0x0000 0x00ff (2 hexbds)
total: 2 hexbds
The piR10 line will change depending on the hardware setup you have. One line will be printed for each active readout board. In the current case, we have one readout board with Raspberry Pi piR10, with two hexaboards connected on the top two ports.
If you see the correct number of readout boards and hexaboards, the ./reset script worked correctly. Refer to the HGCal-RPi README for more instructions (there is a small set of cosmic stand specific instructions in the README of the umn-cosmic branch)
Once the hardware has been started, you can begin taking data with the IPBusDAQ.py script.
Run ./IPBusDAQ.py --help to see all available options. The run number is generated automatically using the file data/raw/RunNumber if you do not specify one.
Make sure you run the DAQ script as ./IPBusDAQ.py or python -O IPBusDAQ.py. This will enable optimizations, and disable the debug printing mode.
NOTE: This DAQ script is only intended for use with one readout board! The DAQ script as well as the rest of the analysis chain would have to be updated to use multiple readout boards.