<!-- Title: 12:14:19  Wed Apr  2 2003 -->
<!-- Crewchief: Prof TOF -->
<!-- Op1: &nbsp; -->
<!-- Op2: &nbsp; -->
<!-- Op3: &nbsp; -->
<!-- Op4: &nbsp; -->
<!-- Op5: &nbsp; -->
<!-- Op6: &nbsp; -->
<!-- Notes: -->
<pre>Quartly elog break</pre>


<!-- Date: Wed Apr 2 12:20:53 2003 -->
<pre>At beginning of run (160886) several TOF channels did  
not come up. All channels on Crate 1 Board 2 (ch 16-23,  
& 232-239) had no HV after repeated trials. Light in the 
back of the module was not on either. Declare this a bad 
run for TOF. 
  Turn everything off, pull module (A-4 property No 575497) 
and replace with a spare (C-8) 
Turn everything back on, it WORKS! 
Tell Ace to start a new run (160887) with TOF now GOOD. 
 
gerry, sham, denys</pre>
<!-- Author: bauerg -->


<!-- Date: Thu Apr 3 11:27:45 2003 -->
<pre>was paged at about 10:50. 
They were about to drop the store, but TOF HV would not go down, giving 
an error message about SMACS being busy. 
SMACS downstairs  did not update TOF system properly, giving 
an error message about "Unable to connect to remote server or server  
doesnt exist" 
However it was showing all channels to be at 1-5V. Despite of that,  
crates 2 and 3 were green and crate 1 blue. Again, SMACS  update 
cycle was NOT running. 
We used the emergency OFF switch on TOF HV crates to bring down the HV  
so that the beam could be dropped. 
The suspicion was that the software glitch happened because of the 
 people messing with it yesterday, resulting in miscommunication 
 between iFix and SMACS, so we restarted everything.  
This seems to have fixed the problem.</pre>
<!-- Author: Denys, Gerry -->


<!-- Date: Sun Apr 6 07:52:47 2003 -->
<pre>run 161011 
 
there something strange west average charge plot in YMON. 
I think channel 400 is too low charge. 
checking needs!</pre>
<!-- Author: jaison -->
<!-- Comment: Sun Apr  6 08;30;51 comment by...jaison -->
<pre>now fine, It maybe stats problem?</pre>


<!-- Date: Thu Apr 10 11:16:15 2003 -->
We now have the opportunity to replace the TOAD board for 
channel 122.  We will replace the middle TOAD board on the 
TOMAIN board in slot 6 of b0wcal06 with TOAD s/n 1671.  This 
was the one that had the +5 V filter capacitor replaced on 
<a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=10&frame=2&anchor=15:32:25'> 
Dec 3, 2002</a>.
<!-- Author: M Jones -->


<!-- Date: Thu Apr 10 11:43:33 2003 -->
<pre>Ooops.  TOAD 1671 is already on the detector.  We will use 
TOAD 1668 instead.  It looks like a good candidate.</pre>
<!-- Author: M Jones -->


<!-- Date: Thu Apr 10 11:51:12 2003 -->
<pre>Took TAC calibration run 0x275b9 with b0wcal01 and b0wcal02 
excluded since Nokolai was working on them.  Channel 122 
is seen to be bad in this data.</pre>
<!-- Author: M Jones -->


<!-- Date: Thu Apr 10 12:37:01 2003 -->
<pre>Channel 122 is okay now but channel 120 is bad.  I guess we 
need to request another access.  Maybe that TOAD board wasn't 
good after all.  It's not clear what the problem is...  channel 
120 is sufficiently different that the calibration code doesn't 
converge.  Perhaps it is okay but just needs some help.  I'll 
investigate later.</pre>
<!-- Author: M Jones -->


<!-- Date: Wed Apr 16 12:04:37 2003 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-164&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-164  width='300' align='top'></td><td>For future reference, here is the behavior of channel 120. I think this is symptomatic of one side of a differential clock signal not being present.  That could result from the daughter board just not being seated properly on the TOMAIN board.</a></td></tr></table>
<!-- Author: M Jones -->


