<!-- Title: Day shift. Sat Mar 31, 2007 -->
<!-- SciCo: Ankush Mitra -->
<!-- DAQAce: 	Gheorghe Lungu & Koji Nakamura -->
<!-- MonAce: --- -->
<!-- CO: Jaroslav Antos -->
<!-- OpManager: Sasha Pronko -->
<!-- Notes: -->
<pre>Inheriting store 5314 
Current Lumi: 117.7E30 
Stack: 105.87mA 
Stack/Rate: 15.50 mA/Hr 
Stash: ~0 
 
Owl shift had a smooth run. We will try our best.</pre>


<!-- Date: Sat Mar 31 08:26:44.519 2007 -->
<center><a href='/cgi/elog/elog.pl?nb=2007&action=view&page=-3248&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/elog.pl?nb=2007&action=view&page=-3248' width='300'></a><a href='/cgi/elog/elog.pl?nb=2007&action=view&page=-3249&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/elog.pl?nb=2007&action=view&page=-3249' width='300'></a></center>
<!-- Author: Ankush MItra (SciCo) -->
<!-- Comment: Sat Mar 31 08;29;47 comment by...Ankush Mitra (SciCo) -->
<h4>Deadtime Spike during owl shift</h4>

<p>The owl shift reported <a href=
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2007&action=view&page=268&frame=2&anchor=07:34:56.128'>
a 30% deadtime spike around 7:34am</a>.  You can see this spike in the DEADTIME time.  A bit more investigating shows the origin of the spike is due to INHIBIT-DEAD-TIME.</p>
<!-- Comment: Sat Mar 31 08;35;29 comment by...Ankush Mitra (SciCo) -->
<p>...and the origin of the INHIBIT came from a 

<a href=
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2007&action=view&page=268&frame=2&anchor=07:34:22.283'>
PSM alarm</a> which occured just before.</p>
<!-- Date: Sat Mar 31 08:28:14.538 2007 -->
<pre>Done Timeout detected in crates: 
COT_06 
autoHRR ok</pre>
<!-- Author: Jim & Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=237795' target=_top>237795</a>) -->
<!-- Comment: Sat Mar 31 09;41;44 comment by...Jim & Koji -->
again. autoHRR ok.
<!-- Date: Sat Mar 31 08:43:13.084 2007 -->
<pre>Done Timeout detected in crates: 
PCAL_05 
Shepherd was successful. autoHRR ok.</pre>
<!-- Author: Jim & Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=237795' target=_top>237795</a>) -->


<!-- Date: Sat Mar 31 09:10:21.255 2007 -->
<pre>ProcMon Error : TevMon  (Tevmon web page last updated more than 30s ago) 
Re-check ok </pre>
<!-- Author: Jim & Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=237795' target=_top>237795</a>) -->


<!-- Date: Sat Mar 31 09:15:43.902 2007 -->
<pre>Trigger Inhibit is set from the components: 
 CES HV Trip  		[086] Central EM Strip Trip 00 
BOT NW (18-23) tripped, recoverd fine. Now running. </pre>
<!-- Author: Jim & Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=237795' target=_top>237795</a>) -->
<!-- Comment: Sat Mar 31 09;17;46 comment by...Ankush Mitra (SciCo) -->
<p>Just after the inhibit there was another high deadtime warning.  A repeat case of the INHIBIT creating a downtime spike.</p>


<!-- Comment: Sat Mar 31 10;26;26 comment by...Donatella T. -->
ScalerMon now waits 60 secs after an Inhibit before checking the Deadtime. I can certainly increase this time window .
<!-- Date: Sat Mar 31 09:26:30.135 2007 -->
<pre>PSM alarm : went away too fast.</pre>
<!-- Author: Jim & Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=237795' target=_top>237795</a>) -->
<!-- Comment: Sat Mar 31 09;30;58 comment by...Ankush Mitra (SciCo) -->
<p>I just doubled checked with Steve (Cryo) about the momentary PSM alarm.  He saw the same thing.  Current guess it was a communication glitch.</p>
<!-- Date: Sat Mar 31 09:30:56.410 2007 -->
<pre>We restart ACNET at 2RR11B, because one of the fast time plot(SC) was frosen. now ok.</pre>
<!-- Author: Jim & Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=237795' target=_top>237795</a>) -->




