<!-- Title: 13:25:26  Mon Dec  4 2006 -->
<!-- Crewchief: Juan Pablo (MPC) -->
<!-- Op1: Ulrich (SPL) -->
<!-- Op2: Jose Enrique (SPL) -->
<!-- Op3: &nbsp; -->
<!-- Op4: &nbsp; -->
<!-- Op5: &nbsp; -->
<!-- Op6: &nbsp; -->
<!-- Notes: -->
<pre> sorry I was late ...</pre>


<!-- Date: Mon Dec 4 13:32:00 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10418&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10419  width='300' align='top'></a></td><td>The Silicon Operations group as of December 4, 2006. Missing: Oscar, Takayuki.</td></tr></table>
<!-- Author: Ulrich -->

<!-- Date: Mon Dec 4 14:42:52 2006 -->
Entered in Incident database: <ul>
<li>Incident number: 6 
<li>Date: 12/04/06 
<li>Time: 14:38
<li>Type: DAQ
<li>Submitted by: fernand
<li>Duration of incident (hr.): 1. 
<li>Downtime due to incident (hr.): 1.
<li>Number of shift crew required to fix it: 4 
<li>Experts involved in resolution: Jose,Ulrich,Juan Pablo,Roberto
<li>Description of Problem: Test on new trigger tables first without them with silicon.Rates before putting silicon were :   L1 : ~30 KHz  L2 : ~230 HzRates after putting silicon :  L1 : ~29 KHz  L2 : ~320 Hz
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/idb/DBentry.pl?incident_number=6">Incident Report</a></ul>
<!-- Author: Incident DB -->
<!-- Comment: Mon Dec  4 15;39;28 comment by...Juan Pablo -->
<pre>Sorry, for number of shift crew required I meant 1.</pre>
<!-- Date: Mon Dec 4 15:25:32 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB4W11L1 
<li>problem n: 1819 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: fernand 
<li>description is: Adjusting BIAS limits.<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>55.78</td><td>75.87</td></tr>
<tr><td><b>Lower</b></td><td>0.5</td><td>0.5</td></tr>
<tr><td><b>Upper</b></td><td>100</td><td>120</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B4W11&layer=L1">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Mon Dec 4 15:25:33 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB4W11L1 
<li>problem n: 1819 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: fernand 
<li>description is: Adjusting BIAS limits.<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>55.78</td><td>75.87</td></tr>
<tr><td><b>Lower</b></td><td>0.5</td><td>0.5</td></tr>
<tr><td><b>Upper</b></td><td>100</td><td>120</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B4W11&layer=L1">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Mon Dec 4 15:35:49 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10420&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10421  width='300' align='top'></a></td><td>This is the I_VBIAS plot from IMON for B4W11L1</td></tr></table>
<!-- Author:  Juan Pablo, Roberto -->



<!-- Date: Mon Dec 4 15:41:15 2006 -->
<h3>DS Error Monitor revived</h3> 
After the Fermilab UCSB web server upgrade, David Stuart moved all his scripts to his desktop at UCSB. We had updated links to ADCMon in the past, but the link from the Bit Reporter to David's Error Monitor was still pointing to the old URL. I have updated the URL in /cgi-bin/bitreporter/makeladder.pl and /cgi-bin/bitreporter/makepage.pl. Please report any problems.
<!-- Author: Ulrich -->
<!-- Comment: Tue Dec  5 09;51;01 comment by...Mark -->
I updated the links for the PDB as well.
<!-- Date: Mon Dec 4 15:55:20 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB4W2L0 
<li>problem n: 1768 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: fernand 
<li>description is: Changing BIAS limits<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>63</td><td>78</td></tr>
<tr><td><b>Lower</b></td><td>0.5</td><td>0.5</td></tr>
<tr><td><b>Upper</b></td><td>100</td><td>115</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B4W2&layer=L0">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Mon Dec 4 16:09:53 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB3W0L3 
<li>problem n: 1503 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: fernand 
<li>description is: Increasing limits for this ladder.<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>150</td><td>170</td></tr>
<tr><td><b>Lower</b></td><td>0.5</td><td>0.5</td></tr>
<tr><td><b>Upper</b></td><td>165</td><td>185</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B3W0&layer=L3">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Mon Dec 4 16:16:14 2006 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10422&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10422' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10423&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10423' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10424&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10424' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10425&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10425' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10426&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10426' width='300'></a></center>
<!-- Author:  Juan Pablo and Roberto -->
<!-- Comment: Mon Dec  4 16;17;28 comment by...Juan Pablo & Roberto -->
<pre>These are the IV curves from the above modified ladders 
(either profile or normal scattered)</pre>


<!-- Date: Mon Dec 4 16:49:03 2006 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10427&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10427' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10428&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10428' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10429&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10429' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10430&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10430' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10431&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10431' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10432&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10432' width='300'></a></center>
<!-- Author: Juan Pablo & Roberto -->
<!-- Comment: Mon Dec  4 16;50;34 comment by...Juan Pablo & Roberto -->
<pre>IBias plots for new ladders. We will increase the limits right away.</pre>

<!-- Date: Mon Dec 4 17:05:30 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB5W0L1 
<li>problem n: 1758 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: fernand 
<li>description is: Increasing IMON limits<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>57.75</td><td>72.75</td></tr>
<tr><td><b>Lower</b></td><td>0.5</td><td>0.5</td></tr>
<tr><td><b>Upper</b></td><td>100</td><td>115</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B5W0&layer=L1">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Mon Dec 4 17:10:25 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB4W1L4 
<li>problem n: 1769 
<li>Status: fixed
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: fernand 
<li>description is: Increasing IMON limits<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>79.98</td><td>94.98</td></tr>
<tr><td><b>Lower</b></td><td>0.5</td><td>0.5</td></tr>
<tr><td><b>Upper</b></td><td>100</td><td>115</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B4W1&layer=L4">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Mon Dec 4 17:15:18 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB5W2L3 
<li>problem n: 1805 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: fernand 
<li>description is: increasing IMON limits. Bias 0.<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>63.98</td><td>78.98</td></tr>
<tr><td><b>Lower</b></td><td>0.5</td><td>0.5</td></tr>
<tr><td><b>Upper</b></td><td>100</td><td>115</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B5W2&layer=L3">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Mon Dec 4 17:19:11 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB2W1L1 
<li>problem n: 1629 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: fernand 
<li>description is:  Increasing IMON limits  BIAS 1<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>100</td><td>115</td></tr>
<tr><td><b>Lower</b></td><td>0.5</td><td>0.5</td></tr>
<tr><td><b>Upper</b></td><td>120</td><td>135</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B2W1&layer=L1">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Mon Dec 4 20:34:37 2006 -->
<pre>Trigger rates seem fine (close to the values before using 
the new trigger test ~ 28 KHz @ L1 ) 
L2 is 221 Hz (it was 376 before)</pre>
<!-- Author: Juan Pablo -->
<!-- Comment: Mon Dec  4 20;47;31 comment by...Juan Pablo -->
<pre>No running with Silicon and new trigger test; everything
is fine so far (similar rates and no pinkies).</pre>


<!-- Date: Tue Dec 5 00:02:52 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10433&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10434  width='300' align='top'></a></td><td> </td></tr></table>
<!-- Author:   -->
<!-- Comment: Tue Dec  5 00;07;24 comment by...Juan Pablo -->
<pre>Initial lumi 180 E30. Problems with TOF at the
beginning. Loosses fine. SVXMon is all right.
Here it is the SVTSpy Mon plot.
</pre>


<!-- Date: Tue Dec 5 03:14:21 2006 -->
hockerization of PS crate no. 1<a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2006&action=view&page=921&frame=2&anchor=03:05:32.500'> 
details here </a> 
 
  
<!-- Author: Juan Pablo -->


<!-- Date: Tue Dec 5 03:48:01 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10435&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10435  width='300' align='top'></a></td><td> This is the IBIAS for SB2W9L4</td></tr></table>
<!-- Author:  Juan Pablo -->
<!-- Comment: Tue Dec  5 03;48;46 comment by... Juan Pablo -->
<pre>currently this bias line is set to ignore (since it is
already a known problem)</pre>


<!-- Date: Tue Dec 5 06:47:58 2006 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10436&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10436' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10437&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10437' width='300'></a></center>
<!-- Author: Juan Pablo -->
<!-- Comment: Tue Dec  5 06;48;41 comment by...Juan Pablo. -->
<pre>pinky : Sb2W10L2, will increase the Ibias limit</pre>

<!-- Date: Tue Dec 5 06:56:32 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB2W10L0 
<li>problem n: 1820 
<li>Status: fixed
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: fernand 
<li>description is: The values shown in IMON are different to those written in thread 1759. I am adjusting the limits acording to the current values.<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>53</td><td>73</td></tr>
<tr><td><b>Lower</b></td><td>0.5</td><td>0.5</td></tr>
<tr><td><b>Upper</b></td><td>100</td><td>120</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B2W10&layer=L0">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Tue Dec 5 07:00:34 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10438&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10439  width='300' align='top'></a></td><td> SB2W10L0, adjusting IBIAS limits (the current 
values do not match with the PDB thread 1759).</td></tr></table>
<!-- Author:  Juan Pablo -->

