Running   CODA   on   Spectrometer   DAQ   Systems

Robert Michaels, rom@jlab.org, Jefferson Lab Hall A, updated Feb 9, 2009

This file: hallaweb.jlab.org/equipment/daq/guide2_2daq.html

I.   NORMAL   DAQ   OPERATIONS

This assumes that runcontrol is running.   If not, see Cold Start in section III.

• This guide is for two independent DAQs for Bigbite and L-HRS.

• The run coordinator should know the passwords, which are also posted on the wall on a paper near the whiteboard.

• Normally, runcontrol will be already running.   If not, see section on Cold Start below.   To start and stop runs, push the buttons "Start Run" and "End Run".   Start Run is the same as the sequence prestart, go.

• To change configurations, use the "Run Type" button. If you've been running, you will first have to push "Abort" button. Choose the configuration from the dialog box, then press "Download". The relevant configurations include:

• We have two modes of running the DAQ:
  • 2-daq mode  The Left HRS runs on adaql1 on the adev account.  The Bigbite DAQ runs on adaql2 on the a-onl account.
  • 1-daq mode   Both spectrometers run on adaql2 on the a-onl account. Necessary for coincidences.   Only available after a 1 hour access to switchover.

Attributes of the Two DAQ Setups

Attribute
System being read out	Bigbite   DAQ   (or both HRS if 1-daq).	Left   HRS   (if 2-daq mode)
Computer where to run	adaql2	adaql1
Account from which to run	a-onl	adev
ROCs involved	TS12, ROC5, ROC8, ROC9, ROC10 (2-daq)   (+ L-HRS if 1-daq)	TS11, ROC3, ROC4
Disk areas for data	/adaql2/dataN,   N=1,2,3,4	/adaql1/dataN,   N=1,2,3,4
Run numbers	sequence below 20,000	numbers > 20,000
Prescale factors	~a-onl/prescale/prescale.dat	~adev/prescale/prescale.dat
Deadtime and Disk monitor	datamon (from a-onl)	datamon (from adev)
runcontrol configuration	"bigbite"   ("TWOARM_FB" for coincidences, i.e. 1-daq)	LeftHrs
runcontrol config for pedestals	N/A	pedrun
Location of pedestal files	~a-onl/ped/ped*.dat	~adev/ped/ped*.dat
Location of scaler_history.dat	~a-onl/scaler/	~adev/scaler/

II.  FREQUENTLY   ASKED   QUESTIONS

• Where is the data ?     To find run 1602, type "find_run 1602" from adaq computers on the adaq accounts. Another command: "lastrun" prints where the latest run is. The data are on /adaqlM/dataN (M=1,2, N=1,2,3,..) as explained in the table above.
• What is the deadtime ?   The deadtime is displayed in the "datamon" window -- make sure you are using the one on same computer as runcontrol. Probably datamon is already running near the runcontrol window. If it is not running, type "datamon"
• Prescale Factor ?   Go to ~/prescale and edit file "prescale.dat"
• Disk Handling ?   There are several hundred Gbytes of disk for data taking. Automatic scripts choose the disk to write data, copy to MSS, delete the data when its safe, and avoid simultaneous read/write on a disk. Things to *NOT* do:

• Do *NOT* erase or move data files (even if you think its junk).
• Do *NOT* try to change run numbers.
• Do *NOT* change names of run files.
• Do *NOT* try to put data by hand into MSS.

