<!-- Title: 11:04:02  Mon Dec  3 2007 -->
<!-- Crewchief: Ricardo (MPC) -->
<!-- Op1: Ignacio (SPL on call) -->
<!-- Op2: &nbsp; -->
<!-- Op3: &nbsp; -->
<!-- Op4: &nbsp; -->
<!-- Op5: &nbsp; -->
<!-- Op6: &nbsp; -->
<!-- Notes: -->
Keep on taking good data.


<!-- Date: Mon Dec 3 12:46:26 2007 -->
While working in the first floor on setting cables to pinpoint the clock problems we produced a chain of clock glitches. The ace recovered them by HRR as per my request.   
<!-- Author: Ricardo & SebaG -->
<!-- Comment: Mon Dec  3 13;36;39 comment by...Ignacio -->
<a href=
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2007&action=view&page=944&frame=2&anchor=13:29:30.289'>
This </a> also happened.


<!-- Date: Mon Dec 3 14:43:54 2007 -->
We finished the setup. The LA has now two extra CDF_CLK (SYNC) clock signals. One is named "SILI SYNC 1" and is taken from the silicon clock fanout in the first floor, directly from the NIM output where the input clock cables go in. The other is named "SYNC 2" and is taken from the clock fanout crate that is just below the silicon clock fanout crate. This is one is also taken from the nim output. <br> 
In addition we have the clock in the 2nd floor triggering with the LA in the first floor, and looking at the SYNC signal that comes from a board of the silicon clock fanout crate.  
In the next clock glitch, if everything is up an running, we should see if this is a cdf-wide clock problem, a silicon fanout problem, or a board problem.
<!-- Author: Ricardo/SebaG/SashaS -->
<!-- Comment: Mon Dec  3 16;15;32 comment by...Ricardo/SebaG/Ignacio/SashaS -->
<table border=0><td><tr><td>The file in the LA is now called "CLK_SRCERR_V1_Dec3_2007_1604.ala"  if you have a resonance  please save this file with the NEW DATE AND TIME, and make sure you save also the clock trace of channel 1 and 4 in the 2nd floor scope, and then re-trigger it.
</td></tr></td></table>


<!-- Comment: Tue Dec  4 08;58;33 comment by...Ricardo & SashaS -->
<table border=0><td><tr><td bgcolor=#e0e030>I came this morning during quiet time, generated an SRC error and the LA did not fire. I won't bother explaining why. Bottom line I made a trigger that is tested under ALL conditions and it seems to work, this one is called "CLK_SRCERR_V1_Dec4_2007_0839.ala". In addition I connected the nim SYNC clock output of the clock fanout in 2RR29C  to the scope in channel 2.<br>
The mail servers are not working at this time, so we need to test the mail capabilities of the LA at some point later today.<br>
 </td></tr></td></table>
<!-- Comment: Tue Dec  4 14;11;31 comment by...Ricardo -->
I tested the email and it is back to working. The problem was associated with the imapserver1 server.

<!-- Date: Mon Dec 3 21:17:21 2007 -->
They aborted the beam during scrapping, a couple of minutes after the squezze was done. A pity since there were around 70 mA pbars per bunch.
<!-- Author: Ignacio -->




<!-- Date: Tue Dec 4 15:05:47 2007 -->
It happend again during the night. Ricardo has posted the diamond abort data in the main e-log.
<!-- Author: Ignacio -->


<!-- Date: Tue Dec 4 15:06:46 2007 -->
I have added 131.225.240.250 to /etc/resolv.conf in b0sili01, b0sili02 and b0sili03 as Lammel advices.
<!-- Author: Ignacio -->


<!-- Date: Tue Dec 4 15:38:02 2007 -->
We have measured the flow coming out fomr the Air Separators. SVX 0. ISL <b>9-9.5 </b>GPM.
<!-- Author: Ignacio -->


<!-- Date: Wed Dec 5 10:11:18 2007 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-12122&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-12122  width='300' align='top'></a></td><td>Store 5780 is in with initial lum of 125E30 and losses about 13KHz. SVTmon looks good and SVXMon is ok, except perhaps for e393 that gives bit 3 low, as always.</td></tr></table>
<!-- Author: Ricardo -->


<!-- Date: Wed Dec 5 11:11:19 2007 -->
For the day I'm testing the new version of IMON, in the directory ~svxii/imon_dev_Dec05_2007 with Jose's improvements.
<!-- Author: Ricardo -->
<!-- Comment: Wed Dec  5 13;02;48 comment by...Jose -->
Notes of the <i>new features</i> are:
<ul>  <li>Possibility to stop alarm pop-ups. </li>
 <li> Duplicated saving of the History plot (History_XXX.jpg and Last_History.jpg). </li> 
 <li> Lengthy ToolTips including more information.</li>
 <li> Display of the cooling lines on the channel information.</li>
 <li> New mapping utility to show ladders on certain PS crate, Fib crate and cooling line.</li>
