From: Frank Geurts (geurts_at_rice.edu)
Date: Fri Mar 14 2003 - 13:23:40 EST
dear tof experts -- i analyzed the log file of the test run this
morning. Everything looks just fine and the pedAsPhys run nicely process
~9600 tokens filling our localmon data files. But, all of a sudden we
are not getting any LAMs generate by the LAMG anymore. Assuming the LAMG
works properly (it does so for the first few 1000s of events) and
responses to EVENT this typically means that the local logic is not
pulsed anymore by the TCD.
Along the same line I see the Bira generate LAMs but when teh Bira tries
to read out the word it only reads 0s (for token, daqcmd and trg),
although strangly enough the unused part (remember: the bira provides us
with a bigger word than the TCD "delivers") remains to be 0xF ...
While receiving all these empty words from the TCD the local DAQ busy
remains CLEARED ... the tofpdaq software sees no reason to go busy
because there's no (pulsed) data available. So, the fact the TCD reports
100% back to STAR DAQ does not make sense. During the first 9000 events
this TOF busy (reported by the TCD) starts at about 40% and climbs up to
some ~80%.
I suspect the TCD has a problem. Does anyone know of any changes that
have been made to it recently?
-frank
Frank Geurts wrote:
>
>
> Tonko A. Ljubicic wrote:
>
>>
>>
>> I was just checking and I see the TOF BUSY (the _actual_ BUSY at the TCD)
>> go to 100% after few hundred events without any messages in det.log
>> running pedAsPhys (with TPC).
>>
>> Everything else looks peachy... System continues to respond to
>> start/stop etc. Don't know... Hardware?
>>
>> Did TOF run OK after Wednesday's access at all?
>>
>
> Hi Tonko -- thanks for checking. AFAIK tof ran after the Wed-access.
> We'll look into this 100% busy issue. Maybe later today a short test run
> with maximum debugging log level on our side will be requested.
>
> more later ...
>
> -f.
>
>
>
>
This archive was generated by hypermail 2.1.4 : Thu Jul 24 2003 - 00:39:37 EDT