G2p DAQ How-To

Normal DAQ Operations

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

• For g2p and gep we are running two separate DAQs, one for each HRS arm. The LHRS DAQ is run on the adaql2 computer on the a-onl account. The RHRS DAQ is run on the adaql1 computer on the a-onl account.
  
  
• Normally, runcontrol will be already running. If not, see section on Cold Start below (for the impatient: type “startcoda”). To start and stop runs, push the buttons “Start” (6th button from left, looks like >>) and “End” (5th button, looks like a box). Start is the same as the sequence prestart, go
  
  
• We are using the LHRSHAP configuration for the LHRS and RHRSBUFF configuration for the RHRS. These are located in the “LHRS” and “RHRS” configurations respectively. The configurations should be loaded by default.
  
  
• To change configurations, use the “Configurations” menu and select COOL. If you’ve been running, you will first have to push the “Reset” (<<) but- ton. Choose the configuration from the dialog box, then press “Download” (looks like a disk drive).
  
  
• Re: the buttons in rcgui: If you let the mouse hover over the button for a few seconds you can discover what the buttons mean because a little dialog box comes up and tells you, e.g. which button is “Start”, etc.
  
  

Frequently Asked Questions

• Run number synch problem. With CODA 2.6.1 there seems to be a small probability that the run number reported by rcgui is different from the one in the data file. Firstly, the one that is correct is the one in the datafile name, which also appears as a record in the datafile, and which derives from MSQL. Secondly, fixing this goofy problem is sometimes tricky; you can try Options ... Set Run Number, but the GUI needs to be in a proper state. Or just report it to the expert and let him/her fix it.
  
  

• What is the deadtime ? Normally the deadtime is displayed in the ”datamon” window – make sure you are using the one on the same computer as runcontrol. Datamon is probably already running near the runcontrol window. If it is not running, type “datamon”
  
  

• Prescale Factor? Go to a-onl/prescale and edit the files “prescaleL.dat” and “prescaleR.dat”

Rebooting

Quick Resets

Problems with CODA 2.6.1 can usually be solved with a simple Reset (<< in rcgui) or with a Cold Start. Call an expert if you are stuck. 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). 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). NOTE: If the LHRS crate is power cycled, the boot parameters for ROC3 will need to be re-entered. The boot parameters are located in doc/vmeram g2p.doc and also on the g2p Wiki. To change the boot parameters, go to the vxWorks prompt for ROC3 and type ”c”. This will allow you to enter the parameters, one line at a time. When finished, type ”p” to print the boot parameters (and check that they are correct) then type ”@” to reboot the ROC. If you reboot the ROC, or if something on the workstation is hung up, try push- ing the ”Reset” button in runcontrol (<<” in rcgui). Then Configure, Download, and Start a run as usual. If a “quick” reset doesn’t work, try a Cold Start (see below)