</ul>


<!-- Date: Wed Dec 5 13:08:16 2007 -->
There was an SVX resonance that was cleared by the ACE. The trace was saved to disk, the LA re-armed, and the scope in the 2nd floor rearmed.
<!-- Author: Ignacio & Ricardo -->


<!-- Date: Wed Dec 5 13:14:35 2007 -->
From cryo e-log: 
<pre> 
Warren and KC are relocating the O2 and flow instruments on the vacuum pump exhaust for ISL and SVX to the alcove area main floor. No readings until later. - Bill Noe 
</pre>
<!-- Author: Ignacio -->

<!-- Date: Wed Dec 5 13:35:24 2007 -->
Entered in Silicon database: <ul>
<li>Ladder: IB1W1L0 
<li>problem n: 2276 
<li>Status: fixed
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: ricardo 
<li>description is: Bumping up imons limits for Bias 1.<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>50</td><td>0.5</td></tr>
<tr><td><b>Lower</b></td><td>0.5</td><td>0.5</td></tr>
<tr><td><b>Upper</b></td><td>155</td><td>180</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B1W1&layer=L0">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Dec 5 13:36:11 2007 -->
Entered in Silicon database: <ul>
<li>Ladder: IB1W1L0 
<li>problem n: 2276 
<li>Status: fixed
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: ricardo 
<li>description is: Bumping up imons limits for Bias 1.<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>50</td><td>0.5</td></tr>
<tr><td><b>Lower</b></td><td>0.5</td><td>0.5</td></tr>
<tr><td><b>Upper</b></td><td>155</td><td>180</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B1W1&layer=L0">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Dec 5 13:39:11 2007 -->
Entered in Silicon database: <ul>
<li>Ladder: IB1W0L2 
<li>problem n: 2216 
<li>Status: fixed
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: ricardo 
<li>description is: Bumping up Bias 1 limits. <table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>68</td><td>68</td></tr>
<tr><td><b>Lower</b></td><td>0.5</td><td>0.5</td></tr>
<tr><td><b>Upper</b></td><td>160</td><td>180</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B1W0&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Dec 5 14:12:16 2007 -->
Entered in Silicon database: <ul>
<li>Ladder: IB2W0L2 
<li>problem n: 2269 
<li>Status: fixed
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: ricardo 
<li>description is: Changing bias 1 limits<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>160</td><td>160</td></tr>
<tr><td><b>Lower</b></td><td>0.5</td><td>0.5</td></tr>
<tr><td><b>Upper</b></td><td>215</td><td>250</td></tr></table> 
<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: Wed Dec 5 14:17:16 2007 -->
b0fib00 went red while running. At reboot the crate reported "Unable to open startup script boot/front-end/startup.cdf". We took the silicon out, page DAQ, while simultaneously having an autohockerization on crate 15. DAQ pager called back (BillW) and told us he mistakenly has done something, and he fixed the problem in the spot. We are now back taking data with silicon, and I instructed the ACE to put the downtime under DAQ. 
  
  
<!-- Author: Ricardo -->

<!-- Date: Wed Dec 5 14:20:19 2007 -->
Entered in Silicon database: <ul>
<li>Ladder: IB2W0L0 
<li>problem n: 2267 
<li>Status: fixed
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: ricardo 
<li>description is: Increasing the Bias 0 limits.<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>130</td><td>130</td></tr>
<tr><td><b>Lower</b></td><td>0.5</td><td>0.5</td></tr>
<tr><td><b>Upper</b></td><td>190</td><td>220</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B2W0&layer=L0">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Dec 5 14:34:35 2007 -->
Entered in Silicon database: <ul>
<li>Ladder: IB4W1L0 
<li>problem n: 2359 
<li>Status: fixed
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: ricardo 
<li>description is: Increasing Bias 1 limits<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>100</td></tr>
<tr><td><b>Lower</b></td><td>0.5</td><td>0.5</td></tr>
<tr><td><b>Upper</b></td><td>155</td><td>185</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B4W1&layer=L0">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Wed Dec 5 15:53:39 2007 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-12123&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-12123' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-12124&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-12124' width='300'></a></center>
<!-- Author: Ignacio -->
<!-- Comment: Wed Dec  5 15;59;11 comment by...Ricardo/Ignacio -->
Ricardo noticed many ISL ladders that go up/down in bias current at around 11/15/07.  I have seen a jump in ISL east flows around that time but I am no sure if it si actually the result of rebooting svxiicon. Could the silicon cooling pager investigate a bit?
<pre>
For instance: 
f520,f400,f414, f424 go up
f430 go down
f422, oen bias line goes up, one down.
</pre>


