<!-- Title: 10:25:02  Mon Feb  9 2004 -->
<!-- Crewchief: PC Ben Brau -->
<!-- Op1: Det Jared 612-8214 -->
<!-- Op2: Mon: Lauren -->
<!-- Op3: DAQ: Julia -->
<!-- Op4: &nbsp; -->
<!-- Op5: &nbsp; -->
<!-- Op6: &nbsp; -->
<!-- Notes: -->
<pre>Continue recording these record stores and pray for smooth running (knock on silicon)...</pre>


<!-- Date: Mon Feb 9 13:21:42 2004 -->
<pre>Had another trip of ISL B5W0 (while it was in standby).   
Seemed to be correlated with a message 
 
"Lost Communication with iFix" in PS control log window. 
 
I restored it to standby with no problem.</pre>
<!-- Author: bbrau -->


<!-- Date: Mon Feb 9 13:26:35 2004 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-3539&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-3540  width='300' align='top'></a></td><td>IB5W0</td></tr></table>
<!-- Author: bbrau -->
<!-- Comment: Mon Feb  9 13;29;04 comment by...bbrau -->
<pre>ISL B5W0 tripped again.
It seems to first go pink for all layers in AVDD current
before it trips.</pre>


<!-- Date: Mon Feb 9 14:01:18 2004 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-3541&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-3542' ></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-3543&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-3544' ></a></center>
<!-- Author: bbrau -->
<!-- Comment: Mon Feb  9 14;02;33 comment by...bbrau -->
<pre>The trips of IB5W0 AVDD seem to be accompanied by a slight decrease
in DOIM current after each trip.  
</pre>


<!-- Comment: Tue Feb 10 07;56;00 comment by...SCN -->
From the log yesterday, this looks like a problem with the PC 
voltages-the "external trips" on the ladders are triggered by 
a 5VDOIM or 2VDOIM trip.  It makes some sens that AVDD would go up
if the DDRs stopped working, because you'd lose PREAMP RESETs etc.<BR>
I recall this happening for a LB1W0 (<a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=L00&wedge=B1W0&layer=All">PDB</a> 
and <a href="http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=copyentry&page=164&time=21:56:09"> Si Elog</a>) and power cycling the CAEN crate seems to have fixed the problem.
<!-- Date: Mon Feb 9 15:38:55 2004 -->
<pre>more wib work at FCC: 
 
1) worked on ESE 54 
   channels 1 and 3 work, 0,2,4 not (don't read back) 
 
2) checked ESE 99 
   channels 0 and 1 do not work (no readback)</pre>
<!-- Author: Julia, David, Jared, Stan, Florencia -->


<!-- Date: Mon Feb 9 16:15:34 2004 -->
<pre>wib work: 
 
1)returned (3 channel) PC ESE37 to cabinet with note ("ch1 no readback") 
 
2) checked out ESE 36 from cabinet:   
   ch4 ok 
   ch3 ok 
   ch2 no readback, high DVDD2 current 210mA 
   ch1 ok 
   ch0 ok 
 
this one is a winner! 
Plan for tomorrow 4pm: hook up ladders to ch4,3,1,0 
and we'll have a living wib.  </pre>
<!-- Author: Florencia, Jared, David, Julia -->


<!-- Date: Mon Feb 9 18:14:29 2004 -->
<b> dmod calibrations taken </b> <p> 
Solenoid OFF while beam is in the machine. <p> 
<pre> 
Error: mysqlconnect/db server: Can't connect to MySQL server on 'pcdaq.lbl.gov' (145) 
<p> 
 179005 DPS ON 
 179006 DPS OFF 
</pre>
<!-- Author: Rainer -->