<!-- Date: Sat Apr 19 22:02:01 2003 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-165&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-165  width='300' align='top'></td><td>The problem seems to be intermittent...  for TAC calibration runs 0x2771e, 0x27782 and 0x277d1 the problem is gone.  This is also consistent with the daughter board not being seated properly on the TOMAIN board.  This graph is from run 0x277d1.</a></td></tr></table>
<!-- Author: M Jones -->


<!-- Date: Wed Apr 23 06:17:33 2003 -->
<pre>TOF Heart beat problem.  Rebooted PC.  Now OK.</pre>
<!-- Author: mulhearn -->


<!-- Date: Fri Apr 25 04:04:11 2003 -->
<P> We are having problems with IFIX.  During the turning on process for SMACS, we get an error:  "Run Time Error: '6' Overflow."  Then SMACS crashes.  This happened a few times.  We restart, and find that turning on crate by crate worked (perhaps just luck).  There is still a problem with IFIX, we get the following error upstairs:  "TOF1.TOF_WRN_IGN.F_CV:  Connection NOT established with node" and about 432 like it. </P>  
<!-- Author: mulhearn and piedra -->
<!-- Comment: Fri Apr 25 04;37;25 comment by...jonatan -->
<pre>SMACS crashed again and I restarted the PC. Then I turned on
the HV crate by crate, and it has been fine for a while
until almost all the boards on crate 3 lost HV. So I went
down again and turned on the HV on this crate.</pre>


<!-- Date: Fri Apr 25 12:46:54 2003 -->
<pre>I checked the TOF HV System. Both hw and sw are   
OK and everything seems to work w/o problems.   
On the other hand there is a problem on   
the iFix server side:  
  
on vnode1/vnode2 the TOF H(-beat) button is always   
purple, when I rstarted iFix and Smacs on the TOF pc   
(pctof1) there where a bunch of warning/error   
messages in vnode1/vnode2 like:  
  
Error #1914 (0 000077c)  
TOF1.TOF_WRN_IGN.F_CV Connection NOT established with node  
  
As a result it's not possible to open/use the main   
monitoring window for TOF (i.e. clik on the D button on   
the global alarms display has no effect).  
  
It is still possible instead to turn on and off the TOF   
HV using the standard way (i.e. click on the up and down   
arrows on the HV summary) and also the hardware and   
trigger inhibits are working correctly.  
I'll send these infos to J.C. that should try to fix the   
iFix problems. 
 
</pre>
<!-- Author: Stefano -->


<!-- Date: Fri Apr 25 12:47:02 2003 -->
<pre> 
OK Now everything works also on the iFix side. 
The HB window is still purple but we checked  
comunications between vnode1 and tof1 are OK  
(so we expect the HB becomes green in a wyile). 
</pre>
<!-- Author: Stefano -->


<!-- Date: Thu May 8 19:02:23 2003 -->
<pre>at around 17:45 today the heartbeat for TOF monitoring was lost. 
 Monitoring ACE went downstairs and the TOF PC was hung. 
He waited for a few minutes then paged me. I was at home taking shower  
so I advised him to follow the instruction and try to reboot the PC by himself, 
and in the meantime I was going to get to Fermilab in case he fails. 
 
Monitoring ACE was unable to reboot the computer - he couldn't read the 
handwriting on the instructions we have and didn't even get past the password stage. 
 
At 18:20 I arrived to FNAL and rebooted the PC, and 18:25 the moniroting was 
back, but HV was down for all the channels. It's not clear weather TOF has 
tripped or something has caused the system to turn off. 
This set off the TOF trigger inhibit in the control room. 
We turned the system on from the iFix in the control room and the running 
resumed at around 18:30-18:35. 
 
It's not clear how much of the beam data was taken without TOF, but it could be 
almost an hour.</pre>
<!-- Author: Denys -->
<!-- Comment: Thu May  8 19;46;06 comment by...Denys -->
<pre>so that this situation with unreadable handwriting  doesn't happen 
in the future, I typed in and printed out the TOF PC reboot instructions.
</pre>