<!-- Date: Sat Mar 31 09:42:34.176 2007 -->
<center><a href='/elog/notebooks/2007/Sat_Mar_31_2007_Day.093621.ps'><img src='/cgi/elog/elog.pl?nb=2007&action=view&page=-3253' ></a></center>
<!-- Author: Jaroslav -->
<!-- Comment: Sat Mar 31 10;06;16 comment by...Ankush Mitra (SciCo) -->
<p>One curious feature of this plot is each layer has a dead <em>spike</em> at phi~44, phi=70. Is this coincident or is this pointing to something else ?</p>
<!-- Date: Sat Mar 31 09:44:14.661 2007 -->
Done Timeout detected in crates: 
COT_03 
auto HRR. ok 
<!-- Author: Jim & Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=237795' target=_top>237795</a>) -->


<!-- Date: Sat Mar 31 09:45:45.925 2007 -->
<table><tr><td><a href=/elog/notebooks/2007/Sat_Mar_31_2007_Day.094525.ps align=top><img src=/cgi/elog/elog.pl?nb=2007&action=view&page=-3255  align='top'></a></td><td>more dead channells than in reference (also for previous plot)</td></tr></table>
<!-- Author: Jaroslav -->


<!-- Date: Sat Mar 31 10:04:14.711 2007 -->
*** Node b0pcal01 in Error *** 
Heap is Corrupt 
Shepherd was successful. now ok
<!-- Author: Jim & Koji  :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=237795' target=_top>237795</a>) -->


<!-- Date: Sat Mar 31 10:07:23.121 2007 -->
Run <A HREF=/java/cdfdb/servlet/RunSummary?RUN_NUMBER=237795>237795</A>
muons: <tt>There have been &nbsp;dead channels in BSU west and east and in BMU west in comparison with reference see plots in elog. </tt>
<!-- Author: Consumer Operator( Jaroslav Antos) -->


<!-- Date: Sat Mar 31 10:07:24.910 2007 -->
Run <A HREF=/java/cdfdb/servlet/RunSummary?RUN_NUMBER=237795>237795</A>
trigger: <tt>problem in trigmon xcess trigger efficiency. But was fixed latter</tt>
<!-- Author: Consumer Operator( Jaroslav Antos) -->


<!-- Date: Sat Mar 31 10:07:26.461 2007 -->
Run <A HREF=/java/cdfdb/servlet/RunSummary?RUN_NUMBER=237795>237795</A>
general: <tt>OK. some caution about BMU and BSU. Seen there more dead channels. See relevant entry in elog</tt>
<!-- Author: Consumer Operator( Jaroslav Antos) -->


<!-- Date: Sat Mar 31 10:07:27.158 2007 -->
Run <A HREF=/java/cdfdb/servlet/RunSummary?RUN_NUMBER=237795>237795</A>
muons: <tt>There have been &nbsp;dead channels in BSU west and east and in BMU west in comparison with reference see plots in elog. </tt>
<!-- Author: Consumer Operator( Jaroslav Antos) -->


<!-- Date: Sat Mar 31 10:07:28.916 2007 -->
Run <A HREF=/java/cdfdb/servlet/RunSummary?RUN_NUMBER=237795>237795</A>
trigger: <tt>problem in trigmon xcess trigger efficiency. But was fixed latter</tt>
<!-- Author: Consumer Operator( Jaroslav Antos) -->


<!-- Date: Sat Mar 31 10:07:29.370 2007 -->
Run <A HREF=/java/cdfdb/servlet/RunSummary?RUN_NUMBER=237795>237795</A>
general: <tt>OK. some caution about BMU and BSU. Seen there more dead channels. See relevant entry in elog</tt>
<!-- Author: Consumer Operator( Jaroslav Antos) -->


<!-- Date: Sat Mar 31 10:07:30.562 2007 -->
Run <A HREF=/java/cdfdb/servlet/RunSummary?RUN_NUMBER=237795>237795</A>
muons: <tt>There have been &nbsp;dead channels in BSU west and east and in BMU west in comparison with reference see plots in elog. </tt>
<!-- Author: Consumer Operator( Jaroslav Antos) -->


