<!-- Title: 10:30:40  Mon Mar 28 2005 -->
<!-- Crewchief: Ankush(pops si cherry) -->
<!-- Op1: Rong-Shyang LU (SPL) -->
<!-- Op2: &nbsp; -->
<!-- Op3: &nbsp; -->
<!-- Op4: &nbsp; -->
<!-- Op5: &nbsp; -->
<!-- Op6: &nbsp; -->
<!-- Notes: -->
<pre>...hmmm...what will happen this week.....</pre>


<!-- Date: Mon Mar 28 10:57:31 2005 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6339&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6339  width='300' align='top'></a></td><td>Current history of SB0W0L2 AVDD.</td></tr></table>
<!-- Author: Ankush and Ron -->

<!-- Date: Mon Mar 28 10:59:23 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W0L2 
<li>problem n: 1 
<li>Status: needs_observation
<li>Type: AVDD2
<li>Action: IMON_limits
<li>entered by: rong 
<li>description is: change IMON limits<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>780</td><td>800</td></tr>
<tr><td><b>Lower</b></td><td>770</td><td>760</td></tr>
<tr><td><b>Upper</b></td><td>800</td><td>810</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B0W0&layer=L2">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Mon Mar 28 11:22:02 2005 -->
<pre>..oopos forgot to click copy to e-log option. 
 
IMON limits for SB0W0L2 have been redefined 
 
|         | Old | Current | 
|Nominal  | 800 | 800     | 
|Low End  | 760 | 760     | 
|High End | 810 | 825     | </pre>
<!-- Author: Ankush -->


<!-- Date: Mon Mar 28 12:53:25 2005 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6340&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6340  width='300' align='top'></a></td><td>e132 bit error in Run 195780</td></tr></table>
<!-- Author: boveia -->

<!-- Date: Mon Mar 28 12:54:15 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W3L2 
<li>problem n: 1136 
<li>Status: needs_observation
<li>Type: Chip_bit_error
<li>Action: Monitoring
<li>entered by: boveia 
<li>description is: Bit 0 error back for 80% of events in Run 195780.<a href= 'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=242&frame=2&anchor=12:53:25'> e-log</a>.  
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B1W3&layer=L2">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Mon Mar 28 18:50:13 2005 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6341&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6341  width='300' align='top'></a></td><td>Kicker prefires split up per Kicker, so main trouble maker is AAK1 followed by PAK3 </td></tr></table>
<!-- Author: Marcel -->


<!-- Date: Mon Mar 28 18:51:59 2005 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6342&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6342  width='300' align='top'></a></td><td>Kicker prefires as a function of hours into the store. If it is happens at flattop, it is defined as 0. So there is tendency for these things to happen at the begin of the store. </td></tr></table>
<!-- Author: Marcel -->


<!-- Date: Mon Mar 28 18:52:39 2005 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6343&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6343' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6344&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6344' width='300'></a></center>
<!-- Author: Marcel -->
<!-- Comment: Mon Mar 28 18;54;12 comment by...Marcel -->
Kicker prefires depending on the month, left plot for all kicker prefires from 2001-2005, right one only for 2003-2005. Preference for spring is clear, anyone knows why ?



<!-- Date: Mon Mar 28 18:55:30 2005 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6345&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6345  width='300' align='top'></a></td><td>Kicker prefires vs on the date of incident. The clustering in 2004 and 2005 is nicely visible.  
</td></tr></table>
<!-- Author: Marcel -->


<!-- Date: Mon Mar 28 19:03:32 2005 -->
<h2> A short Kicker prefire study</h2> 
<p> 
I got a lot of data from Dean Still ( Tevatron Expert) this afternoon about all the kicker prefires they had. Plots extracted from the data is shown above. </p> 
A few comments: 
<p> 
There are a few incidents, where there was a power loss in A0, a malfunction in the whole system and a possible lightning induced prefire. I have included those anyway. For the curious, these events are 
<pre> 
27.07.2002 possible lightning induced 
04.09.2002 Faulty cable cause unsynced firing 
20.12.2003 A0 power failure 
</pre> 
anyway, some preliminary conclusions: 
<ul> 
<li> There is a trend for these things to happen at the beginning of the store and even at flattop, I ll add a flatop vs lowbeta plot later. </li> 
<li>Kickers love the spring, may be it is geese induced ? </li> 
<li>The clustering especially for 2004 and 2005 is very obvious</li> 
</ul> 
Probably we can learn a lot more from this data. For the curious, from 18.12.2003 onwards, A48 was in use.  
</p>
<!-- Author: Marcel -->


<!-- Date: Mon Mar 28 19:12:17 2005 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6346&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6346  width='300' align='top'></a></td><td>Flattop vs 150 GeV vs Low Beta</td></tr></table>
<!-- Author: Marcel -->


<!-- Date: Tue Mar 29 08:01:12 2005 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6347&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6348  width='300' align='top'></a></td><td>Store 4063 just went in...the SVTSPYMon plot look good</td></tr></table>
<!-- Author: Ankush -->


<!-- Date: Tue Mar 29 09:29:20 2005 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6349&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6350  width='300' align='top'></a></td><td>snapshot of one SVX VRB status</td></tr></table>
<!-- Author: Rong -->
<!-- Comment: Tue Mar 29 09;32;09 comment by...Rong -->
<pre>Don't know if it's related. We were told by Frank that the reformatter errors are higher than earlier and part of them come from SIXD bank. From the limit information, Marcel and Frank can't pinpoint what and which crate cause the problem. I saw a few error message in SVXMon complained about 'VRB out of sync' for a few events and saw also the Event ID error in many VRB crate of SVX.
Not sure if it's relavent, just post it up.</pre>

<!-- Comment: Tue Mar 29 10;58;14 comment by...Marcel -->
A cleanup of the EVB did the trick .... something went bad...


<!-- Date: Tue Mar 29 15:56:48 2005 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6351&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6351' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6352&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6352' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6353&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6353' width='300'></a></center>
<!-- Author: Marcel -->
<!-- Comment: Tue Mar 29 15;58;15 comment by...Marcel -->
B0PAGC vs AGIGIX for stores 4059 4044 and 4046. There is clearly a dependence between the variable sin the gap and particles flying out of the gap. However there is no 100 % correlation.


<!-- Date: Tue Mar 29 20:44:06 2005 -->
<h3> On reformatter Errors </h3> 
I had a look at the recent reformatter error rate. The problem seems to come from b0eb17,(b0svx00), because the fib ID's that I can see, are all either e080 or e0a0. The interesting fact is though, that it complains about the VRB header..., stating the bytecount would be wrong betwenn the total bytecount and the sum of of VRB header + data. Looking at the errors, the failure mode is always the same 
<pre> 
      0880      0980      0100 
      08D0      09D0      0100 
      0BF8      0CF8      0100 
      0980      0A80      0100 
      0AB8      0BB8      0100 
      0A80      0B80      0100 
      0920      0A20      0100 
      0710      0810      0100 
      0AE0      0BE0      0100 
      0840      0940      0100 
      0A78      0B78      0100 
      0B58      0C58      0100 
      0830      0930      0100 
      09D0      0AD0      0100 
      0730      0830      0100 
      0D38      0E38      0100 
      0368      0468      0100 
      06B8      07B8      0100 
      09E8      0AE8      0100 
      05F8      06F8      0100 
      0600      0700      0100 
      0940      0A40      0100 
      0DB8      0EB8      0100 
      0A40      0B40      0100 
      0B18      0C18      0100 
      0A30      0B30      0100 
      0708      0808      0100 
      07B8      08B8      0100 
      0758      0858      0100 