<!-- Date: Tue Dec 5 07:03:11 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB2W10L0 
<li>problem n: 1820 
<li>Status: fixed
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: fernand 
<li>description is:  <a href= 'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=330&frame=2&anchor=07:00:34'> see plot </a> for entry above   <table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>??</td><td>??</td></tr>
<tr><td><b>Lower</b></td><td>??</td><td>??</td></tr>
<tr><td><b>Upper</b></td><td>??</td><td>??</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B2W10&layer=L0">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Dec 5 07:21:23 2006 -->
Entered in Incident database: <ul>
<li>Incident number: 7 
<li>Date: 12/05/06 
<li>Time: 03:00
<li>Type: Hockerization
<li>Submitted by: fernand
<li>Duration of incident (hr.): 0.1 
<li>Downtime due to incident (hr.): 0.1
<li>Number of shift crew required to fix it: 1 
<li>Experts involved in resolution: Juan Pablo
<li>Description of Problem: Usual hockerization (PS crate 1)
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/idb/DBentry.pl?incident_number=7">Incident Report</a></ul>
<!-- Author: Incident DB -->


<!-- Date: Tue Dec 5 07:25:33 2006 -->
Entered in Incident database: <ul>
<li>Incident number: 9 
<li>Date: 12/04/06 
<li>Time: 20:00
<li>Type: DAQ
<li>Submitted by: fernand
<li>Duration of incident (hr.): 0.5 
<li>Downtime due to incident (hr.): 0.5
<li>Number of shift crew required to fix it: 1 
<li>Experts involved in resolution: Juan Pablo
<li>Description of Problem: New trigger test at end of store (also used in new store...)
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/idb/DBentry.pl?incident_number=9">Incident Report</a></ul>
<!-- Author: Incident DB -->



<!-- Date: Tue Dec 5 12:44:09 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: LB0W3L3 
<li>problem n: 1821 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: husemann 
<li>description is: During a jump in all bias currents, the BIAS1 current of this ladder slipped over the limit. Bumping up the limit.<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>28.209</td><td>100.0</td></tr>
<tr><td><b>Lower</b></td><td>0.5</td><td>0.5</td></tr>
<tr><td><b>Upper</b></td><td>100.0</td><td>125.0</td></tr></table> 
<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: Tue Dec 5 12:47:11 2006 -->
Entered in Incident database: <ul>
<li>Incident number: 10 
<li>Date: 12/05/06 
<li>Time: 12:45
<li>Type: IMON_Limits
<li>Submitted by: husemann
<li>Duration of incident (hr.): 0.1 
<li>Downtime due to incident (hr.): 0.1
<li>Number of shift crew required to fix it: 0 
<li>Experts involved in resolution: Husemann
<li>Description of Problem: Bumped up one L00 Bias limit (LB0W3L3, BIAS1)
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/idb/DBentry.pl?incident_number=10">Incident Report</a></ul>
<!-- Author: Incident DB -->



<!-- Date: Tue Dec 5 13:05:56 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10440&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10440  width='300' align='top'></a></td><td>A textbook resonance. LA rearmed.</td></tr></table>
<!-- Author: Ulrich -->

<!-- Date: Tue Dec 5 16:16:44 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB3W0L0 
<li>problem n: 1822 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: husemann 
<li>description is: Bias current hit limit, bumping up the limit.<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>50.9235</td><td>100.0</td></tr>
<tr><td><b>Lower</b></td><td>0.5</td><td>0.5</td></tr>
<tr><td><b>Upper</b></td><td>100.0</td><td>125.0</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B3W0&layer=L0">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Dec 5 16:18:06 2006 -->
Entered in Incident database: <ul>
<li>Incident number: 11 
<li>Date: 12/05/06 
<li>Time: 16:17
<li>Type: IMON_Limits
<li>Submitted by: husemann
<li>Duration of incident (hr.): 0.1 
<li>Downtime due to incident (hr.): 0.0
<li>Number of shift crew required to fix it: 0 
<li>Experts involved in resolution: Husemann
<li>Description of Problem: Bumped up bias current limit for B3W0L0
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/idb/DBentry.pl?incident_number=11">Incident Report</a></ul>
<!-- Author: Incident DB -->


<!-- Date: Tue Dec 5 16:46:01 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB3W2L1 
<li>problem n: 1823 
<li>Status: needs_observation
<li>Type: AVDD
<li>Action: IMON_limits
<li>entered by: husemann 
<li>description is: Pre-emptive strike on the bias current limits on a couple of yellow ladders (still on initial limit of 100 μA)<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>56.5921</td><td>100.0</td></tr>
<tr><td><b>Lower</b></td><td>0.5</td><td>0.5</td></tr>
<tr><td><b>Upper</b></td><td>100.0</td><td>125.0</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B3W2&layer=L1">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Dec 5 16:49:57 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB3W4L0 
<li>problem n: 1824 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: husemann 
<li>description is: Pre-emptive strike on the bias current limits on a couple of yellow ladders (still on initial limit of 100 μA)Pre-emptive strike on the bias current limits on a couple of yellow ladders (still on initial limit of 100 μA)<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>58.9</td><td>100.0</td></tr>
<tr><td><b>Lower</b></td><td>0.5</td><td>0.5</td></tr>
<tr><td><b>Upper</b></td><td>100.0</td><td>125.0</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B3W4&layer=L0">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Dec 5 16:51:30 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB3W7L0 
<li>problem n: 1825 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: husemann 
<li>description is: Pre-emptive strike on the bias current limits on a couple of yellow ladders (still on initial limit of 100 μA)<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>52.6714</td><td>100.0</td></tr>
<tr><td><b>Lower</b></td><td>0.5</td><td>0.5</td></tr>
<tr><td><b>Upper</b></td><td>100.0</td><td>125.0</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B3W7&layer=L0">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Dec 5 16:54:10 2006 -->
Entered in Incident database: <ul>
<li>Incident number: 12 
<li>Date: 12/05/06 
<li>Time: 16:52
<li>Type: Unknown
<li>Submitted by: aarond
<li>Duration of incident (hr.): 0.16 
<li>Downtime due to incident (hr.): 0.0
<li>Number of shift crew required to fix it: 0 
<li>Experts involved in resolution: Husemann
<li>Description of Problem: Bumped up IMON limits in 3 wedges (SB3W2L1, SB3W4L0, SB3W7L0).
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/idb/DBentry.pl?incident_number=12">Incident Report</a></ul>
<!-- Author: Incident DB -->



<!-- Date: Tue Dec 5 21:35:12 2006 -->
Another XFT firmware change from which we only learned via the elog: 
<pre> 
 Tue Dec 5 19:10:06 Mark called with the plan. When we call MCR to tell them our HV is down, we call cryro to let them know as well. We then take calibrations. XFT experts will swap back the firmware on xft01,03,07 and also work on diagnosing a bug on XFT 06, 07. We can take calibrations. D0 has requested an access for 1-1.5h. Our magnet will take 40 min to go down. The UPS swap will take 30 min and the magnet will take another 40 min to go up. So things should be buttoned up for shot setup at about 11:30. - Rick :: (run 229490) 
</pre> 
Juan Pablo will be around for shot setup and watch things. Keep your fingers crossed.
<!-- Author: Ulrich -->