<!-- Date: Mon Feb 9 18:37:59 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: IB1W0L3 
<li>problem n: 1032 
<li>Status: needs_study_time
<li>Type: Chip_other
<li>Action: Monitoring
<li>entered by: tompkins 
<li>description is: Cap id error and 9b in readall mode still seen.  Errors at 99.9% in data runs, not present in calibration runs 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=ISL&wedge=B1W0&layer=L3">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Mon Feb 9 19:01:51 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: IB0W0L0 
<li>problem n: 1019 
<li>Status: needs_work
<li>Type: Chip_bit_error
<li>Action: Monitoring
<li>entered by: tompkins 
<li>description is: bit 3 still found fluctuating both high and low in the same run. errors at 100% 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=ISL&wedge=B0W0&layer=L0">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Mon Feb 9 22:00:05 2004 -->
<p><font size=+1> D-mode Calibration Job Started </font>
<p><pre>
Job id            : 312
Calibration type  : nonstandard
Run period tag    : Feb_2004
DPS-off run       : 179006
DPS-on run        : 179005
Requested by      : Jason Nielsen
Main process id   : 11082850
Comment           : magnet off
</pre>
<!-- Author: CDF silicon D-mode calibration job server v1.4 -->
<!-- Comment: Tue Feb 10 09;14;17 comment by...Jason -->
This is a new one.  We had to reboot pcdaq, but now it seems to be down again.
<!-- Date: Mon Feb 9 22:00:05 2004 -->
<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 312 FAILED.

Job info
--------
Calibration type : nonstandard
DPS-off run      : 179006
DPS-on run       : 179005
Requested by     : Jason Nielsen
Submitted        : 2004-02-09 19:59:33
Completed        : 2004-02-09 19:59:53
Status           : FAILURE
Comment          : magnet off

Last processing stage reported : start of the run_calib_analysis.tcl script
Failure diagnostics :
You have no controlling tty and no DISPLAY.  Cannot read passphrase.
</pre>
<!-- Author: D-mode script run_calib_analysis.tcl -->




<!-- Date: Tue Feb 10 08:31:37 2004 -->
IB5W0 5V DOIM had several trips yesterday when we had no 
solenoid and were not taking data.  It has been relatively 
stable but pink and at the upper end of the Caution range (1775) since we got the solenoid back last 
evening.  I have asked the monitoring ace to page silicon if it 
goes above 1790 and to paste history plots into elog until 
further notice.  I'll look at the history of this wedge and if 
there are no errors we should consider changing the range.
<!-- Author: bbrau -->
<!-- Comment: Tue Feb 10 09;34;24 comment by...rainer -->
it's probably worth hockerizing the crate at some time during quiet time.


<!-- Date: Tue Feb 10 12:04:29 2004 -->
Rainer and I Hockerized the power supply feeding IB5W0 (Crate 10). 
We hope this will help stabilize the currents in this wedge which 
has been fluctuating since the solenoid went down yesterday morning. 
  
<!-- Author: bbrau -->

<!-- Date: Tue Feb 10 12:15:57 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: SB3W7L2 
<li>problem n: 1046 
<li>Status: needs_observation
<li>Type: AVDD2
<li>Action: Monitoring
<li>entered by: tompkins 
<li>description is: Chip 89 has cap id errors that have spiked to 98% in some recent runs.  Errors do not occur in every run.  This seems to have been seen before but not in the near past.  i don't know if it is directly related to AVDD2.   
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B3W7&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Feb 10 12:50:54 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: IB4W1L3 
<li>problem n: 1179 
<li>Status: needs_observation
<li>Type: Chip_other
<li>Action: Chip_bit_changes
<li>entered by: dkclark 
<li>description is: Changed thresholds for phi side chips: 8f, 9->10; 8e, 9->10; 8d,  9->11; 8c->9-10. Also changed ISEL bits for chips 9b-98 back to 0101  since this ladder is unbiased (see thread 465). IMON limits will  need adjusting. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=ISL&wedge=B4W1&layer=L3">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Feb 10 12:50:54 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W3L4 
<li>problem n: 1201 
<li>Status: needs_work
<li>Type: Chip_bit_error
<li>Action: Monitoring
<li>entered by: tompkins 
<li>description is: Seen bit 6, bit 0, bit 2 problems spiking to ~95% in cap ids of chips 88 and 8c.   
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B0W3&layer=L4">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Feb 10 12:53:11 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: IB2W1L0 
<li>problem n: 1184 
<li>Status: needs_observation
<li>Type: Chip_other
<li>Action: Chip_bit_changes
<li>entered by: dkclark 
<li>description is: Changed chip thresholds: b5,b6,b7,99,9a, 9->10; 98,9b, 9->11. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=ISL&wedge=B2W1&layer=L0">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Feb 10 12:55:25 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: IB0W2L1 
<li>problem n: 1178 
<li>Status: needs_observation
<li>Type: Chip_other
<li>Action: Chip_bit_changes
<li>entered by: dkclark 
<li>description is: Changed chip thresholds: a1,a2,a3,8e,8d, 9->10; a0,8f,8c, 9->11. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=ISL&wedge=B0W2&layer=L1">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Tue Feb 10 13:29:05 2004 -->
<table><tr><td><a href=/elog/notebooks/silicon/Tue_Feb_10_2004_132901.ps align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-3548  align='top'></a></td><td><h4>Estring Fires Again!</h4> At approximately 12:19 today, the  
Estring fired on what appears to be a real resonating condition, 
approximate time between events 25 &mu;s. 
Logic Analyzer Traces saved under ESTRG_1.B for further analysis if 
warranted.  A quick query of control room personnel indicated that a certain 
SPL and pager carrier may have been running svxdaq at that time. 
If so, they may have noticed some trouble in collecting events...<P> 
It makes sense that if one is running one ladder or wedge READ ALL, one 
may get into a resonant situation depending on the size of the events.</td></tr></table>
<!-- Author: SCN, Marcel -->