• Pedestal Runs   The purpose of a pedestal run is to obtain pedestal files used by fastbus for pedestal suppression.   If you've been running the normal spectrometer DAQ configuration, you'll need to press "Abort", then "RunTypes" and select the PEDRUN configuration. Download, StartRun. Run for about 5000 events, then EndRun. You may check the pedestal files in ~/ped (pedN.dat corresponding to ROC #N). See README there for more details. After pedestal run, change back to the running configuration. NOTE: DONT try to use PEDRUN for anything other than pedestal determination -- its confusing since the prescale factors are in a different file, etc. If you want a run with pedestal suppression turned off, see the README.

HOW TO SHUTDOWN or REBOOT WORKSTATIONS

Rarely, the workstations don't function properly and the simplest way out is to reboot. Ole usually keeps some instructions posted near the PC terminal.   One may hit Ctrl-Alt-F1 to go to console mode, then Ctrl-Alt-Del.   If you have trouble starting X, type "startxfce4".

QUICK   RESETS

Problems with CODA can usually be solved with a simple reset or with a Cold Start. Call Bob Michaels, Vince Sulkosky, or Alexandre Camsonne for DAQ problems. Do NOT waste an hour stuck on resets.

If a ROC seems to be hung up, you can reboot it by going to the workspace with all the small x-terms logged into the frontend computers and typing "reboot" at the vxWorks prompt (-> reboot). Wait 2 minutes and telnet back in to verify its alive. The name of the ROC computer is normally written in the name of the xterm (hallasfi1, hallasfi2, etc). You need to know what subset of these computers are used for your configuration, see the table in section V below. If the ROC seems really frozen, use the "Crate Resets" button in the magnet EPICS screen on hacsbc2 (controls computer). Note, both fastbus crates in one arm are reset with one button.   To reset from the EPICS GUI, toggle the state of the button. Note, if a ROC cannot be reset via the GUI, they can only be reset by typing "reboot" at the vxWorks prompt. Another possibility is to type "ctrl-X" at the vxWorks prompt; this sometimes works when typing reboot does not work. Finally, if the above does not work one can gain access to the cpu and press the reset button (or power cycle the crate). If you don't know how, or don't know where the cpu is located, page Bob Michaels or Alexandre Camsonne.

If you reboot the ROC, or if something on the workstation is hung up, try pushing the "Reset" button in runcontrol. Then Configure, Download, and StartRun as usual.

If a ``quick'' reset doesn't work, try a Cold Start (see below).

COLD   START

To perform a cold start of the processes on the Linux computer (adaql1 or l2), simply type "startcoda" on the a-onl(adev) account. This performs a "kcoda" for you, as well as starts all the components you need.

Before downloading, it is first a good idea to make sure the fastbus and VME crates (i.e. the ROCs) are running. One finds that when resetting, one can frequently avoid rebooting the frontend crates, and just restart runcontrol, but if you must: Press the reset buttons for the relevant subset of crates as explained in the Reset section above. A convenient way to reset (reboot) the ROCs is to go to the adaql2 workspace with x-terms logged into each frontend computer and enter "reboot" at the vxWorks prompt -> of each ROC. But one can also use the EPICS GUI as explained above. After a few minutes, telnet back in and verify they are up. Some of the crates take longer than others to reboot. Be patient. To start everything on the workstation, type "startcoda" as explained above. Eventually runcontrol will pop up. In runcontrol press the Connect button. After "connect", wait 10 seconds, then press "Run Type"; a dialog box pops up and you must choose the configuration you want, which is normally the first choice. Then press download and wait about 30 seconds. If download hangs up, press "Cancel", "Reset", and "Download" in runcontrol. After a successful download, you can "Start Run" to start a run.

If you ever logout of the DAQ computer adaql1 or adaql2 or have rebooted it, here is how to restart the preferred setup. Login as "adev" ("a-onl") for adaql1 (adaql2). See table above for attributes of the two DAQs available (different accounts, etc). Emacs the prescale file in the background: "emacs ~/prescale/prescale.dat &"   Also start datamon by typing "datamon".   Next, in the "components" workspace, login to all the frontend computers by typing "telnet hallasfi1" where the name of the computer like hallasfi1 is in the name of the xterm window. Also in the name of these xterms is the portserver port where you can connect via RS232 (portserver instructions are at hallaweb.jlab.org/equipment/daq/portserver.html). So, an example name may be an xterm with title "ROC2--hallasfi2--hatsv3-port-8" meaning ROC2 is IP address hallasfi2 and on portserver hatsv3 at port 8.   Note: If these xterm windows for components are not there, type "setupxterms" to bring them up.

        CODA Configrations 

        LeftHrs -- DAQ on Left HRS (adev acct, adaql1 computer)
        bigbite -- DAQ on Bigbite (a-onl acct, adaql2 computer)

VI.   THINGS THAT GO WRONG WITH DAQ or COMPUTERS

• Lots of deadtime -- Please see hallaweb.jlab.org/equipment/daq/dtime_faq.html
• Computer/Network problems: Try calling Bob Michaels (pager 584-7410). You may also call the computer-center expert on-call (cell phone 876-1794). For problems with the linux boxes or ROOT analyzer ask Ole Hansen, though Bob can probably help too. For problems with slow controls or hac ask Javier Gomez. Alexandre Camsonne and Dave Abbott are Bob's substitute when out of town.
• How to Program the RAM of the ROCs. When fastbus loses power, it may be necessary to reload the VME RAM (it isn't as non-volatile as it should be.) Up to date info is kept at ~adev/doc/vmeram.doc   Portserver instructions ~adaq/doc/portserver.doc which are also online.
• If Bob is unavailable, some details about recovery are at jlabs1:/home/rom/doc/recovery.doc

More info: hallaweb.jlab.org/equipment/daq/guide_2daq.html   and   hallaweb.jlab.org/equipment/daq/daq_trig.html.