Log entry time 12:14:10 on March 1,2010

Entry number 310296

Run DAQ on adaql5, as well as panFFB and pan_online.
startAnalyzer_prex has been restored since previous test.

This required a bunch of changes to CODA database (EB1 -> EB5, 
etc) and change $SESSION for vxWorks boot, etc.  

Run numbers are 50K+ on adaql5 (may change this later).

Run 50789, 90 -- could not open ET

Oops ! have to recompile panFFB such that fComputer=adaql5
in TaRun.cc.  Too bad it's hard-coded like that.

make clean ; make -f makefile_fdbkonl

Finally got ET / online analyzer to run, but it reports only
150 Hz.  I think it's even worse than before !

Run 50794
There are a very large number of Multiplet / helicity errors
being reported, so maybe that's costing time.

I tried (temporarily) turning off the "cerr" messages with
a fVerbose flag in TaMultiplet.hh.  Still lots of errors.
But this got the rate up to 185 Hz.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Next, using fVerbose flags in VaEvent and TaPairFromOctet I turn
off more printouts.

Didn't help much.  (run 50796)

At the moment, the Prex config runs on adaql5, but I will switch
it back to adaql1 because many configs run on adaql1 (e.g. ChInj2)
and it could be confusing.  I'll do this after lunch.