<!-- Date: Tue Feb 10 14:12:06 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W10L4 
<li>problem n: 603 
<li>Status: needs_work
<li>Type: Chip_bit_error
<li>Action: Monitoring
<li>entered by: tompkins 
<li>description is: Stuck cap id for chip 88 at 97%. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W10&layer=L4">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Feb 10 14:12:38 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W10L4 
<li>problem n: 603 
<li>Status: needs_work
<li>Type: Chip_bit_error
<li>Action: Monitoring
<li>entered by: tompkins 
<li>description is: sorry--the cap id is not stuck, rather it is just incorrect event to event. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W10&layer=L4">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Feb 10 14:16:15 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W5L2 
<li>problem n: 63 
<li>Status: needs_work
<li>Type: Optical_other
<li>Action: Monitoring
<li>entered by: tompkins 
<li>description is: I think this problem was supposed to be in monitoring's domain based on the previous entry . . .  anyways the bit 5 low problem is still present and varies between 50% and 80% for every run.  
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W5&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Feb 10 14:30:13 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: IB0W0L4 
<li>problem n: 130 
<li>Status: needs_observation
<li>Type: TX
<li>Action: Monitoring
<li>entered by: bbrau 
<li>description is: Dropped readout still at ~1% level about every 5th run (bitreporter).  Continue to observe to make sure rate doesn't increase. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=ISL&wedge=B0W0&layer=L4">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Feb 10 15:09:38 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: SB3W8L2 
<li>problem n: 1191 
<li>Status: needs_observation
<li>Type: RX
<li>Action: Diagnosis_update
<li>entered by: rainer 
<li>description is: B7L fixed itself starting run 178921 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B3W8&layer=L2">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Tue Feb 10 15:58:58 2004 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-3549&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-3549' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-3550&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-3550' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-3551&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-3551' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-3552&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-3552' width='300'></a></center>
<!-- Author: -store # 3226 plots  -- Andrew -->


<!-- Date: Tue Feb 10 16:56:34 2004 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-3553&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-3553  width='300' align='top'></a></td><td>z</td></tr></table>
<!-- Author: Susana -->
<!-- Comment: Tue Feb 10 16;58;13 comment by...Susana. -->
<pre>Pink CELL I_AVDD_B4W1L3, 1110 mA, range: 1150-1175 mA,
remains pink after being unmarked twice. Si Expert is coming.</pre>


<!-- Date: Tue Feb 10 17:22:24 2004 -->
<pre>UNUSUAL SUCCESS WITH WIB 2 (ESE61) 
 
using portcard ESE36 with 4 working channels 
we manage to hook up 4 working ladders (3 2chip ladders and one 5 chip ladder) 
 
These we tried but had problems with: 
-ladder QA316X (6 chips) fine except chip bit (?) problem when    initializing 
-ladder BOB (6 chip) probably Z side broken 
 
Ready to test RX, FTMs, VRB until we're blue in the face</pre>
<!-- Author: julia, david, jared, florencia -->


<!-- Date: Tue Feb 10 17:46:57 2004 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-3554&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-3555  width='300' align='top'></a></td><td>AVDD IB4W1L3</td></tr></table>
<!-- Author: Rainer -->
<!-- Comment: Tue Feb 10 17;52;32 comment by...rainer -->
<pre>no conspicuous problems in the bit reporter.</pre>

