<!-- Title: 10:52:26  Mon Aug 14 2006 -->
<!-- Crewchief: Ulrich (MPC) -->
<!-- Op1: Ricardo (shadow) -->
<!-- Op2: ankush (SPL) -->
<!-- Op3: &nbsp; -->
<!-- Op4: &nbsp; -->
<!-- Op5: &nbsp; -->
<!-- Op6: &nbsp; -->
<!-- Notes: -->
<pre>Plans for the week: 
 -Clean up of problem database. 
 -If 3 hs of quiet time do a bias scan. 
 -Investigate ISL cooling problem. 
</pre>


<!-- Date: Mon Aug 14 11:01:49 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9545&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9545  width='300' align='top'></a></td><td>We were paged by the rise of AGIGI2.  
The ace was told to page us again if the limit is about 5. 
We'll call MCR if that happens. 
</td></tr></table>
<!-- Author: Ulrich & Ricardo -->
<!-- Comment: Mon Aug 14 11;55;54 comment by...Ricardo & Ulrich -->
We asked the shift crew to call MCR about AGIGI2. They did a tune change, and AGIGI2 is back to 3.5e9.


<!-- Date: Mon Aug 14 11:57:48 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9550&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9550  width='300' align='top'></a></td><td><h3>A old PRB entry stills needs to be addressed</h3> 
 
<p>In the process of clearing up <a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=265&frame=2&anchor=12:02:12'> 
old PDB entry</a>, I found one for LB0W2L3.  Chip 2 appears not to be seeing any physics since  9/9/05.  Here is the latest ADCMon plot and it still looks the same.  Should check with offline if this ladder is really seeing physics or not.</p> 
 
</td></tr></table>
<!-- Author: Ankush -->
<!-- Comment: Thu Aug 17 11;05;33 comment by...Adam Scott -->
This is NOT the latest ADC mon plot.  You must have hit "Plots1" by mistake.  This is from run number 185848 (The run number is displayed in hex on the plot).
<!-- Comment: Thu Aug 17 11;14;00 comment by...Adam Scott -->
ADC dist in recent run <a href=
'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=314&frame=2&anchor=11:11:53'>
here</a>.
<!-- Date: Mon Aug 14 12:00:32 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: LB0W2L3 
<li>problem n: 1529 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: Monitoring
<li>entered by: amitra 
<li>description is: <p>Chip 2 for this ladder appears not have been seeing any physics since 9/9/05.  The latest ADCMon plot for chip 2 can be found <a href= 'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=314&frame=2&anchor=11:57:48'> here</a>.  I'm transferring this to the monitoring group.  They should check the offline efficiency for this chip...is it seeing physics or not?</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=L00&wedge=B0W2&layer=L3">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Mon Aug 14 12:06:00 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9551&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9551  width='300' align='top'></a></td><td>Tev tune changes when AGIGI2 went down. Apparently they changed the proton vertical tune. The plot is saved in ACNET page D44 under Tev Tunes.</td></tr></table>
<!-- Author: Ulrich -->

<!-- Date: Mon Aug 14 12:07:20 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB3W5L1 
<li>problem n: 1477 
<li>Status: fixed
<li>Type: Chip_other
<li>Action: Monitoring
<li>entered by: amitra 
<li>description is: <p>This ladder is no longer the slowest ladder.  It is not reading out any faster...instead there are now slower ladders.  This one will be reinvestigated when it becomes the slowest ladder...not a priority now.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B3W5&layer=L1">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Mon Aug 14 13:30:57 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9552&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9552  width='300' align='top'></a></td><td>The shift crew has discovered a  
<a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2006&action=view&page=583&frame=2&anchor=12:24:00.891'> 
Bias1 pinkie in IB1W0L3</a>. Plotting the history of the current shows that it increases quite steeply after the shutdown. We will bump up the limits but keep an eye on it. </td></tr></table>
<!-- Author: Ulrich -->
<!-- Comment: Mon Aug 14 15;38;35 comment by...Ricardo & Ulrich -->
We have checked the temperature history of the associated cooling line, W1.1 (supplied from W2 and returned into W4, other ladders: f101, f143, f151, f153). The current input temperature is 5.4 °C, and the output is 6.1 °C. Before the shutdown, the cooling line was a little warmer (input: 6.4°C, output 7.0°C), but the gradient is about the same. So an increase in temperature, at least at the level of the cooling line, cannot be the cause for the increase in bias current.<p>
Idea: What if the thermal conductivity of the water has decreased because of the bubbles? If the heat is still transported away properly, could the sensor actually be warmer than before, and the cooling lines could still be as cold as they were?
<!-- Date: Mon Aug 14 13:38:26 2006 -->
<h3>Roger Dixon's Accelerator talk added to Silicon Talks page</h3> 
 
<p>In the current Fermilab-CERN Hadron Collider Physics Summer school, there was a nice <a href="http://www-cdf.fnal.gov/internal/silicon/talks.html">acclerator physics talk</a> given by Roger Dixon.  I have added this to the Silicon Talk page for our education.</p>
<!-- Author: Ankush -->
<!-- Comment: Mon Aug 14 15;03;09 comment by...Ankush -->
<p>I have also added the second Accelerator talk.  you can find it using the link above.</p>

<p><em>thanks to Ron for pointing that out.</em></p>
<!-- Date: Mon Aug 14 14:13:46 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB1W0L3 
<li>problem n: 1714 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: husemann 
<li>description is: Change limits for bias 1, IB1W0L3. Increase after the shutdown is unusally large and should be cheched again soon.  <table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>135</td><td>145</td></tr>
<tr><td><b>Lower</b></td><td>0.5</td><td>0.5</td></tr>
<tr><td><b>Upper</b></td><td>145</td><td>160</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B1W0&layer=L3">report</a></ul>
<!-- Author: Problem DB -->





<!-- Date: Mon Aug 14 16:38:20 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9553&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9553  width='300' align='top'></a></td><td><h3>CCE1 Output temperature over the weekend</h3> 
 
<p>Over the weekend, the bad ISL cooling line CCE1 jumped up a bit (& also down a bit aswell).</p></td></tr></table>
<!-- Author: Ankush -->


<!-- Date: Mon Aug 14 17:32:53 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9554&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9554  width='300' align='top'></a></td><td>The aces just notified us that the output temperature of CCE1.1 suddenly jumped up from 18.5 to 20.5 °C, apparently uncorrelated to anything else. As before, we instruct them to page us if the temperature exceeds 22°C.</td></tr></table>
<!-- Author: Ricardo & Ulrich -->


<!-- Date: Mon Aug 14 17:46:42 2006 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9555&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9555' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9556&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9556' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9557&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9557' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9558&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9558' width='300'></a></center>
<!-- Author: Ankush -->
<!-- Comment: Mon Aug 14 18;12;37 comment by...Ankush -->
<h3>The case of the odd bias</h3>

<p>The graphs above are the bias history for IB5W1, Layer 0,1,2 and 3.  The <font color="red">bias 0 is red</font> and bias1 is black.</p>

<p>While investigating an old PDB thread, I spotted a curious feature.  The old PDB thread was an IMON limit change for f152, bias 1.  It had jumped in current from ~50μA to 600μA.  This would be an indicator for a pinhole.  Out of curiousity I looked at bias 0.  Strangley enough the bias 0 <em>dropped</em> in current at the same time.....very suspicious.</p>

<p>I then looked at f150, f151 and f153.  Guess what...you see the same effect.  Now all this occured on DS Day 1829 which is 4 Jan 06.  On this 
<a href=
'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=282&frame=2&anchor=18:36:02'>
day</a>, there was an access to fix IB0W3; this CAEN PS is in the neighbouring slot to IB5W1.</p>

