<!-- Title: 10:46:08  Mon Oct 23 2006 -->
<!-- Crewchief: Jose (MPC) -->
<!-- Op1: Ulrich (SPL) -->
<!-- Op2: &nbsp; -->
<!-- Op3: &nbsp; -->
<!-- Op4: &nbsp; -->
<!-- Op5: &nbsp; -->
<!-- Op6: &nbsp; -->
<!-- Notes: -->
Beam should be back hopefully today...


<!-- Date: Mon Oct 23 10:57:18 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10135&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10135  width='300' align='top'></a></td><td>Event sizes from cosmics run <a href="http://www-cdfonline.fnal.gov/java/cdfdb/servlet/RunSummary?RUN=225972">225972</a>.  For this run we have the 4 VRB balanced configuration for ISL/L00.  Keep in mind that the balancing is done at luminosity >200.</td></tr></table>
<!-- Author: Mark -->


<!-- Date: Mon Oct 23 14:11:59 2006 -->
<h3>Cooling Line Inspection</h3> 
Marcel and I have performed a short inspection of the West ISL cooling lines, where Dervin (re-)discovered a leak. We tightened the packings in some manual valves and hoped that this would fix the problem.  The result of today's inspection: the leak seems to be fixed, there has been no new liquid dripping from the cooling lines.
<!-- Author: Ulrich -->
<!-- Comment: Mon Oct 23 14;28;42 comment by...Ulrich -->
From MCR e-log:
<pre>
13:42:50-  CDF made a quick controlled access they are out now. - marty
-- Mon Oct 23 13:47:09 comment by...Terry --  It was a highly relativistic access.
</pre>
<!-- Date: Mon Oct 23 14:20:04 2006 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10136&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10136' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10137&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10137' width='300'></a></center>
<!-- Author: Ignacio & Jose -->
<!-- Comment: Mon Oct 23 14;22;02 comment by...Ignacio & Jose -->
<pre>This ladder has the same behaviour as SB4W8L0.</pre>



<!-- Date: Mon Oct 23 19:51:14 2006 -->
<h3> Store 5019</h3> 
The store had an initial luminosity ~100e30. The variables (B0PAGC and B0AAGC) of the abort gap have had a zero readout.
<!-- Author: Jose -->


<!-- Date: Tue Oct 24 06:27:35 2006 -->
<h3> Tevatron quench </h3> 
Quench at B4. Plot for the abort in <a href=http://www-cdfonline.fnal.gov/cgi/internal/elog/elog.pl?nb=2006&action=copyentry&page=795&time=03:00:41.179> e-log </a> 
<pre> 
02:57:37-  Looks like the frig at B4 went unstable again. Cryo coordinator is aware and is looking into it. - prk 
03:39:29-   Cryo coordinator reports the B4 cold compressor will need replaced. This will take 3-4 hours once their personnel are in place. They are calling them in now. - prk 
05:40:32-   Cryo techs have their keys and are beginning their work. - prk 
</pre>  
<!-- Author: Jose -->


<!-- Date: Tue Oct 24 08:28:29 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10140&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10141  width='300' align='top'></a></td><td><h3>DVDD for IB1W4L2</h3> 
 
<p>Roberto had noted this ladder had gone PINK a couple of times last night.  Also Jose and Ignacio had noticed this yeserday and plotted the current & voltage.  It does look like another power supply with a drooping voltage and irractic current.</p> 
 
<p>I just checked the CAENLVCURRENT.dat file and the DVDD soft limit is 600mA.  So we have a margin of ~200mA before we hit this trip limit.</p> 
 
<p>If we consider a power supply swap, we will need to go to SW Top Top....<em>yuck!!</em></p></td></tr></table>
<!-- Author: Ankush & Jose -->


<!-- Date: Tue Oct 24 08:49:24 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10142&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10143  width='300' align='top'></a></td><td><h3>The Detector after a routine resin exchange</h3></td></tr></table>
<!-- Author: Ankush -->


<!-- Date: Tue Oct 24 09:00:08 2006 -->
<h3>Resin Exchange: Cooling Trip</h3> 
Since there was enough time between the 8:00 meeting and the expected start of shot setup, I requested  that the resin be exchanged in both the SVX and ISL de-ionizers. During the resin exchange for SVX, a trip took out all of SVX and L00. From the iFix log file it seems that they shut down supply flow to the detector by mistake (supply flow was too low, and chiller supply pressure was too high shortly before the trip). A few minutes later also ISL went, as a consequence of a L00 übertrip. 
<p> 
I have spoken with Bill Noe about the incident. Today one of the cryo techs (Steve) was just showing Warren how to do things. From our experience, Steve and also Dean know the resin exchange inside out. It is unclear why we had problems this time. We certainly need better instructions and labels in the alcove.
<!-- Author: Ulrich -->
<!-- Comment: Tue Oct 24 09;31;45 comment by...Ulrich -->
Here is what happened. The techs closed the air supply to the wrong pneumatic valve and disconnected the air line. As a consenquence, the pressure in all air lines dropped, bringing the pneumatic valves into their default position (usually: closed). The system tripped before they could re-connected the line.

