daq:daq - GRETINA

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
======= New in 2022 ======
start run window is obsolete. Two scripts are available for changing the data directory. Daq needs to be stopped, directories need to exist: 
  * changeDataDir_maintainRunNum  <data dir>  : keeps the Run number the same, for when we need to move physics experiment data collection to another disk
  * changeDataDir_resetRunNum <data dir>  : finds the lowest available Run number without any larger RunDir #s



======= This is DAQ page from previous campaigns ======
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

  * S800-Gretina control [[docsS800Grt|docsS800Grt]] 
  * {{ :daq:ulm-e16011_names.png?linkonly |S800 Trigger GUI}}
======= Troubleshoot ======
  * S800-Gretina not correlated: Check CC setfile ~s800/converged_daq/Scripts/CC0105Begin.tcl for extsynch and extclock
  * S800 is losing events. Check the network speed of spdaq45 by /sbin/ethtool eth0 and /sbin/ethtool eth1 , both should show speed as 1000Mb/s, if one shows 100Mb/s then the network is too slow and S800 cannot send data to GEB fast enough which will cause event loss happen.
  * Check the ringbuffer status, $DAQBIN/ringbuffer status - -host=spdaq45 - -all , if the free colum becomes zero, DAQ related people needs to be notified for diagnostics.

======= Decomp Information ======
  * [[easy_decomp_calibrations|Easy Gretina Decomp File Creation]]
  * [[decomp_calibrations|Gretina Decomp Calibrations Explanation]]

======= 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!


  * May 2019, documentation provided from Jackie: [[https://docs.google.com/document/d/1Aq5NkuEKBc4_5fx-95d2RaSZM08VQwVleYWr42QTsFg/edit?invite=CNr_nogM&ts=5cd488d9|Gretina System Documentation]]
  * Instruction to shut down switches for NSCL power shutdown 12/5/2015 {{:daq:gretinaswitchesshutdown.pdf|}}

======= NSCL GRETINA LaBr Array =======

    * [[fastscint_daq| FastScint DAQ Quick Start]]
    * [[fastscint_daq_long | FastScint DAQ Details]]

======= Misc 2019 ======
  * Dual homed NSCL machines are spdaq32 and spdaq07

====== 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 **
  * [[Flash digitizer firmware]]
  * Check digitizer firmware version: on a2 or a1 terminal, type: **DIGSNIDFW** ,all digitizers should have same version firmware
  * [[Replace digitizer with different color ones]]
  * [[Replace fuses of digitizer]]
  * [[No valid decomposed events]]
  * Verify connecedt digitizers, at IOC interface, type **dbior**, it will print all identified digitizers within one bank
  * VME related scripts are located at /global/devel/boot/vmeArray
  * Check connected PVs, at IOC interface, type "casr"
  * [[ Move detectors to new Hole position ]]

====== 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.

  * Switch to a1
    * If a2 cannot be brought back. Gretina DAQ can still run on a1. In the file ~/.profile , environment variable **DAQSERVER** needs changed to be a1.gam . This parameter is used to restrict gretina daq critical scripts to run on specific machine.
Trace: • mode3 • msufeb2017 • lnerror • docss800grt • start • msumay2015 • dnl • alarmresponse • easy_decomp_calibrations • msumay2017
Search

Toolbox

QR Code