<p>So I believe the Bias0 and Bias1 for this PS were mixed up. Whenever the next access comes up, we should undo the swap.  IB5W1 lives in SW Top Top (yuck :-( )</p>
<!-- Date: Mon Aug 14 17:55:48 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9559&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9559  width='300' align='top'></a></td><td><h3>ISL CCE1 just dropped down</h3> 
 
<p>Here is the recent <b>drop</b> for the ISL CCE1 temperature.  A while ago it had jumped up to 20C and then it suddenly jumped down to 19C.  Very odd indeed</p></td></tr></table>
<!-- Author: Ankush -->


<!-- Date: Mon Aug 14 18:16:48 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB1W5L2 
<li>problem n: 374 
<li>Status: needs_access
<li>Type: BIAS
<li>Action: Diagnosis_update
<li>entered by: amitra 
<li>description is: <p>The bias cables for IB1W5 has been mixed up.  An access will be needed to undo this.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B1W5&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Mon Aug 14 18:22:09 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W8L0 
<li>problem n: 633 
<li>Status: needs_observation
<li>Type: Chip_bit_error
<li>Action: Diagnosis_update
<li>entered by: amitra 
<li>description is: <p>This is an old entry which the Monitoring group should look at.  If this ladder looks OK, then close this thread.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B0W8&layer=L0">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Mon Aug 14 18:53:12 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB5W3L4 
<li>problem n: 1591 
<li>Status: needs_work
<li>Type: Chip_capid
<li>Action: Diagnosis_update
<li>entered by: amitra 
<li>description is: <p>Sparsing out the chip doesn't help as CAP-ID is always read out. the next step is to un-sparse the chip and check:  <ol> <li> The data has no digitial error </li> <li> The chip really sees physics and it is not returning charge from the wrong pipeline.</li> </ol> 
<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: Mon Aug 14 18:56:56 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB2W1L2 
<li>problem n: 928 
<li>Status: fixed
<li>Type: Chip_bit_error
<li>Action: Diagnosis_update
<li>entered by: amitra 
<li>description is: <p>Looking at recent BitReporter results, the error rate for this ladder is < 2%.  Close this thread for now.  If it gets >10% then reopen and figure out what is wrong.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B2W1&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Mon Aug 14 19:00:44 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB4W8L3 
<li>problem n: 1644 
<li>Status: fixed
<li>Type: RX
<li>Action: Init_RB_mask
<li>entered by: amitra 
<li>description is: <p>The INIT READBACK mask has been removed and there have been no initialisation errors.  Consider this thread fixed.</p>  
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B4W8&layer=L3">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Mon Aug 14 19:19:42 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB2W11L0 
<li>problem n: 1643 
<li>Status: fixed
<li>Type: Unknown
<li>Action: Diagnosis_update
<li>entered by: amitra 
<li>description is: <p>In the last 30 days of running, this ladder is running error-free. Closing this thread.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B2W11&layer=L0">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Mon Aug 14 19:21:46 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB2W8L0 
<li>problem n: 1497 
<li>Status: fixed
<li>Type: Chip_bit_error
<li>Action: Diagnosis_update
<li>entered by: amitra 
<li>description is: <p>This ladder is running error-free/ <1% error-rate for the last 30 days. Closing this thread.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B2W8&layer=L0">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Mon Aug 14 19:22:10 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB2W8L0 
<li>problem n: 1642 
<li>Status: fixed
<li>Type: Chip_capid
<li>Action: Diagnosis_update
<li>entered by: amitra 
<li>description is: <p>This ladder is running error-free/ <1% error-rate for the last 30 days. Closing this thread.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B2W8&layer=L0">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Mon Aug 14 19:24:15 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB2W2L0 
<li>problem n: 1548 
<li>Status: fixed
<li>Type: Chip_bit_error
<li>Action: Monitoring
<li>entered by: amitra 
<li>description is: <p>This ladder is running error-free/ <1% error-rate for the last 30 days. Looks like the RX swap did the trick. Closing this thread.  </p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B2W2&layer=L0">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Mon Aug 14 19:40:33 2006 -->
<h4>Interlock Test Stand: Update</h4> 
Today I found a DSUB-9 cable for an RS232 serial link to configure the new ethernet interface card. So I connected with the <tt>CTIDiag</tt> tool and changed the default IP address to 192.168.51.2 (just as one of the cards in the real system). Now I can talk with the card via its web interface. We have to wait for the new test stand PC and the iFix licence to arrive before we can proceed.
<!-- Author: Ulrich -->

<!-- Date: Mon Aug 14 20:02:31 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB2W1L3 
<li>problem n: 65 
<li>Status: fixed
<li>Type: Chip_bit_error
<li>Action: Diagnosis_update
<li>entered by: ricardo 
<li>description is: Error rate is lower than 1%. It is deemed not worthy of our attention (wise Ankush words). 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B2W1&layer=L3">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Mon Aug 14 20:15:33 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB0W3All 
<li>problem n: 1523 
<li>Status: fixed
<li>Type: Wedgewide_other
<li>Action: Diagnosis_update
<li>entered by: ricardo 
<li>description is: The current values looks stable after the shutdown.Declared it fixed.   
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B0W3&layer=All">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Tue Aug 15 00:53:07 2006 -->
<pre>I am staying around, so I will look after this shoot. You guys 
enjoy the next one and dream with little angles!</pre>
<!-- Author: Juan Pablo. -->
<!-- Comment: Tue Aug 15 01;01;38 comment by...Ulrich -->
Thanks a lot, Juan Pablo. I was already wondering why they did not page me upon pbar load.


<!-- Date: Tue Aug 15 01:33:05 2006 -->
<pre>Lostp and lostpb in ACNET are not displaying.  
BPPAGC and BOAAGC seem fine.  
We have called MRC and they are looking into that right now.</pre>
<!-- Author: Juan Pablo. -->
<!-- Comment: Tue Aug 15 01;39;28 comment by...Juan Pablo. -->
<pre>MCR called .The losses are so small that we monitoring 
program does not even show them. Waiting for solving
a problem with the TSU (CCU 14 channel 3).</pre>

<!-- Comment: Tue Aug 15 02;13;20 comment by... Juan Pablo -->
<pre>I bet it is BSC related. It was accidentaly off (preventing
us from running)</pre>


<!-- Comment: Tue Aug 15 06;41;28 comment by...Ankush -->
<p>Yes...It is related to the BSC...that's how LOSTP & LOSTPB are measured. See
<a href=
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2006&action=view&page=585&frame=2&anchor=02:04:14.853'>
shift e-log</a> for details. According to Mary, it is related to the earlier CLC work.</p>

<!-- Comment: Tue Aug 15 09;11;49 comment by...Ankush -->
<p>One other comment.  I know we like to blame MCR for all our woes.  But there are times where we should look at ourselves first.  This is one of those occasions.</p>  

<p>As our "super-hot" shift-crew and other CDF colleagues are not aware of each other's systems, we should know how to cross-check the beam monitoring systems.  There is a lot of redundancy and cross-checks in the system. Please familiarise yourself with <a href="http://www-cdfonline.fnal.gov/ops/acnet/ACNET_beamquality/">Rick's page</a> of beam monitoring devices and <a href="http://www-cdf.fnal.gov/internal/WebTalks/Archive/0605/060512_cdf_silicon_workshop_day_2/08_060512_cdf_silicon_workshop_day_2_RadTalk_tesarek_Tesarek_SiWorkshop06_ucsb.pdf">
Rick's UCSB talk</a>.</p>

<p><em>But shouldn't the ACEs and shift crew know this?</em>.  Yes....but somehow this is always lost</p>
<!-- Date: Tue Aug 15 02:18:26 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9560&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9560  width='300' align='top'></a></td><td>SVTSPY Mon plot. 
SVXMon is fine. 
Initial luminosity = 120 E30 
Store number = 4905</td></tr></table>
<!-- Author:  Juan Pablo -->



<!-- Date: Tue Aug 15 08:36:53 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9561&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9561  width='300' align='top'></a></td><td>Bias in channel e270 is going back and forth to pink. 
The plot shows  that the bias current is going up with the expected slope. 
 </td></tr></table>
<!-- Author: Ricardo -->

<!-- Date: Tue Aug 15 08:45:17 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB2W7L0 
<li>problem n: 1700 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: ricardo 
<li>description is: The Bias current keeps going up. Bump the limits again.<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>66</td><td>66</td></tr>
<tr><td><b>Lower</b></td><td>0.5</td><td>0.5</td></tr>
<tr><td><b>Upper</b></td><td>110</td><td>120</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B2W7&layer=L0">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Tue Aug 15 08:54:26 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9563&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9563  width='300' align='top'></a></td><td>Bias0 on channel f103 is going up (see plot). This is consistent with our previous entry  <a href= 
'/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=314&frame=2&anchor=13:30:57'> 
 here </a> where the same behaviour is seen in Bias1.</td></tr></table>
<!-- Author: Ricardo -->
<!-- Comment: Tue Aug 15 09;00;08 comment by...Ricardo -->
<pre>Forgot to mention that the slope of Bias0 and Bias1 is much steeper after the shutdown. We will increase this channel limit and leave it on observation.
</pre>


<!-- Date: Tue Aug 15 09:06:58 2006 -->
<h4>New shelves for the Silicon office</h4> 
In our ongoing fight against the second law of thermodynamics, we have asked Craig Olson to install more shelves in the silicon office. He came around with a tape measure.
<!-- Author: Ulrich -->

<!-- Date: Tue Aug 15 09:09:41 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB1W0L3 
<li>problem n: 1714 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: ricardo 
<li>description is: Bias 0 and Bias 1 of IB1W0L3 are going up very fast since the shutdown. Bias 1 limit was increased yesterday by Ulrich, now we bump the limits of Bias0<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>110</td></tr>
<tr><td><b>Lower</b></td><td>0.5</td><td>0.5</td></tr>
<tr><td><b>Upper</b></td><td>110</td><td>120</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B1W0&layer=L3">report</a></ul>
<!-- Author: Problem DB -->




<!-- Date: Tue Aug 15 09:35:00 2006 -->
<h3>Cooling News</h3> 
 
<ul> 
<li>I have checked temperatures related to the current pinkie in f201 (CCW2.1 from W1-SUP to W3-RET). Unfortunately, the RTD on the return line is broken. The supply tmperature is 7.3°C (was around 8.4°C before the shutdown)</li> 
<li>Plotting the SVX alcove temperatures over the last two month, I observed an increase in the chiller return temperature (-9.5°C → -8.0°C), while all other temperatures are more or less constant. This has nothing to do with temperature probe miscalibrations. The chiller is running at its limit with a set point of -10°C and a measured temperature of -9°C. Why are we heating the SVX coolant more than before, and increasingly so???</li> 
<li>I have asked Bill Noe to ship two additional samples for water analysis: SVX coolant and a pristine water-glycol mixture.</li> 
</ul>
<!-- Author: Ulrich -->


<!-- Date: Tue Aug 15 09:36:52 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9564&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9564  width='300' align='top'></a></td><td>Bias 0 (plot) and Bias 1 (not shown) on f201 are growing too fast. Same behaviour we saw on f103. These two ladders do not belong to the same cooling circuit. 
We will bump the Bias 0 limits of this guy and keep it in observation. It is likely we will have to bump the limits of Bias 1 later on.</td></tr></table>
<!-- Author: Ricardo -->

<!-- Date: Tue Aug 15 09:43:47 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB2W0L1 
<li>problem n: 1560 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: ricardo 
<li>description is: Need to bump IMON limits to 150. Note that although the last entry indicates that the maximum limit is 150, Imon reports it's only 140. So we are going to 150. <table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>86</td><td>86</td></tr>
<tr><td><b>Lower</b></td><td>0.5</td><td>0.5</td></tr>
<tr><td><b>Upper</b></td><td>140</td><td>145</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B2W0&layer=L1">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Tue Aug 15 09:54:43 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9565&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9565  width='300' align='top'></a></td><td>Bias 1 (plot) and Bias 0 (not shown) in f421 have roughly the same behaviour of going way up as we saw in other ladders (f102, f201, e270 and other we probably missed) 
We'll bump the Imon limits. 
</td></tr></table>
<!-- Author: Ricardo -->

<!-- Date: Tue Aug 15 10:01:33 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB4W2L1 
<li>problem n: 1691 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: ricardo 
<li>description is: Raising limit on Bias1. <table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>75</td><td>85</td></tr>
<tr><td><b>Lower</b></td><td>0.5</td><td>0.5</td></tr>
<tr><td><b>Upper</b></td><td>110</td><td>120</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B4W2&layer=L1">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Tue Aug 15 10:08:38 2006 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9566&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9566' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9567&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9567' width='300'></a></center>
<!-- Author: Ulrich -->
<!-- Comment: Tue Aug 15 10;29;05 comment by...Ulrich -->
<h3>Bias currents versus luminosity</h3>
The above plots show the bias currents of an ISL ladder (f103) and an SVX ladder (e270) as a function of the integrated luminosity. The pre-shutdown luminosity is about 1592/pb. After the shutdown, the bias currents increase more steeply as a function of luminsity, both for SVX and ISL. The effect is bigger for ISL, but still visible for SVX.
<p>
These plots have been created like this: I have skimmed Ben's ntuples to extract only the bias currents and voltages. At the same time, I added a mapping of DS Days to integrated luminosity. Antonio runs a script every day which spits out a
<a href="http://nucsb03.fnal.gov/~boveia/luminosity/dsday_dlum.ascii">table of the integrated luminosity as a function of DS Day</a>. The luminosity is the CDF luminosity as recorded by the CLC. It would be good if the luminosity became a standard variable in Ben's ntuple. You can find the skim under <tt>b0sili01:~husemann/psplotter</tt>
<!-- Date: Tue Aug 15 10:12:48 2006 -->
<h3>b0sili01 under heavy load</h3> 
 
<p>3 big jobs have been started on b0sili01.  So it is running extra slow.  Please refrain from using b0sili01 for the time being.</p> 
 
<p>However b0sili02 is begging to be used !!</p>
<!-- Author: Ankush -->


<!-- Date: Tue Aug 15 11:08:50 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W1L2 
<li>problem n: 1635 
<li>Status: fixed
<li>Type: Chip_capid
<li>Action: Diagnosis_update
<li>entered by: amitra 
<li>description is: <p>CAP-ID for chip 85 is now OK.  So closing this thread.However the data from chip 85 is corrupted...see thread 2</p> 
<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: Tue Aug 15 11:12:14 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W0L2 
<li>problem n: 1634 
<li>Status: fixed
<li>Type: No_Init
<li>Action: Diagnosis_update
<li>entered by: amitra 
<li>description is: <p>since removing this mask, there have been no reported initialisation problems.  Closing this thread.</p> 
<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: Tue Aug 15 11:26:43 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB5W0L0 
<li>problem n: 647 
<li>Status: fixed
<li>Type: Chip_bit_error
<li>Action: Diagnosis_update
<li>entered by: amitra 
<li>description is: <p>Over the last 30 days, this ladder has been running error free in the bit reporter.  Closing this thread.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B5W0&layer=L0">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 14:27:48 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB0W1L1 
<li>problem n: 1600 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: Monitoring
<li>entered by: ricardo 
<li>description is: As with many other ladders, this one (Bias0 and Bias1) are going up at a large pace. Keep monitoring over the next weeks.   
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B0W1&layer=L1">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 14:36:05 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB2W1L0 
<li>problem n: 1595 
<li>Status: fixed
<li>Type: BIAS
<li>Action: Diagnosis
<li>entered by: ricardo 
<li>description is: Limits are fine. Bye. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B2W1&layer=L0">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 14:44:21 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB4W0L3 
<li>problem n: 1596 
<li>Status: needs_longterm_monitoring
<li>Type: BIAS
<li>Action: Monitoring
<li>entered by: ricardo 
<li>description is: Keep monitoring Bias0 and Bias1 for 1 month. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B4W0&layer=L3">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 14:45:23 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W0L1 
<li>problem n: 1382 
<li>Status: fixed
<li>Type: RX
<li>Action: Monitoring
<li>entered by: amitra 
<li>description is: <p>Looks like this ladder has been running error free for the last 30 days.  Closing this thread.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B0W0&layer=L1">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 14:49:07 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB3W10L4 
<li>problem n: 1651 
<li>Status: fixed
<li>Type: Optical_other
<li>Action: Diagnosis_update
<li>entered by: amitra 
<li>description is: <p>This ladder has been running error free for the last 30 days.  It looks like plugging a fibre into an FTM really helps :-)</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B3W10&layer=L4">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 14:50:34 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB3W10L4 
<li>problem n: 1500 
<li>Status: fixed
<li>Type: DVDD
<li>Action: PS_work
<li>entered by: amitra 
<li>description is: <p>Something magic happened during the shutdown.  Now this ladder no longer trips whenever the North Wall moves.  Call this fixed for now.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B3W10&layer=L4">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 15:26:32 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W8L1 
<li>problem n: 1637 
<li>Status: fixed
<li>Type: Chip_bit_error
<li>Action: Diagnosis_update
<li>entered by: amitra 
<li>description is: <p>No errors seen in the bit-reporter for 30 days.  Closing this thread.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B0W8&layer=L1">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 15:28:52 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB0W0L0 
<li>problem n: 1019 
<li>Status: fixed
<li>Type: Chip_bit_error
<li>Action: Diagnosis_update
<li>entered by: amitra 
<li>description is: <p>No bit-errors seen in the bit-reporter for 30 days.  Calling this fixed and closing the thread.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B0W0&layer=L0">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 15:30:40 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB1W3L1 
<li>problem n: 1597 
<li>Status: fixed
<li>Type: BIAS
<li>Action: Diagnosis_update
<li>entered by: ricardo 
<li>description is: This Ladder seems fine. Called it fixed.   
<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: Tue Aug 15 15:36:25 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W2L4 
<li>problem n: 1683 
<li>Status: fixed
<li>Type: Unknown
<li>Action: Diagnosis_update
<li>entered by: amitra 
<li>description is: <p>Closing this thread for now.  It is now superseeded by thread 1243.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B1W2&layer=L4">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 15:45:25 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB4W3L4 
<li>problem n: 1599 
<li>Status: fixed
<li>Type: BIAS
<li>Action: Diagnosis_update
<li>entered by: ricardo 
<li>description is: This ladder looks fine in ADCMon. The Vias0 current is steady around 1450.   
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B4W3&layer=L4">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 15:51:26 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB1W5L3 
<li>problem n: 1603 
<li>Status: fixed
<li>Type: BIAS
<li>Action: Diagnosis_update
<li>entered by: ricardo 
<li>description is: This ladder seems to have a proper Bias (line 0 & 1). Call it fixed.  
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B1W5&layer=L3">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 15:58:37 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W8L2 
<li>problem n: 4 
<li>Status: fixed
<li>Type: AVDD2
<li>Action: Diagnosis_update
<li>entered by: amitra 
<li>description is: <p>This ladder has been running with no bit-errors for the last 30 days  Closing this thread.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B1W8&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 16:01:14 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W5L3 
<li>problem n: 867 
<li>Status: fixed
<li>Type: AVDD2
<li>Action: Chip_bit_changes
<li>entered by: amitra 
<li>description is: <p>This ladder has been running error-free for the last 30 days. Closing this thread.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B0W5&layer=L3">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 16:05:26 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB4W0L1 
<li>problem n: 1697 
<li>Status: fixed
<li>Type: PC_Temperature
<li>Action: Added_hdwdb
<li>entered by: amitra 
<li>description is: <p>The ladder has been running for a few weeks with no problems.  The cooling line is still compromised but it is enough for the ladder to stay powered.  Calling this fixed for now and closing this thread.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B4W0&layer=L1">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 16:08:27 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB4W0L3 
<li>problem n: 1695 
<li>Status: fixed
<li>Type: PC_Temperature
<li>Action: Diagnosis_update
<li>entered by: amitra 
<li>description is: <p>The ladder has been running for a few weeks with no problems. The cooling line is still compromised but it is enough for the ladder to stay powered. Calling this fixed for now and closing this thread.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B4W0&layer=L3">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Tue Aug 15 16:08:27 2006 -->
<h3>CD World Domination Plans</h3> 
Just found this in the MCR e-log: 
<pre> 
14:52:43-  Computing Division mandates that all flying wire frontends be rebooted by 17:00 or else the frontends will be knocked off the network. We really hope that the wires don't fly through the collider store or the pbar stash that has been accumulated. It would be a shame if we experienced beam loss from this. - DJC 
</pre> 
No comment...
<!-- Author: Ulrich -->
<!-- Comment: Tue Aug 15 17;01;05 comment by...Ulrich -->
<pre>
16:47:41-   All Instrumentation windows based instruments have been restarted. - dln
-- Tue Aug 15 16:48:27 comment by...dln --  The Tev wire fly at 1626 was missed during the rebooting operation.
</pre>
<!-- Date: Tue Aug 15 16:18:03 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB0W2L1 
<li>problem n: 1628 
<li>Status: fixed
<li>Type: BIAS
<li>Action: Diagnosis_update
<li>entered by: ricardo 
<li>description is: Bias 0 looks fine. Bias 1 has very low read of about 7.  The history shows that Bias 0 is growing as expected. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B0W2&layer=L1">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 16:24:16 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB5W1L2 
<li>problem n: 1690 
<li>Status: fixed
<li>Type: AVDD
<li>Action: PS_work
<li>entered by: alscott 
<li>description is: <p>This ladder hasn't tripped on AVDD since the power supply swap.  Consider this fixed and closing the thread.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B5W1&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 17:11:41 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB1W0L1 
<li>problem n: 1559 
<li>Status: fixed
<li>Type: BIAS
<li>Action: Diagnosis_update
<li>entered by: ricardo 
<li>description is: Bias 0 & 1 look fine and with a reasonable grow in time.Fixed!  
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B1W0&layer=L1">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 17:14:01 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB4W0L4 
<li>problem n: 37 
<li>Status: needs_work
<li>Type: AVDD
<li>Action: Action_request
<li>entered by: amitra 
<li>description is: <p>This ladder needs quiet time to see if can be brought back.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B4W0&layer=L4">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 17:14:58 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB1W2L3 
<li>problem n: 1627 
<li>Status: fixed
<li>Type: BIAS
<li>Action: Diagnosis_update
<li>entered by: ricardo 
<li>description is: Both biases look OK. Call them fixed. . 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B1W2&layer=L3">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 17:16:05 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB4W0L3 
<li>problem n: 1720 
<li>Status: needs_observation
<li>Type: PC_Temperature
<li>Action: Chip_bit_changes
<li>entered by: amitra 
<li>description is: <p>David Stuart pointed out the Phi side of the ladder was changed and <b>not</b> the Z side.  When the next quiet time becomes available, the PHI side should be restored and the Z side should be adjusted.</p>  <p>However there has been an affect of changing BIAS RATIO from 1 to 0.  The mean charge collected has shifted down by ~10%.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B4W0&layer=L3">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 17:20:13 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W8L4 
<li>problem n: 1677 
<li>Status: fixed
<li>Type: AVDD
<li>Action: Monitoring
<li>entered by: amitra 
<li>description is: <p>The AVDD current looks stable now.  Closing this thread.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B0W8&layer=L4">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Tue Aug 15 17:41:26 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9568&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9568  width='300' align='top'></a></td><td>PINK on BIAS_B2W0L2, unmark it</td></tr></table>
<!-- Author: Yanjun -->
<!-- Comment: Tue Aug 15 17;42;55 comment by...Yanjun -->
<pre>It turns to pink again, unmark it once more, now it is yellow</pre>