<!-- Date: Sat Mar 31 10:07:31.701 2007 -->
Run <A HREF=/java/cdfdb/servlet/RunSummary?RUN_NUMBER=237795>237795</A>
trigger: <tt>problem in trigmon xcess trigger efficiency. But was fixed latter</tt>
<!-- Author: Consumer Operator( Jaroslav Antos) -->


<!-- Date: Sat Mar 31 10:07:36.264 2007 -->
Run <A HREF=/java/cdfdb/servlet/RunSummary?RUN_NUMBER=237795>237795</A>
general: <tt>OK. some caution about BMU and BSU. Seen there more dead channels. See relevant entry in elog</tt>
<!-- Author: Consumer Operator( Jaroslav Antos) -->




<!-- Date: Sat Mar 31 10:42:36.162 2007 -->
<pre>PSM alarm (1RR06C_1) comunication error : went away by itself.</pre>
<!-- Author: Jim & Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=237795' target=_top>237795</a>) -->


<!-- Date: Sat Mar 31 12:02:26.088 2007 -->
<pre>evb2b turned red : HRR  ok.  
</pre>
<!-- Author: Jim & Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=237795' target=_top>237795</a>) -->

<!-- Date: Sat Mar 31 12:29:04.363 2007 -->
Run <A HREF=/java/cdfdb/servlet/RunSummary?RUN_NUMBER=237795>237795</A>
general: <tt>everything looks OK except potential problems mentioned in previous check persist</tt>
<!-- Author: Consumer Operator( Jaroslav Antos) -->



<!-- Date: Sat Mar 31 12:35:08.257 2007 -->
<pre>CSP BSU HV alarm : without trigger inhibit. YMon plots also good.  
We will restart the YMon to check.</pre>
<!-- Author: Jim & Koji  :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=237795' target=_top>237795</a>) -->
<!-- Comment: Sat Mar 31 13;04;19 comment by...Ankush Mitra (SciCo) -->
<p>After ~30mins of restarting YMON, we looked at the CSP and BSU occupancy plots and they look normal.  So it appears this is a communication problem.  But we have still paged the expert (Akram Artikov) who is coming in now.</p>
<!-- Comment: Sat Mar 31 14;05;09 comment by...Akram -->
Restored communication for CSP, but I think it is unstable.
Monitoring problem for CCU's SW for BSU. Both occupancy OK as usually.
 Real HV  is OK, but ace monitor still (will?) shows red HV due wrong communication between muon scintillator PC and CCU's. Unfortunately I cannot use power cycling to restore of  communication because we still have -5V problem.
<!-- Comment: Sat Mar 31 14;13;30 comment by...Akram -->
Situation for now: BSU communication restored, wrong HV monitoring for CCU TW&BW for CSP.
<!-- Date: Sat Mar 31 12:59:56.183 2007 -->
<pre>Trigger Inhibit is set from the components: 
 TOF HV  		[132] Time of Flight High Voltage from iFix 
recoverd by itself. now it is ok.</pre>
<!-- Author: Jim &Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=237795' target=_top>237795</a>) -->
<!-- Comment: Sat Mar 31 14;07;31 comment by...Jim & Koji -->
again! recoverd by itself. now good.

<!-- Date: Sat Mar 31 13:08:49.841 2007 -->
CMX HV alarm (NE 18 19) : recovered. now it's ok.
<!-- Author: Jim & Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=237795' target=_top>237795</a>) -->
<!-- Comment: Sat Mar 31 13;35;31 comment by...Jim & Koji -->
again! recoverd. it looks ok now.
<!-- Comment: Sat Mar 31 13;40;16 comment by...Jim & Koji -->
again! recovered.
<!-- Comment: Sat Mar 31 13;47;37 comment by...Jim & Koji -->
again 2 times. the second time was on ramping up. recovered. Now ok.
<!-- Comment: Sat Mar 31 13;55;53 comment by...Jim & Koji -->
again! : recoverd. Now ok.
<!-- Comment: Sat Mar 31 14;09;52 comment by...Jim & Koji -->
again ! recovered. it's ok now.
<!-- Comment: Sat Mar 31 14;15;26 comment by...Jim & Koji -->
again ! recovered. it's ok now.
<!-- Comment: Sat Mar 31 14;43;23 comment by...Jim & Koji -->
again ! recovered it looks ok now.
<!-- Comment: Sat Mar 31 15;06;06 comment by...Jim & Koji -->
again!! recovered. now ok.
<!-- Comment: Sat Mar 31 15;21;27 comment by...Jim & Koji -->
again !! recovered. it looks good now.
<!-- Comment: Sat Mar 31 15;30;32 comment by...Jim & Koji -->
again... recovered. now ok.
<!-- Comment: Sat Mar 31 15;40;30 comment by...Jim & Koji -->
agai. recovered. now ok.
<!-- Date: Sat Mar 31 13:09:05.290 2007 -->
<table border=0><td><tr><td bgcolor=#e0e030><pre>Dear shift crew, 
 