<!-- Date: Tue Dec 5 22:42:20 2006 -->
<h3>Weird ISL trip</h3> 
While the shift crew brought the Silicon to STANDBY for the end of the store, one ISL power supply, in IB5W4, went crazy. It started ramping up all voltages until eventually the overvoltage protection kicked in and tripped the channels. I happened to be in the Silicon office and could switch off the last two channels by hand. Here is the PS GUI log: 
<pre> 
Tue Dec 05 21:52:11 CST 2006                        IFix -  success: Silicon to STANDBY   
Tue Dec 05 21:52:20 CST 2006                        TRIP: ISL  B5  W4 VBIAS02 OverVoltage 
Tue Dec 05 21:52:29 CST 2006                        TRIP: ISL  B5  W4 VBIAS10 OverVoltage 
Tue Dec 05 21:52:38 CST 2006                        TRIP: ISL  B5  W4 External Trip 
Tue Dec 05 21:52:38 CST 2006                        TRIP: ISL  B5  W4 VBIAS14 OverVoltage 
Tue Dec 05 21:55:24 CST 2006                        success: Power Supply ISL B5 W4 to STANDBY 
Tue Dec 05 21:56:03 CST 2006                        success: Power Supply ISL B5 W4 to STANDBY 
Tue Dec 05 21:56:08 CST 2006                        TRIP: ISL  B5  W4 VBIAS10 OverVoltage 
Tue Dec 05 21:56:08 CST 2006                        TRIP: ISL  B5  W4 VBIAS02 OverVoltage 
Tue Dec 05 21:56:08 CST 2006                        TRIP: ISL  B5  W4 VBIAS14 OverVoltage 
Tue Dec 05 21:56:46 CST 2006                        success: Channel0 ISL B5 W4 to STANDBY 
Tue Dec 05 21:56:51 CST 2006                        success: Channel1 ISL B5 W4 to STANDBY 
Tue Dec 05 21:56:54 CST 2006                        TRIP: ISL  B5  W4 VBIAS03 OverVoltage 
Tue Dec 05 21:56:57 CST 2006                        success: Channel3 ISL B5 W4 to STANDBY 
Tue Dec 05 21:57:03 CST 2006                        TRIP: ISL  B5  W4 VBIAS03 OverVoltage 
Tue Dec 05 21:57:10 CST 2006                        success: Channel0 ISL B5 W4 OFF 
Tue Dec 05 21:57:16 CST 2006                        success: Channel1 ISL B5 W4 OFF 
</pre> 
So after a while I tried again, and the supply started to act up again. Next Ace Timo and I hockerized Crate 15. When we were back up in the control room, IMON still showed blue wedges, while they were already red in the PS GUI. The last update was also two minutes ago. As it turned out, IMON crashed with the following exception: 
<pre> 
Exception in thread "Thread-1" java.lang.IndexOutOfBoundsException: Index: 85, S 
                                  ize: 85 
        at java.util.ArrayList.RangeCheck(ArrayList.java:546) 
        at java.util.ArrayList.get(ArrayList.java:321) 
        at IMONpackage.Calculation2.CheckSpontaneousSwitchOff(Calculation2.java: 
                                  652) 
        at IMONpackage.Calculation2.ReportAlarms(Calculation2.java:489) 
        at IMONpackage.Calculation2.UpdateChannels(Calculation2.java:471) 
        at IMONpackage.Calculation2.process(Calculation2.java:322) 
        at com.smartsockets.TipcConnClientImpl.callProcessCallbacks(TipcConnClie 
                                  ntImpl.java:1344) 
        at com.smartsockets.TipcSrvImpl.process(TipcSrvImpl.java:864) 
        at com.smartsockets.TipcConnClientImpl.mainLoop(TipcConnClientImpl.java: 
                                  1216) 
        at com.smartsockets.TipcSrvImpl.mainLoop(TipcSrvImpl.java:745) 
        at IMONpackage.Calculation2.run(Calculation2.java:99) 
</pre> 
So the new spontaneous switch-off mechanism has an array overflow. That should be easy to fix.
<!-- Author: Ulrich -->
<!-- Comment: Tue Dec  5 23;00;02 comment by...Ulrich -->
I think I found the bug:
<pre>
	    for (int en=0;en < off_list.size();en++) { 
	
		ChannelBox cb = (ChannelBox) npresent_list.get(en);

		//Check that this channel is not in the old_off_list
		if (IsChannelOnlist(cb,old_off_list)) continue;
		
		PScrates_off[cb.PScrate]++;
	    
	    }
</pre>
So there is a direct access to an array which isn't checked, probably a copy-and-paste error.


<!-- Comment: Wed Dec  6 04;25;16 comment by... Juan Pablo -->
<pre>Sorry I forgot to mention that yesterday I experienced the same
problem Ulrich did. This happened when taking data (around
3 am) and I just restarted IMON.
Another comment is the fact in this case, IMON told me to 
hockerize PS 2 while it was 1 the problematic</pre>
<!-- Comment: Wed Dec  6 09;59;54 comment by...Jose -->
IMON should now point to the right PS to Hockerize. I have restarted IMON with the bug fixed.
<!-- Date: Tue Dec 5 23:51:17 2006 -->
<h3>L00 Biasing Test</h3> 
After dealing with the CAEN and IMON mess, I can now come to the real reason why I'm still at B0. I wanted to see if all wide L00 ladders hold 90 V bias voltage. I tried the entire West side Unfortunately, two ladders keep tripping after a minute or so if I bias them to 90 V: f811, and f830. All of them hold at 85 V though. So the plan is to change the entire West side to 85 V and see where we are at.
<!-- Author: Ulrich -->
<!-- Comment: Wed Dec  6 00;13;10 comment by...Ulrich -->
Ok, the changes to the HWDB are done now. I have created a new CAENvolts.dat file and biased the West L00 to see if the voltage holds everywhere. Should there be a problem during data-taking later on, the short-term fix would be to set the voltages back to 80 V by hand on the PS GUI.


<!-- Date: Wed Dec 6 00:21:45 2006 -->
Forgot to mention that I also rebooted all Silicon VRB crates. They started to get sluggish in COLDSTART again. No problems.
<!-- Author: Ulrich -->


<!-- Date: Wed Dec 6 04:23:00 2006 -->
<pre>Need to hockerize PS 1 tonight as well (better now that 
later since we are about to start taking data ...)</pre>
<!-- Author:  Juan Pablo. -->
<!-- Comment: Wed Dec  6 04;48;36 comment by...Juan Pablo -->
<pre>Sb2W9L4 set to ignore (known bias problem) on IMON</pre>


<!-- Date: Wed Dec 6 04:55:57 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10441&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10442  width='300' align='top'></a></td><td> SVTspy plot with usual holes. 
 SvxMon looks fine. 
 Initial luminosity ~170 E30 
 </td></tr></table>
<!-- Author:  Juan Pablo -->
<!-- Comment: Wed Dec  6 04;57;46 comment by...Juan Pablo -->
<pre>Smoothly data taking so far.</pre>

<!-- Comment: Wed Dec  6 05;01;05 comment by...Juan Pablo -->
<pre>currently loosses stable and well under control by TeV guys</pre>

<!-- Date: Wed Dec 6 07:42:25 2006 -->
Entered in Incident database: <ul>
<li>Incident number: 13 
<li>Date: 12/05/06 
<li>Time: 04:54
<li>Type: Hockerization
<li>Submitted by: fernand
<li>Duration of incident (hr.): 0.1 
<li>Downtime due to incident (hr.): 0.1
<li>Number of shift crew required to fix it: 1 
<li>Experts involved in resolution: Juan Pablo
<li>Description of Problem: PS 1 again
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/idb/DBentry.pl?incident_number=13">Incident Report</a></ul>
<!-- Author: Incident DB -->



<!-- Date: Wed Dec 6 10:37:15 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB2W0L4 
<li>problem n: 1776 
<li>Status: fixed
<li>Type: Chip_bit_error
<li>Action: Diagnosis_update
<li>entered by: sasha 
<li>description is: No problems during data taking during the past 30 days. Fixed. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B2W0&layer=L4">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Dec 6 10:49:03 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W1L2 
<li>problem n: 2 
<li>Status: needs_work
<li>Type: AVDD2
<li>Action: Diagnosis_update
<li>entered by: sasha 
<li>description is: Data from chip 85 looks like garbage and causes c2c2. This ladder needs to be studied with SVXDAQ, and chip85 needs to be chopped.  
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B0W1&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Dec 6 11:07:43 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB2W2L4 
<li>problem n: 1423 
<li>Status: fixed
<li>Type: Chip_bit_error
<li>Action: Diagnosis_update
<li>entered by: sasha 
<li>description is: This ladder runs essentially error free since 11/21/06. I guess it's another case of magic recovery. Fixed. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B2W2&layer=L4">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Wed Dec 6 11:09:55 2006 -->
<pre>Tevatron abort, aces performed the post quench c-o and  
went fine</pre>
<!-- Author: Juan Pablo -->