<!-- Date: Tue Aug 15 17:43:12 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB5W1All 
<li>problem n: 1712 
<li>Status: fixed
<li>Type: VDOIM
<li>Action: Monitoring
<li>entered by: amitra 
<li>description is: <p>The DOIM current looks stable. Closing this thread.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B5W1&layer=All">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 17:43:23 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB5W1All 
<li>problem n: 1713 
<li>Status: needs_observation
<li>Type: VDOIM
<li>Action: Monitoring
<li>entered by: amitra 
<li>description is: <p>The DOIM current looks stable. Closing this thread.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B5W1&layer=All">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 17:54:15 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB3W1L4 
<li>problem n: 1598 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: Diagnosis_update
<li>entered by: amitra 
<li>description is: <p>As far as IMON limits go, 130&#956;A is still OK.  However one should look at the rate of Bias current change.  It seems to be changing at a faster rate. that it did before the shutdown.</p>  <p>Need to check we can explain this increase....it may be luminosity related or it could be an indication of heating due to a compromised ISL cooling.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B3W1&layer=L4">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Tue Aug 15 18:03:55 2006 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9569&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9569' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9570&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9570' width='300'></a></center>
<!-- Author: Ulrich -->
<!-- Comment: Tue Aug 15 18;13;09 comment by...Ulrich -->
Both bias0 and bias1 of f202 are increasing very steeply after the shutdown. Global ISL warming?
<!-- Comment: Tue Aug 15 18;33;25 comment by...Ricardo -->
<pre>Limits were raised from  140 to 160 for both Bias channels.</pre>
<!-- Date: Tue Aug 15 18:08:13 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB2W6L3 
<li>problem n: 1619 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: Monitoring
<li>entered by: ricardo 
<li>description is: The history of the bias current shows sharp fluctuations from 900 to 1500 and back to 900. These fluctuations are not understood, and  an eye must be kept to see how this ladder develops.  
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B2W6&layer=L3">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 18:12:22 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB4W0L1 
<li>problem n: 1561 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: Monitoring
<li>entered by: amitra 
<li>description is: <p>The IMON limits should be OK for now.  However the BIAS0 and BIAS1 currents have been going up steeply after the shutdown.  This ladder is cooled by the compromised cooling line.  So the change in gradient could be due to local heating.</p>  <p>Monitoring group should look at this ladder and note any changes in the bias current gradient.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B4W0&layer=L1">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Tue Aug 15 18:30:54 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB2W0L2 
<li>problem n: 1724 
<li>Status: needs_observation
<li>Type: Unknown
<li>Action: IMON_limits
<li>entered by: ricardo 
<li>description is: Bumped the limits of Bias 0 and Bias 1.<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>76</td><td>76</td></tr>
<tr><td><b>Lower</b></td><td>0.5</td><td>0.5</td></tr>
<tr><td><b>Upper</b></td><td>140</td><td>160</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B2W0&layer=L2">report</a></ul>
<!-- Author: Problem DB -->




<!-- Date: Tue Aug 15 18:49:46 2006 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9571&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9571' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9572&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9572' width='300'></a></center>
<!-- Author: Ankush -->
<!-- Comment: Tue Aug 15 18;51;13 comment by...Ankush -->
<h3>Bias history for IB4W1L1</h3>

<p>The two grpah above are the BIAS current history for IB4W1L4.  The Bias 0 line is drawing current, but the BIAS 1 line has been steadily falling and is now at zero.</p>
<!-- Date: Tue Aug 15 18:49:57 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9574&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9574  width='300' align='top'></a></td><td>What is going on with the Bias0 current of f032 ? 
Bias 1 (not shown) looks ok. 
An access maybe needed to determine whether this is PS problem.</td></tr></table>
<!-- Author: Ricardo -->


<!-- Date: Tue Aug 15 18:51:55 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB0W3L2 
<li>problem n: 717 
<li>Status: needs_access
<li>Type: BIAS
<li>Action: Diagnosis_update
<li>entered by: ricardo 
<li>description is: The history of the Bias0 current of this guy is <a href= '/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=314&frame=2&anchor=18:49:57'> here </a>. An access is needed to determine whether this stems from the PS or not. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B0W3&layer=L2">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Tue Aug 15 18:53:28 2006 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9575&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9575' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9576&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9576' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9577&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9577' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9578&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9578' width='300'></a></center>
<!-- Author: Ankush -->
<!-- Comment: Tue Aug 15 18;56;24 comment by...Ankush -->
<em>sorry, please ignore....this problem has been known since the dawn of time</em>


<!-- Date: Tue Aug 15 18:54:15 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB0W3L2 
<li>problem n: 717 
<li>Status: needs_access
<li>Type: BIAS
<li>Action: Diagnosis_update
<li>entered by: ricardo 
<li>description is: This is the working <a href= 'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=314&frame=2&anchor=18:49:57'> link</a>.     
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B0W3&layer=L2">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Tue Aug 15 19:01:25 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB1W2L1 
<li>problem n: 1507 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: husemann 
<li>description is: Bumping up Bias0 current limit.<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>97.0395</td><td>135.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>130</td><td>200</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B1W2&layer=L1">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 19:04:06 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB1W3L1 
<li>problem n: 1597 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: husemann 
<li>description is: Bumped up Bias0 current limit.<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>70.8421</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>150.0</td></tr></table> 
<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: Tue Aug 15 19:04:06 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB4W1L1 
<li>problem n: 1692 
<li>Status: fixed
<li>Type: BIAS
<li>Action: Diagnosis
<li>entered by: amitra 
<li>description is: <p>Bias1 has been reading zero for a long time. So no surprise that the swaped in CAEN PS also read zero.  This is detailed in thread 1250.  So closing this one now.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B4W1&layer=L1">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 19:06:10 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB2W1L4 
<li>problem n: 1592 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: husemann 
<li>description is: Bumped up Bias0 current limit.<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>??83.6979</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>105.0</td><td>150.0</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B2W1&layer=L4">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 19:07:10 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB5W1All 
<li>problem n: 1713 
<li>Status: fixed
<li>Type: VDOIM
<li>Action: Monitoring
<li>entered by: amitra 
<li>description is: <p>Closing this thread...fixed fixed</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B5W1&layer=All">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 19:09:14 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB1W2L3 
<li>problem n: 1627 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: husemann 
<li>description is: Bumped up Bias1 current limit<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>75.5636</td><td>105.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>105.0</td><td>150.0</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B1W2&layer=L3">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 19:09:14 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB4W1L4 
<li>problem n: 1454 
<li>Status: fixed
<li>Type: BIAS
<li>Action: PS_work
<li>entered by: amitra 
<li>description is: <p>Both BIAS lines see current now.  Currents look fine. So the swapped worked.  Closing this thread for now.</p> 
<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: Tue Aug 15 19:13:22 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB4W0L4 
<li>problem n: 1584 
<li>Status: fixed
<li>Type: BIAS
<li>Action: PS_work
<li>entered by: amitra 
<li>description is: <p>Both BIAS lines are now reading back current.  So the PS swap worked.  Closing this thread.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B4W0&layer=L4">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Tue Aug 15 19:42:54 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9586&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9586  width='300' align='top'></a></td><td><li> 
The last point of the permanent light level  
<a href='http://www-cdfonline.fnal.gov/cgi/internal/elog/det-system-elog.pl?nb=silicon&action=copyentry&page=313&time=13:44:47'> 
 graph </a> 
from the previous week had  a wrong dsday as Jose spotted during the meeting. This is the correct plot. <li> 
 
Also I have automatized a bit the scripts in /data01/pll to avoid errors. If you go to /data01/pll and do ./pll.sh it 
asks you to update the file (pll.dat) with the scope measurements and gives you the dsday. 
 
</td></tr></table>
<!-- Author: Ignacio -->
<!-- Comment: Tue Aug 15 19;46;04 comment by...Ignacio -->
<pre>
Note that if 
you run it form a shell that has run source ~cdfsoft/cdf2.cshrc
the perl script that converts into dsdays breaks.

This is what you see when you run the script. 
[svxii@b0sili01 pll]$ ./pll.sh
Please enter the date mm/dd/yy
08/10/06
DS days conversion ==&gt; 2047
Please update pll.dat with the new measurement

FORMAT: The first 9 entries  in the file are
the readings(in mW) from fibers 2 -10.
Last value is time in DS days
Hit enter when ready

5 Did you really update the file?
Now we run the root macro. Are you sure?

root [0] 
Processing pll.C++(5)...
</pre>