</pre> 
The first row shows the total bytecount, the second the sum from data +  VRB header, which by construction, should be the same.  
However, they differ by exactly 0x100 which corresponds to a bit 9 low in the transaction.<br> 
As far as I know, the EVB checks the data while reading them out for header consistency, so one would assume, this happens between EVB and L3. We can run the ladders tomorrow and see, if we get corrupted VRB headers. If so, we swap the VRB, if not, the problem could be the EVN/SCRAMNET/L3. 
  
<!-- Author: Marcel -->
<!-- Comment: Sun Apr  3 09;45;53 comment by...SCN -->
This is an 
<a href=
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2002&action=view&page=735&frame=2&anchor=20:53:12'>
old problem</a>, deemed to be in the EVB side of things (ATM data transmission).  EVB people know about it.  For more info, follow link.
<!-- Date: Tue Mar 29 23:16:37 2005 -->
<h3>SB2W0L2</h3> 
 
<p>SB2W0L2 kept tripping.  The ACEs tried to put onto STANDBY 3 time with no success. It was reporting undervoltage </p> 
 
Under Rong's instruction the following was tried: 
<ul> 
 <li>Put the ladder onto STANDBY..no success</li> 
 <li>Hockerize the crate...no success</li> 
 <li>Power the whole wedge off and on...no sucesss</li> 
</ul> 
  
<p>In the end Rong removed the ladder from the database</p> 
 
<em>...so much for my first call....</em>
<!-- Author: Ankush -->
<!-- Comment: Tue Mar 29 23;31;42 comment by...Rong -->
It's actually <h3>SB2W0L3</h3>.


<!-- Comment: Tue Mar 29 23;57;23 comment by...Ankush -->
<p>...just one worrying thing....</p>

<p> The DAQ light in PSGUI is red where in the examples, it's supposed to be green....</p>
<!-- Date: Tue Mar 29 23:33:19 2005 -->
<pre>Tue Mar 29 22:03:30 CST 2005     TRIP: SVX  B2  W0 External Trip 
Tue Mar 29 22:04:46 CST 2005     success: Resetting trips 
Tue Mar 29 22:05:30 CST 2005     success: Power Supply SVX B2 W0 OFF 
Tue Mar 29 22:05:38 CST 2005     TRIP: SVX  B2  W0 DVDD1 OverCurrent 
Tue Mar 29 22:05:50 CST 2005     success: Power Supply SVX B2 W0 ON 
Tue Mar 29 22:05:58 CST 2005     TRIP: SVX  B2  W0 AVDD3 UnderVoltage 
Tue Mar 29 22:06:08 CST 2005     success: Channel3 SVX B2 W0 to STANDBY 
Tue Mar 29 22:06:17 CST 2005     TRIP: SVX  B2  W0 AVDD3 UnderVoltage 
Tue Mar 29 22:06:29 CST 2005     success: Channel3 SVX B2 W0 to STANDBY 
Tue Mar 29 22:06:34 CST 2005     TRIP: SVX  B2  W0 External Trip 
Tue Mar 29 22:06:53 CST 2005     success: Channel3 SVX B2 W0 to STANDBY 
Tue Mar 29 22:07:02 CST 2005     TRIP: SVX  B2  W0 AVDD3 UnderVoltage 
Tue Mar 29 22:08:31 CST 2005     success: Channel3 SVX B2 W0 to STANDBY 
Tue Mar 29 22:08:34 CST 2005     TRIP: SVX  B2  W0 AVDD3 UnderVoltage 
Tue Mar 29 22:08:56 CST 2005     success: Channel3 SVX B2 W0 to STANDBY 
Tue Mar 29 22:09:01 CST 2005     TRIP: SVX  B2  W0 AVDD3 UnderVoltage 
Tue Mar 29 22:10:03 CST 2005     success: Channel3 SVX B2 W0 to STANDBY 
Tue Mar 29 22:10:15 CST 2005     TRIP: SVX  B2  W0 AVDD3 UnderVoltage 
Tue Mar 29 22:10:21 CST 2005     success: Channel3 SVX B2 W0 to STANDBY 
Tue Mar 29 22:10:34 CST 2005     TRIP: SVX  B2  W0 AVDD3 UnderVoltage 
Tue Mar 29 22:15:03 CST 2005     success: Channel3 SVX B2 W0 to STANDBY 
Tue Mar 29 22:15:08 CST 2005     TRIP: SVX  B2  W0 AVDD3 UnderVoltage 
Tue Mar 29 22:29:11 CST 2005     success: Channel3 SVX B2 W0 to STANDBY 
Tue Mar 29 22:29:19 CST 2005     TRIP: SVX  B2  W0 DVDD3 OverCurrent 
Tue Mar 29 22:29:39 CST 2005     success: Channel3 SVX B2 W0 to STANDBY 
Tue Mar 29 22:29:47 CST 2005     TRIP: SVX  B2  W0 AVDD3 UnderVoltage 
Tue Mar 29 22:30:09 CST 2005     success: Channel3 SVX B2 W0 to STANDBY 
Tue Mar 29 22:30:14 CST 2005     TRIP: SVX  B2  W0 AVDD3 UnderVoltage 
Tue Mar 29 22:31:33 CST 2005     success: Channel0 SVX B2 W0 to STANDBY 
Tue Mar 29 22:31:38 CST 2005     success: Channel1 SVX B2 W0 to STANDBY 
Tue Mar 29 22:31:58 CST 2005     success: Channel1 SVX B2 W0 to STANDBY 
Tue Mar 29 22:32:03 CST 2005     success: Channel2 SVX B2 W0 to STANDBY 
Tue Mar 29 22:32:07 CST 2005     success: Channel4 SVX B2 W0 to STANDBY 
Tue Mar 29 22:32:12 CST 2005     success: Channel2 SVX B2 W0 to STANDBY 
Tue Mar 29 22:32:17 CST 2005     success: Channel3 SVX B2 W0 to STANDBY 
Tue Mar 29 22:32:23 CST 2005     TRIP: SVX  B2  W0 DVDD3 OverCurrent 
Tue Mar 29 22:32:25 CST 2005     success: Channel2 SVX B2 W0 to STANDBY 
Tue Mar 29 22:33:09 CST 2005     success: Channel2 SVX B2 W0 to STANDBY 
Tue Mar 29 22:33:20 CST 2005     success: Channel3 SVX B2 W0 to STANDBY 
Tue Mar 29 22:33:27 CST 2005     TRIP: SVX  B2  W0 AVDD3 UnderVoltage 
Tue Mar 29 22:33:32 CST 2005     success: Channel2 SVX B2 W0 to STANDBY 
Tue Mar 29 22:33:40 CST 2005     success: Channel3 SVX B2 W0 to STANDBY 
Tue Mar 29 22:33:46 CST 2005     TRIP: SVX  B2  W0 AVDD3 UnderVoltage 
Tue Mar 29 22:36:28 CST 2005     ALARM:   SVX  B2  W0  L2 is reported OFF, but low/high voltage is above 2/5 V  
Tue Mar 29 22:36:37 CST 2005     success: Power Supply SVX B0 W1 ON 
Tue Mar 29 22:36:48 CST 2005     success: Power Supply SVX B0 W10 ON 
Tue Mar 29 22:36:58 CST 2005     success: Power Supply SVX B1 W1 ON 
Tue Mar 29 22:37:08 CST 2005     success: Power Supply SVX B1 W11 ON 
Tue Mar 29 22:37:15 CST 2005     success: Power Supply SVX B1 W10 ON 
Tue Mar 29 22:37:20 CST 2005     success: Power Supply SVX B2 W1 ON 
Tue Mar 29 22:37:37 CST 2005     success: Power Supply SVX B1 W10 ON 
Tue Mar 29 22:37:46 CST 2005     success: Power Supply SVX B0 W11 ON 
Tue Mar 29 22:38:01 CST 2005     success: Power Supply SVX B2 W0 ON 
Tue Mar 29 22:38:13 CST 2005     TRIP: SVX  B2  W0 AVDD3 UnderVoltage 
Tue Mar 29 22:38:17 CST 2005     success: Power Supply SVX B2 W10 ON 
Tue Mar 29 22:38:28 CST 2005     success: Power Supply SVX B2 W11 ON 
Tue Mar 29 22:38:46 CST 2005     success: Channel3 SVX B2 W0 to STANDBY 
Tue Mar 29 22:38:53 CST 2005     TRIP: SVX  B2  W0 AVDD3 UnderVoltage 
Tue Mar 29 22:39:21 CST 2005     ERROR: Channel3 SVX B2 W0 Handshake - No response from the FIB 
Tue Mar 29 22:39:25 CST 2005     TRIP: SVX  B2  W0 AVDD3 UnderVoltage 
Tue Mar 29 22:46:59 CST 2005     success: Loading CAENvolts.dat 
Tue Mar 29 22:56:25 CST 2005     success: Resetting trips 
Tue Mar 29 22:56:30 CST 2005     ERROR: Channel3 SVX B2 W0 masked 
Tue Mar 29 22:57:45 CST 2005     success: Resetting trips</pre>
<!-- Author: Ankush -->
<!-- Comment: Tue Mar 29 23;35;44 comment by...Ankush -->
<pre>Here's what came out of the PSGUI log file during the trip of SB2W0L3.  The curious piece is thing is it's tripping on UnderVoltage....</pre>