<!-- Comment: Thu Dec  6 21;32;43 comment by...Ulrich -->
Those lines are nicely distributed among East supply lines 2-4. So if the observed behavior has a single cause, it must be global to the cooling system. Looking at where these ladders live geometrically, you'll find that everybody is in the forward inner Layer7 bulkhead (except f520), all in the upper half of the detector. Could the ambient temperature in that area have changed?
<!-- Date: Wed Dec 5 16:08:41 2007 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-12125&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-12125  width='300' align='top'></a></td><td>I will increase the AVDD upper limit that Juan Pablo set to 1410. BTW, I think the symptoms suggest this is another candidate for broken wire bond.</td></tr></table>
<!-- Author: Ignacio -->

<!-- Date: Wed Dec 5 16:10:11 2007 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W2L4 
<li>problem n: 1243 
<li>Status: fixed
<li>Type: AVDD
<li>Action: IMON_limits
<li>entered by: ignacio 
<li>description is: Increase upper limit since AVDD fluctuates continously.<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>1180</td><td>1180</td></tr>
<tr><td><b>Lower</b></td><td>1140</td><td>1140</td></tr>
<tr><td><b>Upper</b></td><td>1240</td><td>1410</td></tr></table> 
<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: Wed Dec 5 17:18:33 2007 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-12126&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-12126  width='300' align='top'></a></td><td>SVX air separtor level getting close to the warning limit and fluctuating below it.  Time to refill.  I have silenced the alarm for now and will e-mail Bill to have it refilled.  Interestingly the level dropped when a stronger vacuum pump was valved in.  The pressure dropped but so did the level.</td></tr></table>
<!-- Author: Tom Junk -->


<!-- Date: Wed Dec 5 17:46:47 2007 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-12128&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-12128  width='300' align='top'></a></td><td>This may be linked to the change in ISL bias currents around  11/14/07.</td></tr></table>
<!-- Author: Tom/Ignacio -->
<!-- Comment: Thu Dec  6 14;51;08 comment by...Ulrich -->
I doubt that there is such direct connection between ladder temperatures (which translate to bias currents) and flow changes. As long as a cooling line gets sufficient flow, the coolant should be able to transport away all the heat. With a flow rate of above 2 lpm, the flow should be plenty. There is one big "if": If a given ladder has restricted flow, you could get such an effect. So one question would be what temperature gradient between input and output of the affected ladders is. If such a connected between low global flow, low local flow and temperature can be established, it is still not clear what to do against it. If we increase the flow rates it is not clear if the flow to an individual cooling line would increase (it could even decrease). Just my two cents.
<!-- Comment: Thu Dec  6 20;17;46 comment by...Tom -->
These flow changes are rather small (of the order of 5% of the flow in the individual channels).  The e-log only has an svxiicoin reboot at the time of the step indicated above.

<pre>
Circuit  Pre-step flow (lpm)     Post-step     Flow on Dec. 6
CCE1       1.76                    1.82          1.83
CCE2       2.39                    2.26          2.26
CCE3       2.33                    2.24          2.26
CCE4       2.00                    1.97          1.94
PCE        2.37                    2.34          2.34
</pre>

I can try to open the valves a bit on CCE2 and CCE3 to try to recover the pre-step flows, but only move them a tiny bit.

A longer-term history plot is attached later in the e-long (Dec. 6, around 8:30 PM).
<!-- Comment: Thu Dec  6 21;17;34 comment by...Ulrich -->
The iFix PC reboot would definitely explain the step in the historical plots. We've seen values not coming back to exactly the same reading before.
<!-- Date: Wed Dec 5 17:48:37 2007 -->
Jose passed by and solved the problem with new IMON mapping. We had also forgotten to change the file with the limits (now ../imon/lookup.txt) so we have reincluded the changes from this week.
<table border=0><td><tr><td bgcolor=#e0e030> Come and try it!</td></tr></td></table>
<!-- Author: Jose/Ttito/Ignacio -->


<!-- Date: Wed Dec 5 21:13:08 2007 -->
There was a resonance  
<pre> 
25'15" b0svx02:Messenger:Dec 5, 2007 06:25:15 PM->SRC Fatal Error:Sl 6 Resonance Detected  
</pre> 
and two clock glitches.  
<pre> 
39'59" b0svx02:Messenger:Dec 5, 2007 08:39:59 PM->SRC FatalError:Sl 6 Too Many L1A 2 L1A to Buff  
49'27" b0svx06:Messenger:Dec 5, 2007 08:49:27 PM->SRC Fatal Error:Sl 6 L2A w/o L1A  
</pre>. I have saved the trace of the first one (could not catch the second one). The LA triggered on the sync clock trigger (which shows a clear glitch), the SRC error arriving 120 mus later. All the other clocks look fine but I have not scan all the time range available since I wanted to have it up and running. The scope has trigger and I have asked to leave it like that so we can have a look in the morning. The coincidence with a BMU SE 156 trip in both glitches really blows my mind! 
 
