This is an old revision of the document!


This is DAQ page for the 2015 campaign

The DAQ page from the former S800-GRETINA campaign in 2012 can be found at https://wikihost.nscl.msu.edu/gretina/doku.php/daq:daq_2012

Troubleshoot

  • S800-Gretina not correlated: Check CC setfile ~s800/converged_daq/Scripts/CC0105Begin.tcl for extsynch and extclock

Decomp Information

Gretina Computing

Gretina computer farm is maintained by LBNL computer group and local NSCL IT department. Nonetheless I put documents here, but we do NOT do anything to the GRETINA computers!

NSCL GRETINA LaBr Array

Misc 2019

  • Dual homed NSCL machines are spdaq32 and spdaq45

miscellaneous

  • Validation/Trigger window width is set by Dig116_CS_X55WidthP, Dig116_CS_X55WidthN. N/P stands for positive/negative maximum difference relative to Trigger timestamp which will be read out.
  • Bringing up just the EPICs screen: in gretina home ./startGRETINA_EPICSdisplay
  • Set trigger multiplicity: caput Trig0_CS_FSCThr n (n=0,1,2,3… for mult 1,2,3,4…)
  • See trigger pulse width: CheckLED.sh
  • Change trigger pulse width: SETLEDWIN <# of 20ns ticks>
  • Check timestamps, report boards that are out-of-sync: CheckTS
  • Force timestamps to reset, DO NOT USE DURING RUN!!!: SINGLEIMPSYNC
  • Warning script: run on a2 as gretina in ~/scripts: ./warningMessage4.sh
  • Check decomp stats recordDecomp.sh | head -n50

Reboot a2

  • If a2 is rebooted due to system failure, two scripts need to be brought up
    • from ~gretina: nohup scripts/warningMessage4.sh &
    • from ~gretina/scripts/watcherdir: nohup watcher &

The first is the alarm script that talks to users. The second is responsible for two things: writing record{Counters,Decomp,Settings} in the current run directory and cleaning up cluster process issues (usually restarting broken processes) soon after starting or stopping runs.


QR Code
QR Code daq:daq (generated for current page)