<!-- Comment: Wed Mar 30 09;00;08 comment by...Jen -->
<pre>Tripping Overcurrent or Undervoltage is the same thing to the power supply (current spike causes it to clamp down on the voltage, and if the current doesn't decrease it trips).</pre>
<!-- Comment: Wed Mar 30 09;05;09 comment by...Pursley and Herndon -->
<pre>Likely not even a power supply problem</pre>
<!-- Date: Tue Mar 29 23:53:51 2005 -->
<center><a href='/elog/notebooks/silicon/Tue_Mar_29_2005_235242.ps'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6355' ></a><a href='/elog/notebooks/silicon/Tue_Mar_29_2005_235314.ps'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6357' ></a></center>
<!-- Author: Ankush -->
<!-- Comment: Tue Mar 29 23;55;02 comment by...Ankush -->
<pre>...supposed to be SVXMOn plots...they do look good..honest...</pre>


<!-- Date: Wed Mar 30 00:04:47 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: SB2W0L3 
<li>problem n: 1458 
<li>Status: needs_work
<li>Type: BIAS
<li>Action: Incident
<li>entered by: amitra 
<li>description is: <p>During running this ladder kept tripping on AVDD3 UnderVoltage.  I couldn't recover from the trip and the ladder was taken out of the database.  Need to understand why it's tripping.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B2W0&layer=L3">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Wed Mar 30 04:57:10 2005 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6358&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6359  width='300' align='top'></a></td><td><p>This ladder made a jump from 635mA to ~1040mA when run was started.  This made the ladder go pink.  However this has now settled down to 950mA which is just in its good range.</p> 
 
<p>In the problem DB, this ladder had its Z-side chopped.  Does such a large current suggest the Z side has come back ?</p></td></tr></table>
<!-- Author: Ankush Mitra -->

<!-- Date: Wed Mar 30 05:01:20 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W2L2 
<li>problem n: 49 
<li>Status: needs_quiet_time
<li>Type: jumper
<li>Action: Diagnosis_update
<li>entered by: amitra 
<li>description is: <p>During running the AVDD current jumped to ~1040mA. Its Z-side was chopped aboput a year ago. Does such a large current suggest the Z side is back ?...need looking at during quiet time.</p>  
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B1W2&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Mar 30 08:33:56 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: SB3W3L2 
<li>problem n: 1426 
<li>Status: needs_observation
<li>Type: AVDD2
<li>Action: Diagnosis_update
<li>entered by: rong 
<li>description is: No error seens recently. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B3W3&layer=L2">report</a></ul>
<!-- Author: Problem DB -->




<!-- Date: Wed Mar 30 09:04:52 2005 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6360&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6360  width='300' align='top'></a></td><td>pretest data for SB3W9L3 (e393). Still bit 3 low errors.</td></tr></table>
<!-- Author: Rong -->



<!-- Date: Wed Mar 30 10:42:26 2005 -->
<h3>Access Report for SB3W9L3 (e393)</h3> 
 
<p>SB3W9L3 (e393) was complaining about bit 3 low errors which were confirmed in SVXDaq.  Rong and I went to measure the light levels.</p> 
 
<ul> 
<li>OBDV : 224 uW</li> 
<li>bit 0: 120 uW</li> 
<li>bit 1:  56 uW</li> 
<li>bit 2:  76 uW</li> 
<li>bit 3:  26 uW</li> 
<li>bit 4:  51 uW</li> 
<li>bit 5:  80 uW</li> 
<li>bit 6:  88 uW</li> 
<li>bit 7: 280 uW</li> 
</ul> 
 
<p> We then swapped the fibres going to e392 and e393. Both FIB channels initialised (indicating Bit 3 is OK), but the bit errors moved with the fibre.</p> 
 
<p>Although the light level to bit 3 is low, it can be read by some RXs.  So the plan is either to select a better RX for e393 or see if the DOIM voltage can be adjusted to make bit 3 give more light.</p>
<!-- Author: Ankush & Rong-Shyang -->

<!-- Date: Wed Mar 30 10:49:36 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: SB3W9L3 
<li>problem n: 1410 
<li>Status: needs_access_4hr
<li>Type: RX
<li>Action: Diagnosis_update
<li>entered by: amitra 
<li>description is: <p>During an access, the light levels were measured.  The results are:</p>  <ul> <li>OBDV:  224 uW</li> <li>bit 0: 120 uW</li> <li>bit 1:  56 uW</li> <li>bit 2:  76 uW</li> <li>bit 3:  26 uW</li> <li>bit 4:  51 uW</li> <li>bit 5:  80 uW</li> <li>bit 6:  88 uW</li> <li>bit 7: 280 uW</li> </ul>  <p>Although the light from bit 3 is low, it can be read by some RXs.  If you swap the fibres for e392 and e393, both channels can be intialised..which indicates bit 3 can be read.  But bit errors are still present and do move with fibre.</p>  <p>The plan is to either find a better matched RX for e393 or adjust the DOIM voltage to boost the power out of bit 3</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B3W9&layer=L3">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Wed Mar 30 11:07:59 2005 -->
<h2>Cable probing access summary</h2> 
Went in to probe the low voltage cable of SB2W0, see if there is any obvious reason for L3 to be tripping Ovc/Unv.  Results: 
<ul> 
<li> AVDD3 negative to positive: 1.296 MOhms 
<li> AVDD3 positive to negative: 1.028 MOhms 
<li> AVDD3 negative to negative: 70 Ohms 
<li> AVDD3 positive to positive: 2.5 Ohms 
</ul> 
Probed L2 and L4 for comparisons; results are perfectly consistent with these healthy ladders.  Also took a look at DVDD: 
<ul>  
<li> DVDD3 negative to positive: 2.89 MOhms 
<li> DVDD3 positive to negative: 1.838 MOhms 
</ul> 
Again, results consistent with healthy ladders.  No problems visible from cable probing.<br><br>
<!-- Author: Jen & Marcel -->


<!-- Date: Wed Mar 30 15:57:38 2005 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6361&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6361' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6362&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6362' width='300'></a></center>
<!-- Author: Ankush and Rong -->
<!-- Comment: Wed Mar 30 15;59;02 comment by...Rong -->
<pre>The bit error of SB1W3L3 (e133) came back and make a new SVT hole.</pre>


<!-- Date: Wed Mar 30 16:01:02 2005 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6363&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6364  width='300' align='top'></a></td><td>SVTSPYMon plot for store 4065.  It looks like we've got an extra hole; most likely due to errors from e133</td></tr></table>
<!-- Author: Ankush -->
<!-- Comment: Wed Mar 30 19;33;17 comment by...Ankush -->
<p>...but only lasted to 17:22...Tevatron quenched</p>

<p>..apparently it had to do with the rain...hmmm...I always thought that was the British excuse....</p>
<!-- Date: Wed Mar 30 16:06:01 2005 -->
<p>A nice new trick from Roberto.  This web-page gives a text summary for the SVT Performance.</p> 
 
<a href="http://www-cdfonline.fnal.gov/cgi/ops/cdf_svt/spycheck.cgi"> 
http://www-cdfonline.fnal.gov/~cdf_svt/cgi-bin/spycheck.cgi</a> 
 
<p>The output for Store 4065 is below.  It shows the rate from B1W3 is 15%...not zero, but still very low.</p> 
 
<pre> 
Processing /cdf/people1/cdf_svt/bin/spycheck.C... 
           W0   W1   W2   W3   W4   W5   W6   W7   W8   W9   WA   WB 
davg_B0    16   21    1   -6  -24  -14  -22  -72  -65   -7   -8    7 
davg_B1    40   29   40   16  -31  -25  -32    0  -49  -15   -2   32 
davg_B2    37   51   29  -10  -14  -25  -66  -54  -42  -13   -7   26 
davg_B3    32   43   36   -4   -8  -38  -56  -39  -49  -29    4   20 
davg_B4    42   36   28   -2  -19  -46  -66  -48    0  -28    3   -1 
davg_B5    23   59   38  -22    0  -30  -65 -103  -71  -36  -16    9 
dtail_B0   27   20   20   10   24   27   26   30   16   17   19   15 
dtail_B1   30   36   21   17   22   35   35    0   23   16   15   30 
dtail_B2   34   38   23   18   13   28   37   39   32   16   16   25 
dtail_B3   31   43   27   16   17   31   38   33   26   14   10   25 
dtail_B4   38   35   19   20   22   32   38   36    0   17   17   23 
dtail_B5   41   40   35   19    0   35   44   52   41   25   17   32 
chisqw     16   18   18   18   16   19   17   18   16   16   17   17 
rate_B0    79   54* 100   76   97   97   53*  93   60*  86   74   65  
rate_B1    78   94   84   15*  67   75   64    0*  86   85   75  100  
rate_B2    65   89   70  100   86   72   64   61   81   89   90   92  
rate_B3    72  100   54*  82   93  100   86   94   86   78   53*  98  
rate_B4    57*  75   63   92   94   84   23*  88    0* 100   78   74  
rate_B5    86   95   89  100    0*  99   90   88   88   82   75   83  
dead 3 B1W7 B4W8 B5W4 
ineff 8 B0W1 B0W6 B0W8 B1W3 B3W2 B3WA B4W0 B4W6 
chisq 16.94 
</pre>
<!-- Author: Ankush -->


<!-- Date: Wed Mar 30 16:19:52 2005 -->
<h4>...act of desparation....</h4> 
 
<p>We stopped the run and power-cycled B1W3 to see if that would fix the SVT hole.  Unfortunatly this prooved unsuccessful :-( </p>
<!-- Author: Ankush,  Marcel, Rong -->


<!-- Date: Wed Mar 30 16:39:24 2005 -->
<h3>I'm Clean !!!!</h3> 
 
<p>My masters felt my insides and gave me a good scrubbing. I'm nice and clean and ready to serve you once more</p> 
 
 
<!-- Author: Saeco  -->

<!-- Date: Wed Mar 30 17:47:08 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: IB0W1L4 
<li>problem n: 185 
<li>Status: needs_observation
<li>Type: Chip_bit_error
<li>Action: Diagnosis_update
<li>entered by: rong 
<li>description is: No error seen recently. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B0W1&layer=L4">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Wed Mar 30 18:21:31 2005 -->
<pre>Update of SVX/L00/ISL power supply alarms: 
A new alarm is introduced if any of the power supplies which are not masked in the hardware database are turned off. The alarms have been added to the SVX/L00/ISL alarm summary pages.</pre>
<!-- Author: U. Husemann -->


<!-- Date: Wed Mar 30 18:22:09 2005 -->
<table><tr><td><a href=/elog/notebooks/silicon/Wed_Mar_30_2005_182156.ps align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6366  align='top'></a></td><td>During quiet time, I ran SB1W3L3 (e133) with SVXDaq.  The error is in all chips.  I tried playing with RDRiver current to no avail.  The error is most likely in the DOIM.</td></tr></table>
<!-- Author: Ankush -->
<!-- Comment: Wed Mar 30 18;23;40 comment by...dumbo -->
<pre>sorry, I attached the wrong graph...DOH !!</pre>


<!-- Date: Wed Mar 30 18:25:31 2005 -->
<table><tr><td><a href=/elog/notebooks/silicon/Wed_Mar_30_2005_182520.ps align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6368  align='top'></a></td><td>During quiet time, I ran SB1W3L3 (e133) with SVXDaq. The error is in all chips. I tried playing with RDRiver current to no avail. The error is most likely in the DOIM.</td></tr></table>
<!-- Author: Ankush -->


<!-- Date: Wed Mar 30 19:17:19 2005 -->
<h3>Trying to bring some old ladders back</h3> 
 
<p>During quiet time, we tried to bring back several ladders which had been taken out of the hardware database.  However there was no success as these ladders kept tripping :-(</p> 
 
<p>The ladders tried were:</p> 
<ul> 
<li>SB4W6L2 (e462)</li> 
<li>SB1W6L4 (e164)</li> 
<li>SB2W0L3 (e203)</li> 
</ul>
<!-- Author: Ankush, Rong & Marcel -->
<!-- Comment: Wed Mar 30 19;19;21 comment by...Ankush -->
<p>..forgot to mention that I brought the silicon through COLDSTART after I had finished.</p>


<!-- Comment: Thu Mar 31 09;15;12 comment by...corrinne -->
Hey, someone should see if e224 will stay powered w/o tripping.  I took it out during my week, maybe it has calmed down now that it has had some time off.  


<!-- Comment: Thu Mar 31 23;28;48 comment by...Grumpy -->
The question is, do you feel lucky, Punk ?  :-)
<!-- Date: Thu Mar 31 14:14:44 2005 -->
<h3>Changes to SVXMon</h3> 
 
<p> 
Satyajit&#39s changes to SVXMon are now in.   The format for svxmon_yellow.txt has been changed.  During running I&#39ll have a butchers at it. 
</p> 
  
<!-- Author: Ankush -->
<!-- Comment: Fri Apr  1 00;01;40 comment by...Ankush -->
<p>Here&#39s the output of svxmon_yellow.txt after 1000 events. It all looks OK.</p>

<pre>
Status: ERROR
---------------------------------------
Run 196042, Thu Mar 31 23:56:48
SVX
Status: OK
ISL
Status: ERROR
Silicon/I/B3/W1/L4/C10
Silicon/I/B3/W1/L4/C11
Silicon/I/B3/W1/L4/C13
Silicon/I/B3/W1/L4/C14
L00
Status: OK
</pre>
<!-- Date: Thu Mar 31 22:42:19 2005 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6371&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6371' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6372&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6372' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6373&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6373' width='300'></a></center>
<!-- Author: Ankush -->
<!-- Comment: Thu Mar 31 22;43;20 comment by...Ankush  -->
<h3>Lost the Clock</h3>

<p>We were just about to put silicon in and then this happened...we lost the CDF clock...</p>

<!-- Comment: Thu Mar 31 23;20;06 comment by...Ankush and Rong-Shyang -->
<p>Once we recovered the CDF Clock, we did a cold start and ran a few events to check everthing is OK.  No problems were found...everything OK :-)</p>
<!-- Comment: Thu Mar 31 23;27;46 comment by...Marcel -->
so we have definetely lost the beam structure .... (Abort Gaps...), this also explains the failure of Ricks Counters...

<!-- Date: Thu Mar 31 23:13:15 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: SB2W10L4 
<li>problem n: 1459 
<li>Status: needs_observation
<li>Type: AVDD2
<li>Action: IMON_limits
<li>entered by: amitra 
<li>description is: <p>This guy has been at 1145mA for last 12 hours.  So raising its upper limit.</p><table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>1130</td><td>1130</td></tr>
<tr><td><b>Lower</b></td><td>1105</td><td>1105</td></tr>
<tr><td><b>Upper</b></td><td>1140</td><td>1145</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B2W10&layer=L4">report</a></ul>
<!-- Author: Problem DB -->






<!-- Date: Thu Mar 31 23:37:00 2005 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6374&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6374  width='300' align='top'></a></td><td><p>SVTSPYMon plot for store 4072....did you notice B1W3 was slightly darker...it appears SB1W3L3 (e133) is back again :-)</p></td></tr></table>
<!-- Author: Ankush & Rong-Shyang -->