<!-- Date: Tue Aug 15 22:41:24 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB2W9L1 
<li>problem n: 1585 
<li>Status: fixed
<li>Type: DVDD
<li>Action: PS_work
<li>entered by: amitra 
<li>description is: <p>After the power supply swap, the DVDD voltage and current are now stable.  PS swap worked. Now closing this thread.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B2W9&layer=L1">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 22:48:30 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB5W0L2 
<li>problem n: 1652 
<li>Status: fixed
<li>Type: BIAS
<li>Action: PS_work
<li>entered by: amitra 
<li>description is: <p>After the power supply swap, this ladder hasn*#39t tripped on BIAS1 undervoltage.  The CAEN PS swap worked.  Closing this thread.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B5W0&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 22:51:13 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB5W1L4 
<li>problem n: 1707 
<li>Status: fixed
<li>Type: AVDD
<li>Action: Monitoring
<li>entered by: amitra 
<li>description is: <p>This is a duplicate of thread 1706.  So closing this thread.</p>  
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B5W1&layer=L4">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 22:53:45 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB5W1L4 
<li>problem n: 1706 
<li>Status: fixed
<li>Type: AVDD
<li>Action: Monitoring
<li>entered by: amitra 
<li>description is: <p>AVDD looks stable after the PS swap.  Closing this thread.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B5W1&layer=L4">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 22:58:51 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB5W1L3 
<li>problem n: 1708 
<li>Status: fixed
<li>Type: DVDD
<li>Action: Monitoring
<li>entered by: amitra 
<li>description is: <p>DVDD Currents are stable after PS swap. Closing this thread.</p> 
<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: Tue Aug 15 22:58:51 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB5W1L3 
<li>problem n: 1709 
<li>Status: fixed
<li>Type: AVDD
<li>Action: Monitoring
<li>entered by: amitra 
<li>description is: <p>AVDD is stable after the power supply swap. Closing this thread.</p> 
<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: Tue Aug 15 23:02:59 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB2W9L0 
<li>problem n: 1669 
<li>Status: fixed
<li>Type: DVDD
<li>Action: Monitoring
<li>entered by: amitra 
<li>description is: <p>The currents have remained stable since the shutdown.  Now closing this thread.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B2W9&layer=L0">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 23:14:31 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB2W0L2 
<li>problem n: 1601 
<li>Status: fixed
<li>Type: BIAS
<li>Action: Monitoring
<li>entered by: amitra 
<li>description is: <p>The limit of 140 will suffice for now.  So I am closing this thread.  However the bias current for this ladder is growing at a steep rate.  In a week or two, this ladder will go pink again.  A pre-emptive IMON limit change may be warranted.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B2W0&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 23:20:43 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB2W0L4 
<li>problem n: 809 
<li>Status: fixed
<li>Type: BIAS
<li>Action: Monitoring
<li>entered by: amitra 
<li>description is: <p>Looks like Bias0 and Bias1 look OK.  The currents are increasing at a similar rate as before the shutdown.  However the Bias 0 will probably be exceeded in a few days.  So a pre-emptive IMON change for Bias0 may be needed.</p> 
<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: Tue Aug 15 23:24:52 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB3W0L4 
<li>problem n: 1506 
<li>Status: fixed
<li>Type: BIAS
<li>Action: Monitoring
<li>entered by: amitra 
<li>description is: <p>The Bias0 and Bias1 limits given will do for now. So I am closing this thread.</p>  <p>However the limits will probably be exceeded in a few weeks.  Also the Bias currents for this ladder seem to be growing at a larger rate.</p> 
<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: Tue Aug 15 23:26:56 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB2W1L2 
<li>problem n: 1606 
<li>Status: uncooled
<li>Type: BIAS
<li>Action: Diagnosis_update
<li>entered by: amitra 
<li>description is: <p>Looks like the current for this ladder are OK.  However the IMOn limit will probably be exceeded in a week.  A pre-emptive IMON change may be needed.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B2W1&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 23:35:13 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W3L4 
<li>problem n: 1216 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: Currents_investigated
<li>entered by: amitra 
<li>description is: <p>Seems this ladder has always had a history of bad bias currents.  But it seems to be doing better for now.  So closing this thread.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B1W3&layer=L4">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 23:39:21 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB4W1L1 
<li>problem n: 1630 
<li>Status: fixed
<li>Type: BIAS
<li>Action: Monitoring
<li>entered by: amitra 
<li>description is: <p>This IMON limit is OK for now. So closing this thread.</p>  <p>But this IMON limit wil probably be exceeded in a week.  Also the bias current is changing at a faster compared to before the shutdown.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B4W1&layer=L1">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 23:43:03 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB3W11L2 
<li>problem n: 1522 
<li>Status: fixed
<li>Type: BIAS
<li>Action: Monitoring
<li>entered by: amitra 
<li>description is: <p>After the initial post-shutdown bias current fluctuation, it seems to have settled.  So closing this thread for now.</p> 
<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: Tue Aug 15 23:49:42 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB4W5L3 
<li>problem n: 585 
<li>Status: fixed
<li>Type: BIAS
<li>Action: Monitoring
<li>entered by: bachacou 
<li>description is: <p>The BIAS1 IMON limit for this ladder is OK for now.  So I am closing this thread.</p>  <p>However the current seems to be increasing after rate compared to before the shutdown.</p> 
<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: Tue Aug 15 23:52:38 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB2W1L1 
<li>problem n: 1602 
<li>Status: fixed
<li>Type: BIAS
<li>Action: Monitoring
<li>entered by: amitra 
<li>description is: <p>The IMON limit should be Ok for a week or two.  So closing this thread for now.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B2W1&layer=L1">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 23:53:50 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W3L4 
<li>problem n: 1216 
<li>Status: fixed
<li>Type: BIAS
<li>Action: Currents_investigated
<li>entered by: amitra 
<li>description is: <p>Really closing this thread now.  Fixed Fixed.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B1W3&layer=L4">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Aug 15 23:56:46 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB2W6L0 
<li>problem n: 1723 
<li>Status: fixed
<li>Type: BIAS
<li>Action: Monitoring
<li>entered by: amitra 
<li>description is: <p>The upper IMON limit should be OK for now.  So closing this thread.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B2W6&layer=L0">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Aug 16 00:03:43 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB2W9L1 
<li>problem n: 1667 
<li>Status: fixed
<li>Type: AVDD
<li>Action: Monitoring
<li>entered by: amitra 
<li>description is: <p>AVDD current looks stable now.  Closing this thread.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B2W9&layer=L1">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Aug 16 00:06:58 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W1All 
<li>problem n: 1678 
<li>Status: fixed
<li>Type: VDOIM
<li>Action: Monitoring
<li>entered by: amitra 
<li>description is: <p>2V DOIM looks stable after shutdown.  The IMON limit is OK.  Closing this thread.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B1W1&layer=All">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Aug 16 00:08:19 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W1All 
<li>problem n: 1679 
<li>Status: fixed
<li>Type: VDOIM
<li>Action: Monitoring
<li>entered by: amitra 
<li>description is: <p>5V DOIM looks stable after shutdown.  The IMON limit is OK.  Closing this thread.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B1W1&layer=All">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Wed Aug 16 00:14:07 2006 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9587&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9587' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9588&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9588' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9589&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9589' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9590&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9590' width='300'></a></center>
<!-- Author: Ankush -->
<!-- Comment: Wed Aug 16 00;16;15 comment by...Ankush -->
<h3>SB4W6 DOIM seems to be dropping</h3>

<p>A PDB thread had shown the IMON limits for the 2V and 5V DOIM had to be lowered.  The current for the DOIM lines are continuing to drop.  Also the 5V DOIM voltage is also drooping.  We&#39ll need to investigate this...it could be a flaky SVX supply :-( </p>

<!-- Date: Wed Aug 16 00:18:20 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB4W6All 
<li>problem n: 1681 
<li>Status: needs_observation
<li>Type: VDOIM
<li>Action: Diagnosis_update
<li>entered by: amitra 
<li>description is: <p>The 2V DOIM current continues to droop with time.  The current history can be found in the  <a href= 'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=314&frame=2&anchor=00:14:07'> Silicon e-log</a>. Continue to obsever along with the voltage to see if this continues.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B4W6&layer=All">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Aug 16 00:20:44 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB4W6All 
<li>problem n: 1682 
<li>Status: needs_observation
<li>Type: VDOIM
<li>Action: Diagnosis_update
<li>entered by: amitra 
<li>description is: <p>The current for the 5V DOIM line continues to droop after the shutdown.  Also the voltage for the 5V DOIM line is also drooping.  The graphs for the 5V DOIM line can be found in the  <a href= 'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=314&frame=2&anchor=00:14:07'> Silicon e-log</a>.  Continue to observe for now to see if this drooping continues.</p>  <p>However, if an access comes up, one should check this supply.  The drooping 5V DOIM line could be an indicator of a dying supply.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B4W6&layer=All">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Wed Aug 16 01:41:10 2006 -->
<pre>ISL B4 tripped on temperature: 
Strangely enough Wedge IB4W3 was not turned off. 
  
The following is the output of PS gui : 
 
 
Wed Aug 16 01:03:24 CDT 2006                        TRIP: ISL  B4  W0 External Trip 
Wed Aug 16 01:03:24 CDT 2006                        TRIP: ISL  B4  W0 External Trip 
Wed Aug 16 01:03:24 CDT 2006                        TRIP: ISL  B4  W0 External Trip 
Wed Aug 16 01:03:24 CDT 2006                        TRIP: ISL  B4  W0 External Trip 
Wed Aug 16 01:03:24 CDT 2006                        TRIP: ISL  B4  W0 External Trip 
Wed Aug 16 01:03:24 CDT 2006                        TRIP: ISL  B4  W0 External Trip 
Wed Aug 16 01:03:24 CDT 2006                        TRIP: ISL  B4  W1 External Trip 
Wed Aug 16 01:03:24 CDT 2006                        TRIP: ISL  B4  W1 External Trip 
Wed Aug 16 01:03:24 CDT 2006                        TRIP: ISL  B4  W1 External Trip 
Wed Aug 16 01:03:24 CDT 2006                        TRIP: ISL  B4  W1 External Trip 
Wed Aug 16 01:03:24 CDT 2006                        TRIP: ISL  B4  W1 External Trip 
Wed Aug 16 01:03:24 CDT 2006                        TRIP: ISL  B4  W2 External Trip 
Wed Aug 16 01:03:24 CDT 2006                        TRIP: ISL  B4  W2 External Trip 
Wed Aug 16 01:03:24 CDT 2006                        TRIP: ISL  B4  W2 External Trip 
Wed Aug 16 01:03:24 CDT 2006                        TRIP: ISL  B4  W2 External Trip 
Wed Aug 16 01:03:24 CDT 2006                        TRIP: ISL  B4  W2 External Trip 
Wed Aug 16 01:03:24 CDT 2006                        TRIP: ISL  B4  W4 External Trip 
Wed Aug 16 01:03:24 CDT 2006                        TRIP: ISL  B4  W4 External Trip 
Wed Aug 16 01:03:24 CDT 2006                        TRIP: ISL  B4  W4 External Trip 
Wed Aug 16 01:03:24 CDT 2006                        TRIP: ISL  B4  W4 External Trip 
Wed Aug 16 01:03:24 CDT 2006                        TRIP: ISL  B4  W5 External Trip 
Wed Aug 16 01:03:24 CDT 2006                        TRIP: ISL  B4  W5 External Trip 
Wed Aug 16 01:03:24 CDT 2006                        TRIP: ISL  B4  W5 External Trip 
Wed Aug 16 01:03:24 CDT 2006                        TRIP: ISL  B4  W5 External Trip 
Wed Aug 16 01:03:24 CDT 2006                        TRIP: ISL  B4  W5 External Trip 
Wed Aug 16 01:03:24 CDT 2006                        TRIP: ISL  B4  W5 External Trip 
Wed Aug 16 01:03:51 CDT 2006                        Interlock ISL B4 is not enabled 
Wed Aug 16 01:05:39 CDT 2006                        Interlock SVX B3 is not enabled 
Wed Aug 16 01:05:39 CDT 2006                        Interlock SVX B4 is not enabled 
Wed Aug 16 01:05:39 CDT 2006                        Interlock SVX B5 is not enabled 
Wed Aug 16 01:05:39 CDT 2006                        Interlock SVX B2 is not enabled 
Wed Aug 16 01:05:39 CDT 2006                        Interlock SVX B1 is not enabled 
Wed Aug 16 01:05:39 CDT 2006                        Interlock SVX B0 is not enabled 
Wed Aug 16 01:05:39 CDT 2006                        Interlock ISL B3 is not enabled 
Wed Aug 16 01:05:39 CDT 2006                        Interlock ISL B5 is not enabled 
Wed Aug 16 01:05:39 CDT 2006                        Interlock ISL B1 is not enabled 
Wed Aug 16 01:05:39 CDT 2006                        Interlock ISL B2 is not enabled 
Wed Aug 16 01:05:39 CDT 2006                        Interlock ISL B0 is not enabled 
Wed Aug 16 01:05:39 CDT 2006                        Interlock L00 EAST is not enabled 
Wed Aug 16 01:05:39 CDT 2006                        Interlock L00 WEST is not enabled 
Wed Aug 16 01:06:33 CDT 2006                        IFix -  ERROR: Silicon to STANDBY  Handshake - Could not turn on power - checked 10 times  
Wed Aug 16 01:06:42 CDT 2006                        Interlock SVX B3 is enabled 
Wed Aug 16 01:06:42 CDT 2006                        Interlock SVX B4 is enabled 
Wed Aug 16 01:06:42 CDT 2006                        Interlock SVX B5 is enabled 
Wed Aug 16 01:06:42 CDT 2006                        Interlock SVX B2 is enabled 
Wed Aug 16 01:06:42 CDT 2006                        Interlock SVX B1 is enabled 
Wed Aug 16 01:06:42 CDT 2006                        Interlock SVX B0 is enabled 
Wed Aug 16 01:06:42 CDT 2006                        Interlock ISL B3 is enabled 
Wed Aug 16 01:06:42 CDT 2006                        Interlock ISL B5 is enabled 
Wed Aug 16 01:06:42 CDT 2006                        Interlock ISL B1 is enabled 
Wed Aug 16 01:06:42 CDT 2006                        Interlock ISL B2 is enabled 
Wed Aug 16 01:06:42 CDT 2006                        Interlock ISL B0 is enabled 
Wed Aug 16 01:06:42 CDT 2006                        Interlock L00 EAST is enabled 
Wed Aug 16 01:06:42 CDT 2006                        Interlock L00 WEST is enabled 
</pre>
<!-- Author: Ricardo -->


<!-- Date: Wed Aug 16 02:07:30 2006 -->
<h3>ISL Cooling Trip Due to CCE1.1</h3> 
So finally it happened: the temperature in CCE1L6_1OUT  
<a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2006&action=view&page=588&frame=2&anchor=01:14:22.125'> 
jumped up within a short time</a> (less than 5 minutes). The interlock system tripped the power supplies of ISL Bulkhead 4, except for wedge 3 (we have to check why!!!). The aces got confused about what to do and tried to switch the entire silicon OFF from iFix. Fortunately, this is not possible in one step, so the detector went to STANDBY only. Unfortunately, they did not remember what they should have done, i.e. hitting the crash button if in doubt! We acknowledge the ISL trip and start to power up the tripped wedges one by one.
<!-- Author: Ricardo & Ulrich -->
<!-- Comment: Wed Aug 16 02;26;39 comment by...Ricardo & Ulrich -->
We switched on BH4 wedge by wedge, and then f401, f403, f451, and f453 ladder by ladder. After switching on the first of them (f451), the temperature increased from 11&deg;C to 13&deg;C and jumped back to 11&deg;C after two minutes or so. This would be consistent with a bubble in the cooling line which got flushed out. We switched on all the rest without problems. The temperature seems to be settling below 17&deg;C, more than 1&deg;C lower than before the trip.

<!-- Comment: Wed Aug 16 02;28;36 comment by...Ricardo & Ulrich -->
We have also given the Aces a quick lecture about the interlock mechanism and what we expect them to do. The issue is complicated because a localized temperature trip takes out only one bulkhead, not the entire ISL (as we usually tell them in the Ace lectures). We will have to clarify the situation in the next Ace meeting.