If looking at the traces tomorrow we have clear indication that the fanout board has to be changed, the LINAC problems could offer a good oportunity.  
<!-- Author: Ignacio -->
<!-- Comment: Thu Dec  6 09;40;49 comment by...Sebastian -->
How do you know that the second error (08:49) is a clk glitch? It reports a L2 without a L1.
<!-- Comment: Mon Dec 10 08;38;25 comment by...Ignacio -->
We have seen clock glitches reporting that error, but you are right 
that without the LA trace I cannot claim it 100 % sure.
<!-- Date: Thu Dec 6 01:09:38 2007 -->
Electron lense tripped. Now running.
<!-- Author: Ignacio -->


<!-- Date: Thu Dec 6 09:02:57 2007 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-12129&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-12129  width='300' align='top'></a></td><td>LA trace of the first clock glitch. The scope in the 2nd floor was connected to two channels: the cdf clock of a different board and the cdf clock of crate 2RR29C. Both these clocks show no interruption, or irregulatities at the moment of the trigger and in the range of plus/minus 2 us. The scope was trigger directly by the signal of the LA. If the delay between the LA triggering and the scope triggering is less than 2 us, this clearly indicates a failure of the clock between the backplane of the silicon clock fanout crate and the input of the SRC. It could be the clock fanout board or the cable from the clock to the SRC. But since we saw the glitch in both SRC's it is unlikely is the cable. This incident in itself point to the clock fanout board.</td></tr></table>
<!-- Author: Ricardo/SashaS/Ignacio -->



<!-- Date: Thu Dec 6 10:55:11 2007 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-12130&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-12130' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-12131&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-12131' width='300'></a></center>
<!-- Author: Oscar/Ignacio -->
<!-- Comment: Thu Dec  6 10;57;01 comment by...Oscar -->
These are the trigger rates at L1 and L2 for the first run of the Silicon Bias Scan we are currently taken. The L2 is stable at 200 Hz due to a rate-limited trigger. The L1 has a DPS trigger that is unprescaled as we are taking data due to the available bandwidth.


<!-- Date: Thu Dec 6 12:05:05 2007 -->
We have performed the bias scans for different detector layers.  
For all the scans we used the AAA_CURRENT table using for the trigger the decoupled table SILI_BIAS_SCAN [4,995,706], for which we use the suggested L3.<br> 
Store number: 5780<br> 
We performed a course scan for L00 using run 254826 and a fine scan for L00 and SVX-L0 in the same run 254826 and 254827, started after some L2 Decision Time Out. 
<br> 
<b>Coarse scan points (for the L00) are:</b> 
 
<pre>  
         VOLTAGE      EVENT RANGE    START TIME   
            0            0-41134        8:42am  RUN 254826 
         -130        41135-67672        8:48  
         -110        67673-91155        8:52  
          -90        91156-115760       8:56   
          -70       115761-140449       9:01 
          -50       140450-166278       9:06   
          -30       166279-190356       9:12            
          -10       190357-215632       9:18     
            0       215633-240735       9:24        
</pre> 
<b>Extended scan points (for the L00 and L0) are:</b> 
<pre> 
         -120       240736-291404        
          -95       291405-318072 
          -90       318073-343365         
          -85       0-25526             10:00 RUN 254827           
          -80       25527-50411    
          -75       50412-74501          
          -65       74502-100689          
          -60       100690-125130          
          -55       125131-152830         
          -45       152831-173674              
          -40       173675-200010              
          -35       200011-225531        
          -25       225532-250694              
          -20       250695-275742              
          -15       275742-308570  
           -5       308571-335129 
            0       335130-386422        11:13 
</pre>  
<br>  
  