Your OpsMan, Sasha, will be unavailable today between 6pm-11pm. 
Please call Maxim Goncharov if something happens during this  
time period and you need to involve/consult the OpsMan. Maxim's 
cell phone number is on the white board. After 11pm, I will  
return back to my OpsMan duties. 
 
Please propagate this information to the evening shift crew. 
 
Thanks, 
Sasha.</pre></td></tr></td></table>
<!-- Author: Sasha Pronko (OpsMan) -->




<!-- Date: Sat Mar 31 13:42:42.091 2007 -->
<pre>Trigger Inhibit is set from the components: 
 SVX HV  		[128] Silicon Tracker High Voltage from iFix 
 
Crate 6 cominucation failure, auto hockerization ok.  
Powered on now taking data.</pre>
<!-- Author: Jim & Koji  :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=237795' target=_top>237795</a>) -->




<!-- Date: Sat Mar 31 13:59:38.835 2007 -->
<center><a href='/cgi/elog/elog.pl?nb=2007&action=view&page=-3256&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/elog.pl?nb=2007&action=view&page=-3256' width='300'></a><a href='/cgi/elog/elog.pl?nb=2007&action=view&page=-3257&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/elog.pl?nb=2007&action=view&page=-3257' width='300'></a></center>
<!-- Author: Jim/Koji -->
<!-- Comment: Sat Mar 31 14;01;08 comment by...Jim/Koji -->
<pre>the plots above are the humidity in the NE miniskirt region of the detector. Left: last 24hrs. Right: last 12 days. As you can see the humidity is going up down there and this might cause the repeated CMX HV trips for wedges 18-19.</pre>

<!-- Comment: Sat Mar 31 14;02;42 comment by...Ankush Mitra (SciCo) -->
<p>Have now paged CMX....now waiting for they wisdom.</p>







<!-- Comment: Sat Mar 31 14;27;09 comment by...Ankush Mitra (SciCo) -->
<p>Just paged them again in case the first page was lost.</p>
<!-- Comment: Sat Mar 31 14;49;10 comment by...Ankush Mitra (SciCo) -->
<p>In the end, I called Dale directly (sorry).  Dale suggested we just continue recovering the trips. Hopefully the collision hall humidity will drop in the evening.</p>
<!-- Comment: Sat Mar 31 14;54;25 comment by...Dale Stentz -->
As the humidity is pass 45% on the NE side I expect problems will eventually occur with NE 20 (one trip should set it off).  NE 18-19  is bad in part that it draws more current via sections that would be hooked up to NE 20.  <br><br>As it has been recovering I've suggest that we wait a bit longer before taking action.  Normally however, the pace of one trip every 10-20 minute is much too often but the alterative it to run with CMX bad so we have to weight the pros and cons.<br><br>
Note that I tried John (the pager carrier) cell phone and came up short as well.
<!-- Comment: Sat Mar 31 15;57;55 comment by...Dale Stentz -->
As of right now, we and the shift crew are willing put up with the trips.  Since the wedge has been reseting ok, I've adjusted the settings so that the voltage on the anode (the part that isn't tripping) ramps up faster.  We got it so that the dead time is about 30 seconds while resetting the trip.
<!-- Date: Sat Mar 31 14:18:16.072 2007 -->
<pre>shepherding b0pcal00 because of trigmon error.</pre>
<!-- Author: Jim & Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=237795' target=_top>237795</a>) -->
<!-- Comment: Sat Mar 31 14;21;24 comment by...Ankush Mitra (SciCo) -->
<p>Carla Grosso-Pilcher (L1 Trigger) called about a low level error in the ADMEM-DCAS seen in trigMon.  She suggested a shpeard of PCAL00 may help.  As a CMX trip had occured, we took advantage and sheparded PCAL00.  However it appears the error is persistent.</p>