<!-- Comment: Wed Aug 16 03;16;33 comment by...Ulrich -->
Just checked the interlock code. The logic is as follows: the highest temperature of a given bulkhead is compared with the trip limit. If it is above, a trip coil is set. If the trip coil is set, the 5V enable line of the bulkhead is dropped, so each power supply connected to the line should turn off. The wedge which apparently stayed on (IB4W3) is in CAEN crate 11 (SE Top Top), together with IB4W2, which switched off fine. We should use the next access to check if the interlock cabling at the crate is correct.
<!-- Comment: Wed Aug 16 03;22;21 comment by...Ricardo & Ulrich -->
We have also tried to bias the silicon. As expected, the temperature is unchanged, currently at 16.6&deg;C.
<!-- Date: Wed Aug 16 02:50:03 2006 -->
Waiting for the Tevatron beam to be dumped, we have rebooted SVXIICON.
<!-- Author: Ricardo & Ulrich -->




<!-- Date: Wed Aug 16 05:35:27 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9591&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9592  width='300' align='top'></a></td><td><h3>Store 4906</h3> 
Store 4906 came in with an initial luminosity of 123e30. All losses are below 400 Hz. I was watching things from home (also the Fast Time Plot of the losses kind of works from here) and gave the permission to ramp the silicon. SVTSpyMon looks fine.</td></tr></table>
<!-- Author: Ulrich -->
<!-- Comment: Wed Aug 16 05;43;33 comment by...Ulrich -->
SVXMon is fine as well.


<!-- Date: Wed Aug 16 06:22:01 2006 -->
Got paged because the CO re-discovered the yellow chips we have in one ISL ladder due to low statistics. Apparently, she did not appreciate the low statistics reference plot...
<!-- Author: Ulrich -->

<!-- Date: Wed Aug 16 09:09:37 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB4W5L3 
<li>problem n: 1693 
<li>Status: fixed
<li>Type: pinhole
<li>Action: Diagnosis_update
<li>entered by: amitra 
<li>description is: <p>Bias current is now stable after the pinhole developed  and the ladder still looks biased. Closing this thread.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B4W5&layer=L3">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Wed Aug 16 09:42:27 2006 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9595&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9595' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9593&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9593' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9594&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9594' width='300'></a></center>
<!-- Author: Ankush -->
<!-- Comment: Wed Aug 16 09;47;42 comment by...Ankush -->
<h3>Bias current history for SB0W9L2</h3>