<!-- Comment: Tue Feb 10 17;56;08 comment by...David -->
The currents are lower because the ISEL bits were changed again. See <a href=
'/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=184&frame=2&anchor=12:50:54'>
previous entry</a>. Adjust the IMON limits accordingly.


<!-- Comment: Tue Feb 10 17;56;42 comment by...rainer -->
got fooled by PDB (showed empty entry) - ISEL bit change (see
<a href=
'/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=184&frame=2&anchor=12:50:54'>
here </a>)  warrants imon limit adjustement.

<!-- Comment: Tue Feb 10 17;59;01 comment by...Rainer -->
<h3> grrrr you scooped me ;) </h3>

<!-- Comment: Tue Feb 10 18;11;45 comment by...David -->
<pre>You gotta be fast, otherwise life will pass you by.</pre>
<!-- Date: Tue Feb 10 18:03:36 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: IB4W1L3 
<li>problem n: 1179 
<li>Status: needs_observation
<li>Type: Chip_other
<li>Action: IMON_limits
<li>entered by: rainer 
<li>description is: ISEL change warrants AVDD IMON limit change by -50mA<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>1160</td><td>1110</td></tr>
<tr><td><b>Lower</b></td><td>1150</td><td>1100</td></tr>
<tr><td><b>Upper</b></td><td>1125</td><td>1175</td></tr></table> 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=ISL&wedge=B4W1&layer=L3">report</a></ul>
<!-- Author: Problem DB -->




<!-- Date: Tue Feb 10 22:04:35 2004 -->
<h1> An old Friend Stopping By ... </h3> <p>

<p> <center><table BORDER COLS=3 WIDTH="500" NOSAVE > <tr> <td>Date</td> <td>Failure mode</td> <td>Crate number (1-16)</td> 
</tr> <tr> <td>12-MAR-2003</td> <td>Communication failure</td> <td>16</td> </tr> <tr> <td>27-MAR-2003</td> <td>Spontaneous reboot</td> <td>2</td> </tr> <tr> 
<td>02-APR-2003</td> <td>Communication failure</td> <td>15</td> </tr> <tr> <td>13-APR-2003</td> <td>Spontaneous reboot</td> <td>6</td> </tr> <tr> 
<td>16-APR-2003</td> <td>Communication failure</td> <td>1</td> </tr> <tr> <td>03-MAY-2003</td> <td>Spontaneous reboot</td> <td>13</td> </tr> <tr> 
<td>07-MAY-2003</td> <td>Spontaneous reboot</td> <td>4</td> </tr> <tr> <td>09-MAY-2003</td> <td>Spontaneous reboot</td> <td>8</td> </tr> 
<tr><td>08-JUN-2003</td> <td>Communication failure</td> <td>12</td> </tr> <tr><td>10-JUN-2003</td> <td>Communication failure</td> <td>7</td> </tr> 
<tr><td>10-JUN-2003</td> <td>Communication failure</td> <td>16</td> </tr> <tr><td>08-JUL-2003</td> <td>Communication failure</td> <td>12</td> </tr> 
<tr><td>09-JUL-2003</td> <td>Communication failure</td> <td>7</td> </tr> <tr><td>09-JUL-2003</td> <td>Communication failure</td> <td>5</td> </tr>  
<tr><td>10-FEB-2004</td> <td>Communication failure</td> <td>9</td> </tr> 
 
 
</table></center> 
</p> 
<!-- Author: Rainer, Ben -->


<!-- Date: Wed Feb 11 09:43:06 2004 -->
<table><tr><td><a href=/elog/notebooks/silicon/Wed_Feb_11_2004_094259.ps align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-3557  align='top'></a></td><td>spy spy once in a while (to be more precise once per store)</td></tr></table>
<!-- Author: rainer -->


<!-- Date: Wed Feb 11 15:25:54 2004 -->
<table><tr><td><a href=/elog/notebooks/silicon/Wed_Feb_11_2004_152550.ps align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-3563  align='top'></a></td><td><h3>More 4 Channel Estring testing</h3> Following up on  
<a href="http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=copyentry&page=182&time=12:18:46">this study</a> we set up the GB in the diagnostic crate to fire after 3 kicks, within a &#948;t of 1 &#956;s.  AS you can see from the plot, there is a 136 micro second delay between the first FFO signal in (trigger) to the first GB signal clocked, (X marker) and the BRAKE  (O Marker) is similarly delayed.  This demonstates that the delay is real, not an artifact of the LA.  Taka went to talk to Ken about it.</td></tr></table>
<!-- Author: SCN, Taka, Marcel -->