<!-- Date: Wed May 14 14:25:24 2003 -->
<P> Before yesterday's failed store, Bill Badgett upgraded the fer version to v2_41.  This change now causes the TOF ADMEMs to look for calibration files of form 
<PRE> 
/cdf/code-common/tof/mulhearn/calib/trigcalib.b0wcalXX.txt</P> 
</PRE> 
If these files all exist, and are successfully read, then these calibration constants are used to form the hip and mip thresholds based on: 
<PRE> 
THRESH = A + B*(GLOBAL THRESH) 
</PRE> 
It also adds a fake header to the TOTRIB readouot (until the board firmware is upgraded to provide an actual header).  This syncs the fer code with the specs for the TFTD_StorableBank.  It appears to have worked perfectly. 
</P>  
<!-- Author: mulhearn -->


<!-- Date: Wed Jun 4 06:35:44 2003 -->
<a href= 
'/cgi/elog/elog.pl?nb=2003&action=view&page=463&frame=2&anchor=00:04:46.890'> 
Channel 135 has been tripping recently</a>.  This is the CAEN 
channel that is attached to PMT channel 350 on the detector. 
So, finally, we conclude that the chronic problems with channel 
350 are somewhere downstairs.  Since we've swapped the red HV 
cable, the PMT and the CAEN channel, the only thing left is the 
connector board, cable assembly and the card in the HV patch 
pannel.
<!-- Author: M Jones -->


<!-- Date: Wed Jun 4 11:49:26 2003 -->
<pre>CH135 (aka old channel 350 (but the red cable say 354?))  
has been disabled permanently. 
New HV setup file created and loaded by default in  
Smacs: STEFANOSWAP350135-030604_....._ch135disbaled_.... </pre>
<!-- Author: Stefano -->


<!-- Date: Fri Jun 6 03:31:50 2003 -->
<PRE> 
The thresholds used by the ADMEMs are read from files located at 
 
/cdf/code-common/cdfonline/tof/mulhearn/calib/trigcalib.b0wcal0X.txt 
 
I keep an archive all files used to take data at: 
 
/cdf/code-common/cdfonline/tof/mulhearn/calib/archive/RUN/... 
 
Where RUN is the first time these files were used.   
 
The plan for calibrating the trigger is to first use all the available 
min bias data to estimate democratic thresholds.  Successive runs are used 
to further squeeze down the rate. 
 
Here are some of the key runs so far: 
 
163960 100 Hz phi fit 
164079  10 Hz phi fit 
164107 CM estimate with coarse extrapolation 
164109 back to 164079 settings 
164250 CM estimate with finer extrapolation 
 
The phi fit was my first stab at calibrating, the center of mass 
estimate is an improved algorithm.  My extrapolation was too coarse at 
first, but that has now been corrected.  I have just copied the latest 
constants which come from using the trigger data (instead of min bias) 
to squeeze down the occupancy in the louder channels.  These won't be 
added to the archive until I see what run picks them up first. 
</PRE>  
<!-- Author: mulhearn -->


<!-- Date: Sat Jun 7 15:42:51 2003 -->
<table><tr><td><a href=/elog/notebooks/tof/Sat_Jun__7_2003_154223.ps align=top><img src=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-167  align='top'></td><td>Here is the analysis of the change in calibration parameters after the painful power cut on May 30.  The parameters did not change much over the past few months.  This figure shows the change from March 3 to May 29.</a></td></tr></table>
<!-- Author: M Jones -->


<!-- Date: Sat Jun 7 15:44:16 2003 -->
<table><tr><td><a href=/elog/notebooks/tof/Sat_Jun__7_2003_154349.ps align=top><img src=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-169  align='top'></td><td>Here is the change from the last calibration before the power cut to the first calibration after the power cut.</a></td></tr></table>
<!-- Author: M Jones -->


<!-- Date: Sat Jun 7 15:49:16 2003 -->
<table><tr><td><a href=/elog/notebooks/tof/Sat_Jun__7_2003_154910.ps align=top><img src=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-171  align='top'></td><td>Here is the change since then.  Run 0x28046 was taken on May 31 and run 0x281c7 was taken on Jun 7th.  I suggest we change the accepted range for the parameters to be 0.055<gamma<0.115 and 3.5<tau<8.5 ns.</a></td></tr></table>
<!-- Author: M Jones -->
<!-- Comment: Sat Jun  7 15;50;11 comment by...M Jones -->
<pre>Oops... html screwed up there.  I suggest we change the
accepted range for the parameters to be
0.055&lt;gamma&lt;0.115 and 3.5&lt;tau&lt;8.5 ns.</pre>