<!-- Date: Wed Dec 6 11:12:54 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB4W0L2 
<li>problem n: 571 
<li>Status: fixed
<li>Type: Chip_other
<li>Action: Diagnosis_update
<li>entered by: sasha 
<li>description is: No problems in data after 11/21/06. Fixed. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B4W0&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Dec 6 11:22:12 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W8L4 
<li>problem n: 1801 
<li>Status: fixed
<li>Type: Chip_capid
<li>Action: Incident
<li>entered by: sasha 
<li>description is: No problems since 11/21/06. Fixed. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B1W8&layer=L4">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Dec 6 11:48:07 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB1W4L1 
<li>problem n: 1826 
<li>Status: needs_work
<li>Type: Chip_bit_error
<li>Action: Incident
<li>entered by: sasha 
<li>description is: There is bit0 low problem which occurs on chip a3 (read out as a2) causing c2c2. According to previous entries, it looks like this chip was causing problems before and was chopped. But it's in data again. So, this ladder needs to be studied with SVXDAQ, and, if necessary, the chip chain should be chopped starting from a3.  
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B1W4&layer=L1">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Dec 6 12:00:33 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB4W5L3 
<li>problem n: 1827 
<li>Status: unfixable
<li>Type: Chip_other
<li>Action: Diagnosis_update
<li>entered by: sasha 
<li>description is: I opened a new thread for duplicate channel problem which was reported in thread 585. Somehow that thread went into IMON limits 'mode'. So, just to keep things separate, I opened this one for chip problems only. Regarding the doublicate channel problem itself, it was already pointed out in thread 585 that it's unfixable and doesn't cause to much harm.  
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B4W5&layer=L3">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Dec 6 12:00:33 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB4W5L3 
<li>problem n: 1827 
<li>Status: unfixable
<li>Type: Chip_other
<li>Action: Diagnosis_update
<li>entered by: sasha 
<li>description is: I opened a new thread for duplicate channel problem which was reported in thread 585. Somehow that thread went into IMON limits 'mode'. So, just to keep things separate, I opened this one for chip problems only. Regarding the doublicate channel problem itself, it was already pointed out in thread 585 that it's unfixable and doesn't cause to much harm.  
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B4W5&layer=L3">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Dec 6 12:03:48 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB5W4/5All 
<li>problem n: 1689 
<li>Status: needs_observation
<li>Type: Chip_capid
<li>Action: Diagnosis_update
<li>entered by: sasha 
<li>description is: Wedge wide CAP_ID problems are still there. By some reason they are mostly seen on wedge IB5W4. Needs to be investigated. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B5W4/5&layer=All">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Dec 6 13:30:31 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W2L1 
<li>problem n: 784 
<li>Status: needs_work
<li>Type: Chip_bit_error
<li>Action: Diagnosis_update
<li>entered by: sasha 
<li>description is: Bit0 high problem is back at ~30% rate. It mostly affects chipID on z-side. Sometimes it causes c2c2 if a0->a1. Needs to be studied during quiet time. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B0W2&layer=L1">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Dec 6 13:30:31 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W2L1 
<li>problem n: 784 
<li>Status: needs_work
<li>Type: Chip_bit_error
<li>Action: Diagnosis_update
<li>entered by: sasha 
<li>description is: Bit0 high problem is back at ~30% rate. It mostly affects chipID on z-side. Sometimes it causes c2c2 if a0->a1. Needs to be studied during quiet time. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B0W2&layer=L1">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Dec 6 13:56:19 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W5L2 
<li>problem n: 1828 
<li>Status: needs_work
<li>Type: Chip_other
<li>Action: Incident
<li>entered by: sasha 
<li>description is: Starting 11/17/06, this ladder developped 'no first chip' problem (no data at all in this case). The current rate is fluctuating in the range 10-100%. This ladder needs to be studied during quiet time. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B0W5&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Dec 6 14:17:31 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB3W6L4 
<li>problem n: 74 
<li>Status: needs_work
<li>Type: Chip_other
<li>Action: Diagnosis_update
<li>entered by: sasha 
<li>description is: Chip a5 is currently sparsed out, but it looks OK in svxdaq (<a href= 'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=326&frame=2&anchor=11:40:05'> see here</a>). This chip only gives cap_id errors, but this is not a reason to get rid off it during data taking. Needs to be reconfirmed with SVXDAQ and unsparsed. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B3W6&layer=L4">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Dec 6 14:38:37 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB5W3L4 
<li>problem n: 1591 
<li>Status: needs_work
<li>Type: Chip_capid
<li>Action: Monitoring
<li>entered by: sasha 
<li>description is: Chip 87 gives CAP_ID errors. It also has dead FE (see <a href= 'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=326&frame=2&anchor=11:40:05'>here</a>). According to previous entries, chip a6 was diagnozed as dead FE and was sparsed out, but I think a6 is OK and was confused with chip 87. One needs to check all settings in HWDB and re-confirm in SVXDAQ that chip 87 has dead FE (and to be sparsed out) and that chip  a6 is OK (and to be unsparsed).  
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B5W3&layer=L4">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Wed Dec 6 15:49:19 2006 -->
<h3>PDB review and list of things TO DO</h3> 
 