<!-- Date: Wed Feb 11 17:56:56 2004 -->
<p><font size=+1> D-mode Calibration Job Started </font>
<p><pre>
Job id            : 313
Calibration type  : nonstandard
Run period tag    : Feb_2004
DPS-off run       : 179006
DPS-on run        : 179005
Requested by      : Jason Nielsen
Main process id   : 15847221
Comment           : magnet off
</pre>
<!-- Author: CDF silicon D-mode calibration job server v1.4 -->



<!-- Date: Wed Feb 11 21:03:41 2004 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-3564&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-3565' ></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-3566&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-3567' ></a></center>
<!-- Author: Rainer -->
<!-- Comment: Wed Feb 11 21;13;26 comment by...Rainer -->
current history if IB5W0 5VDOIM. This guy was  acting up at the end of the <a href='ttp://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=copyentry&page=172&time=01:43:18'>shutdown</a>.  day 1048 =Nov 15th, 2003  when above elog entry was made. Does it co-incide with solenoid ramps ? Cell went pink first time
<a href=
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2004&action=view&page=105&frame=2&anchor=16:52:24.927'>
Feb 4th </a> which is DS day 1129.

<!-- Date: Wed Feb 11 22:33:16 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: IB5W0All 
<li>problem n: 1202 
<li>Status: needs_observation
<li>Type: Unknown
<li>Action: IMON_limits
<li>entered by: rainer 
<li>description is: 5V DOIM PC current has shown  signifcant increase around Nov15th, 2003, see  <a href= '/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=184&frame=2&anchor=21:03:41'> elog.</a> Take into account increased pedestal by redefining the ranges, but keep an eye on it. Is there a correlation with solenoid ramps ?<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>1705</td><td>1775</td></tr>
<tr><td><b>Lower</b></td><td>1695</td><td>1765</td></tr>
<tr><td><b>Upper</b></td><td>1785</td><td>1715</td></tr></table> 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=ISL&wedge=B5W0&layer=All">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Feb 11 22:37:44 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: IB5W0All 
<li>problem n: 1202 
<li>Status: needs_observation
<li>Type: VDOIM
<li>Action: IMON_limits
<li>entered by: rainer 
<li>description is: bullsh ... one more time...<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>1705</td><td>1755</td></tr>
<tr><td><b>Lower</b></td><td>1695</td><td>1745</td></tr>
<tr><td><b>Upper</b></td><td>1765</td><td>1715</td></tr></table> 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=ISL&wedge=B5W0&layer=All">report</a></ul>
<!-- Author: Problem DB -->
<!-- Comment: Wed Feb 11 22;39;23 comment by...Rainer -->
I think the script has OLD and NEW intertwixt for Upper ...

<!-- Date: Wed Feb 11 23:28:19 2004 -->
<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 313 finished successfully.

Job info
--------
Calibration type : nonstandard
DPS-off run      : 179006
DPS-on run       : 179005
Requested by     : Jason Nielsen
Submitted        : 2004-02-11 15:56:51
Completed        : 2004-02-11 21:27:56
Status           : SUCCESS
Comment          : magnet off
</pre>
<!-- Author: D-mode script run_calib_analysis.tcl -->
<!-- Comment: Thu Feb 12 08;47;02 comment by...Jason -->
Yee-ha!


<!-- Date: Thu Feb 12 10:09:08 2004 -->
<table><tr><td><a href=/elog/notebooks/silicon/Thu_Feb_12_2004_100859.ps align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-3569  align='top'></a></td><td>Spy 	</td></tr></table>
<!-- Author: bbrau -->

<!-- Date: Mon Mar 8 23:18:22 2004 -->
<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 316 FAILED.

Job info
--------
Calibration type : standard
DPS-off run      : 179701
DPS-on run       : 179700
Requested by     : Jason Nielsen
Submitted        : 2004-03-08 07:43:28
Completed        : 2004-03-08 11:52:20
Status           : FAILURE
Comment          : Resubmit job 315

Last processing stage reported : calculating DPS-on pedestals
Failure diagnostics :
child process exited abnormally
</pre>
<!-- Author: D-mode script  -->