<!-- Date: Sat Jun 7 18:49:22 2003 -->
<pre>I was paged because TOF channel 139 was oscillating in HV causing 
trigger inhibits every few seconds. I turned it off and took it 
out of monitoring for now, and re-enabled the TOF trigger inhibit. 
 
IMPORTANT: there is an offset of 4 between the channels in SMACS and the channels in iFIX, so ch139 downstairs shows up as channel 
135 in the control room. This seems to be the case only for the EAST channels. I have no idea how this could happen..... 
I will try to reboot everything at the end of the store. 
</pre>
<!-- Author: Gervasio -->


<!-- Date: Sun Jun 8 02:03:31 2003 -->
<pre>Rebooted PC and restarted iFIX and SMACS. The channel ambiguity between SMACS and iFIX continues for both iFIX pictures downstairs and in the control room. Double clicking on a channel on the ring display brings up the correct channel, but if the channel trips, the wrong channel changes color in the ring display. In the case of 139, it shows up as 135. Very confusing for the crew and myself.  
I turned channel 139 on and it has held voltage for the last 25 minutes, so I will leave it on and leave clear instructions to the ACEs if it should trip. The instructions are: turn it off and take it out of monitoring, and page TOF if there is any doubt.</pre>
<!-- Author: Gervasio -->
<!-- Comment: Tue Jun 10 10;37;31 comment by...Gervasio -->
<pre>I contacted Stefano about this. He says they know about this bug,
it is a SMACS problem which happens when you mask out one or more
channels, and it will be fixed during the summer.</pre>


<!-- Date: Tue Jun 10 12:37:13 2003 -->
<pre>Saved a new HV configuration file and made it the default. If  
the TOF PC or SMACS needs to be restarted, it will load 
this file. I also noted this in the instructions by the PC. 
This file leaves channels 350 and 139 out of monitoring. 
Updated the YMON reference plots for TOF in the control room.</pre>
<!-- Author: Gervasio -->


<!-- Date: Wed Jun 11 11:24:06 2003 -->
<pre>For future reference: b0dap10:/dev/ttyC109 --&gt; Cyclades port 146.</pre>
<!-- Author: M Jones -->


<!-- Date: Wed Jun 11 20:36:27 2003 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-172&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-172' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-173&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-173' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-174&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-174' width='300'></a></center>
<!-- Author: Gervasio -->
<!-- Comment: Wed Jun 11 20;42;16 comment by...Gervasio -->
<pre>The first plot is a DBANA plot for a recent calibration
BEFORE the power outage. The second and third plots are the beta,
gamma and tau distributions AFTER the power outage. 
NOTE CAREFULLY the changes in gamma and tau histogram limits and
sanity limits. Also, the tau distribution is double peaked now.
I will put these calibrations into the database and change the
histogram limits and sanity limits for gamma and tau in DBANA
shortly. I will then tag the new DBANATof version and try to 
make it the default in the Control Room.</pre>


<!-- Date: Thu Jun 12 07:49:52 2003 -->
<pre>Bringing down all the HV from iFIX due to the end of the store TOF was not responding. We went downstairs and we saw that SMACS 
was frozen, not the PC. Restarting SMACS didn't work, so we decided to reboot the PC. Following the current instructions we tried to enter the TOF bars graph 
from the Slow Control icon but it doesn't work at all. Once we opened TOF bars graph iFIX updated HV values properly</pre>
<!-- Author: Jonatan -->


<!-- Date: Thu Jun 12 09:46:41 2003 -->
<pre>As Jonatan says above, the Slow Controls button in the Hello  
public account picture in the TOF PC does not work. I changed the  
instructions by the PC so ACEs know how to open the toffinal.grf 
picture directly. 
</pre>
<!-- Author: Gervasio -->


<!-- Date: Thu Jun 12 10:26:28 2003 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-175&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-175  width='300' align='top'></td><td>Recent YMON plot with channels 350 and 139 OFF (and out of monitoring)</a></td></tr></table>
<!-- Author: Gervasio -->