<!-- Comment: Sat Mar 31 14;37;34 comment by...Ankush Mitra (SciCo) -->
<p>This plot has also been added to the CO fix list as it is now a known problem.</p>
<!-- Date: Sat Mar 31 14:23:24.369 2007 -->
<h4>L00 DOIM Pinky</h4> 
 
<p>L00 5V DOIM B1W2 gave a PINKY and is now reading 0.0</p>
<!-- Author: Ankush Mitra (SciCo) :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=237795' target=_top>237795</a>) -->
<!-- Comment: Sat Mar 31 14;26;11 comment by...Ankush Mitra (ex Silicon SPL) -->
<p>The 0.0 current reading for the 5V DOIM is likely to be a false reading.  If it were true, the wedge would have tripped. So this is likely to be a communication error.  But I will investigate further.</p>





<!-- Comment: Sat Mar 31 15;24;49 comment by...Ankush Mitra (with Silicon hat on) -->
<p>After checking the SVXMon strip plots, the data from L00 B1W2 ladders are fine.  So this is a corrupted readback problem from CAEN PS 12.  This crate will need to be hockerised during at a convenient time.</p>
<!-- Date: Sat Mar 31 14:32:01.159 2007 -->
<table><tr><td><a href=/elog/notebooks/2007/Sat_Mar_31_2007_Day.143149.ps align=top><img src=/cgi/elog/elog.pl?nb=2007&action=view&page=-3259  align='top'></a></td><td>according to instructions is OK</td></tr></table>
<!-- Author: Jaroslav -->




<!-- Date: Sat Mar 31 14:44:11.294 2007 -->
<table><tr><td><a href=/elog/notebooks/2007/Sat_Mar_31_2007_Day.144403.ps align=top><img src=/cgi/elog/elog.pl?nb=2007&action=view&page=-3262  align='top'></a></td><td>may be just low statistic problem?</td></tr></table>
<!-- Author: Jaroslav -->



<!-- Date: Sat Mar 31 14:50:56.225 2007 -->
<h4>iFIX History for today lost</h4> 
 
<p>Steve Gordon (Cryo-tech) call to say he had a problem with the iFIX history.  Unforutanly the only way this was restarted was to start froms scratch which means history plots from midnight to now have been lost.</p>
<!-- Author: Ankush Mitra (SciCo) :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=237795' target=_top>237795</a>) -->



<!-- Date: Sat Mar 31 15:02:31.397 2007 -->
<table><tr><td><a href=/cgi/elog/elog.pl?nb=2007&action=view&page=-3263&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/elog.pl?nb=2007&action=view&page=-3263  width='300' align='top'></a></td><td><h4>For attention of next shift crew</h4> 
 
<P>If your trigMon ADMEM-DCAS plot looks like this, this is a known problem to the L2-Cal people.</p> </td></tr></table>
<!-- Author: Ankush Mitra (SciCo) -->


<!-- Date: Sat Mar 31 15:16:13.676 2007 -->
Run <A HREF=/java/cdfdb/servlet/RunSummary?RUN_NUMBER=237795>237795</A>
general: <tt>OK, no new problems</tt>
<!-- Author: Consumer Operator( Jaroslav Antos) -->






<!-- Date: Sat Mar 31 15:32:29.399 2007 -->
<h4>A word from the Run Co-Ordinator</h3> 
 