<p>This is the bias current history for SB0W9L2.  The first graph covers the period from DSDay 1700 (28 Aug '05) to now.  This sensor has had a history of badly behaving bias curent (it's a micron sensor after all!).  However the behaviour seems to be worse after the shutdown.  The next two graphs are zoomed in versions of the bias current after DSDay 1900 (16 March '06) and the period from DSDay 1700 to 1800 (28 Aug '05 to 6 Dec' 05).</p>

<!-- Date: Wed Aug 16 09:50:30 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W9L2 
<li>problem n: 1699 
<li>Status: needs_longterm_monitoring
<li>Type: BIAS
<li>Action: Monitoring
<li>entered by: amitra 
<li>description is: <p>The new IMON limit will suffice for now.  However this ladder has a history of bad BIAS current behaviour. The monitoring group should look at the current history for this ladder every month.  If  it gets worse, the Detector group should look at it. In addition to checking the bias history, the Monitoring group should check the ladder is still fully depleated.</p>   
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B0W9&layer=L2">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Wed Aug 16 10:03:14 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9597&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9597  width='300' align='top'></a></td><td><h3>SB3W6L2 Bias Current History</h3> 
 
<p>The Bias current history for this ladder is not well behaved:  
yet another Micron ladder.  After the shutdown, the current went 
up and it still jumps up and down quite a bit.</p></td></tr></table>
<!-- Author: Ankush -->

<!-- Date: Wed Aug 16 10:07:11 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB3W6L2 
<li>problem n: 1508 
<li>Status: needs_longterm_monitoring
<li>Type: BIAS
<li>Action: Monitoring
<li>entered by: amitra 
<li>description is: <p>This ladder has a history of a bad bias current behaviour.  After the shutdown the bias current went up.  For the time being the new IMON limit will suffice. A graph of the bias history can be found in the <a href= 'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=314&frame=2&anchor=10:03:14'> Silicon e-log</a>.</p>  <p>The monitoring group should examine the bis history of this ladder every month.  They should check if it is stable and the ladder continues to be fully depleated.  If there are any problems, it should be given to the detector group.</p>   
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B3W6&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Aug 16 10:18:15 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB5W0L2 
<li>problem n: 1686 
<li>Status: fixed
<li>Type: AVDD
<li>Action: Monitoring
<li>entered by: amitra 
<li>description is: <p>This ladder has a history of <em>noisy</em> AVDD current.  However the ladder is running error free and the SVXMon strip plots look OK.  The current upper limit of 895 should befine for now. So closing this thread.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B5W0&layer=L2">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Wed Aug 16 10:27:40 2006 -->
<h3>Interlock Problem: Word from the Experts</h3> 
After consulting with Jen Pursley and Andy Hocker, we now have a better understanding of the 
<a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=314&frame=2&anchor=02:07:30'> 
interlock problem</a> we observed last night. The interlock signal for a given bulkhead from the PLC is fed into two different lines which go to the North and South of the detector. These lines are split up and distributed over the crates by a maze of T-connectors. So there is no active component in the system. The three hypotheses according to Andy are: 
<pre> 
Most likely: 
The wrong ISL enable line is plugged into IB4W3.  When you get a chance, 
drop the ISL enables one at a time and see who actually kills IB4W3. 
 
Less likely: 
An SVX or L00 enable is plugged into IB4W3 --- if this is one of those "mixed" 
crates with supplies of different flavor.  Again you could find this out by dropping 
enables one at a time.  (Obviously the reason we've never noticed this problem 
before is that we rarely trip individual bulkheads, usually we've done something 
to take down the whole detector in one fell swoop.) 
 
Extremely unlikely: 
The IB4W3 supply is bad such that it defeats the interlocks.  But I believe 
this is on the PS crew's checklist when they install a supply. 
</pre> 
We have requested an access to fix the interlock problem. We will 
<ul> 
<li>Drop the PS enables of all ISL bulkheads one by one to see which wedges are taken out by which line.</li> 
<li>Check (and correct) the cabling in the collision hall. Crate 11 is in SE Top Top and serves IB3W0, IB3W1, IB4W2, IB4W3, and IB5W3.</li> 
<li>Possibly check the 5V lines with a DVM</li> 
</ul>
<!-- Author: Ulrich -->


<!-- Date: Wed Aug 16 10:29:18 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9598&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9598  width='300' align='top'></a></td><td><h3>SB3W8L0 Bias current history</h3> 
 
<p>The graph shows the bias current history from DSDay (20 May '05) to the present.  The rate of change now seems to be steeper but we are accumalating more luminosity now.  Need to look at it a bit more carefully.</p></td></tr></table>
<!-- Author: Ankush -->

<!-- Date: Wed Aug 16 10:33:27 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB3W8L0 
<li>problem n: 1701 
<li>Status: fixed
<li>Type: BIAS
<li>Action: Monitoring
<li>entered by: amitra 
<li>description is: <p>For cheecking the IMON limit is still OK, one can close this thread for now.  But the current is creeping up to its limit and will probably exceed it in a week.  So a preemptive IMON change may be needed.  A plot showing the bias current history can be found in the <a href= 'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=314&frame=2&anchor=10:29:18'> Silicon e-log</a>.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B3W8&layer=L0">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Aug 16 10:37:45 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB2W1L0 
<li>problem n: 1702 
<li>Status: fixed
<li>Type: BIAS
<li>Action: Monitoring
<li>entered by: amitra 
<li>description is: <p>Current looks fine and the IMON limit is still valid.  Closing this thread.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B2W1&layer=L0">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Wed Aug 16 19:26:24 2006 -->
<h3>New, improved Silicon office</h3> 
 
<p>Today new shelves were put in !!!  Ulrich, Ricardo and I then started a major campaign of tidying up the Silicon office.  Nothing was left untouched.  The result is a much tidier, more organised and streamlined office.  Come over and have a look.</p> 
 
<p>...and as an added bonus, a lot of fiber related gear was found.  4 <em>octupuses</em> were found!!!! (...they&#39ll need testing to check they are really OK...).  A gadget to clean fibres for you.  Another gadget to test fibres.... and spare GLINK and DOIM fibers.</p> 
  
<!-- Author: Ulrich, Ricardo and Ankush -->


<!-- Date: Wed Aug 16 19:38:43 2006 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9599&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9600' ></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9601&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9602' ></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9603&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9604' ></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9605&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9606' ></a></center>
<!-- Author: Ankush -->
<!-- Comment: Wed Aug 16 19;40;57 comment by...Ankush -->
<h4>Photos of the new, improved Silicon Office</h3>

<p>The photos are of the new, improved Silicon office.  New shelves added under the white-board.  Re-arrangement of office iterm. Then last picture shows the re-discovered Octopuses....in the bag they are ~4 unused octopuses.</p>


<!-- Date: Wed Aug 16 21:41:20 2006 -->
The aces spotted a 
<a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2006&action=view&page=590&frame=2&anchor=21:00:24.259'> 
new pinkie</a> in the AVDD line of e502. An HRR brought it back in line.
<!-- Author: Ulrich -->
<!-- Comment: Thu Aug 17 10;19;05 comment by...Ulrich -->
During the night, several other HRRs were needed for e502. We should keep an eye on this guy. See
<a href=
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2006&action=view&page=591&frame=2&anchor=01:52:54.240'>
here</a>,
<a href=
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2006&action=view&page=591&frame=2&anchor=03:27:08.406'>
here</a>, and
<a href=
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2006&action=view&page=591&frame=2&anchor=06:54:39.568'>
here</a>.

<!-- Date: Wed Aug 16 22:02:36 2006 -->
<H3>Access: 8:00 tomorrow morning</h3> 
The access tomorrow morning has been shifted from 6:00 to 8:00. We will go in and debug the interlock problem.
<!-- Author: Ulrich -->


<!-- Date: Thu Aug 17 10:13:03 2006 -->
<h3>Access Report</h3> 
 
Today&#039;s access has been requested by the silicon group to track down the interlock problem in IB4W3. Jen pointed out that the symptoms we see point to the following problem: during the shutdown she had worked on the supply and may have forgot to pull out a jumper (J72) to bypass the 5V enable. 
Once we are down there, we will also try to correct a swapped set of bias cables in IB1W5L3. Ankush found out earlier this week that <a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=314&frame=2&anchor=17:46:42'> 
Bias0 and Bias1 were swapped during an access in January</a>. 
 
 
<h4>Preparation</h4> 
In preparation for the access, we reproduced the problem. We forced the PS enable coils in the PLC code OFF for all ISL bulkheads (C2301-C2303 for East Inner, Central, Outer, and C2306-C2308 for West Inner, Central, Outer). All wedges except B4W3 tripped as they should. 
<p> 
When we switched things back on, we encountered a problem with IB0W2. The PC turned on ok, but all ladders started tripping on AVDD overcurrent immediately. Rebooting FIB crate b0fib01 was not successful, but hockerizing CAEN crate 4 was. 
 
<h4>Interlock Problem</h4> 
We went up to the crate (SE Top Top) with a lift, pulled out the supply, and removed the jumper without problems. We verified that the interlock now works by pulling the 5V cable (trip) and pulling the trip coil in the PLC (trip). 
 
<h4>IB1W5L3 Bias Cable Swap</h4> 
Also here (SW Top Top) we needed a lift. We swapped the cables and made sure the wedge can still be biased. Now the Bias1 lines read about the bias current Bias0 was reading before, and vice versa.  
<p> 
A side remark from the MCR e-log: 
<pre> 
08:17:58-   Dee Hahn is access coordinator for D0. - olli 
-- Thu Aug 17 08:20:02 comment by...fish --  We mean CDF 
</pre>
<!-- Author: Ricardo, Antonio, Ankush, Ulrich -->


<!-- Date: Thu Aug 17 10:14:23 2006 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9607&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9608' ></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9609&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9610' ></a></center>
<!-- Author: Ulrich -->
<!-- Comment: Thu Aug 17 10;24;07 comment by...Ulrich -->
Bias currents for IB1W5L3. After the cable swap, Bias0 reads what Bias1 was reading before and vice versa.

<!-- Date: Thu Aug 17 10:31:18 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB1W5L2 
<li>problem n: 374 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: husemann 
<li>description is: We swapped the bias cables for Bias0 and Bias1. So we swap the IMON limits as well (here: Bias0).<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>73.103</td><td>70.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>115.0</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B1W5&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Thu Aug 17 10:31:51 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB1W5L2 
<li>problem n: 374 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: husemann 
<li>description is: We swapped the bias cables for Bias0 and Bias1. So we swap the IMON limits as well (here: Bias1).<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>87.7525</td><td>11.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=ISL&wedge=B1W5&layer=L2">report</a></ul>
<!-- Author: Problem DB -->




<!-- Date: Thu Aug 17 11:11:53 2006 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9611&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9611' width='300'></a></center>
<!-- Author: Adam Scott -->
<!-- Comment: Thu Aug 17 11;13;12 comment by...Adam Scott -->
ADC dist for f823 chip 2 in run 221500 (recent run).



<!-- Date: Thu Aug 17 12:17:40 2006 -->
<h3>Quiet Time Work</h3> 
 
<p>As there was some quiet time available after the access I did two things: 
 
<ol> 
<li>I fixed the BIAS RATIO for the Z side of IB4W0L3.  So now the PHI side has BIAS RATIO=1 and the Z side has BIAS RATIO=0.  This is part of the study to see if we can we reduce the heat load on ISL Cooling line CCE1.</li> 
<li>I examined SVX ladder SB4W0L4.  This was taken out some time ago but it was brought back after the shutdown and then started giving bad data a few days ago.  In running the ladder, I discovered half of chip a5 (chip 8) was not returning any data.  The chip settings in SVXDAQ seemed to be OK...rsther odd indeed.</li> 
</ol> 
 
</p>
<!-- Author: Ankush -->
<!-- Comment: Thu Aug 17 12;47;38 comment by...Ankush -->
<h4>Raising BIAS1 for ISL IB4W0L1</h3>

<p>At David Stuart&#39s request, I have raised the Bias voltage for ISL IB4W0L1 from the 80V to 82V.  CAENVolts.dat was regenerated.  One should check this bias when detector is turned ON.</p>
<!-- Date: Thu Aug 17 12:20:16 2006 -->
<table><tr><td><a href=/elog/notebooks/silicon/Thu_Aug_17_2006_122007.ps align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9615  align='top'></a></td><td><h3>SVXDAQ plot for SB4W0L4</h3> 
 
<p>Here is the SVXDaq plot for SB4W0L4. If you zoom in, channels 1089 to 1152 are not returning any data.  However this isn't quite one chip as that would be channels 987 to 1152.</p></td></tr></table>
<!-- Author: Ankush -->
<!-- Comment: Thu Aug 17 13;29;27 comment by...Marcel -->
As far as I recall and also checking a <a href="http://www-cdf.fnal.gov/internal/WebTalks/Archive/0605/060511_cdf_silicon_workshop_day_1/12_060511_cdf_silicon_workshop_day_1_SVX3DTalk_mitra_SVX3D_11May06.ppt"> certain</a> talk, the SVX3D has 128 channels, so the boundaries would be 1025 and 1152. The failure mode here looks like this chip does have a bit 6 low, hence half of the chip (channels 64-127, or 1089-1152) are missing. That should be easy to crosscheck.


<!-- Comment: Thu Aug 17 18;13;34 comment by...Ankush -->
<p>OK...so I had a brain fart and made a mistake....if you want the job....it&#39s yours for the taking !</p>
<!-- Date: Thu Aug 17 14:39:27 2006 -->
<h3>The Quadlog has saved our butt</h3> 
It just occured to me that we have been really lucky that we have the Quadlog interlock system. When the RH sensor went crazy a couple of weeks ago, we were wondering why the racks were off. We thought it was because of a temperature &uuml;bertrip. As a matter of fact, the Quadlog kills the racks only if the temperature is above the limit AND the power supplies are still on. Due to the bypassed 5V enable line in B4W3, there was still something on, so the Quadlog killed the racks. 
<!-- Author: Ulrich -->


<!-- Date: Thu Aug 17 17:07:18 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9616&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9617  width='300' align='top'></a></td><td>Store 4909 is in. Initial Luminosity 145 E30. 
SVT spymon looks fine. No problems so far. 
 
</td></tr></table>
<!-- Author: Ricardo -->
<!-- Comment: Thu Aug 17 20;12;24 comment by...Ankush -->
<p>Also IB4W0L1 went to 82V with no problems and no significant increase in the bias current.</p>
<!-- Date: Thu Aug 17 17:32:41 2006 -->
<h3>RT Server Barfed</h3> 
 
<p>The RTServier died...this is waht our stuff said:</p> 
 
 
<p>This is what SVXInter said:</p> 
<pre> 
WARNING: Lost connection to RTserver: error code = 514. 
Waiting before reconnecting. 
Attempting to reconnect to RTserver. 
Connecting to project <cdf_daq> on <tcp:b0server05> RTserver. 
Using tcp protocol. 
connect: S_errno_ETIMEDOUT 
Could not connect to <tcp:b0server05> RTserver. 
Skipping starting <start_never:tcp:b0server05> RTserver. 
Cannot reconnect to RTserver. 
Attempting to reconnect to RTserver. 
Connecting to project <cdf_daq> on <tcp:b0server05> RTserver. 
Using tcp protocol. 
connect: S_errno_ETIMEDOUT 
Could not connect to <tcp:b0server05> RTserver. 
Skipping starting <start_never:tcp:b0server05> RTserver. 
Cannot reconnect to RTserver. 
Attempting to reconnect to RTserver. 
Connecting to project <cdf_daq> on <tcp:b0server05> RTserver. 
Using tcp protocol. 
connect: S_errno_ETIMEDOUT 
Could not connect to <tcp:b0server05> RTserver. 
Skipping starting <start_never:tcp:b0server05> RTserver. 
Cannot reconnect to RTserver. 
Attempting to reconnect to RTserver. 
Connecting to project <cdf_daq> on <tcp:b0server05> RTserver. 
Using tcp protocol. 
connect: S_errno_ETIMEDOUT 
Could not connect to <tcp:b0server05> RTserver. 
Skipping starting <start_never:tcp:b0server05> RTserver. 
Cannot reconnect to RTserver. 
Attempting to reconnect to RTserver. 
Connecting to project <cdf_daq> on <tcp:b0server05> RTserver. 
Using tcp protocol. 
connect: S_errno_ETIMEDOUT 
Could not connect to <tcp:b0server05> RTserver. 
Skipping starting <start_never:tcp:b0server05> RTserver. 
Cannot reconnect to RTserver. 
Attempting to reconnect to RTserver. 
Connecting to project <cdf_daq> on <tcp:b0server05> RTserver. 
Using tcp protocol. 
Message from RTserver: Connection established.Start subscribing to subject </svxHVHdShk> again. 
Start subscribing to subject </caenInfo/power> again. 
Start subscribing to subject </caenInfo/ilocks> again. 
Start subscribing to subject </_svxinter_14851704> again. 
 
svxinter->  
</pre>  
<!-- Author: Ankush -->
<!-- Comment: Thu Aug 17 17;33;42 comment by...Ankush -->
<p>...and this is from PS-GUI</p>

<pre>
Thu Aug 17 16:53:44 CDT 2006                        IFix -  success: Silicon ON  
Thu Aug 17 17:15:05 CDT 2006                        Lost communication with iFix
Thu Aug 17 17:15:14 CDT 2006                        Established communication with iFix
Thu Aug 17 17:15:14 CDT 2006                        Interlock is enabled
</pre>

<!-- Comment: Thu Aug 17 17;34;29 comment by...Ankush -->
<p>....and this is what IMON said...</p>


<pre>
<svxii@b0dasvx03>WARNING: reader: in: connection dropped
Waiting before reconnecting.
Attempting connection to <tcp:b0server05:5101> RTserver.
Connected to <tcp:b0server05:5101> RTserver.
</pre>

<!-- Comment: Thu Aug 17 17;49;35 comment by...Ted -->
<pre>Ankush: that's a lot of words to describe one simple thing.</pre>



<!-- Comment: Thu Aug 17 19;50;31 comment by...Basil Fawlty -->
He starts chattering like an old lady ... may be we should call him Sybil ?

<!-- Date: Thu Aug 17 19:14:01 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9619&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9619  width='300' align='top'></a></td><td>This is the Avdd history of e502, which keeps getting pink in IMON. It certainly draws more current these days, and the spread is also larger. </td></tr></table>
<!-- Author: Ricardo -->



<!-- Date: Thu Aug 17 21:26:10 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB4W0L3 
<li>problem n: 1720 
<li>Status: needs_observation
<li>Type: PC_Temperature
<li>Action: Chip_bit_changes
<li>entered by: amitra 
<li>description is: <p>The unintended switch of changing the Z side BIAS RATIO from 1 to 0 showsed a ~10% reduction in the mean of the collected charge distribution.  The change in current was small; ~50&#956;A.</p>  <p>Now the PHI side chips have BIAS RATIO=0 and the Z side have returned to BIAS RATIO=1.  Need to keep an eye on this ladder during data taking.  THen examine the collected charge offline.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B4W0&layer=L3">report</a></ul>
<!-- Author: Problem DB -->
<!-- Comment: Fri Aug 18 13;48;34 comment by...David Stuart -->
<pre>The phi side chips had their cluster charge return to normal,
and the z side chips had an approximately 10% decrease in cluster charge.

So, both phi and z have reduced cluster charge with bias ratio select = 1. It is not yet known if this is due to a reduction in gain or a loss of charge.</pre>
<!-- Date: Thu Aug 17 21:28:50 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB4W0L1 
<li>problem n: 1725 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: Diagnosis
<li>entered by: amitra 
<li>description is: <p>At David Stuart's request, I have increased the BIAS1 set point from 80V to 82V.  This should improve the charge collection.  Wait for offline analysis to see if this has changed the charge collection.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B4W0&layer=L1">report</a></ul>
<!-- Author: Problem DB -->
<!-- Comment: Fri Aug 18 13;50;21 comment by...David Stuart -->
<pre>There is no significant change in the cluster charge. That is not surprising since my suspicion is that this ladder should run at 100V. So, I think we should keep increasing the voltage in about 5V steps and measure the charge at each step.
</pre>
<!-- Date: Thu Aug 17 22:28:01 2006 -->
<h3>Pinkie Status</h3> 
<ul> 
<li>Currently, the AVDD line of e502 jumps up and down a lot, but the data looks ok</li> 
<li>We just had a new bias pinkie in e380, a jump by 20&mu;A.  I believe this ladder has jumped before, simultaneously with others. 
</ul>
<!-- Author: Ulrich -->

<!-- Date: Fri Aug 18 09:48:23 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB5W0L2 
<li>problem n: 1686 
<li>Status: needs_observation
<li>Type: AVDD
<li>Action: IMON_limits
<li>entered by: ricardo 
<li>description is: This guy keeps fluctuating between 895 and 920. It has a history of large fluctuations, which are becoming larger these days.  <table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>870</td><td>910</td></tr>
<tr><td><b>Lower</b></td><td>835</td><td>865</td></tr>
<tr><td><b>Upper</b></td><td>895</td><td>925</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B5W0&layer=L2">report</a></ul>
<!-- Author: Problem DB -->
<!-- Comment: Fri Aug 18 09;52;17 comment by...Ricardo -->
<pre>We had pinkies many times this week with the Avdd current of e502. I've increase the limits so the crew does not get indifferent (is that an english word?) to pinkies, but we need to keep an eye on this guy. I reopen the thread, ... sorry ankush.
 </pre>


<!-- Date: Fri Aug 18 12:04:36 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9626&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9627  width='300' align='top'></a></td><td><h3>Misbehaving AVDD on SB5W0L2</h3> 
 
<p>The AVDD for this ladder suddenly dropped from ~920μA to 835μA.  An HRR was tried but it had not effect.</p> 
 
 
<p>This kind of jump would usually be an indicator of a chip dropping out.  However this ladder had a nominal current of 835μA before the shutdown and then jumped up.  So now this AVDD current had jumped down to its nominal value.  This ladder is also reading out all chips, so it is not a chip "waking-up".</p> 
 
<p>The question now is this odd jump a chip problem or a PS problem ?.....we'll need an access to really answer that.</p></td></tr></table>
<!-- Author: Ankush & Ricardo -->




<!-- Date: Fri Aug 18 17:14:01 2006 -->
<h3>Reformatter Errors</h3> 
 
<p>Reformatter errors reappeared today, similar to those which occured last week.  I have asked Conor & Markus for the raw data. One thing to note is there are two possible Silicon culprits: the FIB or VRB.  As we swapped the FIB last time, that only leaves the VRB.</p> 
 
<p>But before engaing in VRB swap fest I wait for the raw data and see if that reveals anything.</p>
<!-- Author: Ankush -->


<!-- Date: Sat Aug 19 00:37:57 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9632&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9633  width='300' align='top'></a></td><td><h3>Store 4910</h3> 
Store 4910 came in with an initial luminosity of 140.9e30. I was still in the Users' Center after the DSD gig, so I drove back to the control room for shot setup. I let the aces (Shalhout and Michael) make the call and was just observing. As in almost every previous store, everything was fine in terms of losses. SVTSpyMon and SVXMon look ok, too.</td></tr></table>
<!-- Author: Ulrich -->
<!-- Comment: Sat Aug 19 00;39;51 comment by...Ulrich -->
Brian Drendel was not 100% happy with the luminosity given the stack:
<pre>
00:35:49-   Store 4910 is colliding and had an average initial luminosity of 136.5e30. Considering that we shot from an ~300e10 stash, the store's initial luminosity was about 10-15% lower than expected. Main Injector still is seeing Pbar beam loss at 1.5 and 4.5 seconds. We lost ~80% of Pbar transfer #7 in Main Injector at 4.5 seconds.

We'll see how this store does overnight and see how stacking progresses before making any plans for the next store. - B Drendel
</pre>

<!-- Date: Sat Aug 19 08:36:21 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: LB0W2L3 
<li>problem n: 1529 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: Monitoring
<li>entered by: alscott 
<li>description is: Previous link was reference ADC dist.  Current ADC dist is <a href= 'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=314&frame=2&anchor=11:11:53'> here</a>.  ADC dist looks sick.  Would be good to check offline efficiencies, but they are not working. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=L00&wedge=B0W2&layer=L3">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Sat Aug 19 08:59:35 2006 -->
<center><a href='/elog/notebooks/silicon/Sat_Aug_19_2006_085923.ps'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9635' ></a></center>
<!-- Author: Adam Scott -->
<!-- Comment: Sat Aug 19 09;01;40 comment by...Adam Scott -->
ADC dist looks a lot better (at least, closer to the reference) than before the bias voltage was increased.  See<a href=
'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=267&frame=2&anchor=14:34:05'>
here</a>.

<!-- Date: Sat Aug 19 09:09:31 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB4W4L2 
<li>problem n: 1535 
<li>Status: needs_longterm_monitoring
<li>Type: BIAS
<li>Action: Monitoring
<li>entered by: alscott 
<li>description is: From the ADC dist, this ladder looks fully depleted (or at least, it looks more like the reference again), in run 221571.  See plot in <a href= 'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=314&frame=2&anchor=08:59:35'> elog</a>.  However, Oscar observed that it wasn't fully depleted.  Let's monitor for the next couple of weeks to check that it's still fully depleted.  If it is, I think we can call it fixed. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B4W4&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Sat Aug 19 09:13:39 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB1W2L2 
<li>problem n: 1632 
<li>Status: fixed
<li>Type: Unknown
<li>Action: Monitoring
<li>entered by: alscott 
<li>description is: Bump on chip 1 disappeared; bump on chip 2 not there.  Bumps usually caused by hot channels.  Nothing to be done. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B1W2&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Sat Aug 19 09:19:52 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB4W1L4 
<li>problem n: 1645 
<li>Status: fixed
<li>Type: Unknown
<li>Action: Monitoring
<li>entered by: alscott 
<li>description is: In run 221751, the physics tail is back up to the reference.  Could the PS work in thread 1454 have fixed it?  In any case, the ladder now looks healthy. 
<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: Sat Aug 19 09:28:08 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W10L3 
<li>problem n: 1705 
<li>Status: fixed
<li>Type: Unknown
<li>Action: Monitoring
<li>entered by: alscott 
<li>description is: The ADC dist in that run does look bad!  However, according to DSEM, the ladder was giving back garbage data for 100% of events in that run.  But that problem only spanned 2 runs (3, if you count cosmic runs), and has since disappeared.  The ADC dist now looks good, so we'll call this fixed.  If the garbage data problem comes back and persists, the ladder needs to be passed to detector. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B0W10&layer=L3">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Sat Aug 19 09:33:03 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W8L2 
<li>problem n: 1696 
<li>Status: fixed
<li>Type: Unknown
<li>Action: Monitoring
<li>entered by: alscott 
<li>description is: Nothing to be done for bumps. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B1W8&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Sat Aug 19 13:21:25 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB2W2L3 
<li>problem n: 436 
<li>Status: needs_longterm_monitoring
<li>Type: Chip_bit_error
<li>Action: Monitoring
<li>entered by: husemann 
<li>description is: This ladder has shown bit errors for runs 221604, 221605, and 221657. In the last two runs, the ladder ran error-free. Previous entries say that this problem is intermittent. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B2W2&layer=L3">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Sat Aug 19 15:10:28 2006 -->
<h3>Tevatron Abort</h3> 
The Tevatron just aborted the beam. No problem for the silicon, see 
<a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2006&action=view&page=598&frame=2&anchor=14:54:31.259'> 
main e-log</a>. The messages in the MCR log are rather cryptical: 
<pre> 
14:47:03-   Tev quench. - maggie 
-- Sat Aug 19 14:48:23 comment by...maggie --  F36U&L. 
14:58:23-   It appears the 186 card for the frig IO crate went. The F3NOD0 is in alarm and is not currently responding. The F3NOD0 went 40 seconds prior to the quench. - 2D 
-- Sat Aug 19 15:01:20 comment by...maggie --  CHL is calling the electrical coord to come in and take a look at the I/O crate. 
</pre>  
<!-- Author: Ulrich -->

<!-- Date: Sat Aug 19 16:14:57 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB0W4L0 
<li>problem n: 1653 
<li>Status: needs_observation
<li>Type: Chip_other
<li>Action: Init_RB_mask
<li>entered by: amitra 
<li>description is: <p>Ladder now has no problems returning initialisation bits.  I have removed the INIT READBACK mask.  See how this goes over the next week.  If there are no initialisation problems, then close this thread.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B0W4&layer=L0">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Sat Aug 19 20:00:06 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9636&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9636  width='300' align='top'></a></td><td>Ankush reduced the current consumption by changing the bias ratio from 1 to 0 for all chips. 
 </td></tr></table>
<!-- Author: Ankush and Ricardo -->

<!-- Date: Sat Aug 19 20:08:46 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB4W0L1 
<li>problem n: 1726 
<li>Status: needs_observation
<li>Type: AVDD
<li>Action: IMON_limits
<li>entered by: ricardo 
<li>description is: Wedge with the compromised cooling line. Bias Ratio was reduced to try to reduce the heat load.<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>1126</td><td>1025</td></tr>
<tr><td><b>Lower</b></td><td>1085</td><td>975</td></tr>
<tr><td><b>Upper</b></td><td>1170</td><td>1075</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B4W0&layer=L1">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Sat Aug 19 20:42:32 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB5W1L1 
<li>problem n: 1647 
<li>Status: needs_observation
<li>Type: Chip_other
<li>Action: Diagnosis_update
<li>entered by: amitra 
<li>description is: <p>During the PDB review I saw the first two chips (8f and 8e) could initialise and return data with no errors.  In SVXDAQ I chopped the chip chain and this ladder ran error free for 10,000 events in RA and NN mode.  So we can try to run this ladder with the two functioning chips 8e and 8f.</p>  <p>The HWDB has been updated and now just chips 8f and 8e are read out.  I have set the ISEL bits for other chips to zero.  For chips 8f and 84, the RDriver is now 4 and all other chips have RDriver=0.  Also the threshold for 8e and 8f is 9.</p>  <p>So observe this ladder for the next store and see how it performs.  If it is returning good data then keep this ladder in.  If it looks bad then take this ladder out.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B5W1&layer=L1">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Sat Aug 19 20:48:45 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB5W1L1 
<li>problem n: 1647 
<li>Status: needs_observation
<li>Type: AVDD
<li>Action: IMON_limits
<li>entered by: amitra 
<li>description is: <p>After chopping to just chips 8e and 8f, the AVDD IMON limits needs to be reduced.</p><table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>1225</td><td>1535</td></tr>
<tr><td><b>Lower</b></td><td>1120</td><td>1480</td></tr>
<tr><td><b>Upper</b></td><td>1235</td><td>1580</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B5W1&layer=L1">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Sat Aug 19 20:50:11 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB5W1L1 
<li>problem n: 1647 
<li>Status: needs_observation
<li>Type: DVDD
<li>Action: IMON_limits
<li>entered by: amitra 
<li>description is: <p>After chopping to just chips 8e and 8f, the DVDD IMON limits needs to be changed.</p><table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>445</td><td>290</td></tr>
<tr><td><b>Lower</b></td><td>315</td><td>200</td></tr>
<tr><td><b>Upper</b></td><td>590</td><td>350</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B5W1&layer=L1">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Sat Aug 19 21:15:01 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB4W0L3 
<li>problem n: 1720 
<li>Status: fixed
<li>Type: PC_Temperature
<li>Action: Chip_bit_changes
<li>entered by: amitra 
<li>description is: <p>The effect of changing the Z side ISEL bits was also a 10% reduction in the mean of the charge distribution.  The same effect as on the PHI side.</p>  <p>As the reduction in current and heat load was minimal, this experiment has stopped and the BIAS RATIO for all chips has returned to 1.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B4W0&layer=L3">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Sat Aug 19 21:17:31 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB4W0L1 
<li>problem n: 1725 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: Diagnosis
<li>entered by: amitra 
<li>description is: <p>The increase to 82V did not change the charge collection efficiency.  David Stuart suspects the bias could be off as much as 20V.  The bias was bumped up again to 86V.  We wait for the store to see if the charge collection improves.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B4W0&layer=L1">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Sat Aug 19 21:28:40 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB5W0L2 
<li>problem n: 1686 
<li>Status: needs_observation
<li>Type: AVDD
<li>Action: Diagnosis
<li>entered by: amitra 
<li>description is: <p>The changes in the current are often step functions, no gradual change.  At first glance, one would believe a chip would appear to 'come and go'.  However, there are no chopped chips and the current is going up from its nominal value.</p>  <p>It could be an ISEL chip setting could be changing which drives the up and down.  During quiet time, I adjusted an ISEL bit for all chips to simulate the change in current observed during data taking. ISEL bit 9 (Pipeline WriteAmp) made the AVDD current jump from 835&#956;A to 900&#956;A.  ISEL bit 4 (Integrator Cascade and NMOS Pre-amp) and ISEL Bit 2 (Integrator NMOS) would also drive the current to 900&#956;A. </p>  <p>As a conservative change, I set ISEL Bit 9 to 1 for all chips.  This may keep the AVDD current stable.  The other bit could have been changed but they affect the pre-amp and so may alter the amount of charge collected.</p>  <p>For the next week, check the AVDD current does not jump and down.  Als!
o check the data and ADC spectrum from the ladder are not altered.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B5W0&layer=L2">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Sat Aug 19 21:42:55 2006 -->
<h3>ISL DAQ-to-Cooling Converter</h3> 
Now that I had to learn the mapping of DAQ ladders to ISL cooling circuits in and out due to the ISL cooling problems, I created a little database with a web interface (essentially stolen from Marcel's PS Converter) to facilitate the mapping. Check it out: 
<a href="http://b0sili01.fnal.gov/coolconv/coolconv.html">http://b0sili01.fnal.gov/coolconv/coolconv.html</a>
<!-- Author: Ulrich -->


<!-- Date: Sat Aug 19 22:25:45 2006 -->
<h3>Quiet Time Studies</h3> 
 
<p>After the quench, there was 3+ hours of quiet time. We used the opportunity of go over some old PDB entries and to try reduce the heat load on the bad ISL cooling line CCE1.1.</p> 
 
<p><b>IB0W4L0</b> : I had masked the INIT READBACK during the shutdown.  But now the ladder has no problems initialising.  So I have removed the INIT READBACK mask.</p> 
 
<p><b>IB5W1L1</b> : This ladder has been played with by lots of former experts.  However I found I could always get data from  
chips 8f and 8e.  In SVXDAQ I chopped the chip chain and the ladder ran error free after 10,000 events in RA and NN mode.  So I implemented the changes in the HWDB.  I set the ISEL bits for 8e and 8f to 01-001-0101; all other chips had all ISEL bits set to zero.  The threshold for 8e and 8f was set to 9.  The RDriver values for 8e and 8f were set to 4 and all others were set zero.  It was then put back online via traceSilicon and the last chip was set in the FIB HWDB page.</p> 
 
<p><b>SB5W0L2</b> : Since coming out of the shutdown, the AVDD current for this ladder has been jumping up and down.  Normally this would be an indication of a chip "coming and going". However there are no chopped chips and the current is jumping up from its pre-shutdown value.</p> 
 
<p>Another mechanism driving this change could be the ISEL bits.  If an ISEL bit changes spontaneously, it would drive the AVDD current up.  An ISEL bit of 1 increases the current. So some bit which is normally 0 may jump to 1.</p> 
 
<p>During the quiet time, different ISEL bits were adjusted to simulate the jump in AVDD.</p> 
 
<p>Changing ISEL Bit 6 (INTEGRATOR RESET) from 0 to 1 for all chips increased AVDD from 835&mu;A to 840&mu;A.  So it is unlikely this bit is responsible.</p> 
 
<p>ISEL Bit 4 (INTEGRATOR CASCADE & NMOSE INTEGRATOR) causes AVDD to go 900&mu;A.  This could be responsible for the AVDD jumps.</p> 
 
<p>ISEL Bit 9 (PIPELNIE WRITEAMP) also makes the AVDD current jump upto 900&mu;A.  This bit could be responsible.</p> 
 
<p>ISEL Bit 2 (INTEGRATOR NMOS) make the AVDD current jump to 905&mu;A.  This bit could be responsible.</p> 
 
<p>Given the 3 choices, I decided to change ISEL Bit 9 for all chips to 1.  The other two afffect the integrator and this may affect the amount of collected charge.  Adjusting the currents for the Pipeline *should* not affect the collected charge.</p> 
 
<p>The next thing is to see how AVDD behaves over the next few days and see if it stabilies.</p> 
 
<p><b>IB4W0L1</b> : As part of the experiment to try to reduce the heat load on the bad ISL cooling line; the BIAS RATIO for this ladder was set to 0 for all chips.  If it follows IB4W0L3, one would expect a 10% reduction in the mean charge distribution for both sides.</p> 
 
<p>Also David Stuart suspected this ladder was not fully depleated.  He suspects it may be off by 20V.  The change in bias from 80V to 82V did not change the amount of collected charge.  The bias voltage has now been increased to 86V.  We shall see in the upcoming store if this has any effect.</p> 
 
<p><b>IB4W0L3</b>  The experiment of setting BIAS RATIO=0 did not not sigificantly reduce the heat load.  So BIAS RATIO=1 returned for all chips.</p> 
 
<p><b>Adjusting ISEL bits reduce heat load</b>  After the cooling problem was first discovered, Ulrich and I did play with some chips settings to see if it could reduce the temperature.It did have some effect but we did not carefully record what changes were most beneficial except for the BIAS RATIO.  In the meantime, David Stuart has been helping us out and suggesting settings to try out.</p> 
 
<p>Today, UIrich and I repeated the study and recording what we did at each step and the effect on AVDD and the temperature of the cooling line.  This observation are recorded in a TWiki page at: <a href="http://b0sili01.fnal.gov/cgi-bin/TWiki/bin/view/Silicon/ISLChipSettings"> 
http://b0sili01.fnal.gov/cgi-bin/TWiki/bin/view/Silicon/ISLChipSettings</a>.</p> 
 
<p>The biggest effect was switching ISEL Bit 3 (INITEGRATOR NMOS Current) to zero; the current reduced by 250&mu;A and the temperaure dropped by 0.3C.  The next largest was setting the BIAS RATIO to 0 which reduced AVDD by 120&mu;A and the temperature dropped by 0.2C.</p> 
 
<p>We already know the effect of changing the BIAS RATIO.  The next step in this experiment would be to change ISEL Bit 3 and examine the effect on data.</p>
<!-- Author: Ankush, Ulrich and Ricardo -->


<!-- Date: Sun Aug 20 01:02:35 2006 -->
<h3>Tevatron quenched after proton load</h3> 
Forgot to mention that the Tevatron was in shot setup earlier tonight already. They lost the protons due to a rad abort at D0: 
<pre> 
22:02:42-  
	Tev aborted due to losses at D0 BLMs. Losses at C4SM were pretty high prior to the abort. The separator didn't record a spark, but it happened just after the helix was opened. 
 - dln 
</pre> 
I have checked both D0&#39;s (ACNET E16) and our BLM plots (Java GUI), and both seem fine. The radiation in D0 increases shortly before the abort, but everything was well below 1 rad/s. The ops manager and I were wondering if D0 would request a full checkout and more quiet time, but the Tevatron went into shot setup relatively quickly after the incident.  
<!-- Author: Ulrich -->


<!-- Date: Sun Aug 20 01:37:41 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9637&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9638  width='300' align='top'></a></td><td><h3>Store 4914</h3> 
Store 4914 came in with 114.6e30. The rather low initial luminosity is due to the reduced stacking time after the Tevatron abort yesterday afternoon. All losses were well below 400 Hz, so I gave my permission to include the silicon. However, the startup got delayed due to L3 problems, so the silicon was ramped only after they were resolved. SVTSpyMon looks fine.</td></tr></table>
<!-- Author: Ulrich -->
<!-- Comment: Sun Aug 20 01;53;22 comment by...Ulrich -->
A few <a href=
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2006&action=view&page=600&frame=2&anchor=01:43:16.294'>
bias pinkies</a>...


<!-- Comment: Sun Aug 20 10;13;08 comment by...Ulrich -->
Drendel is almost happy with the store and wishes to keep it in until after midnight. We have requested a Dmode calibration at the end of store. Maybe we can get it done in the evening rather than in the middle of the night. Hereis Drendel again:
<pre>
 Sun Aug 20 09:38:21-  After the struggles during the day and evening that resulted in a ten hours of not integrating luminosity, Store 4914 was colliding by 1am with an average initial luminosity of 112.85e30. This is close to what I expected for the number of Pbars we shot from, but it still could have been better. There were still losses in the Main Injector on the Pbar transfers at 1.5 seconds and 4.5 seconds, with the 4.5 second loss being worse. The third and sixth transfers each lost about a third of the beam. Transfer number six also had a loss that started a around 3.75 seconds.
Initial projections of the Luminosity show that we probably can keep this store until sometime after midnight. I’ll determine an end of store time and a shot plan later on today.  - B Drendel  
</pre>
<!-- Date: Sun Aug 20 08:07:27 2006 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9639&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9639' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9640&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9640' width='300'></a></center>
<!-- Author: Yanjun -->
<!-- Comment: Sun Aug 20 10;14;50 comment by...Ulrich -->
Here are the pinkies of last night again. For unknown reasons, the monitoring Ace put them into our e-log as well.


<!-- Date: Sun Aug 20 19:26:06 2006 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9641&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9641' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9642&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9642' width='300'></a></center>
<!-- Author: Ulrich -->
<!-- Comment: Sun Aug 20 19;28;35 comment by...Ulrich -->
<h3>Recent bias pinkies</h3>
Here is the history of the two bias lines of IB5W1L3. Both show the expected increase in bias current over time, so I bump up both limits. Since IB5W1L1 has been out for quite some time, there is no history available. The Bias1 current appears to be stable, so I will introduce a new limit.

<!-- Date: Sun Aug 20 19:36:43 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB5W1L1 
<li>problem n: 1647 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: husemann 
<li>description is: Not only AVDD and DVDD, but also one of the bias currents (Bias1) needs an adjustment.<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>9.96</td><td>150.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>180.0</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B5W1&layer=L1">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Sun Aug 20 19:40:51 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB5W1L3 
<li>problem n: 1722 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: husemann 
<li>description is: Bias currents show usual increase over time. Bumping up both Bias0 (shown here) and Bias1 at the same time (although Bias1 has not yet reached its limit).<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>63.4841</td><td>105.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>150.0</td></tr></table> 
<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: Sun Aug 20 19:41:12 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB5W1L3 
<li>problem n: 1722 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: husemann 
<li>description is: Bias currents show usual increase over time. Bumping up both Bias0 and Bias1 (shown here) at the same time (although Bias1 has not yet reached its limit).<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>95.0</td><td>110.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>120.0</td><td>150.0</td></tr></table> 
<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: Sun Aug 20 22:54:24 2006 -->
<p><font size=+1> D-mode Calibration Job Started </font>
<p><pre>
Job id            : 445
Calibration type  : standard
Run period tag    : Aug_2006
DPS-off run       : 221807
DPS-on run        : 221805
Requested by      : Chunlei
Main process id   : 10585
Comment           : good
</pre>
<!-- Author: CDF silicon D-mode calibration job server v1.4 -->



<!-- Date: Mon Aug 21 01:14:57 2006 -->
Got paged on the RadCo pager because the BLM FIFOs did not record. Well, what would you expect, two minutes into shot setup? I repeated what I told them in the Ace training: "This is part of the Tevatron sequencer. It does not happen straight away but it should happen before the first beam goes in." Grump!
<!-- Author: Ulrich -->
<!-- Comment: Mon Aug 21 01;36;39 comment by...Sleepless in Naperville -->
But why worry? SVT got paged without reason as well.

<!-- Date: Mon Aug 21 03:39:08 2006 -->
<p><font size=+1> D-mode Calibration Job Finished </font>
<p><pre>
This is a computer-generated silicon D-mode calibration status report.
Silicon D-mode calibration job 445 FAILED.

Job info
--------
Calibration type : standard
DPS-off run      : 221807
DPS-on run       : 221805
Requested by     : Chunlei
Submitted        : 2006-08-20 22:54:19
Completed        : 2006-08-21 03:38:29
Status           : FAILURE
Comment          : good

Last processing stage reported : comparing to the reference calibration
Failure diagnostics :
The calibration failed the following reference comparison criteria:

            Cut Name    Sensor Set   Cut Value   Data Value
--------------------    ----------   ---------   ----------
bad_fraction abs max    SVX_PHI      0.035       0.035564  

Reference calibration runs are 220872 (DPS off) and 220869 (DPS on)
</pre>
<!-- Author: D-mode script run_calib_analysis.tcl -->
<!-- Comment: Mon Aug 21 12;17;33 comment by...Jason -->
I checked the individual ladders, and this calibration is OK.  The previous calibration had a dissimilarity value that was just less than the threshold of 0.035; this one is just greater.
<br>
I have submitted this calibration to the used sets maker so that it can be associated with yesterday's data runs.  I also changed the dissimilarity threshold from 0.035 to 0.040 in the calibration analysis code on b0sili01.
<!-- Date: Mon Aug 21 03:59:34 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9643&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9644  width='300' align='top'></a></td><td><h3>Store 4915</h3> 
Store 4915 started with a luminosity of 167.6e30. The losses were below 700 Hz. SVTSpyMon looks good. 
<p> 
Again I tried to let the shift crew make more of the decision to include the silicon. I was watching things from home closely, and I told them that I would only call in if I do not want the silicon to be ramped. The store looks fine, and they ramped the silicon straight away.</td></tr></table>
<!-- Author: Ulrich -->
<!-- Comment: Mon Aug 21 04;06;05 comment by...Ulrich -->
SVXMon looks fine, too.


<!-- Date: Mon Aug 21 08:23:54 2006 -->
<h3>b0fib06 went red in RC</h3> 
At about 4:30 this morning, 
<a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2006&action=view&page=603&frame=2&anchor=04:32:45.854'> 
b0fib06 went red in RC</a>. The crate was not pingable, so the Aces shepherded it. After an auto-HRR, it turned red again. This time it was pingable, so they rebooted the crate and brought it back to the run.
<!-- Author: Ulrich -->


<!-- Date: Mon Aug 21 08:52:28 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9645&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9645  width='300' align='top'></a></td><td>Bias0 keeps raising in f204. 
</td></tr></table>
<!-- Author: Ricardo -->

<!-- Date: Mon Aug 21 09:00:46 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB2W0L4 
<li>problem n: 809 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: ricardo 
<li>description is: According to the history it looks like the Bias current (channel 0) is ramping faster than before the shutdown. We jut got a pinky in IMON and will raise the limits.  <table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>110</td><td>110</td></tr>
<tr><td><b>Lower</b></td><td>0.5</td><td>0.5</td></tr>
<tr><td><b>Upper</b></td><td>140</td><td>150</td></tr></table> 
<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: Mon Aug 21 09:08:35 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB3W8L0 
<li>problem n: 1701 
<li>Status: fixed
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: ricardo 
<li>description is: Bias current in e380 exceeded the limit, as predicted by Ankush in the last entry.  Limits changed.<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>101</td><td>101</td></tr>
<tr><td><b>Lower</b></td><td>0.5</td><td>0.5</td></tr>
<tr><td><b>Upper</b></td><td>110</td><td>120</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B3W8&layer=L0">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Mon Aug 21 09:17:29 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W10L3 
<li>problem n: 1705 
<li>Status: fixed
<li>Type: Unknown
<li>Action: Monitoring
<li>entered by: alscott 
<li>description is: Also, after I read the above reports by Ankush, he reported that the ladder returned no data on 8/2/2006.  Run 220898 was taken on 8/2/2006.  The problem reported by Ankush has not recurred.  Still fixed. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B0W10&layer=L3">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Mon Aug 21 09:22:41 2006 -->
<pre>For detector: 
LB0W2L3 - ADCdist sick, probably not seeing physics. 
 
Fixed: 
IB1W2L2 - Bump; nothing to be done. 
IB4W1L4 - Physics tail is not low anymore. 
SB0W10L3 - Error free since RX swap. 
SB1W8L2 - Bump. 
 
For monitoring: 
IB4W4L2 - ADCdist looks improved after bias voltage increase; check still good after a few weeks. 
</pre>
<!-- Author: Adam Scott -->
<!-- Comment: Mon Aug 21 09;23;06 comment by...Adam Scott -->
Forgot to say, this is monitoring summary.


<!-- Date: Mon Aug 21 09:29:24 2006 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9646&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9647' ></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9648&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-9649' ></a></center>
<!-- Author: Ankush -->
<!-- Comment: Mon Aug 21 09;31;37 comment by...Ankush -->
<h3>How to make Ankush happy</h3>

<p>A: Reduce the number of "NEEDS OBSERVATION" threads !!!</p>

<p>Next step: Reduce the number of "NEEDS WORK" threads.</p>
<!-- Date: Mon Aug 21 09:30:37 2006 -->
<h3>Summary of the Week</h3> 
 
Monday, August 14 
<ul> 
  <li>AGIGI2 on the rise, cleaned by Tevatron tune change</li> 
  <li>ISL bias pinkies: no correlation of bias current increase and temperature</li> 
  <li>ISL CCE1.1 output temperature on the rise</li> 
  <li>Swapped bias cables in IB5W1 detected</li> 
  <li>Starting clean-up of "needs observation" threads in problem database</li> 
  <li>Interlock test stand: new ethernet card configured</li> 
</ul> 
 
Tuesday, August 15, 
<ul> 
  <li>Store 4905: initial luminosity 120e30, problems with loss monitors</li> 
  <li>More bias pinkies</li> 
  <li>Ordered analysis of more water analyses: SVX coolant and pristine water-glycol mixture</li> 
  <li>SVX chiller return temperature slowly increasing (at the same input temperature</li> 
  <li>Tools to plot bias current vs. integrated luminosity</li> 
  <li>Problem database clean-up continues: 
      <ul> 
	<li>Bias1 current for IB$W1L1 dropped to 0: rediscovered old problem</li> 
	<li>Bias0 current for IB0W3L2 erratic: PS problem?</li> 
	<li>DOIM currents for SB4W6 dropping: flaky SVX supply?</li> 
      </ul> 
  </li> 
  <li>New script to further automate permanant light level measurement</li> 
</ul> 
 
Wednesday, August 16 
<ul> 
  <li>ISL bulkhead 4 tripped on high temperature from CCE1.1 (problematic coolin line), temperature jumped up within &lt;5 minutes, everything recovered fine</li> 
  <li>Interlock problem: IB4W3 did not trip! Reason: J72 (5V enable bypass) not removed after PS swap</li> 
  <li>SVXIICON: regular reboot</li> 
  <li>Store 4906: initial luminosity 123e30, no problems</li> 
  <li>Bias currents for SB0W9L2, SB3W6L2, SB3W8L0 erratic (increasingly after the shutdown)</li> 
  <li>Great silicon office summer clean-up</li> 
</ul> 
 
Thursday, August 17 
<ul> 
  <li>Controlled access & quiet time studies 
      <ul> 
	<li>Fixed interlock problem: removed jumper J72 from PS in IB4W3</li> 
	<li>Unswapped bias cables in IB1W5L3</li> 
	<li>Test of chip settings in IB4W0L3 to reduce heat load: bias ratio 0 (10% reduction in cluster charge)</li> 
	<li>Check IB4W0L1 for under-depletion</li> 
	<li>Check SB4W0L4: bit 6 low</li> 
      </ul> 
  </li> 
  <li>Store 4909: initial luminosity 145e30, RT server died during startup</li> 
       
</ul> 
 
Friday, August 18 
<ul> 
  <li>AVDD current of SB5L0W2 erratic: PS or chip problem?</li> 
  <li>Reformatter errors: cause of problem unclear, FIB already swapped, could swap VRB</li> 
  <li>Silicon General meeting</li> 
</ul> 
 
Saturday, August 19 
<ul> 
  <li>Store 4910: initial luminosity 141e30, aborted around 15:00</li> 
  <li>New ISL DAQ-cooling terminology converter with web interface</li> 
  <li>Quiet time studies: 
      <ul> 
	<li>IB0W4L0: removed INIT READBACK mask</li> 
	<li>IB5W1L1: reincluded, chopped all but two chips</li> 
	<li>SB5W0L2: change ISEL bits to mitigate AVDD current jumps</li> 
	<li>IB4W0L3: systematic check of ISEL bits and BIAS RATIO to reduce heat load</li> 
      </ul> 
  </li> 
  <li>Tevatron quench on D0 BLMs after proton load</li> 
</ul> 
 
Sunday, August 20 
<ul> 
  <li>Store 4914: initial luminosity 115e30, no problems</li> 
  <li>D-mode calibration</li> 
</ul> 
 
Monday, August 21 
<ul> 
  <li>Store 4915: initial luminosity 168e30, no problems</li> 
  <li>b0fib06 went red</li> 
</ul>  
<!-- Author: Ulrich -->