<!-- Date: Fri Jun 13 09:16:02 2003 -->
<pre>This week's pager activity from Friday 6/6 to Friday 6/13 (2003): 
 
                    TOF Pager Activity 
                   ==================== 
 
BEAM DATA: 
========== 
 
date   run number   L3 accepts   lumi(nb-1)   TOF YMON      comments 
----   ----------   ----------   ----------   --------      -------- 
 
Jun-06   164274       689,015     370.62         OK         ch 350 off 
Jun-07   164302       252,207     134.82         OK         ch 350 off 
Jun-07   164303       256,793     127.49         OK         ch 350 off 
Jun-07   164304       139,451      55.35         OK         ch 350 off 
Jun-07   164305       224,923      85.47         OK         ch 350 off 
Jun-07   164306        32,621      12.82         OK         ch 350 off     
Jun-07   164307        37,010      14.07         OK         ch 350,139 off 
Jun-07   164308       312,091     109.42         OK         ch 350,139 off 
Jun-07   164310        92,955      31.35         OK         ch 350,139 off 
Jun-08   164313        35,051      18.06         OK         ch 350,139 off 
Jun-08   164352        43,930      24.82         OK         ch 350,139 off 
Jun-08   164353       984,094     432.40         OK         ch 350,139 off 
Jun-09   164354       749,361     276.53         OK         ch 350,139 off 
Jun-09   164386     1,540,649     626.32         OK         ch 350,139 off 
Jun-10   164393        46,871      16.84         OK         ch 350,139 off 
Jun-10   164451     2,070,193     839.94         OK         ch 350,139 off 
Jun-11   164509        75,082      48.23         OK         ch 350,139 off 
Jun-11   164510        32,226      18.37         OK         ch 350,139 off 
Jun-11   164511       508,693     261.64         OK         ch 350,139 off 
Jun-11   164512       182,637     112.86         OK         ch 350,139 off 
Jun-11   164517       284,990     112.30         OK         ch 350,139 off 
Jun-12   164555       418,503     159.94         OK         ch 350,139 off 
Jun-12   164625     1,016,791     431.28         OK         ch 350,139 off 
 
============================================================================= 
 
High Voltage "issues": 
====================== 
 
- Channel 139 has been disabled because its HV oscillates down every few  
  seconds. It happened twice, after a few hours of operation at nominal HV. 
 
- The downward HV oscillations made the channel turn YELLOW, which means 
  warning, however this caused a TOF trigger inhibit and Steve Hahn asked 
  that we take a look at this. 
 
- When Channel 139 trips or is disabled, the "ring" iFIX picture displays 
  channel 135 in a different color. Clicking on ch135, however, does pop up 
  the channel 135 settings picture. This mismatch is a SMACS bug which 
  Stefano and Daniele know about, it happens when one or more channels are 
  disabled, and it will be fixed this summer. 
 
-  The "Slow Controls" button in the "Hello Public Account" picture in the 
   TOF PC does not work.  
 
- When SMACS loads a setup file with more than one channel disabled, only 
  ONE channel is shown in grey, the other is shown in green in SMACS and in 
  blue in iFIX. If you activate and disactivate the channel, it will become 
  gray both in SMACS and iFIX, but it won't do it on its own.  
 
June 06: 
======== 
 
- Got pager from Stefano. 
- No beam, shot expected around noon. 
- Swapped HV cables for channels 135 and 350 in the CAEN module, now they 
  are BACK to NORMAL. Changed SMACS channel settings back to normal, 
  enabled ch135 and DISABLED chn350. Saved the settings in a file which 
  is now the default configuration file.  
- CHANNEL 350 off monitoring. 
 
 
June 07: 
======== 
 
- Paged around 18:00 because HV for channel 139 oscillated to low values every 
  few seconds and inhibited the run. Turned it off and took it out of  
  monitoring until the end of store. 
- SMACS PROBLEM: when channel 139 trips, channel 135 changes color in the 
  iFIX ring display.  
 
June 08: 
======== 
 
- Went in around 1:00 am as they ended the store. During the 1 hr. access 
  I restarted the PC but the mismatch between iFIX and SMACS continues. 
  Channel 139 held HV fine for about 30 minutes so I left it ON and gave the 
  ACE instructions in case it tripped. 