<pre> 
Saturday Afternoon Quick Checkup:   At the start of our first set of transfers to the Recycler this morning, A:IKIK failed.  Experts were called in and found a shorted power supply cable.   This resulted in about three hours of stacking downtime.   Concurrent with A:IKIK downtime was another H- Source ion gauge trip, that required a dome access and resulted in about 45 minutes of downtime.  The I- Source is ready to go, if our H- problems worsen over the weekend.  The stacking downtime puts us behind our original stacking projections, so we will probably run the store until at least midnight.   Tevatron luminosity decay fits show that the luminosity still should be around 40pb-1 at that time.  Another piece to the puzzle is that we will be modifying the store termination times in order to try to align the stores so that we can end a store at 6am-7am on Tuesday to accommodate the upcoming long CDF access.  This may limit our store duration flexibility over the weekend, and will get complicated if we lose stores at the wrong times.  We will run out projection plots again by mid-evening and post the end of store details at that time. 
 - B Drendel   
</pre>  
<!-- Author: Ankush Mitra (SciCo) :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=237795' target=_top>237795</a>) -->



<!-- Date: Sat Mar 31 15:46:19.324 2007 -->
<h4>Run declared bad by PhysMon ?</h4> 
 
<p>Apparently PhysMon believes this run is bad because the W cross section is off.  I beg to differ.</p>
<!-- Author: Ankush Mitra (SciCo) :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=237795' target=_top>237795</a>) -->


<!-- Date: Sat Mar 31 15:50:13.153 2007 -->
PSM alarm. recovered by it self.
<!-- Author: Jim & Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=237795' target=_top>237795</a>) -->


<!-- Date: Sat Mar 31 15:54:29.736 2007 -->
<h4>8% deadtime at Lumi=62E30</h4> 
 
<p>Out of curiousity I was looking at the ScalarMon deadtime.  It is reporting ~8% deadtime while the lumi is 62E30.  I seem to remember it was lower.</p>
<!-- Author: Ankush Mitra (SciCo) :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=237795' target=_top>237795</a>) -->
<!-- Comment: Sat Mar 31 16;05;03 comment by...Michal (another ACE) -->
If I remember correctly at 65 some triggers get in and deadtime jumps to around 10%. Another such place is around lumi 50.
<!-- Date: Sat Mar 31 15:55:08.949 2007 -->
<TABLE BORDER=2 CELLSPACING=1 CELLPADDING=1 BGCOLOR=WHITE>
<TR BGCOLOR=YELLOW><TH>RunNumber</TH>
<TH>DataType</TH>
<TH>PhysicsTable</TH>
<TH>Begin</TH>
<TH>End</TH>
<TH>LiveTime</TH>
<TH>L3Accepts</TH>
<TH>DelivLumi nb<SUP>-1</SUP></TH>
<TH>LiveLumi nb<SUP>-1</SUP></TH>
<TH>GR</TH>
<TH>SC</TH>
<TH>RC</TH></TR>
<TR><TD><A HREF=/java/cdfdb/servlet/RunSummary?RUN=237795 target=_runSummary>237795</A> x3A0E3</TD>
<TD>BEAM</TD>
<TD><FONT SIZE=-1>PHYSICS_4_01 [5,866,678]</FONT></TD>
<TD ALIGN=CENTER>04:28:43</TD>
<TD ALIGN=CENTER></TD>
<TD ALIGN=CENTER>10:11:27</TD>
<TD ALIGN=RIGHT>   4,552,090</TD>   <TD ALIGN=RIGHT>  4,183.85</TD>
<TD ALIGN=RIGHT>  3,729.19</TD>
<TD ALIGN=CENTER></TD>
<TD ALIGN=CENTER></TD>
<TD ALIGN=CENTER>1</TD></TR>

<TR><TD>Totals</TD>
<TD> </TD>
<TD> </TD>
<TD> </TD>
<TD>15:55:01</TD>
<TD ALIGN=CENTER>10:11:27</TD>
<TD ALIGN=RIGHT>     4,552,090</TD> <TD ALIGN=RIGHT>  4,183.85</TD>
<TD ALIGN=RIGHT>  3,729.19</TD>
<TD> </TD>
<TD> </TD>
<TD> </TD></TR>

</TABLE>
<!-- Author: End of Shift Report -->