<!-- Author: Roberto, Ignacio y yo mismo -->
<!-- Comment: Thu Dec  6 12;06;32 comment by...Oscar et al. -->
<pre>The CAENVolts.dat file was at this moment: /cdf/onln/data/svxii/caencontrol/PSfiles/caenvoltsfiles/CAENvolts_11302007_0354PM.dat</pre>
<!-- Date: Thu Dec 6 12:05:09 2007 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-12132&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-12132' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-12133&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-12133' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-12134&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-12134' width='330'></a></center>
<!-- Author: Roberto/Oscar/Ignacio/Ricardo -->
<!-- Comment: Thu Dec  6 12;19;25 comment by...Oscar/Roberto/Ricardo/Ignacio -->
We were measuring the RBSY distribution during the bias scan using SebasC histogramming utility:
<ul>
<li> First plot is the RBSY for the first biasscan run. We were integrating and we realized that althiugh no 35 mus peak was present, the distribution was moving towards higher values. The L1 rate went in 3 steps: 3KHz, 9KHz and 18 KHz. L2 rate was stable at 200 Hz (as it should be). </li>
<li>Then we measured a RBSY while the L1A rate was stable, first at 9KHz and then at 18 KHz (central plot). We could see the shift in the distribution and the increase in the tail. </li>
<li> Then we moved to physics trigger. The initial L1A was really low (600 Hz): no 35 mus peak was visible. After a few minutes the prescale changes  kicked in, taking the rate to 24 KHz (right plot): the 35 mus peak became apparent.</li>
</ul>
So, the conclusion is that either the L1A level makes a difference or that the prescale change introduces events that 
have the 35 mus feature in. The suspect triggers would be:
<pre>
14 L1_TRK5.5_TRK2.5_&_CJET5_LUMI_150 [2] 1 2007.12.06 11:46:45 204 0 0.0 688.8 0 1 Y 
17 L1_TWO_TRK2_B_HAD_LUMI_80 [2] 1 2007.12.06 11:46:45 204 0 0.0 688.8 0 1 Y 
18 L1_TWO_TRK2_DPHI90_LUMI_35 [2] 1 2007.12.06 11:46:45 204 0 0.0 688.8 0 1 Y 
48 L1_MET15_&_JET5_&_TWO_TRK2_LUMI_150 [2] 1 2007.12.06 11:46:45 204 0 0.0 688.8 0 1 Y 
29 L1_TAU0_TRK10_LUMI_0_40 [1] 1 2007.12.06 11:46:45 204 0 0.0 688.8 0 1 Y 
33 L1_TWO_TRK2_DPHI90_PS2_LUMI_50 [2] 1 2007.12.06 11:46:45 204 0 0.0 688.8 0 2 Y 
34 L1_TWO_TRK10_DPHI20_LUMI_0_60 [2] 1 2007.12.06 11:46:45 204 0 0.0 688.8 0 1 Y 
20 L1_BMU10_BSUR_TSUO_LUMI_190 [1] 1 2007.12.06 11:46:45 204 0 0.0 688.8 0 1 Y 

</pre>






<!-- Comment: Thu Dec  6 15;02;27 comment by...Ignacio -->
To compare, the biasscan trigger is a track trigger based, L1 bits 5 7, 23.
<pre>
5       L1_TWO_TRK2_DPS_v-1
7	L1_TEN_TRK2_PS250_v-2
23	L1_MB_XING_PS1M_v-2
</pre>
So, no overlap.
<!-- Date: Thu Dec 6 12:41:13 2007 -->
Switch off L00 for crystal collimator studies.
<!-- Author: Ignacio -->
<!-- Comment: Thu Dec  6 20;13;00 comment by...Ricardo -->
studies are done, we are in access but I put L00 back to stand by.

<!-- Date: Thu Dec 6 13:33:21 2007 -->
Bill asked for a good time to swap the DI flowmeters and to refill the air separator.  We just told  Bill/KC that now is a good time for these operations.
<!-- Author: Ignacio -->
<!-- Comment: Thu Dec  6 13;51;33 comment by...Ignacio -->
There was a small glitch in the flows.

<!-- Comment: Thu Dec  6 14;45;53 comment by...Ignacio -->
It is done (See cryo e-log). The SVX conductivity has gone up to 1.4 muSi/cm as the news coolent was added. Now going slowly down.






<!-- Date: Thu Dec 6 20:19:02 2007 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-12135&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-12135  width='300' align='top'></a></td><td>ISL East side flow history, going back to early November.  There are several small steps in the flows before and since.</td></tr></table>
<!-- Author: Tom -->
<!-- Comment: Thu Dec  6 20;52;37 comment by...Tom -->
<pre>I have increased the flows a bit to the ISL east side.
The table now:

&lt;pre&gt;
Circuit    Pre   Post   Morning   Tuned (now)  Valve pos
CCE1       1.76   1.82   1.83     1.81          48% (unchanged)
CCE2       2.39   2.26   2.26     2.38          51%
CCE3       2.33   2.24   2.26     2.37          51%
CCE4       2.00   1.97   1.94     2.44          51%
PCE        2.37   2.34   2.34     2.34          50% (unchanged)
&lt;/pre&gt;

One thing I noticed is that there is some hysteresis in the valves.  I opened them all up to 57% and nothing happened.  Closing them to 50% and opening them to 59% made flows change.  Easing them back towards 50% had a slow effect on the flows I did not see on the way up.  I suspect that the history of how the valves get to these settings is as important as the settings themselves when trying to control the flows at the 5% level.

Anyhow, let's let the flows sit at these levels for a while and see if there's any effect on the bias currents.</pre>


<!-- Comment: Thu Dec  6 21;20;36 comment by...Ulrich -->
Yes, there is some hysteresis, especially when you change things by less than 5% at a time. In the end it shouldn't matter too much. My guess is that equalizing effects between the cooling lines are a much bigger effect. If the system can redirect a small pressure change somewhere else, you don't see an effect on the flows. Again, I would be very surprised if the this has an effect on the bias currents.