<!-- Comment: Tue Oct 24 09;53;15 comment by...Ulrich -->
The ISL PS enable dropped out as well as a consequence of a flow fluctuation during the resin exchange.

<!-- Comment: Tue Oct 24 09;54;35 comment by...Ulrich -->
I used the incident to train the cryo crew how to re-establish flow after a cooling trip. As only the SVX/L00 flow were tripped, we were up again in a couple of minutes.

<!-- Comment: Tue Oct 24 11;09;12 comment by...Jose -->
Silicon is back to Standby. One of the ladders e084 has been taken out of the data taking because it was giving zero DVDD current. This is a known problem for this ladder.
<!-- Comment: Sun Oct 29 22;53;38 comment by...Jose -->
Entry in the cryo e-log:

<pre>
Fri Oct 27 08:41:08
I installed yellow caution tags on the manual valves (MV-FI IN) for both SVX and ISL. These are the valves we use to isolate PV_FI IN when changing resin.
 - Bill Noe
</pre>
<!-- Date: Tue Oct 24 11:07:16 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W8L4 
<li>problem n: 1287 
<li>Status: unfixable
<li>Type: DVDD
<li>Action: Removed_hdwdb
<li>entered by: jgarcian 
<li>description is: This ladder has been taken out of the problem database was giving no current on DVDD. This is a known problem for this ladder. 
<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 Oct 24 11:41:06 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10146&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10147  width='300' align='top'></a></td><td>Pinkie in DVDD line of e414. Recovered by a coldstart</td></tr></table>
<!-- Author: Ulrich -->
<!-- Comment: Tue Oct 24 16;28;09 comment by...Jose & Ankush -->
This ladder has an AVDD2 problem that has come back for the moment is ignored.
<!-- Date: Tue Oct 24 14:11:30 2006 -->
<h3>Silicon workshop slides </h3> 
The 2nd CDF Silicon workshop slides are now available as print-outs. There are two sets of two volume books. You can find them in the Silicon office. Enjoy! 
<br>
<!-- Author: Tuula -->
<!-- Comment: Tue Oct 24 16;41;11 comment by...Ankush, Jose, Ulrich -->
Great job, thanks a lot!


<!-- Date: Tue Oct 24 16:56:32 2006 -->
<h3>Store 5021: Abort Gap Counter Problems and Quench</h3> 
At the beginning of Store 5021 (initial luminosity 170e30), the Silicon was still in STANDBY. For this store the Recycler used an adaptive feed forward system to adjust the RF buckets. As a result the pbar bunches were distributed in the Tevatron much more evenly than before. 
<p> 
From the beginning of the store, we saw problems with the abort gap counters. The pbar top counter was reading a rate of 1.5 MHz, leading to a 50 kHz coincidence rate into C:B0AAGC. We got a hold of Rick Tesarek, who checked the counters and realized that the one giving the high rate was actually powered at the wrong gain. This resulted in rates which were an order of magnitude larger than the usual rates. After this was corrected, the counters were fine for a while, but then they started to ramp up to very high rates and then drop to 0. Rick has not yet found an explanation for this behavior. More in the 
<a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2006&action=view&page=796&frame=2&anchor=15:13:34.833'> 
main e-log</a>. 
<p> 
Around 16:30 the Tevatron quenched, and the experts are investigating: 
<pre> 
-- Tue Oct 24 16:41:14 comment by...m.m --  ... Store 5021 aborted on what appears to be an ESS-related glitch. Tev quenches at E1, D1. Many people investigating. 
16:39:44-  
	F_Sector audio permit dropped taking down several CDC's. This is also an input to the Tevatron Coasting Beam Safety system, so the coasting beam valves closed causing the abort and quench. 
</pre> 
The quench was  
<a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2006&action=view&page=797&frame=2&anchor=16:41:00.454'> 
clean for us</a>, and the post-quench checkout worked fine.
<!-- Author: Ulrich -->


<!-- Date: Tue Oct 24 17:16:07 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10150&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10151  width='300' align='top'></a></td><td><h3>The Happy Couple</h3> 
His Grumpiness, Spawn of Nahn, Dark Lord of the DAQ, in union with the Lord of the Tevatron.</td></tr></table>
<!-- Author: The Paparazzi -->
<!-- Comment: Thu Oct 26 12;58;00 comment by...m mattson -->
Mr Photogenic of the Silicon group was also in the
<a href=
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2006&action=view&page=802&frame=2&anchor=11:30:52.339'>
shift e-log</a>.
<!-- Date: Tue Oct 24 22:20:07 2006 -->
<h3> Halo Counters/Abort Gap variables: </h3> 
 
 Rick came in to have a look to the problems with the counters. This is the entry in the e-log. 
 