<!-- Date: Thu Mar 31 23:39:20 2005 -->
<p>Here's the text output of SVT...you see the rate for B1W3 has gone up to 49%</p> 
 
<pre> 
Processing /cdf/people1/cdf_svt/bin/spycheck.C... 
           W0   W1   W2   W3   W4   W5   W6   W7   W8   W9   WA   WB 
davg_B0     2  -14    0    1   20   -1   37   -8   -8   -8  -23   -6 
davg_B1   -10  -11   -8    8    5    1    1    0    0   -3   -8  -13 
davg_B2   -23  -15   -4   -3    3   16   11  -16  -12  -17  -11  -26 
davg_B3   -28  -11    5   -9    6   13   11   13  -18  -17  -11  -30 
davg_B4   -21   -8  -19   16   -1    8   15   -1    0  -18  -15  -31 
davg_B5   -10  -11   13   -8    0    2    7   -5  -16  -23  -26  -24 
dtail_B0   14   11   16   12   14   16   19   11   10   13   15   13 
dtail_B1   19   12   15   13   11   20   13    0   10   11   12   19 
dtail_B2   13   11   10   11   12   16   10   22   11   11   14   14 
dtail_B3   14   13    9   13   11   14   13   12   12   10   10   15 
dtail_B4   16   13   15   14   14   16   17   12    0   13   14   14 
dtail_B5   18   11   15   13    0   14   16   13   17   14   17   14 
chisqw     14   15   14   14   13   16   13   15   13   14   14   14 
rate_B0    80   76   88   77   92  100   78   82   68   85   83   61  
rate_B1    78  100   90   49*  74   79   93    0*  80   92   74   97  
rate_B2    68  100   75  100   83   75   77   62   75   82   78   98  
rate_B3    63   85   63   79   86   95  100   85   75   67   53*  84  
rate_B4    62   87   70   94  100  100   39*  93    0*  87   82   98  
rate_B5    79   82   93   92    0* 100   90   78   77   78   74   78  
dead 3 B1W7 B4W8 B5W4 
ineff 3 B1W3 B3WA B4W6 
chisq 14.27 
</pre>
<!-- Author: Ankush and Rong-Shyang -->