<p>I went through PDB and Bit reporter to check for new problems, investigate old ones, and do clean up. Last time such a review was conducted about a month ago, so it is right time to do it again. Based on this review, I came up with the following list of things TO DO. 
<lu> 
<li>f552--try to reproduce CAP_ID in SVXDAQ.</li> 
<li>e012--garbage is read out from chip 85 (currently last chip), test is SVXDAQ and chop chip 85, if necessary.</li> 
<li>e053-- check init read back and remove mask, if necessary.</li> 
<li>f141--bit0 low on chip a3 (causes a3->a2 and c2c2); needs to be studied more carefully; chips a3-a0 may be chopped if problem causes too large readout time.</li> 
<li>e021-- bit0 high on z-side, affects chipID and causes c2c2; needs quiet time.</li> 
<li>e052-- no first chip-> no data at all; needs quiet time.</li> 
<li>e364-- follow up on old problem (see PDB); chip a5 is sparsed out, but it looks OK (besides CAP_ID errors) in svxdaq; re-confirm and unsparse.</li> 
<li>e534-- follow up on old problem (see PDB); chip 87 has dead FE and needs to be sparsed out; it looks like chip a6 was confused with 87 and was sparsed out instead. One needs to check HWDB settings and reconfirm the problem with SVXDAQ, followed by appropriate changes in HWDB.</li> 
</lu> 
<h4>Other comments</h4> 
<lu> 
<li>DS error monitor is functioning OK again after a link change.</li> 
<li>ADCMon is still in "reduced capability mode". Plots for individual chips are missing. It would be nice to have ADCMon operating in the previous style.</li> 
<li>A link to a log file with ladders with long read out time is broken (http://nucsb03.fnal.gov/cgi-bin/readoutocc). It would be nice to have it back.</li> 
<li>This is a general comment regarding making PDB entries for IMON limits. The number of such entries is climbing up. It is partially happening because we do regular bump ups for Bias limits and report them in PDB as "needs_observation". I would propouse to make such entries as "fixed" if this is just a routine bump up. In all other cases (AVDD, DVDD, bad behavior, PS swaps, etc.), of course, the entry should be "needs_observation".</li> 
</lu> 
</p>
<!-- Author: sasha -->


<!-- Date: Wed Dec 6 17:17:24 2006 -->
<h3><b> IMON Bias Currents </b></h3> 
<p> 
I had a look at Bias currents as a function of DS days for all ladders, where the IMON limits had to be bumped up since August'06. 
</p> 
<p> 
The result is a bit frustrating again. After a short stable period (DS 2090-2125; 09/22/06 - 11/01/06) the bias currents seem again to increase in general. For ISL ladders the increase is similar as direct after the long shut down (may be a bit lower), but for SVX I got the impression, that we had to increase more limits than ever before and that the increase of the bias current is now even slightly stronger than direct after the shutdown. 
</p> 
<p> 
Thus I will leave most of the ladders with "needs observation" in the PDB and I will declare only those ladders as momentarily fixed, where I think, we don't have to bump up the current limits in the next few months (at least 1-2month(s)). 
</p>
<!-- Author: Jeannine -->
<!-- Comment: Wed Dec  6 18;57;26 comment by...Ulrich -->
Two comments:
<ol>
<li>In the period from 9/22 to 11/01 we had two weeks without data taking, so we integrated only 1.7/pb per day. For comparison: between 11/7 and 12/3, we integrated 4.0/pb per day. There is also the effect of beneficial annealing during the shutdown.</li>
<li>Having bumped up more than a dozen of SVX bias currents, my guess is the following: the initial bias current limit is 100 μA. The ladders just happen to hit this limit at about the same time.</li>
</ol>
<!-- Date: Wed Dec 6 17:34:59 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB5W1L3 
<li>problem n: 1722 
<li>Status: fixed
<li>Type: BIAS
<li>Action: Diagnosis_update
<li>entered by: jwagner 
<li>description is: Bias currents are still increasing. However, even if the BIAS current increases with the same rate as in the moment no further limit bump is needed in the next 3-4 months. Thus I declare it as fixed for the moment. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B5W1&layer=L3">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Dec 6 17:36:42 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB1W3L1 
<li>problem n: 1597 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: Currents_investigated
<li>entered by: jwagner 
<li>description is: The currents are increasing again. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B1W3&layer=L1">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Dec 6 17:44:59 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB5W0L3 
<li>problem n: 1743 
<li>Status: fixed
<li>Type: BIAS
<li>Action: Currents_investigated
<li>entered by: jwagner 
<li>description is: After a short stable period the bias current is increasing again. However, even if the BIAS current increases with the same rate as in the moment no further bump up of the limit is needed in the next 3-4 months. Thus I declare it as fixed for the moment. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B5W0&layer=L3">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Dec 6 17:47:28 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB3W0L4 
<li>problem n: 1506 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: Currents_investigated
<li>entered by: jwagner 
<li>description is: The bias currents are almost stable now (very slightly increasing). Thus I will declare it as fixed. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B3W0&layer=L4">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Dec 6 17:50:07 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB5W0L4 
<li>problem n: 1784 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: Currents_investigated
<li>entered by: jwagner 
<li>description is: After a short stable period the bias current is increasing again. However, even if the BIAS current increases with the same rate as in the moment no further bump up of the limit is needed in the next 3-4 months. Thus I declare it as fixed for the moment. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B5W0&layer=L4">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Dec 6 17:53:17 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB4W3L2 
<li>problem n: 1789 
<li>Status: fixed
<li>Type: BIAS
<li>Action: Currents_investigated
<li>entered by: jwagner 
<li>description is: The bias currents seem to be stable now. Thus I declare it as fixed. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B4W3&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Dec 6 17:56:21 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB3W11L2 
<li>problem n: 1522 
<li>Status: fixed
<li>Type: BIAS
<li>Action: Currents_investigated
<li>entered by: jwagner 
<li>description is: Bias currents are still slightly increasing. However, even if the BIAS current increases with the same rate as in the moment no further limit bump is needed in the next few months. Thus I declare it as fixed for the moment. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B3W11&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Dec 6 17:58:17 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB5W7L2 
<li>problem n: 1704 
<li>Status: fixed
<li>Type: BIAS
<li>Action: Currents_investigated
<li>entered by: jwagner 
<li>description is: Bias currents are still slightly increasing. However, even if the BIAS current increases with the same rate as in the moment no further bump of the limit is needed in the next few months. Thus I declare it as fixed for the moment. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B5W7&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Dec 6 18:02:06 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB0W2L3 
<li>problem n: 1774 
<li>Status: fixed
<li>Type: BIAS
<li>Action: Currents_investigated
<li>entered by: jwagner 
<li>description is: Bias currents are still increasing. However, even if the BIAS current increases with the same rate as in the moment the limit should not be reached for about 2-3 months. Thus I declare it as fixed for the moment. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B0W2&layer=L3">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Dec 6 18:04:12 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB2W1L3 
<li>problem n: 1757 
<li>Status: fixed
<li>Type: BIAS
<li>Action: Currents_investigated
<li>entered by: jwagner 
<li>description is: The currents are still increasing. However, the new limit should not be reached in the next few months. Thus I declare it as fixed for the moment. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B2W1&layer=L3">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Dec 6 18:06:22 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB3W0L0 
<li>problem n: 1717 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: Currents_investigated
<li>entered by: jwagner 
<li>description is: The currents are still increasing. However, the new limit should not be reached in the next few months. Thus I declare it as fixed for the moment. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B3W0&layer=L0">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Dec 6 18:07:53 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB3W0L1 
<li>problem n: 1537 
<li>Status: fixed
<li>Type: BIAS
<li>Action: Currents_investigated
<li>entered by: jwagner 
<li>description is: The currents are still increasing. However, the new limit should not be reached in the next few months. Thus I declare it as fixed for the moment. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B3W0&layer=L1">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Dec 6 18:08:47 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB3W0L2 
<li>problem n: 1531 
<li>Status: fixed
<li>Type: BIAS
<li>Action: Currents_investigated
<li>entered by: jwagner 
<li>description is: The currents are still increasing. However, the new limit should not be reached in the next few months. Thus I declare it as fixed for the moment. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B3W0&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Dec 6 18:12:58 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W2L1 
<li>problem n: 1806 
<li>Status: fixed
<li>Type: BIAS
<li>Action: Currents_investigated
<li>entered by: jwagner 
<li>description is: The bias currents are now stable below the new limit. Thus I declare it as fixed for the moment. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B0W2&layer=L1">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Dec 6 18:17:06 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB4W10L2 
<li>problem n: 1703 
<li>Status: fixed
<li>Type: BIAS
<li>Action: Currents_investigated
<li>entered by: jwagner 
<li>description is: The bias current is still a bit spiky but stable below the new limit. Thus I declare it as fixed. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B4W10&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Dec 6 18:18:17 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB1W3L0 
<li>problem n: 991 
<li>Status: fixed
<li>Type: BIAS
<li>Action: Currents_investigated
<li>entered by: jwagner 
<li>description is: The currents are still slightly increasing. However, the new limit should not be reached in the next few months. Thus I declare it as fixed for the moment. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B1W3&layer=L0">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Dec 6 18:22:26 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB3W0L3 
<li>problem n: 1503 
<li>Status: fixed
<li>Type: BIAS
<li>Action: Currents_investigated
<li>entered by: jwagner 
<li>description is: The currents are almost stable now, only very slightly increasing now. We should be able to live with new limit for a few months. Thus I declare it as fixed for the moment. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B3W0&layer=L3">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Dec 6 18:22:26 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB2W1L1 
<li>problem n: 1629 
<li>Status: fixed
<li>Type: BIAS
<li>Action: Currents_investigated
<li>entered by: jwagner 
<li>description is: The currents are still increasing. However, the new limit should not be reached in the next few months. Thus I declare it as fixed for the moment. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B2W1&layer=L1">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Dec 6 18:24:09 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB3W0L0 
<li>problem n: 1822 
<li>Status: fixed
<li>Type: BIAS
<li>Action: Currents_investigated
<li>entered by: jwagner 
<li>description is: The currents are still increasing. However, the new limit should not be reached in the next few months. Thus I declare it as fixed for the moment. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B3W0&layer=L0">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Dec 6 18:24:09 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB3W7L0 
<li>problem n: 1825 
<li>Status: fixed
<li>Type: BIAS
<li>Action: Currents_investigated
<li>entered by: jwagner 
<li>description is: The currents are still slightly increasing. However, the new limit should not be reached in the next few months. Thus I declare it as fixed for the moment. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B3W7&layer=L0">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Dec 6 18:30:22 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB3W0L0 
<li>problem n: 1717 
<li>Status: fixed
<li>Type: BIAS
<li>Action: Currents_investigated
<li>entered by: jwagner 
<li>description is: See entry above. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B3W0&layer=L0">report</a></ul>
<!-- Author: Problem DB -->




<!-- Date: Wed Dec 6 21:48:18 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10443&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10444  width='300' align='top'></a></td><td> SVTspy Mon ok; SVXMon ok as well; initial lum 132 E30</td></tr></table>
<!-- Author:  Juan Pablo -->


<!-- Date: Thu Dec 7 00:13:25 2006 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10445&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10446' ></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10447&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10448' ></a></center>
<!-- Author:  Juan Pablo -->
<!-- Comment: Thu Dec  7 00;18;29 comment by... Juan Pablo. -->
<pre>pinky on SB5W10L0.
This ladder has dropped ~40mA on AVDD.
Since on SVXMon seem fine, i.e., all 4 chips of this
layer 0 ladder are presently there (see the strip occupancy
of the plots for the current run), I will set it to ignore
and will hockerize the correspondent PS crate whenever
posible ( just in case it is a hockerization issue ...
but it seems AVDD on this ladder came to normal values as I write ) </pre>


<!-- Date: Thu Dec 7 07:25:45 2006 -->
<pre>b0svx07 failing coldstart config . Details
 <a href='http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2006&action=view&page=927&frame=2&anchor=07:10:08.902'> 
here </a>.</pre>
<!-- Author: Juan Pablo -->

<!-- Date: Thu Dec 7 07:28:41 2006 -->
Entered in Incident database: <ul>
<li>Incident number: 14 
<li>Date: 12/06/06 
<li>Time: 07:12
<li>Type: DAQ
<li>Submitted by: fernand
<li>Duration of incident (hr.): 0.1 
<li>Downtime due to incident (hr.): 0.1
<li>Number of shift crew required to fix it: 1 
<li>Experts involved in resolution: Juan Pablo
<li>Description of Problem: b0svx07 solt 20 had to be reset
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/idb/DBentry.pl?incident_number=14">Incident Report</a></ul>
<!-- Author: Incident DB -->



<!-- Date: Thu Dec 7 10:15:05 2006 -->
<h3>More Progress on the AutoHocker</h3> 
The new AutoHocker panel is about ready for installation. The initial panel had problems with the voltage drop in the digital output card, which is a problem with the 50 Ω load of the reset line. So our techs had an engineer (Scott Holm) looking at the card and the panel. He was very unhappy with National Instruments's support. In the end, they came up with the following solution: 
<ul> 
<li>Use a 12 V power supply instead of 5 V</li> 
<li>Have two separate circuits for the manual and the automatic Hockerization (can be chosed by a flip switch)</li>  
<li>Divide the voltage down with resistors (different for manual and automatic) and limit the voltage with a Zener diode</li> 
<li>Have push buttons instead of flip switches for manual reset of individual CAEN crates.</li> 
</ul> 
I have tested the panel both in manual and automatic mode yesterday, and it seems fine.  The remaining question is if we actually reset a CAEN SY527 with the voltage the panel delivers. We will follow up on this soon. In the meanwhile, the software with dummy calls to the Hockerization functions runs without problems.
<!-- Author: Ulrich -->
<!-- Comment: Thu Dec  7 22;10;18 comment by...Ulrich -->
Spoke with Dervin about the time plan for the integration of the AutoHocker.George is out of town this weekend and from the following weekend until the New Year. I'm leaving on Sunday. So the commissioning can only take place during the first week of January. 
<!-- Date: Thu Dec 7 10:19:13 2006 -->
<h3>Finally: The New Test Stand PC</h3> 
We ordered it in July/August, now it is finally operational: the new cooling/interlock test stand PC. Currently I have installed the SoftShop and National Instruments software on it. I'm able to talk to the PLC. The next thing is to get the digital output card and some more software installed (Visual Studio, Office). Stay tuned.
<!-- Author: Ulrich -->


<!-- Date: Thu Dec 7 10:37:46 2006 -->
<h3> SVXMon with new Slides </h3> 
 
The modified version of SVXMon with new expert slides is now in the repository. I will put some instructions on how to run it in the TWiki. The official version of SVXMon will have the changes applied for the new consumers release.  

<!-- Author: Jose -->

<!-- Date: Thu Dec 7 11:22:59 2006 -->
Entered in Incident database: <ul>
<li>Incident number: 15 
<li>Date: 12/07/06 
<li>Time: 11:15
<li>Type: DAQ
<li>Submitted by: fernand
<li>Duration of incident (hr.): 0.1 
<li>Downtime due to incident (hr.): 0.1
<li>Number of shift crew required to fix it: 1 
<li>Experts involved in resolution:  
<li>Description of Problem: fib07 need to be shepharded
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/idb/DBentry.pl?incident_number=15">Incident Report</a></ul>
<!-- Author: Incident DB -->



<!-- Date: Thu Dec 7 12:37:06 2006 -->
<pre>b0fib07 showed a buch of yellow ladders ; decided to start a new 
run ; everything is ok now</pre>
<!-- Author: Juan Pablo, Ulrich, Jose, Rainer -->

<!-- Date: Thu Dec 7 13:07:00 2006 -->
Entered in Incident database: <ul>
<li>Incident number: 16 
<li>Date: 12/07/06 
<li>Time: 12:50
<li>Type: FIB_SEU
<li>Submitted by: fernand
<li>Duration of incident (hr.): 0.5 
<li>Downtime due to incident (hr.): 0.5
<li>Number of shift crew required to fix it: 2 
<li>Experts involved in resolution: Juan Pablo,Rainer,Ulrich,Jose Enrique
<li>Description of Problem: b0fib07
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/idb/DBentry.pl?incident_number=16">Incident Report</a></ul>
<!-- Author: Incident DB -->
<!-- Comment: Thu Dec  7 13;45;54 comment by...Ulrich -->
It is unclear if this particular problem is really a single-event upset. When we started a new run, we looked at the startup message from the FIB crate, expecting messages about corrupted sequence RAM, but there weren't any. We have seen this failure mode in the past, and sometimes it went away by itself. We have decided to mark the run bad for ISL.
<!-- Date: Thu Dec 7 13:07:00 2006 -->
Entered in Incident database: <ul>
<li>Incident number: 16 
<li>Date: 12/07/06 
<li>Time: 12:50
<li>Type: FIB_SEU
<li>Submitted by: fernand
<li>Duration of incident (hr.): 0.5 
<li>Downtime due to incident (hr.): 0.5
<li>Number of shift crew required to fix it: 2 
<li>Experts involved in resolution: Juan Pablo,Rainer,Ulrich,Jose Enrique
<li>Description of Problem: b0fib07
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/idb/DBentry.pl?incident_number=16">Incident Report</a></ul>
<!-- Author: Incident DB -->




<!-- Date: Thu Dec 7 16:14:04 2006 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10449&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10449' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10450&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10450' width='300'></a></center>
<!-- Author: Ignacio -->
<!-- Comment: Thu Dec  7 16;14;57 comment by...Juan Pablo/Roberto/Ignacio -->
We were monitoring these during the bias scan today.


<!-- Date: Thu Dec 7 16:28:51 2006 -->
<h3> 
Another trigger test : <br> 
started without silicon <br>  
rates were fine (27KHz at L1 and 200ish Hz at L2); <br> 
included silicon <br> 
rates still ok (26.1 KHz and 299 Hz at L2) <br> 
no pinkies <br> 
low deadtime (~3%) <br> 
</h3>
<!-- Author: Juan Pablo -->


<!-- Date: Thu Dec 7 16:56:54 2006 -->
<h3>Rasnik Work: New Ntupler</h3> 
During the last week I have an ntupler to the Rasnik system to make it easier to access the Rasnik data. The details are in the 
<a href="http://b0sili01.fnal.gov/cgi-bin/TWiki/bin/view/Silicon/SiliconRasnik#New_Rasnik_ntuples">Silicon TWiki</a>
<!-- Author: Ulrich -->


<!-- Date: Thu Dec 7 17:26:07 2006 -->
<h3> Signal Bias Scan</h3> We took a new signal bias scan at the end of store 5111.Before the scan the whole wides of L00 were brought up to 85. We continued  scannning  L00 and 10 SVX L0 ladders. The ladders are L0 of the following wedges: B2W1 B2W3 B2W5 B2W9 B2W11 B3W1 B3W3 B3W7 B3W9 B3W11. <par> Runnumber: <a href= 'http://www-cdfonline.fnal.gov/java/cdfdb/servlet/RunSummary?RUN=227885'> 229676</a> </par> <par> Reference voltage file is: </par> <par> /cdf/onln/data/svxii/caencontrol/PSfiles/caenvoltsfiles/CAENvolts_12072006_0102PM.dat 
</par> We changed the trigger prescales as appear in the twiki. 
 The dead time was less than 3.3 % and L2A 442 Hz at initial luminosity of 36E30.   
 
 <pre> # Voltage_offset First_L2_Event Last_L2_Event Start End Remarks 
                
 1              130        32900        65655 
 2              110        67661        97793 
 2              110        97898       109211          
 3               90       111211       139550 
 4               70       140401       170403 
 5               50       171803       202138 
 6               30       205207       235234 
 7               10       236443       266504 
 8                0            1        30934 
   
EXTENDED 
 
 9              120      269940        291996 
 9              120      291996        301962 
 10             100      302561        333255 
 11              95      335980        365097 
 12              90      366925        399293 
 13              85      400796        421321 
 14              80      423912        456729 
 15              75      458100        491128  
 16              65      493054        525665 
 17              60      527303        558851 
 18              55      559545        590127 
 19              45      592614        624813 
 20              40      626682        657103 
 21              35      659290        691397 
 22              25      693218        730436 
 23              20      733115        765270 
 24              15      766545        800134 
 25              10      802000        835100 
 26               5      837710        867803 
 27               0      869840        901651 
 
</pre>  
  
<!-- Author: Ignacio/Juan Pablo/Roberto -->


<!-- Date: Thu Dec 7 20:05:42 2006 -->
<pre>Hockerization (comunication failure) of PS crate 10. Sorry Jose, you were right. 
</pre>
<!-- Author: Juan Pablo & Jose -->
<!-- Comment: Thu Dec  7 20;30;48 comment by...Juan Pablo and Jose -->
While going to Standby they had a communication failure. iFix showed it as usual, but also reported a "confusing": PS-CAEN-OFF for "crates 9, 10". <br> This time also IMON pointed to crate 10.

<!-- Comment: Thu Dec  7 22;04;28 comment by...Ulrich -->
The CAEN-PS-OFF happens because there are channels which don't have the ON bit set due to the hockerization. I should change PSMon.exe such that the CAEN-PS-OFF alarm is change to the same as the hockerization alarm whenever a communication failure is detected. There will still be some residual confusion for about 7 seconds as the hockerization alarm is only issued after at least two consecutive updates without communication to the crate. The PS-CAEN-OFF in crate 9 sounds like a bug to me. I'll have a look tomorrow.
<!-- Comment: Fri Dec  8 11;44;01 comment by...Ulrich -->
<h3>PSMon.exe: bugfix release</h3>
I have introduced two changes to PSMon.exe:
<ul>
<li>Fixed the problem with reporting Crate 9 and Crate 10 when only Crate 10 was affected. The CAEN crate to DAQ wedge mapping was buggy: e41x was appearing twice</li>
<li>Removed confusing iFix message of CAAN-PS-OFF when communication is lost at the same time.</li>
</ul>
<!-- Date: Thu Dec 7 21:48:33 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W5L2 
<li>problem n: 1828 
<li>Status: needs_access_2hr
<li>Type: Chip_other
<li>Action: Diagnosis_update
<li>entered by: sasha 
<li>description is: We tested the ladder during quiet time. It turns out that ladder runs error free in RA mode (we tried a few runs with 5K each). However, it does not return data in NN mode. What is interesting is that it runs OK again if we switch to back RA, but gives problem if we return into NN mode. Changing Rdriver didn't help. Given the nature of the problem, it's unlikely to be RX or TX. How would RX or TX know what mode we're running? So, it's either a chip or FIB/FTM. In any case, we need test this ladder (fiber swap) during the next access.    
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B0W5&layer=L2">report</a></ul>
<!-- Author: Problem DB -->
<!-- Comment: Fri Dec  8 13;57;24 comment by...Jose -->
Investigating this ladder using the calibration runs seems to show some data with DPS-off but not with DPS-on. We would need to have a look better to this ladder in quiet time.
<!-- Date: Fri Dec 8 07:25:58 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10455&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10456  width='300' align='top'></a></td><td>SVTSpyMon looks fine; SVXMon ok too. Initial lumi = 170 E32; L1A = 11 KHz, L2A = 500Hz; ref.err.=2%.</td></tr></table>
<!-- Author: Juan Pablo -->

<!-- Date: Fri Dec 8 08:59:08 2006 -->
Entered in Incident database: <ul>
<li>Incident number: 17 
<li>Date: 12/08/06 
<li>Time: 08:50
<li>Type: Hockerization
<li>Submitted by: fernand
<li>Duration of incident (hr.): 0.15 
<li>Downtime due to incident (hr.): 0.15
<li>Number of shift crew required to fix it: 0 
<li>Experts involved in resolution: Juan Pablo,Satyajit and Ulrich
<li>Description of Problem: hockerization of PS 13 (corrupted readback)
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/idb/DBentry.pl?incident_number=17">Incident Report</a></ul>
<!-- Author: Incident DB -->


<!-- Date: Fri Dec 8 09:10:51 2006 -->
Entered in Incident database: <ul>
<li>Incident number: 18 
<li>Date: 12/08/06 
<li>Time: 09:05
<li>Type: Hockerization
<li>Submitted by: fernand
<li>Duration of incident (hr.): 0.1 
<li>Downtime due to incident (hr.): 0.1
<li>Number of shift crew required to fix it: 1 
<li>Experts involved in resolution: Juan Pablo,Ulrich,Satyajit
<li>Description of Problem: PS 5
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/idb/DBentry.pl?incident_number=18">Incident Report</a></ul>
<!-- Author: Incident DB -->



<!-- Date: Fri Dec 8 09:12:12 2006 -->
JDL pointed out that our new VRB crate b0svx09 is not included in the power supply monitoring. We will speak with Steve Hahn and Dervin about this.
<!-- Author: Ulrich -->


<!-- Date: Fri Dec 8 09:53:36 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10457&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10457  width='300' align='top'></a></td><td>green bef oct shutdow ; black after (L0W10B2) 
normalized charge distribution</td></tr></table>
<!-- Author: Juan Pablo -->



<!-- Date: Fri Dec 8 13:08:02 2006 -->
Problems with the <a href='http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2006&action=view&page=931&frame=2&anchor=12:40:36.758'> 
 beam </a>. Now B0AAGC is skipy but still acceptable. We gave run control guys permission to run with silicon.
<!-- Author: Juan Pablo, Jose, Ulrich -->


<!-- Date: Fri Dec 8 17:42:12 2006 -->
Entered in Incident database: <ul>
<li>Incident number: 19 
<li>Date: 12/08/06 
<li>Time: 17:40
<li>Type: Hockerization
<li>Submitted by: fernand
<li>Duration of incident (hr.): 0.5 
<li>Downtime due to incident (hr.): 0.5
<li>Number of shift crew required to fix it: 1 
<li>Experts involved in resolution: Juan Pablo
<li>Description of Problem: PS crate 14
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/idb/DBentry.pl?incident_number=19">Incident Report</a></ul>
<!-- Author: Incident DB -->



<!-- Date: Fri Dec 8 21:55:50 2006 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10460&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10461' ></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10462&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10463' ></a></center>
<!-- Author: Jennifer :-) & Ted -->
<!-- Comment: Fri Dec  8 22;02;51 comment by...The SIllys & Triggers -->
<h2>THE PARTY @ the Hahn's: </h2> 
<p> (Left): The "Ladies" of the Silicon group: Lady Mitra at her best coupled with Her Pinkness. (Check out Peter Wilson in the background)
<p> (Right):This is what happens after Marcel leaves the group: Burkard finally gets a night with his blonde and a L2 pulsar board.
<!-- Comment: Sat Dec  9 09;27;36 comment by...The Muppets at RAL & Oxford -->
<h2>
Lady Mitra, you are the girl of our dreams !!!
</h2>
<!-- Date: Fri Dec 8 21:56:27 2006 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10464&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10465' ></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10466&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10467' ></a></center>
<!-- Author: Jennifer :-) & Ted -->
<!-- Comment: Fri Dec  8 22;08;23 comment by...The Sillys & Triggers -->
"Dear Post-Doc" at the grill: we put the German in charge of the sausages. Our cooling SPL in his natural environment at a balmy -10°C.
<!-- Date: Fri Dec 8 21:57:02 2006 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10458&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10459' ></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10468&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10469' ></a></center>
<!-- Author: Jennifer :-) & Ted -->
<!-- Comment: Fri Dec  8 23;25;04 comment by...Her Pinkness & Ted for the Sillys and the Triggers -->
Our shoes are properly placed by the door, although we are a few days late for the arrival of Kris Kringle...
<p>
We have, however, spotted an elf. Santa must be near!
<p>
<p>
Twas the night before Ankush's retirement and Burkart's departure, and all through Hahn's house
<br>each and every creature was stirring, including the mouse
<br>the not-so-fashionable shoes were placed by the door without care
<br>in hopes that Marcel would soon be there.