- Channel 139 HV started oscillating again early in the morning and was turned 
  off. 
 
June 09: 
======== 
 
- Data taking... 
- Stefano says he knows about the mismatch problem. It is a bug in SMACS which 
  happens when one or more channels are masked out. He and Daniele will fix 
  it during the summer. 
 
June 10: 
======== 
 
- Updated the TOF pager guide on the WEB with the Usynin YMON page, since 
  the YMON instructions were obsolete. 
- Saved a new SMACS HV configuration and made it the default. It has 
  channels 350 and 139 out of monitoring. 
- Updated YMON reference plots for TOF. 
- Data taking... 
 
June 11: 
======== 
 
- Data taking...followed by TeV studies...followed by data taking... 
 
June 12: 
======== 
 
- Data taking...end of store. 
- Paged around 7:40 am because ACEs could not turn off HV as end of store 
  approached. Jonatan rebooted the PC twice and then it worked fine. 
- Changed the HV instructions since the Slow Controls button in the Hello 
  Public Account picture downstairs does not work. 
- Quench at D0 around 22:38. Store and stack lost. 
 
June 13: 
======== 
 
- No beam, no stack. Quench recovery... 
 
</pre>
<!-- Author: Gervasio -->


<!-- Date: Fri Jun 13 11:33:12 2003 -->
<pre>We swapped channels 138 and 139 in the CAEN, crate 2, board 7 
(board channels 4,6), and swapped the channel settings in SMACS: 
 
139 had originally V0=2060, Vmax=2085 
138 had originally V0=1634, Vmax=1659. 
 
These were swapped as well to keep HV the same for the PMTs. 
Both channels are being monitored, and the new SCAMS setup file is  
 
DEFAULTSWAP139138-030613-today-b14kG-g30k_ch350_disabled.suf 
 
Also renamed a few older suf files, changing "today" with their 
actual "termination date". This is noted in the HV logbook.</pre>
<!-- Author: Gervasio and Gerry -->


<!-- Date: Fri Jun 13 19:09:02 2003 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-176&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-176  width='300' align='top'></td><td>New DBANA for TOF</a></td></tr></table>
<!-- Author: Gervasio -->
<!-- Comment: Fri Jun 13 19;10;45 comment by...Gervasio -->
<pre>I tagged the new DBANATof version as v5_0_0int1a, and it should
be part of the next code release. In the meantime, Jack Cranshaw
will make this new version the one used in the Control Room as 
soon as possible. </pre>


<!-- Date: Sat Jun 14 05:36:42 2003 -->
<pre>I checked TAC calibration run 0x2833c and it looks like we blew 
either a fuse on either the +15 or -15 on the ADMEM in b0wcal06 
slot 8.  We will need an access in which the south muon wall is 
opened to fix this.</pre>
<!-- Author: M Jones -->


<!-- Date: Sat Jun 14 07:08:13 2003 -->
<pre>The bad news continue..... 
We seem to have lost CAEN board 7 in crate 1. The 16 channels 
affected are 56-63 in the East and 272-279 in the West. 
Would like to replace crate asap, will try to find help.</pre>
<!-- Author: Gervasio -->
<!-- Comment: Sat Jun 14 07;10;29 comment by...Gervasio -->
<pre>Took affected channels out of monitoring for now. Affected runs
will be marked BAD for TOF: no need to wait for end of store
to replace board.</pre>


<!-- Date: Sat Jun 14 09:17:55 2003 -->
<pre>Replaced CAEN board 7 in crate 1: serial number 575500 replaced  
by 575517. TOF seems back to normal. Asked SciCo to integrate 
TOF at earliest convenience. 
NOTE: we are running out of spare CAEN boards. Only ONE left! 
====                </pre>
<!-- Author: Gervasio -->


<!-- Date: Sat Jun 14 22:39:29 2003 -->
<pre>Replaced admem in slot 8 of b0wcal06 (was S/N 49) with 
Admem S/N 300.  I took S/N 300 from the test stand on the 
2nd floor.  I replaced all the CAFE/deCAF cards on 300 with 
the ones that were on 049 and it was installed on the 
detector.  The TAC calibration appeared to be fine. 
 