<!-- Date: Fri Apr 1 05:54:40 2005 -->
something was driving a huge amount of beam into the GAP. Shift crew put silicon to standby. Looking at the plots, everything has already calmed down and the Lense started to kick out beam from the GAP. 
While looking tevMon already went to pink again so I gave go ahead for the aces as the trend was pretty clear.
<!-- Author: Marcel -->

<!-- Date: Fri Apr 1 07:20:21 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: SB3W3L2 
<li>problem n: 1426 
<li>Status: needs_observation
<li>Type: AVDD
<li>Action: IMON_limits
<li>entered by: amitra 
<li>description is: <p> This ladder's AVDD has been at 660mA overnight.  So going to increase the IMON upper limit.</p><table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>630</td><td>630</td></tr>
<tr><td><b>Lower</b></td><td>620</td><td>620</td></tr>
<tr><td><b>Upper</b></td><td>640</td><td>660</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B3W3&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Fri Apr 1 18:58:11 2005 -->
<p><font size=+1> D-mode Calibration Job Started </font>
<p><pre>
Job id            : 401
Calibration type  : nonstandard
Run period tag    : Apr_2005
DPS-off run       : 196061
DPS-on run        : 196060
Requested by      : Xiaojian Zhang
Main process id   : 11052
Comment           : beam on, lum 18.50 E30
</pre>
<!-- Author: CDF silicon D-mode calibration job server v1.4 -->



<!-- Date: Fri Apr 1 19:28:06 2005 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6375&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6376  width='300' align='top'></a></td><td><p>DVDD jumped up at the end of DMode calibrations. This ladder has a history of a bad DVDD.  I'm currently keeping an eye on it.</p></td></tr></table>
<!-- Author: Ankush -->


<!-- Date: Fri Apr 1 19:50:31 2005 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6377&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6378  width='300' align='top'></a></td><td><p>DVDD for B0W5L2 is now OK.  As soon as the trigger tests started, the config resettled the ladder.</p> 
 
<p>..it's back to being a happy ladder :-) </p></td></tr></table>
<!-- Author: Ankush Mitra -->


<!-- Date: Fri Apr 1 19:53:46 2005 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6379&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6380  width='300' align='top'></a></td><td><p>The SVTSPYMon plot for trigger table test.  The SPYMon plots looks good and IMON is happy...no pinikies</p> 
 
<p>The L1 rate is ~13.2KHz..roughly the same as before.</p></td></tr></table>
<!-- Author: Ankush Mitra -->