<p>
The Sillys were all nestled and snug with some wine
<br>while visions of pinkies danced in their minds
<br>Lady Mitra in her blonde wig, and I in my pink 
<br>Had just settled down for some e-log stink 

<p>
When out by the grill, there arose such a clatter
<br>we arose from our wine glasses to see what was the matter
<br>When what to our half-drunken eyes should appear
<br>But a miniature SVX-II with eight tiny Siliconeers

<p>
<br>With a German driver, quite grumpy yet quick
<p>I knew in a moment that, "this store is sick!"
<br>More rapid than pre-fires his minions they came
<br>And he swore and shouted and called them by name

<p>
On Ankush! now, Jen! now, Ulrich and Jennifer!
<br>On David! On Ben, on Rong-Shyang on Sebby!
<br>To the alcove! Into the collision hall!
<br>Now dash away! Dash away! Time to make that "Hello Dimitri" call!

<p>
The stump of an ACE held tight in his teeth
<br>the resonance of the crash button encircles his head like a wreath
<br>He had a stern German face and a round little belly
<br> He shook the ACEs while he laughed and they wiggled like jelly

<p>
He spoke not a word, and went straight to his work
<br>Hockerizing power supplies and turing on wedge-by-wedge and shouting like a jerk
<br>From the toilet his pager he rose, 
<br>He then powered on the silicon while picking his nose.


