Thursday October 7.


On Thursday morning Jeremy took a substantial data set of about 3Gb HCAL+EMU
integrated data. The xdaq configuration for this set-up is now ready
for the Dubna folks who are planning to use it for their ME1/1'+HCAL
program for Thursday night and Friday afternoon.

A bug/misconfiguration in the online  run log dbase has prevented the
HardwareDumper to update the various tables which are derived from the
configTestBeam2004.xml. This got fixed and dbase tables are updated
automatically again.

Although the SP trigger has been working well for several days it
turned out on Thursday that the L1A signal never really got send back
to the TTCvx for distribution to EMU and HCAL. After this was fixed
the system was timed in again to match the timing of the EMU
scintillator trigger.

Analysis based on special SP firmware showed that the orbits are
exactly 924 BXs as configured. Adjusting the start trigger signal from
WE to WWE showed errors as expected since this the time between WWE
and WE the RF is not fully synch'ed.

Testing of the DDU/DCC continued with various higher intensity runs
mostly achieved by increasing the SP trigger rate.


Friday October 8.

On Friday, the ME1/1' folks have been running large sets of data with the
EMU+HCAL DAQ while running another parallel data stream from the DCC
for comparison. Some differences were reported and are currently
looked into. On Friday night they finished their program.

The SPRUI was tested and integrated with the EmuRUI and run for a
short while (run# 506). Work continues to resurrect the EmuCommander
(TFGUI) which was used in the May/June test as the EMU Runcontrol.

Parallel to ME1/1'+HCAL data taking the new production peripheral crate
backplane was used to replace the prototype small backplane from
UCLA. Chamber ME3/2 was hooked up into it and muons could be observed

Tomorrow, Saturday, around 9am the RPC colleagues will bring in their
electronics from the X5a.

-Frank