<!-- Date: Fri Apr 1 19:57:11 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: SB3W3L2 
<li>problem n: 1426 
<li>Status: needs_observation
<li>Type: AVDD
<li>Action: IMON_limits
<li>entered by: amitra 
<li>description is: <p>Changing the IMON limits again.  This ladder has been constant at 665mA  for most of the day.</p><table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>630</td><td>630</td></tr>
<tr><td><b>Lower</b></td><td>620</td><td>620</td></tr>
<tr><td><b>Upper</b></td><td>660</td><td>670</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B3W3&layer=L2">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Fri Apr 1 23:41:53 2005 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6383&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6383' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6384&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6384' width='300'></a></center>
<!-- Author: Yuji -->
<!-- Comment: Fri Apr  1 23;51;20 comment by...Yuji -->
<br>
From offline monitor shifter:<br>
Run 196042 LB0W3L3 (f833) bit2 stacked high.<br>


<font color=yellow><b>10</b></font><font color=yellow><b>50</b></font><font color=blue>0d</b></font><font color=cyan><b>0b</b></font> <font color=yellow><b>04</b></font><font color=yellow><b>10</b></font><font color=yellow><b>41</b></font><font color=yellow><b>00</b></font> <font color=yellow><b>00</b></font><font color=yellow><b>00</b></font><font color=yellow><b>00</b></font><font color=yellow><b>00</b></font> <font color=yellow><b>00</b></font><font color=yellow><b>00</b></font><font color=yellow><b>00</b></font><font color=yellow><b>00</b></font> <font color=yellow><b>00</b></font><font color=yellow><b>00</b></font><font color=yellow><b>00</b></font><font color=yellow><b>00</b></font> <font color=yellow><b>00</b></font><font color=yellow><b>00</b></font><font color=yellow><b>00</b></font><font color=yellow><b>00</b></font> <font color=yellow><b>08</b></font><font color=yellow><b>16</b></font><font color=yellow><b>08</b></font><font color=yellow><b>16</b></font> <font color=yellow><b>00</b></font><font color=yellow><b>00</b></font><font color=yellow><b>00</b></font><font color=yellow><b>00</b></font> 
<br>
<font color=black>f8</b></font><font color=black>33</b></font><font color=green>7c</b></font><font color=cyan>fc</b></font> <font color=green><b>86</b></font><font color=black>1c</b></font><font color=blue><b>04</b></font><font color=black>4b</b></font> <font color=blue><b>05</b></font><font color=black>4b</b></font><font color=blue><b>06</b></font><font color=black>57</b></font> <font color=blue><b>07</b></font><font color=black>4b</b></font><font color=red><b>04</b></font><font color=black>48</b></font> <font color=blue><b>05</b></font><font color=black>49</b></font><font color=blue><b>06</b></font><font color=black>4a</b></font> <font color=blue><b>07</b></font><font color=black>57</b></font><font color=blue><b>0c</b></font><font color=black>57</b></font> <font color=blue><b>0d</b></font><font color=black>57</b></font><font color=blue><b>0e</b></font><font color=black>56</b></font> <font color=blue><b>0f</b></font><font color=black>48</b></font><font color=red><b>0c</b></font><font color=black>57</b></font> <font color=red>200ns</font>
<br>
<font color=blue><b>0d</b></font><font color=black>59</b></font><font color=blue><b>0e</b></font><font color=black>7a</b></font> <font color=blue><b>0f</b></font><font color=black>5b</b></font><font color=blue><b>14</b></font><font color=black>54</b></font> <font color=blue><b>15</b></font><font color=black>54</b></font><font color=blue><b>16</b></font><font color=black>57</b></font> <font color=blue><b>17</b></font><font color=black>48</b></font><font color=red><b>14</b></font><font color=black>49</b></font> <font color=blue><b>15</b></font><font color=black>48</b></font><font color=blue><b>16</b></font><font color=black>56</b></font> <font color=blue><b>17</b></font><font color=black>55</b></font><font color=blue><b>1c</b></font><font color=black>48</b></font> <font color=blue><b>1d</b></font><font color=black>55</b></font><font color=blue><b>1e</b></font><font color=black>54</b></font> <font color=blue><b>1f</b></font><font color=black>55</b></font><font color=red><b>1c</b></font><font color=black>56</b></font> <font color=red>840ns</font>



<!-- Date: Sat Apr 2 03:20:13 2005 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6385&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6386  width='300' align='top'></a></td><td><p>SVTSPYMon Plot for Store 4073...looks good and B1W3 is looks dark :-)</p></td></tr></table>
<!-- Author: Ankush -->


<!-- Date: Sat Apr 2 03:37:14 2005 -->
<p>Here's a text version of the output of SVT:</p> 
 
<pre> 
Processing /cdf/people1/cdf_svt/bin/spycheck.C... 
           W0   W1   W2   W3   W4   W5   W6   W7   W8   W9   WA   WB 
davg_B0   -10  -11  -17  -11    3   -9   -6  -10   -4    9  -22    7 
davg_B1     4    7   -2    7  -11    0  -15    0   -8   -6   -9    2 
davg_B2    -8  -16   -2   -2  -14   10   -0  -17   -7  -20   -5  -16 
davg_B3   -12   -5   12  -15   -8   -2   -0  -12   -6  -16  -14   -9 
davg_B4   -21  -15  -24  -20    1   -4   -1  -10    0   -7   -9   -4 
davg_B5    -1   -3   -1  -16    0   17  -10  -14  -11   -6   -7  -17 
dtail_B0   13   11   17   13   18   17   15   18   14   14   14   13 
dtail_B1   17   18   12   13   11   24   12    0   14   14   16   13 
dtail_B2   10   14   11   12   13   16   10   21   15   13   14   13 
dtail_B3   13   18    9   11   12   14   12   12   12   12    8   14 
dtail_B4   16   13   14   15   17   18   16   14    0   16   15   12 
dtail_B5   14   22   18   19    0   20   12   16   16   14   19   14 
chisqw     17   17   16   17   15   17   16   17   15   15   15   16 
rate_B0    80   74   92   81  100   97   62   88   65   85   71   69  
rate_B1    78  100   86   41*  67   83   66    0*  86   91   75   89  
rate_B2    64   90   68  100   84   63   55*  58*  84   83   85   88  
rate_B3    73   96   73   93   94  100   92   97   92   84   60   94  
rate_B4    60*  87   63  100   97   93   27*  86    0*  93   87   93  
rate_B5    77   83  100   91    0*  88   73   84   76   81   65   81  
dead 3 B1W7 B4W8 B5W4 
ineff 5 B1W3 B2W6 B2W7 B4W0 B4W6 
chisq 16.02 
</pre>
<!-- Author: Ankush -->


<!-- Date: Sat Apr 2 04:44:12 2005 -->
<h3>Cooling Alarm</h3> 
 
<p>Run was going smoothly when suddenly the L00 Cooling alarm fired and L00 west bulkhead tripped.  Coincidently, the Cryo-tech had just poured in new resin into the SVX chiller.</p> 
 
<p>Silicon was immediatley put into standby and the run was restarted without Silicon.  I recovered the trip and put the Silicon through coldstart.</p> 
 
 
</p>
<!-- Author: Ankush -->
<!-- Comment: Sat Apr  2 05;33;33 comment by...Ankush and Rong-Shyang -->
<p>Rong came in to help me.</p>  

