BCAL DAQ instructions as of 17/06/14
Updated DAQ Instructions:
- Open a terminal
- >ssh hdbcalops@gluon105
- >pass: GlueX_2come
- >cd daq_pro_vers/work
- >source online_setup.cshrc
- >daq_setup.sh –s bcal_n4 (or bcal_s4 for south)
- At this point, the four green crate windows should pop up, along with the “Gui”
- Get a different terminal open, and then:
- >ssh hdops@gluon49 (gluon29 is fine as well)
- >pass: GlueX_2come
- A box called "Select Workspace" will pop up on the large monitor; select either BCAL or Default
- Get open the BCAL LED Pulser in addition to the BCAL_Voltages window that should open. You may have to click around a bit if all the options are not available right away. One of the buttons at the top, called "Open Top OPIs in Run Mode" should bring up the sidebar, which has all the options including the LED Pulser and BCAL_Voltages.
On the gui:
> control > connect > first button(configure) > second button(download) > third button(prestart)
At this point, there are two ways you can operate - either with a Custom LED pattern, or a bias voltage script:
Custom LED pattern
Press whatever LEDs you want on in the LED Pulser window, and set their pulse rate and whatnot. Once you want to start taking data, press play on the Gui, and then start the pulsers. Stop the Gui when the pulsing is done, or you have sufficient data.
Open a terminal and login to hdbcalops@gluon105 (It may not matter where you login but this should work)
- > cd /gluonfs1/home/hdbcalops/daq_pro_vers/work/tools/bcal_pulse_sequence
- > BCAL_test.py –s D –q 1
Here, the –s can have either a D or a U following it, for up or downstream LEDs to fire. The –q indicates which quadrant you wish to select. Also, by having a 1 or a 10 after a –n you can select either 1 or 10 pulses per configuration (default is 1). The command BCAL_test.py –h will bring up a help menu. You can run multiple trials in the same data set; just enter new commands and keep the Gui running. For example, to run both north side quadrants you would use –q 1 and then –q 4.
Now, you are ready to write the file. It helps to keep things organized if you open a third terminal for this; using hdops@gluon105 should work.
Make sure to keep a note of the run number, to use in your file.
- > cd /gluex/Subsystems/BCAL/data/north4
- > cd/gluex/Subsystems/BCAL/data/south
(Depending on which side you have run) There are a few ways you can write the file, depending what you wish to accomplish.
For looking at individual events in dump_tree_waveform_dalton.C, use the following command:
- > hd_root -PPLUGINS=DAQ,DAQTree datafile –o newfilename
Where datafile is the original file created from the run (which can be found on the gui under "Output File") and new filename is what you want to call the root file. For example:
- > hd_root –PPLUGINS=DAQ,DAQTree bcal_n4_3049.0 –o bcal_n4_3049.0.root
Here, the 3049 is an example run number. Use whatever run number you have. The n4 is for the north side, and one should use an s4 for the south side.
For the SiPM_Tester, the command is:
- > hd_root -PPLUGINS=DAQ,DAQTreeBCAL,TTab datafile –o newfilename
We are now ready to run the file in root!
- > root
Then, for dump_tree_waveform_dalton.C,
- > .L /gluex/Subsystems/BCAL/scripts/dump_tree_waveform_dalton.C+
- > dump_tree_waveform_dalton(“filename”)
OR, for SiPM_Tester,
- > .L /gluex/Subsystems/BCAL/scripts/SiPM_Test.C+
- > SiPM_Tester(“filename”)
Note: The tab key will be very useful in both speeding up the command process and ensuring you (and I) have written things correctly in the terminal. Use it as often as you can.
Note 2: To exit the Gui one can type the same command they used to start it, but with a –e at the end; for example:
- > daq_setup.sh –s bcal_n4 -e
So you've diligently followed the steps above, and something still isn't right. What gives? Here are some things to watch out for:
- Ensure you are running the DAQ from the proper machine and account. hdbcalops@gluon105 should definitely work, but not all machines and accounts are properly configured for it.
- The voltages of one or more modules may be inhibited or otherwise refusing to cooperate. Open up CSS and make sure they can all turn on. If they are inhibited, you can reset them all by clicking ALL U/D BIAS > Reset and turn OFF Bias channels. You can do one module at a time by clicking on that particular module, then menu > show bias channels > clear events and turn off
- You may also need to reset the physical fADC crates down in the hall. You may want to get someone to show you how to do this part properly, but effectively you turn off the crate(the green I/O switch), unplug it at the bottom (the big plug with the orange cord), wait a few seconds, plug it back in, and turn it back on.
- Make sure your triggers are enabled correctly. The trigger configurations can be found in the log book.
- Check that the timing offsets are correct, or adjust them accordingly. Timing information can also be found in the logbook.
This list is far from extensive - feel free to add to it!