<p>
He sprang into his Escort, and to his team he gave them the bird
<br>And in a rush, they were all off to Oxford
<br>But I heard him exclaim as he flew out of sight
<br>"Don't you break it, you Muppets and to all a good night!"


<!-- Date: Fri Dec 8 23:59:04 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10470&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10471  width='300' align='top'></a></td><td>Thanks so much Dee and Steve, for hosting THE PARTY !!!</td></tr></table>
<!-- Author: Jose, Ulrich and Ted -->



<!-- Date: Sat Dec 9 11:32:44 2006 -->
<table border=0><td><tr><td bgcolor=#e0e030>Until December 27, Sebastian Grinstein will be carrying my SPL pager (722-8740). Jose (218-9520) will be SPL on call during this time, and Sebastian will serve as a backup. Thanks a lot, Sebastian.</td></tr></td></table>
<!-- Author: Ulrich -->


<!-- Date: Sat Dec 9 12:38:51 2006 -->
<pre>Quiet time studies. There was an opportunity to go to the collision 
hall in saturday morning. 
We decided (before going) to test SB0W5L2 again with the DAQ. 
That turned to be quite useful in fact. 
The problem with this ladder is just on the last chip on the 
z-side.  
After scratching our heads and receiving the help of the blond-wig 
(thank you Ankush!) we learnt how to test it in the DAQ before 
moving further. It worked, i.e., when setting the last chip in 
the DAQ to one before the last (21 instead of 20) we could 
run fine in NN AND DPS ON (we could not do that otherwise). 
So Jose got the axe and cut the head of the last chip of this 
e052 (z-side). 
We have also, following the instructions, set all ISEL bits, 
BIAS resistor, etc to 0 to minimize power comsuption. 
EOR.</pre>
<!-- Author: Juan Pablo, Jose Enrique, Satyajit, Roberto -->


<!-- Date: Sat Dec 9 17:11:25 2006 -->
<pre>NOISE VS BIAS SCAN 
 
RUN NUMBER: 229819 
 
VOLTAGE      L2A EVENT NUMBER 
-130             1177 
-110             2200  
-90              3387 
-70              5889  
-50              7066 
-30              8362 
-10              9526 
  
COMMENT: FIRST OF THE TAKEN RUNS</pre>
<!-- Author: Juan Pablo, Roberto -->
<!-- Comment: Wed Dec 20 03;17;40 comment by...Oscar -->
The CAENvolts file used was<br>

/cdf/onln/data/svxii/caencontrol/PSfiles/caenvoltsfiles/CAENvolts_12072006_0356PM.dat
<br>
which seems to be the same as the previous one (i.e. the one used in the previous signal-to-bias scan).
<!-- Date: Sat Dec 9 17:48:21 2006 -->
<pre>NOISE VS BIAS SCAN 
RUN NUMBER: 229850 
 