<!-- Date: Fri Dec 7 08:58:32 2007 -->
We put a hygrometer in the svx06 crate. We will monitor humidity, temperature and DP in this crate.
<!-- Author: Ricardo/SashaS -->
<!-- Comment: Fri Dec  7 10;08;15 comment by...Ricardo & SashaS -->
Here's a set of measurements done 30 minutes after the probe was in each place. 
<table border=1>
<tr><th></th> <th> Inside Rack 1RR21I</th><th> Outside Rack 1RR21I </th> </tr>
<tr><td> RH     </td><td> 32.8  </td><td> 22.6  </td></tr>
<tr><td> T  (C) </td><td> 15.26 </td><td> 20.75 </td></tr>
<tr><td> DP (C) </td><td> -1.0  </td><td> -1.3  </td></tr>
</table>



<!-- Date: Fri Dec 7 12:42:12 2007 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-12136&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-12136  width='300' align='top'></a></td><td>Store 5787 is in with an initial lum of 163E30, losses around 8 kHz. SVTmon and SVXMOn look OK.</td></tr></table>
<!-- Author: Ricardo -->


<!-- Date: Fri Dec 7 14:36:51 2007 -->
The electron less went off and after 10 minutes to stand-by. Ron Moore (as SciCo) call his guys and they are working on the electron lens now. See main <a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2007&action=view&page=956&frame=2&anchor=14:11:56.668'> 
entry</a>. 
 
 
  
<!-- Author: Ricardo -->


<!-- Date: Fri Dec 7 16:34:29 2007 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-12137&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-12138  width='300' align='top'></a></td><td>There was a SRC error: L2A w/0 L1A. There is clock glitch in the SRC bunch structure 250 mus earlier. The glitch last for around 200 mus. Sync and ISL clocks looked fine.</td></tr></table>
<!-- Author: Ssha/RIcardo/Ignacio -->
<!-- Comment: Fri Dec  7 16;42;29 comment by...Ignacio -->
There were a few AVDD/DVDD pinkies but the HRR cycle after the error cured them.


<!-- Date: Fri Dec 7 19:19:09 2007 -->
We had another clock glitch and again only the SRC inputs were affected. And while writing this we got another, 5 minutes apart! 
We arranged today with Steve Chappa to put a new board on Monday. We will connect it to the ISL SRC  sometime after that. 
<!-- Author: SashaS/RIcardo -->
<!-- Comment: Fri Dec  7 19;35;20 comment by...Ricardo -->
Forgot to say that the BMu tripped twice as well.
<!-- Date: Fri Dec 7 19:33:04 2007 -->
Hockerization of crate #15. L00 B1W5 came back only after the second trial.
<!-- Author: Ricardo/SashaS -->



<!-- Date: Sat Dec 8 08:04:37 2007 -->
Clock glitch at 1:57, BMU SE 156 tripped too. The glitch is seen only in the SRCs, the scope shows nothing. I re-armed the LA and the scope.  
<!-- Author: Ricardo -->


<!-- Date: Sat Dec 8 11:34:16 2007 -->
Resonance at 8:03. It was not a clock glitch.
<!-- Author: Ricardo -->
<!-- Comment: Sat Dec  8 11;34;55 comment by...Ricardo -->
Sved the LA trace and re-armed the LA and the scope. 


<!-- Date: Sat Dec 8 12:54:38 2007 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-12140&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-12140  width='300' align='top'></a></td><td>e033 gave a pinky. The bias current of this guy is shooting for the stars. I'll set it to ignore in IMON, but we need to understand what's happening with it. 
</td></tr></table>
<!-- Author: Ricardo -->


<!-- Date: Sat Dec 8 15:28:31 2007 -->
Got paged because of a hockerization. 
Ace (Tito) was not sure what to do.
<!-- Author: Ricardo -->


<!-- Date: Sat Dec 8 20:37:32 2007 -->
Store 5788 is in, but I left the sili out since losses were above 20 KHz. Then I noticed MCR started tuning the Tevatron, and losses wondered about and below our limits. Once they stabilize it we put silicon in.
<!-- Author: Ricardo -->


<!-- Date: Sat Dec 8 21:27:57 2007 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-12141&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-12141  width='300' align='top'></a></td><td>Store 5788 came in with an initial lum of about 160E30. Losses had a weird structure so I left silicon out until MCR stopped changing the tunes and the losses stabilized. After including silicon SVT looks OK, and SVXmon too.</td></tr></table>
<!-- Author: Ricardo -->


<!-- Date: Sun Dec 9 10:52:47 2007 -->
Auto-hockerization of PS#2 happened while RC was having other problems. They were trying to solve the other problems first, but of course they got a lot of initialization failures when finishing the Recover-Run part of HRR. After they realized that the shift crew recover from the autohockerization by themselves.
<!-- Author: Ricardo -->


<!-- Date: Sun Dec 9 18:11:45 2007 -->
Got paged because the heartbeat box in the HV summary page is purple, while the heartbeats in the Alarms page is green. Since we were not taking data I asked the Ace (Mark) to reboot svxinter and the PS-Gui, and later asked the Cryo-tech to reboot svxiicon.  All the work is done, but the purple remains there. I suggested Mark to page someone in the IFIX side. 
  
