daq instructions for start counter

  • What account do I log into hdops or hdstops?
    • hdstops
  • How do I find out which gluon node is being used.
    • the gluon gui will show unused gluons in green. used ones in yellow. Click on the node to see info in the text window including what account is running the DAQ on that node.
  • If hdstops, how do I do the set-up?
    • cd DAQ/daq_run/work and source online_setup.cshrc[?]
  • What is the difference between “setup” and “config”?
    • setup names the rocs that participate in daq run, whether read-out or not
    • config specifies specifics of the DAQ settings like trigger and whether we are running on a local TI or on the global TS

From: “Alexander Somov” <somov@jlab.org>
To: “Mark Ito” <marki@jlab.org>
Sent: Friday, December 4, 2015 5:07:36 PM
Subject: ST stand alone setup

login under hdops (hdstops)

cd /gluonfs1/home/hdops/CDAQ/daq_dev_v0.31/daq/config/hd_st

Two configurations:

st_ti_pulser.conf (TI periodic pulser)

st_cosmic_ti.conf (Self trigger with Master TI)


Notes on Electronics Convos


gates in a circle, gate delay depends on temp and voltage, this sets the least count to something like 100 ps. There is a circuit that senses the phase of an external clock and adjusts the voltage to keep the ring in synch with the external clock. when clocks are out of sync, the chip indicates that in a bit and that bit is added to the output stream. the changes on the bit are not strictly syncronous with the condition of the clock sync, there may be a few triggers plus or minus between the indication of the bit vs. the sync condition under which the data were recorded.

Resolution could be worse when unlocked. He has seen factors of 5 to 8. This even though unlocked, the clock period should only change by 10% or so.

the unlocked state is unrecoverable. the meanderings of the period while lock is being sought is not recorded anywhere.

He recommends looking at the correlation of unlocked state and high rate. He has been able to knock a chip out of lock by putting in 20 MHz rate.


Had not heard of the missing bit on the DAC problem. If we get a board to him he will have a look.

Taking data for start counter hot checkout

  • Sergey F. suggests always start with a pulser run if the system has not been exercised recently.
  • If ROCs of interest are blue (not green?), setup up the daq setup and configuration and then press “stop” on RCM run conf gui
  • red letters on the ROC display in the roc box means cpu busy
  • ROCSTPSC2 is full of discriminators, does not participate in data taking, should show 0 data rate
    • right click on “roc box” in run control monitor and click on update to see contents of crate
  • run control rcgui shows location of output data file
  • https://halldweb.jlab.org/rcdb show list of runs taken

Start Counter Checkout

Monday, September 26, 2016

Tom Carstens wanted an OK on start counter cabling before doing a beamline survey upstream of the target. Removing the target cart would disturb this part of the beamline and therefore would trigger another survey. We wanted to ensure that all channels are working, i. e., that all cables are connected properly.

  • checked visually that crates were on, racks on floor, south side
  • At first Nick reported no discriminator counts. Confirmed by MMI.
  • Fixed by Sascha [reboot of the crate?]
  • Hovanes explains scalars stuff:
    • process starts automatically to get discriminator scalers
    • EPICS spies on DAQ-filled shared memory
    • DAQ read-out uses same shared memory values
    • DAQ does not touch “trigger” scalers
    • DAQ allowed to change settings on “readout” scalers
    • readout2 and trigger2 are dead [expected?]
  • Sascha explains DAQ stuff:
    • to run stand-alone, suffices to log in as hdops
    • select stand-alone mode by using appropriate configuration file
    • trying to run reveals bad TDC for start counter (1 of 2). Sascha will replace it.
  • Eric P.:
    • channel 20 has always been hot
  • Gave Tom C. the go-ahead to do the beamline survey

Notes on Running the Data Acquisition for the Start Counter

  • need to be an unused user account on an unused gluon node
  • to check on crates available for use:
    • rcm.sh
    • click on “ROCs” in RCM RUN CONF gui
    • click on “Update”
    • should be green background, black letters
      • blue background -> in use
      • red letters -> needs reboot
  • to check on gluon status
    • rcm.sh
    • click on “Gluons”
    • should be green if unused
      • yellow -> in use
  • Rebooting ROCST is a special case
    • rocs.sh st reset

ST stand alone setup, v2

from Sascha, supercedes previous post


Configuration files



Start rcm.sh

SETUP: hd_st.ti   – ST stand alone (Master TI)
hd_st.tsg  – ST with TS

CONFIG:  st_pulser_ti.conf   ST stand alone