EXTENDED: 
NUM.       VOLTAGE        FIRST L2 EVENT      LAST L2 EVENT 
1             120              1                   1132 
2             100           1149                   2135 
3             95            2179                   3200 
4             90            3227                   4213 
5             85            4271                   5221 
6             80            5247                   6268 
7             75            6319                   7305 
8             65            7326                   8208 
9             60            8244                   9229 
10            55            9265                  10215 
11            45           10266                  11253 
12            40           11269                  12219 
13            35           12248                  13208 
14            25           13389                  14352 
15            20           14381                  15331 
16            15           15353                  16339 
17             7           16367                  17317 
18             5           17352                  18372 
19             3           18398                  19400 
20             0           19432                  20640 
 
MINIMUM: 
 
21           130           20707                  21799 
22           110           21825                  22811 
23            90           22844                  23830 
24            70           23854                  24840 
25            50           24859                  25810 
26            30           25826                  26812 
27            10           26857                  27808 
29             0           27839                  28895   </pre>
<!-- Author: Juan Pablo, Roberto -->
<!-- Comment: Sat Dec  9 18;04;27 comment by...Juan Pablo and Roberto -->
<pre>WE experienced the same problems with ladders SB0W5L2 and
SB3W9L2 (high DVDD current showing pinkies) that already hapenned in preivous scans (see for example the previous week). We use RC and selected run configuration CODLSTAR and did a config that fix the DVDD currents to the usual values.</pre>


<!-- Date: Sat Dec 9 18:17:02 2006 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10472&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10473' ></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10478&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10479' ></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10474&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10475' ></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10476&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10477' ></a></center>
<!-- Author: Juan Pablo and Roberto -->
<!-- Comment: Sat Dec  9 18;18;17 comment by...Juan Pablo and Roberto -->
<pre>IBias current for two ladders (ISL and SVX examples) and
DVDD current behaviour during noise vs bias scan on 
above mentioned ladders.</pre>


<!-- Date: Sat Dec 9 21:01:25 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10480&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10481  width='300' align='top'></a></td><td>SvtSpyMon plot fine; SVXMon fine; init.lum. 74e32; L1A - 26Khz; L2A 450Hz; dead time 4%</td></tr></table>
<!-- Author:  Juan Pablo -->


<!-- Date: Sat Dec 9 21:35:31 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10482&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10482  width='300' align='top'></a></td><td>unmarked this cell</td></tr></table>
<!-- Author: gold -->


<!-- Date: Sat Dec 9 21:49:37 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10483&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10483  width='300' align='top'></a></td><td>reset </td></tr></table>
<!-- Author: gold -->

<!-- Date: Sat Dec 9 22:06:39 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W5L2 
<li>problem n: 1829 
<li>Status: needs_observation
<li>Type: Chip_other
<li>Action: Change_last_chip
<li>entered by: fernand 
<li>description is: he problem with this ladder is just on the last chip on the  z-side.   After scratching our heads and receiving the help of the blond-wig  (thank you Ankush!) we learnt how to test it in the DAQ before  moving further. It worked, i.e., when setting the last chip in  the DAQ to one before the last (21 instead of 20) we could  run fine in NN AND DPS ON (we could not do that otherwise).  So Jose got the axe and cut the head of the last chip of this  e052 (z-side).  We have also, following the instructions, set all ISEL bits,  BIAS resistor, etc to 0 to minimize power comsuption.  I am going to change the AVDD limits acordingly. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B0W5&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Sat Dec 9 22:13:03 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W5L2 
<li>problem n: 1829 
<li>Status: needs_observation
<li>Type: AVDD2
<li>Action: IMON_limits
<li>entered by: fernand 
<li>description is:  since we chopped last chip of this ladder I am going to lower the limits by 80mA<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>795.89</td><td>755</td></tr>
<tr><td><b>Lower</b></td><td>770</td><td>700</td></tr>
<tr><td><b>Upper</b></td><td>825</td><td>785</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B0W5&layer=L2">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Sat Dec 9 23:56:43 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10484&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10484  width='300' align='top'></a></td><td>unmarked and hrr</td></tr></table>
<!-- Author: gold -->


<!-- Date: Sun Dec 10 00:19:16 2006 -->
<h3>A bunch of resonances</h3> 
Checking my e-mail and the e-log, I noticed that we pulled a bunch of resonances during the last 1/2 hour. Since the lumi-enabled triggers at 50e30 kicked in, the L1A rate was as high as 34 kHz. I haven't seen that in a while. The had a problem with the TSI earlier, but Greg fixed it. It is not clear to me why the L1A rate is so high.
<!-- Author: Ulrich -->
<!-- Comment: Sun Dec 10 00;35;41 comment by...Ulrich -->
Thinking a little bit while brushing my teeth it came to me: this is a 36x24 store! The measured luminosity is distributed on 24 collisions instead of 36, so that the per-bunch luminosity is higher and fixed instantaneous luminosity. So the lumi-enabled triggers are enabled earlier that usual.


<!-- Comment: Sun Dec 10 08;22;58 comment by...Mark -->
Since triggers in general do not scale linearly with luminosity, I guess it is no suprise that the L1A rate should be higher with less buches, but more luminosity per bunch, than it would be with the same number of p/pbar but more bunches.
<!-- Date: Sun Dec 10 06:15:05 2006 -->
<pre>I was paged at 5. ACNET refuses to work and there is nothing 
monitoring the beam so we are on Stdby. Steve Hahn is here. Rebooting the console did not help. It seems the problem is in MCroom end (they also have experienced problems with a monitoring computer). We are waiting ..</pre>
<!-- Author: Juan Pablo. -->
<!-- Comment: Sun Dec 10 08;35;59 comment by...Ulrich -->
I just called and talked with Steve Hahn to suggest an alternative way of getting the ACNET information, via the <a href="http://www-bd.fnal.gov/controls/public/linux-console.html">ACNET Java console</a>. I also pointed him to Ron Moore's new running averages of TevMon parameters on ACNET page E7 (under junk, subpage 9). With such a setup, we would not be blind any more (it works fine from home), except the TevMon decision. Juan Pablo is around, and Steve and he will judge if this is enough monitoring.

<!-- Comment: Sun Dec 10 10;56;02 comment by...Jose -->
<pre>09:56:51-   CDF's ACNET problem was traced to a failed network switch. It has been replaced. - DJC
-- Sun Dec 10 10:08:24 comment by...DJC --  Steve Conlon and Nino Strothman performed the troubleshooting and replacement.
</pre>


<!-- Date: Sun Dec 10 11:55:20 2006 -->
<pre>New trigger test. As usual we try 1st wo.silicon. Run no. 229893 
Rates are 18.5 KHz for L1A (before starting this run it was 
approximately the same), 142 Hz for L2A (being 270 before this 
run). Dead time is 0.27 % (1.37 before). 
We wait for 5 minutes. 
Including silicon . Run no. 229896 
L1A 17.8 KHz, L2A ~200sh, dead time 1.07 % 
No prolems found.</pre>
<!-- Author: Juan Pablo and Satyajit -->


<!-- Date: Sun Dec 10 14:33:54 2006 -->
<pre>New store (5116). Lumi at start of run 117E30. 
L1A 20 Khz, L2A 330 Hz. 
Dead time 3 %. 
Waiting for SVTSpyMon and SVXMon plots to get filled.</pre>
<!-- Author: Juan Pablo -->


<!-- Date: Sun Dec 10 14:48:09 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10485&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10485  width='300' align='top'></a></td><td><h3>Store 5116 Init. lumi. 121.02 e^30</h3> 
Store started smoothly with silicon included from the start.</td></tr></table>
<!-- Author: Juan Pablo -->


<!-- Date: Sun Dec 10 20:33:04 2006 -->
<h3> 
Summary of the week: 
<ul>  
Along the week the usual hockerizations here and there and changes in the 
IMON_limits. 
<li> <b>Monday: </b> trigger test </li> 
<li> <b>Tuesday: </b> new store (180 E30) weird <a href='http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=330&frame=2&anchor=22:42:20'> isl trip </a> </li> 
<li> <b>Wednesday: </b> new store at 170 E30 but Tevatron abort. Quiet time  
<a href='http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=330&frame=2&anchor=15:49:19'> 
studies </a> . New store 132 E30</li> 
<li> <b>Thrusday:</b>SB5W10L0 dropped 40 mA; b0svx07 <a href='http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2006&action=view&page=927&frame=2&anchor=07:10:08.902'> failing coldstart  </a>. Bunch of yellows in SVXMON at beggining of run (restarted fixed problem).  Bias scans for L00.</li> 
<li> <b>Friday: new store with 170 E32. VRB crate b0svx09 is not included in the power supply monitoring and Ankush & Burhard party !</b> </li> 
<li> <b>Saturday: quiet time studies with e052 and noise vs bias scans; store with 74E32</b> </li> 
<li> <b>Sunday:Store 5116 with 121.02 e^30</b> </li> 
</ul> 
</br> 
 IBIAS for SB2W9L4 set to ignore for the moment </br> 
 Rasnik Work: New Ntupler, SVXMon with new Slides, PSMon.exe and IMON: bugfix release</br> 
 I have enjoied the music and the pinky voice. 
</h3>
<!-- Author: Juan Pablo -->