S/N 049 blows the +15 V fuse consistently so it needs to 
be repaired.</pre>
<!-- Author: M Jones -->


<!-- Date: Sat Jun 14 22:42:44 2003 -->
<pre>While waiting for people to come up from the pit, I reassembled 
TOMAIN S/N 0x18, which used to be in b0wcal06 slot 6.  It now 
has TOAD boards 1614, 1513, 1655 installed on it. 
 
It is a good candidate for the next spare to be installed.</pre>
<!-- Author: M Jones -->


<!-- Date: Mon Jun 16 00:37:05 2003 -->
<pre>At around 0:10 we heard a heartbeat alarm in the iFIX PC. It came from TOF, so we went downstairs to check it. SMACS was frozen, 
and we couldn't close iFIX properly, so we restarted the PC. Meanwhile there was a TOF trigger inhibit (I don't know if related or not) and we had to turn on the 
TOF HV.</pre>
<!-- Author: Stan/Jonatan -->


<!-- Date: Mon Jun 16 19:37:27 2003 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-177&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-177' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-178&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-178' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-179&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-179' width='300'></a></center>
<!-- Author: Gervasio -->
<!-- Comment: Mon Jun 16 19;42;24 comment by...Gervasio -->
<pre>Study of bi-modal tau behavior for TAC. The first plot shows
clearly the two tau peaks. The second plot (bottom) shows tau
for each channel. The blue-ish channels correspond to the lower 
peak, and no clear correlation is observed. The third plot shows
the TOF geometry with PMT and channels in red for tau&lt;6 (the lower
peak), and green for tau&gt;6. They seem to be scattered randomly,
except that WCAL04 has no channel with tau&lt;6.  </pre>


<!-- Date: Tue Jun 17 11:14:29 2003 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-180&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-180  width='300' align='top'></td><td>Since channel 139 and 138 were swapped, there were no more trips. Only channel 350 is off. I will once again update the YMON reference plots in the control room to look like this.</a></td></tr></table>
<!-- Author: Gervasio -->
<!-- Comment: Tue Jun 17 19;40;14 comment by...Gervasio -->
<pre>I was too optimistic too soon. Channel 139 tripped again, so I 
changed the YMON reference plots again: we are back to both 
channels 350 and 139 off.</pre>
<!-- Date: Tue Jun 17 19:20:28 2003 -->
<pre>Channel 139 tripped again (even after swap). Might have to replace the CAEN board? 
Took 139 out of monitoring. Will save the HV setup file with 
both 350 and 139 out of monitoring. Perhaps we should consider  
swapping 138 and 139 back to original settings. 
</pre>
<!-- Author: Gervasio. -->



<!-- Date: Wed Jun 18 11:37:10 2003 -->
<pre>Swapped channels 138&lt;--&gt;139 back to their nominal settings and 
swapped cables in the back of the CAEN crates, so everything is  
back to normal: 139 is 139 and goes to PMT 139, 138 is 138 and  
goes to PMT 138.  
Saved a new default setup file with both channels 350 and 139 out  
of monitoring and made it the default. The current default file  
is: DEFAULT030618-today_b14kG_g30k_ch350_ch139_disabled.suf 
</pre>
<!-- Author: Gervasio -->


<!-- Date: Thu Jun 19 01:06:04 2003 -->
<pre>We had a trigger inhibit with TOF but It recovered by itself in few seconds. In the high voltage summary bars were yellow.</pre>
<!-- Author: Pierluigi -->


<!-- Date: Thu Jun 19 13:04:32 2003 -->
<P>New trigger thresholds applied to run 164916 to squeeze down the rate using a weeks worth of data.  This gets us down to 77Hz at 30E30.</P>
<!-- Author: mulhearn -->


<!-- Date: Thu Jun 19 22:44:53 2003 -->
<pre>TOF alarm. Reboot the TOF computer downstairs (it was frozen). 
Alarm reset. 
The TOF trigger inhibit is disabled per request of svx people</pre>
<!-- Author: Paola -->
<!-- Comment: Thu Jun 19 22;46;35 comment by...Paola -->
<pre>Now TOF trigger inhibit is enable.</pre>