<p>We got hold of Eva and Andy.  After chattting with them, it appears the cooling is OK.  So silicon was powered up and we started a new run with Silicon.</p>
<!-- Comment: Sat Apr  2 06;14;37 comment by...Ankush and Rong-Shyang -->
<pre>The cryo teck acknowledged the trip before I arrived. So the information I got from him is that the interlock fired on L00 flow rate. We couldnt see glitch or anything in the history plot. The flow rate is stable between 2.1 and 2.2 as it was. the warning is set on 2.0 and alarm is 1.8.</pre>
<!-- Comment: Sat Apr  2 08;47;43 comment by...Andy H. -->
We'll look into how exactly a resin exchange caused a low flow trip.  That's pretty weird.
<!-- Date: Sat Apr 2 04:45:20 2005 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6389&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6389  width='300' align='top'></a></td><td>Here's the L00 IMON display during the trip.</td></tr></table>
<!-- Author: Ankush Mitra -->




<!-- Date: Sat Apr 2 16:26:09 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: LB0W3L3 
<li>problem n: 1441 
<li>Status: fixed
<li>Type: Chip_bit_error
<li>Action: Diagnosis_update
<li>entered by: mystery-guest 
<li>description is: In run 196045, bit 2 high problem has gone. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=L00&wedge=B0W3&layer=L3">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Sun Apr 3 03:33:50 2005 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6390&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6390  width='300' align='top'></a></td><td>SVT SPYMON for 4074. Pretty late, because it took quite a while to take off. 
</td></tr></table>
<!-- Author: Grumpy -->



<!-- Date: Sun Apr 3 11:06:54 2005 -->
WHY it's me got paged due to <a href='http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2005&action=view&page=278&frame=2&anchor=10:48:15.396'> 
e122 pinky</a>??? Anyway, asked the ACE to "follow the instruction" and do the HRR. It sounds like recovered. $^#&*
<!-- Author: Rong-Shyang -->
<!-- Comment: Sun Apr  3 11;19;44 comment by...Rong -->
Also got paged 4am due to b0fib07 not going to halt state, see also <a href=
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2005&action=view&page=277&frame=2&anchor=04:32:09.570'>
elog</a>. ACE did reboot the crate but didn't realize that she has to change crate state manually. Now I just realized they skipped the main pager and called my pager number directly.

<!-- Comment: Sun Apr  3 12;00;08 comment by...Marcel -->
I don't know ysterday, they paged me ... welcome to the club.


<!-- Comment: Sun Apr  3 18;16;57 comment by...Ankush -->
<p>err...dunno what happened there guys...what it the ace or the SciCo taking the "initiative" to page you guys.  Looks like we need an ace and/or SciCo cull soon.</p>
<!-- Date: Sun Apr 3 17:29:23 2005 -->
Run was halted with b0svx06 in red and b0fib05 in yellow, see also <a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2005&action=view&page=279&frame=2&anchor=17:10:30.456'> 
elog</a>. I thought the offending one is the svx06 crate, so tried to reboot it but ACE still has no access from RunControl. Asked ACE to abort the run, but it still stuck. Then I tried to reboot the b0fib05 as well. After that, ACE could bring both crate through partition and start a new run.  
<!-- Author: Rong-Shyang -->
<!-- Comment: Sun Apr  3 18;32;12 comment by...Marcel -->
again an example, where Scico paged too many people....




<!-- Date: Sun Apr 3 18:39:01 2005 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6391&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6391  width='300' align='top'></a></td><td>Comparison between run192060 and 196082 for IB0W2L4 
</td></tr></table>
<!-- Author: yuji -->
<!-- Comment: Sun Apr  3 18;42;32 comment by...Yuji -->
<br>
Bit1, 2, 3 stack low?<br>
<pre><font color="yellow"><b>10</b></font><font color="yellow"><b>50</b></font><font
 color="blue">0d</font><font color="cyan"><b>0b</b></font> <font
 color="yellow"><b>04</b></font><font color="yellow"><b>10</b></font><font
 color="yellow"><b>41</b></font><font color="yellow"><b>00</b></font> <font
 color="yellow"><b>00</b></font><font color="yellow"><b>00</b></font><font
 color="yellow"><b>00</b></font><font color="yellow"><b>00</b></font> <font
 color="yellow"><b>00</b></font><font color="yellow"><b>00</b></font><font
 color="yellow"><b>00</b></font><font color="yellow"><b>00</b></font> <font
 color="yellow"><b>00</b></font><font color="yellow"><b>00</b></font><font
 color="yellow"><b>00</b></font><font color="yellow"><b>00</b></font> <font
 color="yellow"><b>00</b></font><font color="yellow"><b>00</b></font><font
 color="yellow"><b>00</b></font><font color="yellow"><b>00</b></font> <font
 color="yellow"><b>08</b></font><font color="yellow"><b>16</b></font><font
 color="yellow"><b>08</b></font><font color="yellow"><b>16</b></font> <font
 color="yellow"><b>00</b></font><font color="yellow"><b>00</b></font><font
 color="yellow"><b>00</b></font><font color="yellow"><b>00</b></font> <br><font
 color="black">f0</font><font color="black">24</font><font color="green">3b</font><font
 color="cyan">fc</font> <font color="green"><b>81</b></font><font
 color="black">21</font><font color="blue"><b>00</b></font><font
 color="black">f3</font> <font color="green"><b>80</b></font><font
 color="black">21</font><font color="green"><b>81</b></font><font
 color="black">21</font> <font color="blue"><b>60</b></font><font
 color="black">f3</font><font color="blue"><b>61</b></font><font
 color="black">01</font> <font color="red"><b>60</b></font><font
 color="black">f3</font><font color="green"><b>80</b></font><font
 color="black">21</font> <font color="blue"><b>70</b></font><font
 color="black">f3</font><font color="blue"><b>71</b></font><font
 color="black">f3</font> <font color="red"><b>70</b></font><font
 color="black">f3</font><font color="red"><b>70</b></font><font
 color="black">01</font> <font color="blue"><b>71</b></font><font
 color="black">01</font><font color="red"><b>70</b></font><font
 color="black">f3</font> <font color="red">240ns</font><br><font
 color="green"><b>91</b></font><font color="black">21</font><font
 color="green"><b>90</b></font><font color="black">21</font> <font
 color="green"><b>91</b></font><font color="black">21</font><font
 color="blue"><b>01</b></font><font color="black">f3</font> <font
 color="blue"><b>10</b></font><font color="black">f1</font><font
 color="blue"><b>11</b></font><font color="black">f3</font> <font
 color="blue"><b>30</b></font><font color="black">f3</font><font
 color="blue"><b>31</b></font><font color="black">1f</font> <font
 color="red"><b>30</b></font><font color="black">01</font><font
 color="green"><b>90</b></font><font color="black">21</font> <font
 color="green"><b>b1</b></font><font color="black">21</font><font
 color="green"><b>b0</b></font><font color="black">21</font> <font
 color="blue"><b>11</b></font><font color="black">01</font><font
 color="blue"><b>20</b></font><font color="black">1e</font> <font
 color="blue"><b>21</b></font><font color="black">01</font><font
 color="green"><b>b1</b></font><font color="black">21</font> <font
 color="red">880ns</font><br><font color="green"><b>b0</b></font><font
 color="black">21</font><font color="blue"><b>01</b></font><font
 color="black">01</font> <font color="red"><b>00</b></font><font
 color="black">01</font><font color="blue"><b>01</b></font><font
 color="black">f3</font> <font color="red"><b>00</b></font><font
 color="black">f3</font><font color="blue"><b>01</b></font><font
 color="black">01</font> <font color="red"><b>00</b></font><font
 color="black">01</font><font color="blue"><b>21</b></font><font
 color="black">f3</font> <font color="red"><b>20</b></font><font
 color="black">01</font><font color="blue"><b>21</b></font><font
 color="black">f3</font> <font color="green"><b>a1</b></font><font
 color="black">21</font><font color="blue"><b>10</b></font><font
 color="black">f3</font> <font color="blue"><b>11</b></font><font
 color="black">01</font><font color="red"><b>10</b></font><font
 color="black">01</font> <font color="blue"><b>60</b></font><font
 color="black">f3</font><font color="blue"><b>61</b></font><font
 color="black">1e</font> <font color="red">1280ns</font><br><font
 color="red"><b>60</b></font><font color="black">f3</font><font
 color="green"><b>a0</b></font><font color="black">21</font> <font
 color="blue"><b>20</b></font><font color="black">f3</font><font
 color="blue"><b>21</b></font><font color="black">1e</font> <font
 color="red"><b>20</b></font><font color="black">f3</font><font
 color="blue"><b>60</b></font><font color="black">f3</font> <font
 color="blue"><b>61</b></font><font color="black">01</font><font
 color="blue"><b>70</b></font><font color="black">f3</font> <font
 color="red"><b>70</b></font><font color="black">f3</font><font
 color="blue"><b>71</b></font><font color="black">f3</font> <font
 color="red"><b>70</b></font><font color="black">f3</font><font
 color="blue"><b>71</b></font><font color="black">f3</font> <font
 color="red"><b>70</b></font><font color="black">f3</font><font
 color="blue"><b>71</b></font><font color="black">f3</font> <font
 color="green"><b>a1</b></font><font color="black">21</font><font
 color="blue"><b>50</b></font><font color="black">f3</font> <font
 color="red">1840ns</font><br><font color="blue"><b>51</b></font><font
 color="black">01</font><font color="red"><b>50</b></font><font
 color="black">01</font> <font color="blue"><b>51</b></font><font
 color="black">f3</font><font color="red"><b>50</b></font><font
 color="black">01</font> <font color="green"><b>a0</b></font><font
 color="black">21</font><font color="blue"><b>31</b></font><font
 color="black">f3</font> <font color="red"><b>30</b></font><font
 color="black">01</font><font color="blue"><b>31</b></font><font
 color="black">f3</font> <font color="blue"><b>60</b></font><font
 color="black">f3</font><font color="blue"><b>61</b></font><font
 color="black">f3</font> <font color="red"><b>60</b></font><font
 color="black">f3</font><font color="blue"><b>71</b></font><font
 color="black">f3</font> <font color="red"><b>70</b></font><font
 color="black">f3</font><font color="blue"><b>71</b></font><font
 color="black">01</font> <font color="red"><b>70</b></font><font
 color="black">f3</font><font color="blue"><b>71</b></font><font
 color="black">f3</font> <font color="red">2520ns</font><br><font
 color="red"><b>70</b></font><font color="black">f3</font><font
 color="blue"><b>71</b></font><font color="black">01</font> <font
 color="red"><b>70</b></font><font color="black">f3</font><font
 color="blue"><b>71</b></font><font color="black">01</font> <font
 color="red"><b>70</b></font><font color="black">f3</font><font
 color="blue"><b>71</b></font><font color="black">01</font> <font
 color="red"><b>70</b></font><font color="black">1e</font><font
 color="blue"><b>71</b></font><font color="black">01</font> <font
 color="red"><b>70</b></font><font color="black">f3</font><font
 color="blue"><b>71</b></font><font color="black">01</font> <font
 color="red"><b>c2</b></font><font color="black">c2</font><font
 color="red"><b>00</b></font><font color="black">00</font>                   <font
 color="red">3120ns</font><br><br></pre>

