FYI:
Not sure what the problem was but warnevent works fine again after
recompilation (pro2003/etSpy/src)
-- ________________________________________________________________________________ Tancredi Botto, phone: +1-617-253-9204 mobile: +1-978-490-4124 research scientist MIT/Bates, 21 Manning Av Middleton MA, 01949 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^On Thu, 22 May 2003, Michael Kohl wrote:
> The shift was mostly a beam-tuning shift without data taking. > > CCR was still tuning the beam when taking over. > beam tuned with BQM optimization. > > >From time to time the BQM's had to be reset. > > At 3.30am a problem with one clystron was reported. > > CCR calls at 7am. The following (poor) tune was achieved: > Injection of 70mA, 10 min lifetime. The BQM rates are a factor of 10 > higher than last week (T=800,B=300,L=650,R=420) with slits at > (L=-4,R=8,T=1,B=-6). We decided to take some data for at least 30 minutes. > > ETSpy repeatedly reports warnings: > Warning there was no DATA in the et for this 10 sec cycle > nread 0 nphys 0 nscaler 0 nepics 0 > > this is still the case after end/start run and restart of caserver. > Warnings of Tspy remain, although caserver is running. > > Have runs #443 (25k events), #445 (50k events), #447 (40k events) with > empty target, 50Hz@30mA, trigger=elastic_een. > > > Regards, > > Michael > > >
This archive was generated by hypermail 2.1.2 : Mon Feb 24 2014 - 14:07:29 EST