<!-- Date: Sat Mar 31 15:55:08.738 2007 -->
<TABLE BORDER=2 CELLSPACING=1 CELLPADDING=1 BGCOLOR=WHITE>
<TR BGCOLOR=YELLOW><TH>RunNumber</TH>
<TH>DataType</TH>
<TH>PhysicsTable</TH>
<TH>Begin</TH>
<TH>End</TH>
<TH>LiveTime</TH>
<TH>L3Accepts</TH>
<TH>DelivLumi nb<SUP>-1</SUP></TH>
<TH>LiveLumi nb<SUP>-1</SUP></TH>
<TH>GR</TH>
<TH>SC</TH>
<TH>RC</TH></TR>
<TR><TD><A HREF=/java/cdfdb/servlet/RunSummary?RUN=237795 target=_runSummary>237795</A> x3A0E3</TD>
<TD>BEAM</TD>
<TD><FONT SIZE=-1>PHYSICS_4_01 [5,866,678]</FONT></TD>
<TD ALIGN=CENTER>04:28:43</TD>
<TD ALIGN=CENTER></TD>
<TD ALIGN=CENTER>10:11:27</TD>
<TD ALIGN=RIGHT>   4,552,090</TD>   <TD ALIGN=RIGHT>  4,183.85</TD>
<TD ALIGN=RIGHT>  3,729.19</TD>
<TD ALIGN=CENTER></TD>
<TD ALIGN=CENTER></TD>
<TD ALIGN=CENTER>1</TD></TR>

<TR><TD>Totals</TD>
<TD> </TD>
<TD> </TD>
<TD> </TD>
<TD>15:55:01</TD>
<TD ALIGN=CENTER>10:11:27</TD>
<TD ALIGN=RIGHT>     4,552,090</TD> <TD ALIGN=RIGHT>  4,183.85</TD>
<TD ALIGN=RIGHT>  3,729.19</TD>
<TD> </TD>
<TD> </TD>
<TD> </TD></TR>

</TABLE>
<!-- Author: End of Shift Report -->



<!-- Date: Sat Mar 31 15:55:30.371 2007 -->
<pre>Done Timeout detected in crates: 
HADRON_TIMING_00 
 
auto HRR ok.</pre>
<!-- Author: Jim & Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=237795' target=_top>237795</a>) -->



<!-- Date: Sat Mar 31 15:59:45.200 2007 -->
<font color=red>Shift Summary: </font><pre>---------------------------------------------------------- 
 
* CES Trip  
  --&gt; ACE qickly recovered trip  
 
 
* BSU & CSP gave alarms in iFIX global summary page but did not pulled a 
trigger inihit.  YMon was restarted to check if the alarm was real. 
Akram Artikov (BSU/CSP expert) came in and confirmed it was a 
communication problem.  He wored on clearing the errors but was not 
compeltely sucessful.  
 
 
* CMX trips : During the shift, CMX Wedged NE 18-19 have repeatidly 
tripped. This appears to be correlated with the increasing collision 
hall humidity.  The trips are very quick to recover and so have not 
affected our efficiency. Dale Stenz (CMX expert) came in and adjusted 
the ramp rate. 
 
 
 
 
13:41 Process System Tech (Steve Gordon) suffered a History crash.  So it had 
to be restarted. Unfortunatly history plots from midnight-14:52 have 
been lost. 
 
 
 
13:42 Si CAEN PS 6 had a communication failure.  The Auto-Hocker did 
its job.   
 
 
A low level error in the ADMEM-DCAS is present in trigMon.  This 
occured after the L2 Cal work.  Calra called and suggested sheparding 
PCAL00.  This was tried, but the error is still present. 
 
 
 
Two momentary PSM alarms..believed to be communication glitches. 
 
 
The same run from the owl shift is running :-) 
 
 
----------------------------------------------------------</pre> 
<br><b>End of Shift Numbers</b>
<table><tr><td width=60% align=left>
<b>CDF Run II <p></b>                       
<pre>
Runs                   237795 
Delivered Luminosity   2372.8 nb-1  
Acquired Luminosity    	2123.5 nb-1  
Efficiency             	 89.5
   
</td></tr></table></pre>
<!-- Author: Ankush Mitra (SciCo) -->



<!-- Date: Sat Mar 31 16:11:33.922 2007 -->
CMP HV trip in channel Bottom A3 and D3, solved
<!-- Author: Andy and Guido :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=237795' target=_top>237795</a>) -->