<!-- Date: Fri Jun 20 09:17:32 2003 -->
<pre>BEAM DATA: 
========== 
 
date   run number   L3 accepts   lumi(nb-1)   TOF YMON      comments 
----   ----------   ----------   ----------   --------      -------- 
Jun-14   164724        20,215      11.52                    no TOF (bad board) 
Jun-14   164725       580,191     265.49                    no TOF (bad board) 
Jun-14   164727       134,986      61.08         BAD        bad chans ~135-143 
Jun-14   164729        23,040      10.56         BAD        bad chans ~135-143 
Jun-14   164733        59,674      26.61         BAD        bad chans ~135-143 
Jun-14   164734        87,870      38.06         BAD        bad chans ~135-143  
Jun-14   164735         7,207       3.75         BAD        bad chans ~135-143  
Jun-14   164736        36,472      41.14         no plot 
Jun-14   164737       563,254     223.36         BAD        bad chans ~135-143  
Jun-15   164761     1,310,218     666.08         OK         ch 350 off 
Jun-15   164762         8,613       4.85         OK         ch 350 off 
Jun-15   164772         1,564       0.90         no plot 
Jun-15   164774         1,682       1.06         no plot 
Jun-15   164775       111,212      41.45         OK         ch 350 off 
Jun-15   164776         1,978       0.95         no plot 
Jun-15   164795       256,979     145.73         OK         ch 350 off 
Jun-15   164797       845,266     372.18         OK         ch 350 off 
Jun-16   164798       415,450     170.61         OK         ch 350 off 
Jun-16   164799       180,610      66.68         OK         ch 350 off 
Jun-16   164819       573,975     262.12         OK         ch 350 off 
Jun-16   164820       771,620     309.62         OK         ch 350 off 
Jun-17   164821         2,931       1.58         no plot 
Jun-17   164822       582,813     216.48         OK         ch 350 off 
Jun-17   164844     1,792,217     781.55         OK         ch 350,139 off 
Jun-18   164870        25,047      13.12         OK         ch 350,139 off 
Jun-18   164871        25,104      13.03         OK         ch 350,139 off 
Jun-18   164872        33,762      17.13         OK         ch 350,139 off 
Jun-18   164916       903,599     421.62         OK         ch 350,139 off 
Jun-19   164952       703,976     291.58         OK         ch 350,139 off 
Jun-19   164953        60,864      24.84         OK         ch 350,139 off 
Jun-19   164956        46,909       3.89         OK         ch 350,139 off 
Jun-19   164957       192,545      16.02         OK         ch 350,139 off 
Jun-19   164958       172,608      65.66         OK         ch 350,139 off 
Jun-19   164959        25,799      10.41         OK         ch 350,139 off 
Jun-19   164960         3,310       1.74         no plot 
Jun-19   164961        13,753       5.80         OK         ch 350,139 off 
Jun-20   164962         3,934       1.95         no plot 
Jun-20   164963        57,664      21.09         OK         ch 350,139 off 
Jun-20   164989       741,718     345.35 
 
</pre>
<!-- Author: Gervasio -->


<!-- Date: Mon Jun 23 17:26:31 2003 -->
<pre>TOF PC hung.  No mouse movement, etc.  Rebooted and it looks okay.</pre>
<!-- Author: Dan Ryan -->


<!-- Date: Fri Jun 27 15:04:30 2003 -->
<pre>Replaced HV board 7 crate 2. 
Channel 139 re-enabled by default and new HV setup file 
created and loaded by default DEFAULT030626...).</pre>
<!-- Author: Stefano -->


<!-- Date: Fri Jun 27 15:07:53 2003 -->
<pre>Paged because TOF PC was hanging. 
Downstair the PC console was frozen. 
TOF PC rebooted, standard disk/fs check done 
(no errors reported). 
Checked basic HW (fans): everything OK 
 
It seems that after the last power glitch the TOF PC started  
to crash/frize more often than usual. 
 
I plan to make some detailed HW/OS test when some quiet time  
will be available (needed 3 hours to run a detailed HV/SOFT  
diagnostic test).</pre>
<!-- Author: Stefano -->