Hints on Hall A Data Taking with CODA 2.2

Robert Michaels, rom@jlab.org, Jefferson Lab Hall A, updated Jan 2001

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

I.  Running Spectrometer DAQ

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

• Use the "adev" account on adaqs2. Use the "atrig" account on adaqs3 if running the two spectrometers in the "two independent DAQ mode".
• Normally, runcontrol will be already running. 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 for 1-Trigger-Supervisor mode are:
  • TWOSPECT -- to run 2 spectrometers for 1-DAQ setup
  • PEDRUN -- to do a pulser run, this generates the pedestal files for pedestal suppression. 5 minutes is sufficient. (Note: PEDRUN uses a different prescale file, the data goes to disk6 or 7, the datamon window doesn't know about it. Only use this config for getting pedestals, see section on pedestal runs below.) Gory details are at adaqs2:/home/adev/ped/README.
• More information about running two DAQ systems see the following URL: hallaweb.jlab.org/equipment/daq/twodaq.html.

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.
• What is the deadtime ? The deadtime is displayed in the "datamon" window -- make sure you are using the one on same computer as runcontrol (presumably adaqs2). Probably it 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 300 Gbytes of disk on adaqs2. Partitions are /adaqs2/dataN, where N=1,2,..6. 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.

  It takes a couple hours for files to appear in MSS, and the files remain on adaq disk for typically 1 or 2 days.

• Pedestal Runs If you've been running the 1-DAQ "twospect" configuration, you'll need to press "Abort", then "RunTypes" and select the PEDRUN configuration. If using the 2-DAQ setups, you instead must use PEDRUNE (E-arm) or PEDRUNH (H-arm). Download, StartRun. Run for about 5000 events, then EndRun. You may check the pedestal files in ~/ped (ped1.dat and ped2.dat), where ~ is adev or atrig, as appropriate. See README files there for 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, the data goes to disk 6, etc. If you want a run with pedestal suppression turned off, see the section in the /home/adev/ped/README.

III.  REBOOTING STUFF

HOW TO SHUTDOWN or REBOOT WORKSTATIONS

Rarely, the workstations don't function properly and the simplest way out is to reboot. To reboot adaqs2,s3 (SunOS): Login as "adaq" and type "reboot". In a few minutes the workstation comes back alive. This solves most problems. For adaqh2,3,4,5 (HP-UX), you have to "shutdown" (cannot "reboot"). Shutdown works on SunOS and HP-UX, and is necessary in case of power failure. To shutdown, login as "adaq" and type "shutdown". After several minutes screen goes black, wait a minute more, then power off. When you power on again, computer reboots. (Eccentricity of adaqs2: When it comes back on from shutdown, there is a sign "Ok" where you have type "boot". When you login to online account you have to type "xhost +adaqs2".) For Linux, Ole usually keeps some instructions posted near the PC terminal.

QUICK   RESETS

Problems with CODA 2.2 can usually be solved with a simple reset or with a Cold Start. If not call Bob Michaels or Dave Abbott.

If a ROC seems to be hung up, you can reboot it by going to the workspace "Components" 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 written in the name of the xterm (hallasfi1, hallasfi2, etc). Of course, you should know what subset of these computers are used for your configuration. For example, experiments in year 2000 typically use hallasfi1 (ROC1), hallasfi2(ROC2), hallasfi3(ROC3), halladaq1(TS0), halladaq4(TS1), and hallavme1(ROC14), If the ROC seems really frozen, use the "Crate Resets" button in the magnet EPICS screen on hac. This GUI is being developed (not by me) as I write this... at the moment the mapping is roc14=bpm/raster, roc1=R-arm fastbus1, roc2=L-arm fastbus1, roc3=L-arm fastbus2, TS0=R-arm Trig Super, TS1=L-arm Trig Super. To reset, toggle the state. E.g. for roc14 toggle 1, wait 10 seconds, then 0. For the others, toggle the right, then left button (even though the button labels are chaotic). 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 "Reset" does not work, try a cold start (see below).

COLD   START

First kill all process on the workstation where CODA is running by typing from anywhere on the adev account "kcoda". This stops runcontrol, the event builder, event recorder, the runcontrol server, and cleans up the ET system. Now you can start everything again by typing "runcontrol" but 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 ROC1, ROC2, ROC3, ROC14, TS0, and TS1 as explained in the Reset section above. A more convenient way to reset (reboot) the ROCs is to go to the Components workspace and enter "reboot" at the vxWorks prompt -> of each ROC. After a few minutes, telnet back in and verify they are up. Some of the crates take longer than others to reboot. Be pateient. If the ROCs are frozen, press the reset buttons instead of typing "reboot". To start everything on the workstation, type "runcontrol". Then 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 presumably "twospect" for two-arm operation. Then press download and wait about 30 seconds. Now you can "Start Run" to start a run.

After bringing up runcontrol you need to "Reset" after configuring the "Run Type" (if msql database gets confused about state of things). If its ever necessary to reprogram the NVRAMS on the ROCs, see adaqs2:/home/adev/doc/vmeram.doc. Sometimes connection via portserver (RS232 interface) is useful, see adaqs2:/home/adaq/doc/portserver.doc

If you ever logout of adaqs2, or have rebooted it, here is how to restart the preferred setup. Run runcontrol on the workspace called "runcontrol". In this same workspace, start emacs in background: emacs /home/adev/prescale/prescale.dat &     Also start datamon by typing "datamon". 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. If these xterm windows for components aren't there, type "setupxterms". Remember which frontent computers are involved; for example ROC3 may be irrelevant (ROC3 is FPP).

IV.   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 881-7897). You may also call the computer-center expert on-call (cell phone 876-1794). For problems with the linux boxes or ESPACE ask Ole Hansen, though Bob can probably help too. For problems with slow controls or hac ask Javier Gomez. Dave Abbott (7190) is 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 adaqs2:/home/adev/doc/vmeram.doc and is posted in the middle room on the rack's inside wall near the VT100 screen.
• If Bob is unavailable, some details about recovery are at jlabs1:/home/rom/doc/recovery.doc

This page maintained by Robert Michaels   rom@jlab.org