<!-- Date: Sun Apr 3 18:56:09 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: IB0W2L4 
<li>problem n: 110 
<li>Status: needs_observation
<li>Type: Chip_bit_error
<li>Action: Diagnosis_update
<li>entered by: yuji 
<li>description is: Bit1, 2 and 3 seems stack low. See <a href=http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=242&frame=2&anchor=18:39:01>e-log </a> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B0W2&layer=L4">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Sun Apr 3 23:07:53 2005 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6392&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6392' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6393&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6393' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6394&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6394' width='300'></a></center>
<!-- Author: Ankush -->
<!-- Comment: Sun Apr  3 23;15;24 comment by...Ankush -->
<h3>Trippy Silicon</h3>

<p>Several wedges in L00 and ISL suddenly went black !!.    The two left most IMON snapshots show this.</p>

<p>The ACE used IFIX as a quick fix to power the ladders up again.    However two L00 wedges still tripped (see right hand plot).  I came in and recovered the remaining wedges.  Everthing now seems to be OK.</p>




<!-- Date: Mon Apr 4 04:26:09 2005 -->
<h3>Bloody CAEN power supplies</h3> 
 
<p>We were about to test a trigger table with Silicon when we noticed a L00:ifix inhibit. On the IFIX Silicon Inhibit Status monitor we see L00 B1W0 Power Supply had raised the alarm.....however we didn&#39t hear the "L00 alarm" lady and the PS GUI looked fined. </p> 
 
<p>Fortunatly the ACE remembered seeing such an alarm and searched the E-Log.  It turns out the solution was to hockerize the crate.  So I did that and it cleared the IFIX inhibit.  I powered up the wedges and everything was OK.</p> 
 
<p>We really need to understand what is going on with the PS.  Our current firefighting strategy is OK...but we can do so much better !!!</p>  
<!-- Author: Ankush -->


<!-- Date: Mon Apr 4 04:29:40 2005 -->
<h3>Trigger Table Tests</h3> 
 
<p>A new trigger table,physics_test_3_02[7.636,561], was tested first without silicon.  The L1 rate was only 3KHz...pretty low.</p> 
 
<p>We will ran with silicon to the end of the store.  The current L1 rate is 3KHz and L2 is 60Hz...again pretty small.</p> 
 
 
  
<!-- Author: Ankush -->


<!-- Date: Mon Apr 4 04:31:06 2005 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6395&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6396  width='300' align='top'></a></td><td>SVTSPYMon plot for the trigger table test...for those interested.</td></tr></table>
<!-- Author: Ankush -->


<!-- Date: Mon Apr 4 09:32:00 2005 -->
<h3>  How do I feel....</h3> 
 
<p> 
As quoted by an "Soccer" coach.... 
 
"My magic words at half-time were f***, b*******, b******, crap and p***-poor" 
Sunderland boss Mick McCarthy reveals his inspiring team-talk away at QPR. </p>
<!-- Author: Dead -->


<!-- Date: Mon Apr 4 11:11:00 2005 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6397&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6397  width='300' align='top'></a></td><td>e133, run 195930 (3/30/05)</td></tr></table>
<!-- Author: boveia -->
<!-- Comment: Mon Apr  4 11;18;30 comment by...Antonio and Yuji -->
<pre>During 195930 on March 30 (the most recent appearance of the SVT hole), e133 had bit 4 always equal to bit 5: when bit 5 is high, bit 4 is stuck high, and when bit 5 is low, bit 4 is stuck low.
</pre>