<pre>Tue Oct 24 21:36:33  Earlier today, I was paged to look into some problems with the abort gap variables. Subsequent investigation indicated that the HV supply for the halo counters was inadvertantly set to 2400V (should have nominally been 1900V); the counters had been running with a HV which gave a gain aproximately 8x the nominal gain. I corrected this problem around 16:00. 
 
However, additional features were observed in the abort gap variables. Spontaneous dips and spikes in the counter rates. I checked the LV for the 2 NIM crates and the CAMAC crate and all is ok. However, while looking at the clock signals into a gate generator, I noticed that the CDF_ABORT signal had dropped out (CDF_BC and CDF_B0 were still present). I witnessed this happen twice, but was not able to make this happen in a controlled way. As a pro-active measure, I replaced a Kings brand Lemo barrel connector for a Lemo brand Lemo barrel connector (I've had problems with Kings brand barrel connectors in previous experiments). An oscilloscope is set up on the 1st floor to capture the CDF_ABORT signals when or if they drop out again. 
 - R.J. Tesarek 
</pre> 
 
 Let's wait for the beam to come in (late tonight probably) and see which is the behaviour of the counters.  
<!-- Author: Jose -->


<!-- Date: Wed Oct 25 02:32:56 2006 -->
<h3> Store 5026 </h3>  
The new store has started with an initial luminosity of 127e30. The  values for the losses and abort gap look good. Values has been as expected during the shot setup, no strange oscillations. 
<!-- Author: Jose -->
<!-- Comment: Wed Oct 25 03;34;44 comment by...Jose -->
Losses look fine after an hour of running. The problem now comes from one of the L1 crates B0L1CL00. Almost from the begining of the store this crate is having problems. They are coming to replace the  PS. 

<!-- Comment: Wed Oct 25 05;42;36 comment by...Jose -->
The problem with the power supply was solved at around 5 and after some more issues data taking was started, no SI.


<!-- Date: Wed Oct 25 07:13:02 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10153&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10153  width='300' align='top'></a></td><td><h3> Small run with silicon </h3> 
After the problems were solved with the DAQ, the losses were fine so we included silicon. We introduced the new crate and no problems in the DAQ were seen. SVTSPYMon looked OK and SVXMon had a yellow (maybe not enough statistics) in e151. I took out silicon after a while, losses look fine but I was not so sure about the beam stability.  
Checking the raw data it seems that data from the ladders in the new crate is coming OK. </td></tr></table>
<!-- Author: Jose -->


<!-- Date: Wed Oct 25 09:39:41 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10154&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10155  width='300' align='top'></a></td><td>AVDD pinkie in e114. At some point the AVDD current of this ladder dropped (with the silicon in standby) and now it is slowly creeping up again.</td></tr></table>
<!-- Author: Ulrich -->
<!-- Comment: Wed Oct 25 09;40;30 comment by...Ulrich -->
The current is a little erratic these days, but this is a little too low. We'll see how it goes once the Silicon is included in the run.


<!-- Comment: Wed Oct 25 10;39;30 comment by...Ulrich -->
The AVDD current is still low. From the raw data ans SVXMon, there is no obvious problem with this ladder.
<!-- Date: Wed Oct 25 10:20:27 2006 -->
<h3>Running again with Silicon</h3> 
After Jose's short test this morning, the plan was to take data with the new trigger table for a while. As usual, there was a short run without silicon first. Then we included silicon in a new run. The startup was without problems, and SVXMon and SVTSpyMon look fine.
<!-- Author: Ulrich -->
<!-- Comment: Wed Oct 25 10;23;46 comment by...Ulrich -->
<h3>Crate 5 hockerized</h3>
While I was hanging out in the control room, CAEN crate 5 lost communication, so I hockerized it. Recovered without problems.


<!-- Comment: Wed Oct 25 18;31;27 comment by...Ulrich -->
<h3>Coldstart</h3>
Both Jose and I realized independently that we haven't changed the run configuration for DaqTest/SVX/COLDSTART yet.  I have saved a version of the run configuration for COLDSTART including the additional crate. Should we have to roll back to the 3-crate configuration, we have to remember to change everything back.

<!-- Date: Wed Oct 25 20:33:47 2006 -->
<p><font size=+1> D-mode Calibration Job Started </font>
<p><pre>
Job id            : 450
Calibration type  : standard
Run period tag    : Oct_2006
DPS-off run       : 226223
DPS-on run        : 226222
Requested by      : Nagesh Kulkarni
Main process id   : 2834
Comment           : Normal calibration
</pre>
<!-- Author: CDF silicon D-mode calibration job server v1.4 -->


<!-- Date: Thu Oct 26 01:14:00 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 450 FAILED.

Job info
--------
Calibration type : standard
DPS-off run      : 226223
DPS-on run       : 226222
Requested by     : Nagesh Kulkarni
Submitted        : 2006-10-25 20:33:33
Completed        : 2006-10-26 01:13:23
Status           : FAILURE
Comment          : Normal calibration

Last processing stage reported : calculating DPS-off pedestals
Failure diagnostics :
child process exited abnormally
</pre>
<!-- Author: D-mode script  -->
<!-- Comment: Mon Oct 30 14;54;02 comment by...Jason Nielsen -->
This has been recovered -- hopefully we ran into the last of the configuration problems stemming from the b0sili01 upgrade.
<!-- Comment: Mon Nov  6 12;05;37 comment by...Jason Nielsen -->
By "recovered," I mean that the job finished successfully.
<br>
No "SUCCESS" entry appears in the e-log because it finished with a special script outside of the usual calibration framework.

<!-- Date: Thu Oct 26 03:48:29 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10158&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10159  width='300' align='top'></a></td><td><h3> Store 5028 </h3> 
The store came late and not as high-lumi as expected (initial luminosity of 158e30). Losses and abort monitors look normal and silicon has been included at the begining of the data taking. SVXMon and SVTSPYMon look normal.</td></tr></table>
<!-- Author: Jose -->


<!-- Date: Thu Oct 26 09:35:12 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10160&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10161  width='300' align='top'></a></td><td>Ok this is weird... we're running w/o silicon right now.  But this is a BIAS current, not low voltage, and it's showing step increases in current.  This was also noted in the main elog, but they didn't worry about it b/c we're running w/o silicon.  I just got pulled into the control room b/c main silicon pager is not responding...</td></tr></table>
<!-- Author: Jen -->
<!-- Comment: Thu Oct 26 09;40;37 comment by...Jen -->
We just started a run w/ silicon and the bias current hasn't changed (no surprise).  I'm sticking around to watch L1 rates (explanation to follow) so I'll check the data coming out.  My guess is hockerization is needed.


<!-- Comment: Thu Oct 26 10;15;39 comment by...Jen -->
<pre>Data looks fine, but I just plotted the current history of this guy (soon to be pasted below) and he's been on a pretty steep rise...</pre>
<!-- Date: Thu Oct 26 09:59:11 2006 -->
<h2>Including silicon with part of COT SL4 masked ON</h2> 
While I was doing PS work in the trigger room, Jason (XFT) came to ask if I was a silicon person.  Seems the silicon main pager was not responding and they wanted permission to reinclude silicon with the COT.  Part of COT SL4 has been masked ON (the part that was tripping this morning).  SL4 has an occupancy of ~60%, and now one quarter of SL4 will be firing 100%.  I said ok and stayed around to watch the L1A rates.  So far so good... we just had one prescale change and are now running with L1A ~ 13kHz.  Waiting around for one more prescale change just to be sure.  From the TrigMon COT plots, the occupancy in the masked sector is ~15% higher than the rest of SL4, not too significant.<br> 
Ah, just had another prescale change.  Now up to 26kHz... still good.<br>
<!-- Author: Jen -->
<!-- Comment: Thu Oct 26 10;23;55 comment by...Jen -->
Detailed explanations of COT work <a href=
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2006&action=view&page=802&frame=2&anchor=10:06:59.647'>available</a>.  Everything is fine on the silicon end.
<!-- Date: Thu Oct 26 10:03:07 2006 -->
<h3>ACNET lost monitoring for a minute</h3> 
Had a TevMon warning, ACNET lost monitoring of LOSTP and LOSTPB, B0AAGC and B0PAGC for ~one minute.  MCR may have rebooted something w/o telling us.  See <a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2006&action=view&page=802&frame=2&anchor=10:01:47.471'>main elog</a>.  Everything back and looks fine now, we took no actions.<br>
<!-- Author: Jen -->




<!-- Date: Thu Oct 26 10:26:24 2006 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10162&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10162' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10163&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10163' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10164&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10164' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10165&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10165' width='300'></a></center>
<!-- Author: Jen -->
<!-- Comment: Thu Oct 26 10;30;15 comment by...Jen -->
<h3>Bias current on IB5W1L2</h3>
As promised... L to R: bias history of Bias0 from DS Day 1000 on, Bias0 from DS Day 1800, Bias1 from DS Day 1000, and Bias1 from DS Day 1800.  Current has been increasing at a pretty steady slope since DS Day 1000.  Bias0 current stayed level after the long shutdown, while Bias1 current dropped considerably.  So while both are still increasing, Bias0 has passed its limit while Bias1 has not.<br>
I take back my hockerization, I think this is a current going over it limit.  I'm not sure why it jumped up so much after DS Day 2050.<br>
For now I'm going to ignore it, let the MPC check the current later and decide what to do ;)<br>

<!-- Comment: Thu Oct 26 11;09;26 comment by...Jen, Ankush, Marcel -->
<h3>After consultation...</h3>
There's no correlation with temperatures here, so it doesn't look like the sensors are getting too warm.  The current on SEVERAL bias lines is showing this weird "step-up" pattern.  Most likely cause is a breakdown of the power supply.<br>
Recommended actions: request a short (1 hr) access to try a cable swap and make sure the problem is the supply, not the sensor.  Assuming it's the supply, we'll then need a longer (~3 hr) access to swap the ISL supply.  LUCKILY, we happen to have EXACTLY 1 spare forward ISL supply right now.  Also luckily, this wedge lives in NE Bot Bot, which is nice and easy to get to.<br>

<!-- Comment: Thu Oct 26 11;24;12 comment by...Jose -->
...sorry, I did not get the page. 


<!-- Date: Thu Oct 26 14:05:35 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB5W1L2 
<li>problem n: 1782 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: jgarcian 
<li>description is: Increasing the limits for this ladder. We should keep an eye on this ladder.<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>57.1087</td><td>95</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>110.0</td></tr></table> 
<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: Thu Oct 26 14:08:30 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB5W1L4 
<li>problem n: 1783 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: jgarcian 
<li>description is: Increasing limits for this ladder (IBias0). We should look for further increases.<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>108.6</td><td>125.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>125.0</td><td>135.0</td></tr></table> 
<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: Thu Oct 26 14:12:54 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10166&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10166  width='300' align='top'></a></td><td>Current for ladder IB5W0L4 (IBias0). I will increase the limits a little bit for this ladder.</td></tr></table>
<!-- Author: Jose -->

<!-- Date: Thu Oct 26 14:15:28 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: IB5W0L4 
<li>problem n: 1784 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: IMON_limits
<li>entered by: jgarcian 
<li>description is: Current on Bias0 just passed above the limit of 100 uA. Limits in IMON are changed.<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>60.5347</td><td>95.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>110.0</td></tr></table> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B5W0&layer=L4">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Thu Oct 26 14:24:57 2006 -->
IMON had a lot of processes running, do we have still a leak somewhere in the code??? Maybe an old version was not properly dead. I have restarted IMON.
<!-- Author: Jose -->


<!-- Date: Thu Oct 26 18:23:31 2006 -->
<h3>Tevatron Quench</h3> 
According to MCR, 
<pre> 
16:33:20-   Store is gone. - DJC 
-- Thu Oct 26 16:34:31 comment by...mig --  Looks to be the F sector ESS on Audio Permit 
-- Thu Oct 26 16:34:36 comment by...DJC --  F-sector audio permit appears to have gone down and the safety valves closed. 
-- Thu Oct 26 16:37:13 comment by...DJC --  Interlocks personnel are investigating. 
-- Thu Oct 26 16:38:15 comment by...DJC --  B1 and D1 quenched. 
</pre> 
 
and later... 
<pre> 
The cylinder/actuator system for F-sector key #31 tripped the F-sector ESS when the actuator was tapped on. The cylinder and actuator are being replaced. 
-- Thu Oct 26 18:04:12 comment by...DJC --  It took a while to find this faulty cylinder/actuator. It was on the second round of key tree testing that it tripped the ESS. 
</pre> 
Quench was <a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2006&action=view&page=803&frame=2&anchor=16:42:31.072'>clean</a> for silicon, post-quench checkout finished successfully.  We requested access to look at IB5W1.<br>
<!-- Author: Jen, Jose, Ankush, Ulrich -->


<!-- Date: Thu Oct 26 18:28:59 2006 -->
<h3>Access report for IB5W1</h3> 
The current for IB5W1L2 and IB5W1L4 had actually settled after noon, and stayed stable the rest of the afternoon.  The value for IB5W1L2 Bias0 was slightly above its limit, so Jose changed the limit.  Even though things had stabilized, we decided to try a cable swap.<br> 
We swapped bias cables between IB5W1 and neighboring wedge IB4W1, then turned both wedges on for ~10 minutes.  We monitored the currents for L2 Bias0 and L4 Bias1, since those were the ladders showing "step" increases earlier today.  When hooked to a new supply, each ladder went to the current it was normally at.  So f512 cabled to the supply for IB4W1 had the same bias current as it had this afternoon.  There was no sign of any "step" increases for either wedge.<br> 
This is very inconclusive... hard to diagnose a problem you can't reproduce.  For now, we'll continue monitoring IB5W1L2 and L4.  If the problem reappears or gets worse, we'll think about swapping the supply out.<br>
<!-- Author: Jen, Ankush, Jose, Ulrich -->


<!-- Date: Thu Oct 26 19:13:08 2006 -->
<h3> Threshold scan trial</h3> 
We have succesfully run a cold start reading the chip configuration from  the development database. We could not actually write the data on file because the HWEVB was being used for CSL tests, so we could not look at occupancies yet.  The plan is to take cosmics  
from the development database with several threshold.
<!-- Author: Jose& Ignaico -->


<!-- Date: Thu Oct 26 23:07:39 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10167&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10168  width='300' align='top'></a></td><td><h3> Store 5030 </h3> 
The store came in with an initial luminosity of 131e30. The losses and abort gap counters looked fine and silicon was included from the begining of the store. SVTSPYMon and SVXMon look normal. </td></tr></table>
<!-- Author: Jose -->


<!-- Date: Thu Oct 26 23:17:20 2006 -->
At 22:50 LOSTPB had a rare increase, see  
<a href=http://www-cdfonline.fnal.gov/cgi/internal/elog/elog.pl?nb=2006&action=copyentry&page=803&time=23:05:01.794> cdf e-log </a>. This was due to a "plate-to-plate spark". 
 
<pre> 
-- Thu Oct 26 23:01:17 comment by...m.m --  This significance of this entry is that D17 negative plate sparked again, and this time it was a plate-to-plate spark. 
</pre> 
 
The shift crew is aware of this and will have a look carefully to the losses.  
<!-- Author: Jose -->


<!-- Date: Fri Oct 27 03:18:35 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10170&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10170  width='300' align='top'></a></td><td><h3> SB2W9L4 Bias current </h3> 
The bias current for this laddes has increased around 100 uA in one hour (<a href=http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2006&action=view&page=-13353&button=yes>e-log</a>). I asked the ACE to check other ladders in the same PS and they look fine. I checked the history of this ladder (in the plot) and it is a bit strange. Nothing concerning to bias is in the problem DB. </td></tr></table>
<!-- Author: Jose -->
<!-- Comment: Fri Oct 27 04;51;46 comment by...Jose -->
Ladder seems to be returning data. Looking to the history, this ladder shows a strange behaviour time to time <a href=http://www-cdfonline.fnal.gov/cgi/internal/elog/det-system-elog.pl?nb=silicon&action=copyentry&page=288&time=16:43:10> link </a>



<!-- Date: Fri Oct 27 06:28:17 2006 -->
The aces report a spontaneous switch-off of CAEN PS #13 around 1:00. Recovered by shift crew without problems.
<!-- Author: Ulrich -->


<!-- Date: Fri Oct 27 10:11:10 2006 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10171&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10172' ></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10173&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10174' ></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10175&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10176' ></a></center>
<!-- Author: Paparazzi -->
<!-- Comment: Fri Oct 27 10;12;06 comment by...Paparazzi -->
<h4>Your SPLs and cooling system experts</h4>


<!-- Date: Fri Oct 27 14:40:53 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10177&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10178  width='300' align='top'></a></td><td><h3> Ladder SB2W9L4 </h3> 
Trip on bias current after an increase of 400 uA during this night and today. We tried to power it up again, but it tripped again. I took it out of the DB up to the end of the store (that will be a bit later today). Let's see what this ladders makes after some rest.</td></tr></table>
<!-- Author: Jose -->

<!-- Date: Fri Oct 27 16:04:00 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB2W9L4 
<li>problem n: 1785 
<li>Status: needs_work
<li>Type: BIAS
<li>Action: Removed_hdwdb
<li>entered by: jgarcian 
<li>description is: This ladder tripped on Bias Current. After some tries it has been taken out of the db. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B2W9&layer=L4">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Fri Oct 27 17:34:56 2006 -->
<table><tr><td><a href=/elog/notebooks/silicon/Fri_Oct_27_2006_173443.ps align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10180  align='top'></a></td><td>Event size vs. Luminosity for b0svx06-09 for run 226246.  A linear extrapolation (which is probably pessimistic) gives less than 20 kBytes at 300.</td></tr></table>
<!-- Author: Mark -->


<!-- Date: Fri Oct 27 22:25:48 2006 -->
<h3>Re-including SB2W9L4</h3> 
The ladder e294 was excluded this afternoon because it started tripping on bias current. We biased it after the store was dropped, and it was "holding" at around 440 μA for a couple of minutes (we only had 10 minutes of quiet time). The actual trip limit was rather low, at 500 μA. So we decided to re-include the ladder and increase the trip limit to 1000 μA. We will also ask the shift crew to keep an eye on the bias currents.
<!-- Author: Jose & Ulrich -->

<!-- Date: Fri Oct 27 22:27:31 2006 -->
Entered in Silicon database: <ul>
<li>Ladder: SB2W9L4 
<li>problem n: 1785 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: Added_hdwdb
<li>entered by: husemann 
<li>description is: We have re-included this ladder again at the end of the store. We increase the trip limit from 500 μA to 1000 μA. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B2W9&layer=L4">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Sat Oct 28 01:16:42 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10181&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10182  width='300' align='top'></a></td><td><h3> Store 5031 </h3> 
The Store started with an initial luminosity of 175e30. Silicon went in from the beginning of the store. Losses and abort gap counters are low. SVTSPYMon and SVXMon look good. For this run we included ladder e294 that was taken out in the previous store. The trip limit has been increased to 1000 uA, hopefully it will hold... </td></tr></table>
<!-- Author: Jose & Ankush -->

<!-- Date: Sat Oct 28 07:17:16 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 450 FAILED.

Job info
--------
Calibration type : standard
DPS-off run      : 226223
DPS-on run       : 226222
Requested by     : Nagesh Kulkarni
Submitted        : 2006-10-25 20:33:33
Completed        : 2006-10-28 07:16:11
Status           : FAILURE
Comment          : Normal calibration

Last processing stage reported : starting histogram transfer
Failure diagnostics :
Received SIGINT. Exiting now.
</pre>
<!-- Author: D-mode script run_calib_analysis_noph.tcl -->


<!-- Date: Sat Oct 28 07:25:38 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 450 FAILED.

Job info
--------
Calibration type : standard
DPS-off run      : 226223
DPS-on run       : 226222
Requested by     : Nagesh Kulkarni
Submitted        : 2006-10-25 20:33:33
Completed        : 2006-10-28 07:23:35
Status           : FAILURE
Comment          : Normal calibration

Last processing stage reported : starting histogram transfer
Failure diagnostics :
Received SIGINT. Exiting now.
</pre>
<!-- Author: D-mode script run_calib_analysis_noph.tcl -->



<!-- Date: Sat Oct 28 08:20:50 2006 -->
<h3> SB4W9L4 OverCurrent </h3> 
This e494 tripped due to a AVDD OverCurrent, this problem is known as it can be seen looking to the problem DB (<a href=http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B4W9&layer=L4>PDB</a>). This time the shift crew was able to recover the ladder.  
<!-- Author: Jose -->
<!-- Comment: Sat Oct 28 08;58;35 comment by...Ulrich -->
But the shift crew didn't know how to get rid of the red cells in IMON...

<!-- Comment: Sat Oct 28 09;55;43 comment by...Ulrich -->
Another problem with e494:
<pre>
Sat Oct 28 09:40:26 CDT 2006     Software protection trip: High DVDD Current  SVX B4 W8 L0 current 159.0 softLimit 150.0
Sat Oct 28 09:40:36 CDT 2006     Software protection trip: High DVDD Current  SVX B4 W8 L0 current 169.0 softLimit 150.0
</pre>
Recovered by the shift crew.

<!-- Comment: Sat Oct 28 10;02;21 comment by...Ulrich -->
Sorry, wrong ladder. the last problem was in B4W8L0...


<!-- Date: Sat Oct 28 12:42:39 2006 -->
<h3>SRC Resonance</h3> 
 
<p>I just got a mail from the Logic Analyser about a resonance.  However I was just logged in when I was <em>rudely</em> bumped off.   So the mystery logger will have to provide the details.</p>
<!-- Author: Ankush -->
<!-- Comment: Sat Oct 28 12;45;36 comment by...Mystery logger -->
Sorry.
<!-- Date: Sat Oct 28 12:45:01 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10183&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10183  width='300' align='top'></a></td><td>Resonance detected in b0svx02. The logic analyzer is re-armed.</td></tr></table>
<!-- Author: Ulrich -->



<!-- Date: Sat Oct 28 16:46:01 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10184&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10184  width='300' align='top'></a></td><td>  </td></tr></table>
<!-- Author:    -->
<!-- Comment: Sat Oct 28 16;47;42 comment by...Ankush -->
<h3>...and another resonance</h3>

<p>This is what the error logger gave</p>

<pre>
CT: 2006.10.28 16:41:06
41'6" b0svx02:Messenger:Oct 28, 2006 04:41:07 PM->SRC Fatal Error:Sl 6 Resonance Detected 
 -->  
 Additional Information: 

 Attention !!!. FERML_SRC_FATALITY ERROR !!! 
 
 SRC Fatal Error from b0svx02: Sl 6 Resonance Detected 
 
 - HALT the run                   
 - record any relevant information in e-log     
 - RECOVER - RUN     
[MLE]
</pre>


<!-- Date: Sat Oct 28 23:46:07 2006 -->
<h3>iFix PC crashed</h3> 
Got paged on the cooling pager because SVXIICON crashed. This didn't happen since we do the regular reboot every two weeks. With the knowledge of the password, the aces rebooted the PC fine. Unfortunately, the database had not been saved after we went back to regular operating temperatures after the bore access. So the old alarm limits and a couple of silenced alarms were still in place. We hit "Set A/W Limits" and unsilenced the alarms. Now everything is back to normal.
<!-- Author: Jose & Ulrich -->
<!-- Comment: Sat Oct 28 23;47;41 comment by...Substitute Cooling Pager Carrier -->
And Jennifer: it's gonna cost ya!

<!-- Comment: Sun Oct 29 00;46;42 comment by...She who owes... -->
It never fails...

<!-- Comment: Sun Oct 29 08;42;10 comment by...Scared Pagan -->
Some kind of witchcraft?


<!-- Comment: Sun Oct 29 12;50;50 comment by...*sigh* -->
I think that would be against my best interest. If I did have something up my sleeve, I wouldn't waste it on irritating Ulrich. I can do that just fine without external forces.
<!-- Date: Sun Oct 29 12:26:13 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10185&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10185  width='300' align='top'></a></td><td><h3> Bias SB4W3L2 </h3> 
 
The last 2-3 weeks the current for this ladder has been increasing more than the "expected".  </td></tr></table>
<!-- Author: Jose -->


<!-- Date: Sun Oct 29 12:37:20 2006 -->
<h3> Tevatron quench !!!</h3> 
They had a really nice store coming... but it quenched while squeezing. Aces checking for radiation monitors.  
<!-- Author: Jose -->
<!-- Comment: Sun Oct 29 12;49;11 comment by...She who has much to accomplish by Monday -->
I heard it from my office!


<!-- Comment: Sun Oct 29 13;21;16 comment by...Jose -->
We made a short cosmics run to test silicon after the quench, everything looks normal. 


<!-- Date: Sun Oct 29 13:29:53 2006 -->
<table border=0><td><tr><td bgcolor=#e0e030><h3> IMON Leak problem, again...</h3> 
 
Please close the "IMON History" plot with the <b>CLOSE</b> button. If you do not do like that the thread it is not properly killed and remains after the windows is closed.</td></tr></td></table>
<!-- Author: Jose -->


<!-- Date: Sun Oct 29 18:35:56 2006 -->
<h3> 2 fb<sup>-1</sup> Integrated luminosity (Tev Lumi) </h3>  
<pre> 
Sun Oct 29 13:46:16  I was updating the Ops Manager store summary page. 
When store 5031 ended, CDF has been delivered 2/fb for Run II. 
It will still be a while before we have 2/fb to tape. - m mattson 
</pre>
<!-- Author: Jose -->



<!-- Date: Mon Oct 30 00:04:56 2006 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10186&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-10187  width='300' align='top'></a></td><td><h3> Store 5037 </h3> 
This time they decided to do a smaller store after the problem with the huge store this morning. The initial luminosity for 5037 is 133e<sup>30</sup>. Losses and abort gap counters are small. SVXMon and SVTSPYMon look fine. 
 
</td></tr></table>
<!-- Author: Jose -->


<!-- Date: Mon Oct 30 08:39:36 2006 -->
<h3> Quench! </h3> 
<pre> 
08:12:46-   Shift Summary: Shift started with tev investigation for quench continuing, beam to stacking, NuMI, and Miniboone. Store 5037 was colliding by 23:45 with an AIL of 135.11e30. 4 transfers to Recycler occurred. Tev quenched at 0734 at E42U&L. Cause was found to be E4TR15. 
</pre>
<!-- Author: Jose -->


<!-- Date: Mon Oct 30 08:45:49 2006 -->
<h3>Heads-up: New CSL &amp; Possible West Bore Access</h3> 
Just a couple of news from the 8:00 meeting this morning: 
<ul> 
<li>The CSL group plans to switch to the new CSL beginning on Wednesday. Further details will be provided at a later point in time.</li> 
<li>The COT group has requested a 4-shift access to the West bore to fix a problem in COT SL4. Right now I don't know any more details, but I'll keep you posted. This could be an opportunity to swap relative humidity sensors on the West COT face, just like we did on the East side.</li> 
</ul>
<!-- Author: Ulrich -->


<!-- Date: Mon Oct 30 09:32:58 2006 -->
<h3> Summary </h3> 
 
<ul> 
<li> Monday:  
 
<p>First 4-VRB setup results & Cooling Line inspection 
 
<li> Tuesday:  
 
<p> Abort Gap Counters problem (started on Monday). In a first stage we lost the reading for B0PAGC and B0AAGC. The problem was "fixed" but we the voltage applied was to large and the gain was 8 times the standard and erratic. Problem was fixed by setting the voltage properly and exchanging a "Lemo barrel connector". 
 
<p>Resin Exchange. Cooling Trip. 
 
<li> Wednesday: 
 
<p> First test and running without problems with beam and new 4-VRBs setup. 
 
 
<li> Thursday:  
<p> ACNET lost monitoring for a minute.  
<p> Increasing Bias current on IB5W1L2. An access later on was done to test if the problem was in the PS or in the ladder. "This is very inconclusive... hard to diagnose a problem you can't reproduce. For now, we'll continue monitoring IB5W1L2 and L4. If the problem reappears or gets worse, we'll think about swapping the supply out." 
<p> Threshold scan trial 
 
<li> Friday: 
 
<p> Running fine. Results from new setup with beam. 
 
<li> Saturday:  
 
<p> SRC Resonances. 
<p> Crash of iFix PC 
<p> 2 fb<sup>-1</sup> Luminosity delivered 
 
<li> Sunday: 
 
<p> Lost/quench of a nice store (400 in recycler). 
 
<p>  
 
 
 
</ul>
<!-- Author: Jose -->