<!-- Author: Ricardo -->
<!-- Comment: Sun Dec  9 19;08;30 comment by...Ricardo -->
Steve was paged and they found out there was a window waiting for confimation behind all windows. That's cleared now.



<!-- Date: Sun Dec 9 19:32:59 2007 -->
<b>ADCmon Monitoring (runs: 254662-254950) 
</b> 
<br> 
<br> 
There is no plot for SB5W6L4 in the checked runs (except for run  <a href=http://stuart.physics.ucsb.edu/~stuart/adcmon/ar037e26.0001_ar03e36e.0001/ >254830</a>, where the plot exists but is marked as 100% errors). 
<br> 
The other ladders are fine. <br> 
Ladder IB3W0L3, marked as bad since last week, is not returning data yet.
<!-- Author: Roberto -->
<!-- Comment: Sun Dec  9 19;51;02 comment by...Roberto -->
<pre>Ladder SB5W6L4 is declared as 'unfixable' in the bit reporter. </pre>


<!-- Date: Mon Dec 10 05:32:49 2007 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-12142&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-12142  width='300' align='top'></a></td><td>Store 5791 is in with initial lum of about 180. Non-silicon problems delayed the start of data acquisition. The losses started at 9KHz, went slowly to 13 kHz and they are coming back again. Svtspymon and svxmon looks fine.</td></tr></table>
<!-- Author: Ricardo -->



<!-- Date: Mon Dec 10 08:56:40 2007 -->
<h3>Summary of the week</h3> 
<ul> 
 
<li> <b> Monday 3th, December 2007.</b> 
  <ul>  
	<li> Cabled clock signals from other places to the LA  
        to pinpoint the problem. Produced several clock glitches  
        in the process. See details <a href=  
	'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=382&frame=2&anchor=14:43:54'> 
 	 here</a>. Waiting for glitches.</li> 
	<li> Store 5772 aborted during scraping.</li> 
  </ul> 
</li> 
 
<li> <b> Tuesday 4th </b> 
  <ul>  
	<li> Store 5776 quenched.</li> 
	<li> Fixed a bug in the LA trigger sequence.</li> 
	<li> Access into the MI to look for a ground fault; stash is dumped.</li> 
  </ul> 
</li> 
 
<li> <b> Wednesday 5th </b> 
  <ul>  
	<li> Store 5780 is in with 125E30 and losses about 13 KHz.</li> 
	<li> New version of IMON installed. Beatiful features added by Jose.</li> 
	<li> Relocation of O2 and flow instruments on the vacuum pump exhaust of ISL and SVX.</li> 
	<li> Changing IMON limits. <li>	 
	<li> b0fib00 went red while running and wouldnt boot up. See details <a href= 
	'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2007&action=view&page=950&frame=2&anchor=13:59:31.223'> 
	here.</a> </li> 
	<li> Noticed weird behavior of some bias currents. See links starting from <a href= 
	'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=382&frame=2&anchor=15:53:39'> 
	here</a>.</li> 
  </ul> 
</li> 
 
 
<li> <b> Thurday 6th </b> 
  <ul>  
	<li> First clock glitch with useful information  
	points to the clock fanout board. </li> 
	<li> Silicon Bias Scan for L00 and SVX-L0. </li> 
	<li> Long readout studies show large peak correlated with L1A rates.  
	Details <a href= 
	'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=382&frame=2&anchor=12:05:09'> 
	here</a>.</li> 
	<li> L00 switched off for collimator studies. </li> 
	<li> Flows changed to try to address the weird bias behavior.</li> 
  </ul> 
</li> 
 
 
 
<li> <b> Friday 7th </b> 
  <ul>  
	<li> Electron lens is off and Sili goes to stand-by. See the main elog  
	<a href= 
	'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2007&action=view&page=956&frame=2&anchor=14:11:56.668'> 
	entry</a>.</li> 
	<li> Clock glitchs could be also static related ?.  
	Measurements of RH and T in the svx06 crate.</li> 
	<li> Store 5787 is in with an initial lum of 163E30 and losses around 8 KHz.</li> 
        <li> SRC error due to wrong bunch structure. </li> 
	<li> SRC error due to wrong SYNC clock. </li> 
  </ul> 
</li> 
 
<li> <b> Saturday 8th </b> 
  <ul>  
	<li> SRC error due to wrong SYNC clock. </li> 
	<li> SRC resonance. </li> 
	<li> Bias current of e033 shoots for the stars. Plot <a href= 
	'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=382&frame=2&anchor=12:54:38'> 
	here.</a></li> 
	<li> Got paged because of a hockerization,  
	ace was not sure what to do.</li> 
	<li> Store 5788 in with losss about 20 KHz and Tev is tuning.  
	Silicon is out until the situation stabilizes. Links <a href= 
	'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=382&frame=2&anchor=21:27:57'> 
	here</a> and <a href= 
	'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2007&action=view&page=960&frame=2&anchor=20:58:21.407'> 
	here</a>.</li> 
  </ul> 
</li> 
 
<li> <b> Sunday 9th </b> 
  <ul> 
	<li> Autockerizarion of PS#2 happened while fixing other problems.  
	See  <a href= 
	'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=382&frame=2&anchor=10:52:47'> 
	here</a>.</li> 
	<li> Paged because heartbeat box in HV summary is purple. Rebooted svxinter, PSGUI and svxiicon with no avail. 
	The problem: "window-behind-windows" effect. </li> 
	<li> Store 5791 is in with an initial lum of 180E30 and losses around 14KHz. The CLC did not power up at the beginning of data-taking.</li> 
  </ul> 
 
</ul> 
 
<h3>Thanks Ignacio for you all your hard work! <br> 
    Welcome Sasha as co-SPL.</h3>  
<!-- Author: Ricardo -->

<!-- Date: Mon Dec 10 10:51:04 2007 -->
Entered in Silicon database: <ul>
<li>Ladder: IB1W4L1 
<li>problem n: 1826 
<li>Status: fixed
<li>Type: Chip_bit_error
<li>Action: Diagnosis_update
<li>entered by: sasha 
<li>description is: This ladder is OK during data taking for the past 30 days. Fixed. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B1W4&layer=L1">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Mon Dec 10 10:53:27 2007 -->
Entered in Silicon database: <ul>
<li>Ladder: IB3W0/1All 
<li>problem n: 2144 
<li>Status: fixed
<li>Type: DropReadOut_nonRX
<li>Action: Diagnosis_update
<li>entered by: sasha 
<li>description is: No more errors on f304. Fixed. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B3W0/1&layer=All">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Mon Dec 10 10:54:48 2007 -->
Entered in Silicon database: <ul>
<li>Ladder: IB3W1L1 
<li>problem n: 2143 
<li>Status: fixed
<li>Type: DropReadOut_nonRX
<li>Action: Diagnosis_update
<li>entered by: sasha 
<li>description is: No more problems. Fixed. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B3W1&layer=L1">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Mon Dec 10 10:57:37 2007 -->
Entered in Silicon database: <ul>
<li>Ladder: LB1W3L3 
<li>problem n: 2163 
<li>Status: fixed
<li>Type: Optical_other
<li>Action: Diagnosis_update
<li>entered by: sasha 
<li>description is: There are no errors during data taking for the past 30 days. Fixed, at least for now. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=L00&wedge=B1W3&layer=L3">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Mon Dec 10 11:00:40 2007 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W5L2 
<li>problem n: 1829 
<li>Status: fixed
<li>Type: DRO_00F3
<li>Action: Diagnosis_update
<li>entered by: sasha 
<li>description is: Error rate has dropped to <1%. Fixed for now. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B0W5&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Mon Dec 10 11:08:57 2007 -->
Entered in Silicon database: <ul>
<li>Ladder: IB3W0L3 
<li>problem n: 2465 
<li>Status: needs_work
<li>Type: Chip_bit_error
<li>Action: Diagnosis_update
<li>entered by: sasha 
<li>description is: This ladder has either nothing or d0d0, which may indicate a problem with a fib. It needs quiet time and, possibly, an access.  
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B3W0&layer=L3">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Mon Dec 10 11:11:02 2007 -->
Entered in Silicon database: <ul>
<li>Ladder: IB4W0L2 
<li>problem n: 571 
<li>Status: fixed
<li>Type: Chip_bit_error
<li>Action: Diagnosis_update
<li>entered by: sasha 
<li>description is: No errors for 30 days. Fixed. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B4W0&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Mon Dec 10 11:13:28 2007 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W0L2 
<li>problem n: 1490 
<li>Status: needs_observation
<li>Type: Chip_bit_error
<li>Action: Diagnosis_update
<li>entered by: sasha 
<li>description is: Error rate has dropped to <1%. Continue observations. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B0W0&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Mon Dec 10 11:15:20 2007 -->
Entered in Silicon database: <ul>
<li>Ladder: SB2W2L3 
<li>problem n: 436 
<li>Status: fixed
<li>Type: Chip_bit_error
<li>Action: Diagnosis_update
<li>entered by: sasha 
<li>description is: Errors disappeared. Fixed, for now. 
<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: Mon Dec 10 11:17:24 2007 -->
Entered in Silicon database: <ul>
<li>Ladder: SB2W2L4 
<li>problem n: 1423 
<li>Status: needs_work
<li>Type: Chip_bit_error
<li>Action: Diagnosis_update
<li>entered by: sasha 
<li>description is: Problem is intermitent, and the error rate has dropped. However, this ladder still needs quiet time studies. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B2W2&layer=L4">report</a></ul>
<!-- Author: Problem DB -->