<!-- Title: Owl shift. Mon Jan  7, 2008 -->
<!-- SciCo: Gerry Bauer -->
<!-- DAQAce: Eusin Lee -->
<!-- MonAce: &nbsp; -->
<!-- CO: Jason Galyardt -->
<!-- OpManager: Massimo -->
<!-- Notes: -->
<pre>continuing with Run 255846...recovering from hcal TDC crate problem....running</pre>


<!-- Date: Mon Jan 7 00:35:21.097 2008 -->
from previous shift ... 
After talking to Steve, i ended the run. disable the VME Power inhibit and started a new run. but htdc00 did not respond. tried ping and login. not successfull. so we power cycled it. ping worked. cannot login though. but shepherding worked! so we are back taking data. then i tried to enable the inhibit. can't. PSM is till RED and it is setting this inhibit. so i diabled it again and decided to leave it like this till morning. We ask the owl shift crew to keep and eye on other PS and HDTC plots.
<!-- Author: Chris/Sam :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=255846' target=_top>255846</a>) -->
<!-- Comment: Mon Jan  7 00;38;45 comment by...bauer -->
<pre>follow up conversation with steve:
  watch HCAL TDC's...if really ok, then have this particular crate masked from the PSM alarms, which will allow us to re-activate the "VME Power" inhibit, in case some other crate decides to take a break.</pre>


<!-- Comment: Mon Jan  7 00;50;20 comment by...jdl -->
The crate should be masked in PSM and the inhibit enabled so that we are sensitive to another crate problem.  If this one were to fix itself, it could be unmasked in PSM.  Gerry tells me that the problem is the Fan Status is reading 5V.  My guess is that after a while the supply will trip on over temperature.  At that point, all voltages will read 0 and the crate will be red in VxMon.  It might make it until Roberto comes in at 6am, or it may not.
<!-- Comment: Mon Jan  7 01;14;50 comment by...bauer -->
Phoned Cryo (Jim) to ask that he mask this crate so we can re-establish the trigger inhibit...he seems not to be able to! Sounded like a permissions problem??
<!-- Comment: Mon Jan  7 01;17;20 comment by...sam -->
i just remembered that we can mask that one rack in PSM. but it seems you guys figured it out already. Steve has a entry on this in <a href=
'/cgi/elog/elog.pl?nb=2008&action=view&page=18&frame=2&anchor=00:02:23.643'>
previous shift.</a> wish you guys a better shift than a one we had. good night.
<!-- Date: Mon Jan 7 00:41:04.510 2008 -->
BMU HV trip : 144SE. I turned on HV.
<!-- Author: Eunsin :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=255846' target=_top>255846</a>) -->
<!-- Comment: Mon Jan  7 03;28;30 comment by...Eunsin -->
<table border=0><td><tr><td bgcolor=#e0e030>happen again</td></tr></td></table>
<!-- Date: Mon Jan 7 00:41:38.281 2008 -->
FERML_SRC_FATALITY ERROR !!!  
  
 SRC Fatality Error for b0svx02: Sl 6 L2A w/o L1A 
HRR issued manually.
<!-- Author: Eunsin :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=255846' target=_top>255846</a>) -->


<!-- Date: Mon Jan 7 00:46:39.056 2008 -->
<table><tr><td><a href=/cgi/elog/elog.pl?nb=2008&action=view&page=-181&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/elog.pl?nb=2008&action=view&page=-182  width='300' align='top'></a></td><td>Pinkie: SVX vbias B5W11l3 
 
do an "unmark"...and seems to be ok...at least for the time being!</td></tr></table>
<!-- Author: bauer -->



<!-- Date: Mon Jan 7 00:50:42.180 2008 -->
Done TO. for crate/s:  
    b0htdc00. 
got stuck in halt again during HRR. 
I shepherd it...but no response...
<!-- Author: Eunsin :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=255846' target=_top>255846</a>) -->
<!-- Comment: Mon Jan  7 00;52;43 comment by...Eunsin -->
I ping the crate htdc00, but no response...


<!-- Comment: Mon Jan  7 00;55;07 comment by...Eunsin -->
A CRYO guy trying to power cycle it.
<!-- Comment: Mon Jan  7 00;59;16 comment by...Eunsin -->
It power-cycled. Shepherding works..taking data.
<!-- Comment: Mon Jan  7 01;02;36 comment by...bauer -->
Since the supply does not last very long after power cycling, I call Dervin, and he will be in to swap the supply.
<!-- Comment: Mon Jan  7 01;35;54 comment by...Eunsin -->
Happened again...got stuck in halt during hrr.
Ping it but no response.
<!-- Comment: Mon Jan  7 01;39;48 comment by...bauer -->
crate fails again....ask cryo to recycle power as we wait for Dervin to arrive
<!-- Comment: Mon Jan  7 01;40;41 comment by...Eunsin -->
Power cycled again.
Shepherding works..taking data again.
<!-- Comment: Mon Jan  7 01;43;33 comment by...bauer -->
Dervin arrives....
<!-- Date: Mon Jan 7 00:54:02.046 2008 -->
<table><tr><td><a href=/cgi/elog/elog.pl?nb=2008&action=view&page=-183&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/elog.pl?nb=2008&action=view&page=-183  width='300' align='top'></a></td><td>Following up on the htdc00 problems encountered earlier, here's the HTDC occupancy YMon slide.  There's no indication of the failure of an entire crate, but there's one hot channel: PHA phi wedge 27 (East).</td></tr></table>
<!-- Author: Jason Galyardt -->





<!-- Date: Mon Jan 7 01:08:29.196 2008 -->
<table><tr><td><a href=/cgi/elog/elog.pl?nb=2008&action=view&page=-184&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/elog.pl?nb=2008&action=view&page=-185  width='300' align='top'></a></td><td>earlier pinkie returns: SVX vbias B5W11L3 
...since it is small jump, set to ignore</td></tr></table>
<!-- Author: bauer -->




<!-- Date: Mon Jan 7 01:18:25.149 2008 -->
L2 Decision Timeout ERROR !!.  
AUTO HRR issued 
<!-- Author: Eunsin :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=255846' target=_top>255846</a>) -->


<!-- Date: Mon Jan 7 01:30:53.195 2008 -->
Still having PHA HV in Yellow. 
Crate 02 S109 Ch14 has over voltage = 101.73%  
<!-- Author: Eunsin :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=255846' target=_top>255846</a>) -->


<!-- Date: Mon Jan 7 01:31:17.770 2008 -->
BUSY Timeout
<!-- Author: Eunsin :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=255846' target=_top>255846</a>) -->
<!-- Comment: Mon Jan  7 01;43;49 comment by...Eunsin -->
again
<!-- Comment: Mon Jan  7 01;57;28 comment by...Eunsin -->
again
<!-- Date: Mon Jan 7 01:42:13.145 2008 -->
<table><tr><td><a href=/cgi/elog/elog.pl?nb=2008&action=view&page=-186&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/elog.pl?nb=2008&action=view&page=-186  width='300' align='top'></a></td><td>West CES phi wedge 15 seems to have a block of "hottish" wires  (lower left plot in the CESWireCanvas); this block has been there a while, I don't remember the scale discrepancy with respect to the reference plot.  The reference plot's maximum temp corresponds to ~300 ADC counts per hit, whereas the maximum temp for this plot is over 3000.  Other recent runs do not exhibit this feature. 
 
This is not a SMXR lookup table corruption, I think, because this is the only plot which exhibits this behavior.  Marked CES "OK" because the block of hot channels is small enough to pass the criteria.</td></tr></table>
<!-- Author: Jason Galyardt -->




<!-- Date: Mon Jan 7 01:50:22.620 2008 -->
Done TO. for crate/s:  
    b0cmx01    
auto hrr issued
<!-- Author: Eunsin :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=255846' target=_top>255846</a>) -->


<!-- Date: Mon Jan 7 02:05:44.054 2008 -->
Run <A HREF=/java/cdfdb/servlet/RunSummary?RUN_NUMBER=255846>255846</A>
 Terminated at 2008.01.07 02:05:37
<!-- Author: RunControl -->



<!-- Date: Mon Jan 7 02:06:46.875 2008 -->
Crate b0htdc00 trips its 5V again, but Dervin is ready to swap. 
We end the run, and will start a run without this crate while the work is ongoing.
<!-- Author: bauer :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=255846' target=_top>255846</a>) -->

<!-- Date: Mon Jan 7 02:10:27.433 2008 -->
Run <A HREF=/java/cdfdb/servlet/RunSummary?RUN_NUMBER=255847>255847</A>
 Activated at 2008.01.07 02:09:33
<!-- Author: RunControl -->


<!-- Date: Mon Jan 7 02:10:28.358 2008 -->
Run <A HREF=/java/cdfdb/servlet/RunSummary?RUN_NUMBER=255847>255847</A>
ACTIVATE: RunSet: AAA_CURRENT  Trigger: PHYSICS_5_01 [3,1016,713] While fixing htdc00 crate we're taking data without that crate
<!-- Author: Eunsin -->



<!-- Date: Mon Jan 7 02:11:41.082 2008 -->
Busy Timeout.
<!-- Author: Eunsin :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=255847' target=_top>255847</a>) -->
<!-- Comment: Mon Jan  7 02;21;19 comment by...Eunsin -->
again
<!-- Comment: Mon Jan  7 02;26;40 comment by...Eunsin -->
Again
<!-- Comment: Mon Jan  7 02;51;49 comment by...Eunsin -->
again
<!-- Date: Mon Jan 7 02:18:45.445 2008 -->
<pre>ProcMon error: RTSERVER. 
Mon Jan 7 02:15:43 CST 2008   procAction  rtserver   check   b0server04 
Checking rtserver 
Found 1 copy of the rtserver watcher 'sscheck' script running (1 expected) 
Found 1 copy of the rtserver (rtserver.x) running (1 expected) 
Found 197 rtserver connections (near >235 will degrade performance) 
Found 0 rtserver FIN_WAIT connections (>0 may degrade performance) 
Found 0 rtserver FIN_WAIT connections from www-cdfonline (TOMCAT) 
Found 1 potentially stuck ports  
Proto Recv-Q Send-Q Local Address               Foreign Address             State       User       Inode      
tcp        0  26752 b0server04.fnal.gov:5101    b0htdc00.fnal.gov:1026      ESTABLISHED cdfdaq     440234169   
RTserver is not running correctly 
 
It seems to be related to excluding hdtc00 crate.</pre>
<!-- Author: Eunsin :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=255847' target=_top>255847</a>) -->



<!-- Date: Mon Jan 7 02:25:44.693 2008 -->
L2 Decision Timeout ERROR !!. auto hrr issued.
<!-- Author: Eunsin :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=255847' target=_top>255847</a>) -->


<!-- Date: Mon Jan 7 02:29:41.472 2008 -->
Run <A HREF=/java/cdfdb/servlet/RunSummary?RUN_NUMBER=255847>255847</A>
 Terminated at 2008.01.07 02:29:08
<!-- Author: RunControl -->


<!-- Date: Mon Jan 7 02:29:42.508 2008 -->
Run <A HREF=/java/cdfdb/servlet/RunSummary?RUN_NUMBER=255847>255847</A>
TERMINATE: htdc00 back
<!-- Author: Eunsin -->


<!-- Date: Mon Jan 7 02:33:19.885 2008 -->
Run <A HREF=/java/cdfdb/servlet/RunSummary?RUN_NUMBER=255848>255848</A>
 Activated at 2008.01.07 02:32:44
<!-- Author: RunControl -->
<!-- Comment: Mon Jan  7 02;34;28 comment by...bauerg -->
now with the HadCal TDC BACK IN!!
<!-- Date: Mon Jan 7 02:33:20.405 2008 -->
Run <A HREF=/java/cdfdb/servlet/RunSummary?RUN_NUMBER=255848>255848</A>
ACTIVATE: RunSet: AAA_CURRENT  Trigger: PHYSICS_5_01 [3,1016,713] 
<!-- Author: Eunsin -->




<!-- Date: Mon Jan 7 02:39:47.949 2008 -->
So Dervin changed the power supply on this crate, and the run is restarted with b0htdc00 IN the run. 
 <br><br>
Two outstanding issues: <br>
 1) it is apparently NOT possible for this individual crate to be masked off in PSM! This shouldn't be this way, and Dervin did not see obvious problem. Needs to be investigated in the morning! 
 <br><br>
 2) The new power supply needs to have its address reprogrammed so that the PSM monitoring properly recognizes it. Right now PSM is NOT properly reading out its voltage/status (although if it fails, an inhibit should still be issued and recognized --- and we ARE now running with the inhibits enabled again!). Thus, this also must be done in the morning.
<!-- Author: bauer :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=255848' target=_top>255848</a>) -->
<!-- Comment: Mon Jan  7 02;47;42 comment by...bauer -->
<table border=0><td><tr><td bgcolor=#e0e030><pre>Also:
   **** Dervin wanted to emphasize that if a PS fan fails the supply should be IMMEDIATELY replaced as the overheating is fast and severe! ***</pre></td></tr></td></table>

<!-- Date: Mon Jan 7 02:51:41.612 2008 -->
Run <A HREF=/java/cdfdb/servlet/RunSummary?RUN_NUMBER=255845>255845</A>
<HTML>Run <A HREF=http://www-cdfonline.fnal.gov/java/cdfdb/servlet/RunSummary?RUN=255845 target=_runSummary>255845</A> has not yet been checked for goodrun status; please do so.</HTML>
<!-- Author: RunControl -->




<!-- Date: Mon Jan 7 02:56:57.008 2008 -->
L2 Decision Timeout ERROR !!.  
 auto hrr issued
<!-- Author: Eunsin :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=255848' target=_top>255848</a>) -->
<!-- Comment: Mon Jan  7 03;16;11 comment by...Eunsin -->
again
<!-- Comment: Mon Jan  7 03;32;22 comment by...Eunsin -->
again
<!-- Comment: Mon Jan  7 03;39;05 comment by...Eunsin -->
again
<!-- Comment: Mon Jan  7 04;38;31 comment by...Eunsin -->
again
<!-- Comment: Mon Jan  7 04;47;28 comment by...Eunsin -->
again
<!-- Comment: Mon Jan  7 04;56;07 comment by...Eunsin -->
again
<!-- Comment: Mon Jan  7 05;01;16 comment by...Eunsin -->
again
<!-- Comment: Mon Jan  7 05;09;09 comment by...Eunsin -->
again
<!-- Comment: Mon Jan  7 05;12;51 comment by...Eunsin -->
again
<!-- Comment: Mon Jan  7 05;28;10 comment by...Eunsin -->
again
<!-- Comment: Mon Jan  7 06;27;08 comment by...Eunsin -->
again
<!-- Comment: Mon Jan  7 06;30;25 comment by...Eunsin -->
again
<!-- Comment: Mon Jan  7 07;20;28 comment by...Eunsin -->
again
<!-- Comment: Mon Jan  7 07;52;18 comment by...Eunsin -->
again
<!-- Date: Mon Jan 7 03:06:49.938 2008 -->
Done TO. for crate/s:  
    b0pcal11   
auto hrr issued.
<!-- Author: Eunsin :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=255848' target=_top>255848</a>) -->



<!-- Date: Mon Jan 7 03:17:52.485 2008 -->
BUSY Timeout. auto hrr issued
<!-- Author: Eunsin :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=255848' target=_top>255848</a>) -->
<!-- Comment: Mon Jan  7 03;43;10 comment by...Eunsin -->
again
<!-- Comment: Mon Jan  7 03;48;32 comment by...Eunsin -->
again
<!-- Comment: Mon Jan  7 03;52;40 comment by...Eunsin -->
<pre>This is from EVB ACE Controls :
--- Report of LoadErrors and byte count errors within the last 20min---
EVB Error due to too large event fragment in scpu b0evme11, at 2008/01/07 03:17:03.
EVB Error due to too large event fragment in scpu b0evme11, at 2008/01/07 03:42:45.
EVB Error due to too large event fragment in scpu b0evme11, at 2008/01/07 03:48:03.
Total errors: 3.</pre>
<!-- Comment: Mon Jan  7 03;53;46 comment by...Eunsin -->
again
<!-- Comment: Mon Jan  7 04;02;04 comment by...Eunsin -->
<pre>This is from the instruction on the related issue:
If the report says "EVB Error due to too large event fragment in scpu #": * If this happens during shot setup, please just record it in the elog, with the scpu number. No further action is needed. * If it happens during data-taking, please continue to take data (HRR as needed), but page EVB/L3. "

Shoud we page EVB/L3? Let's see more...</pre>
<!-- Comment: Mon Jan  7 04;04;20 comment by...Eunsin -->
again.
<!-- Comment: Mon Jan  7 04;15;06 comment by...Eunsin -->
again
<!-- Comment: Mon Jan  7 04;25;13 comment by...Eunsin -->
again
<!-- Comment: Mon Jan  7 04;44;50 comment by...Eunsin -->
again
<!-- Comment: Mon Jan  7 04;58;46 comment by...Eunsin -->
again
<!-- Comment: Mon Jan  7 05;07;48 comment by...Eunsin -->
again
<!-- Comment: Mon Jan  7 05;17;06 comment by...Eunsin -->
again...sigh...
<!-- Comment: Mon Jan  7 05;21;29 comment by...Eunsin -->
again
<!-- Comment: Mon Jan  7 05;25;48 comment by...Eunsin -->
again
<!-- Comment: Mon Jan  7 05;30;25 comment by...Eunsin -->
again...
<!-- Comment: Mon Jan  7 05;32;29 comment by...Eunsin -->
<pre>From EVB ACE Controls:
2008/01/07, 05:29:52 BEGIN: Diagnose TimeOuts
--- Report of LoadErrors and byte count errors within the last 20min---
EVB Error due to too large event fragment in scpu b0evme11, at 2008/01/07 04:58:16.
EVB Error due to too large event fragment in scpu b0evme11, at 2008/01/07 05:07:17.
EVB Error due to too large event fragment in scpu b0evme11, at 2008/01/07 05:16:29.
EVB Error due to too large event fragment in scpu b0evme11, at 2008/01/07 05:21:00.
EVB Error due to too large event fragment in scpu b0evme11, at 2008/01/07 05:25:19.
EVB Error due to too large event fragment in scpu b0evme11, at 2008/01/07 05:29:28.
Total errors: 6.
---------------------- End of Report -----------------------------------
2008/01/07, 05:31:16 END: Diagnose TimeOuts</pre>
<!-- Comment: Mon Jan  7 05;42;43 comment by...Eunsin -->
again
<!-- Comment: Mon Jan  7 05;47;41 comment by...Eunsin -->
<pre>sigh...
Somebody should look it up...
This problem has been persisting from evening shift..</pre>
<!-- Comment: Mon Jan  7 05;54;49 comment by...Eunsin -->
again
<!-- Comment: Mon Jan  7 05;59;02 comment by...Eunsin -->
again
<!-- Comment: Mon Jan  7 06;03;31 comment by...Eunsin -->
again
<!-- Comment: Mon Jan  7 06;20;00 comment by...Eunsin -->
again
<!-- Comment: Mon Jan  7 06;24;09 comment by...Eunsin -->
again
<!-- Comment: Mon Jan  7 06;32;29 comment by...Eunsin -->
again
<!-- Comment: Mon Jan  7 06;45;26 comment by...Eunsin -->
again
<!-- Comment: Mon Jan  7 07;06;23 comment by...Eunsin -->
again
<!-- Comment: Mon Jan  7 07;11;00 comment by...Eunsin -->
again
<!-- Comment: Mon Jan  7 07;27;40 comment by...Eunsin -->
again
<!-- Comment: Mon Jan  7 07;31;14 comment by...Eunsin -->
again
<!-- Comment: Mon Jan  7 07;39;13 comment by...Eunsin -->
again
<!-- Comment: Mon Jan  7 07;57;40 comment by...Eunsin -->
again
<!-- Date: Mon Jan 7 03:24:02.149 2008 -->
Run <A HREF=/java/cdfdb/servlet/RunSummary?RUN_NUMBER=255847>255847</A>
cal: <tt>htdc00 was taken out of the run to be fixed, so there's no had cal timing info!</tt>
<!-- Author: Consumer Operator( Jason Galyardt) -->




<!-- Date: Mon Jan 7 03:34:20.408 2008 -->
Run <A HREF=/java/cdfdb/servlet/RunSummary?RUN_NUMBER=255847>255847</A>
RUNSTATUS: <PRE>Marked Bad, explanation: crate htdc00 NOT in run, its PS being replaced
CCAL 
PCAL 
</PRE>
<!-- Author: cdfscico (G Bauer) -->















<!-- Date: Mon Jan 7 04:51:24.733 2008 -->
Node b0pcal04 in Error *** 
Last data more than 120s ago!  Node is not responsive. 
Shepherding works.
<!-- Author: Eunsin :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=255848' target=_top>255848</a>) -->




<!-- Date: Mon Jan 7 05:00:55.692 2008 -->
RXPT Error for crate/s:  
    b0svx02    
HRR issued manually
<!-- Author: Eunsin :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=255848' target=_top>255848</a>) -->




<!-- Date: Mon Jan 7 05:08:50.742 2008 -->
CER_SVXMON_HALT_RECOVER_RUN_ERROR !!!  
  
 Stuck Cellid S/B2/W4/L4/C0-6 .  
 AUTO HRR  issued  
<!-- Author: Eunsin :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=255848' target=_top>255848</a>) -->











<!-- Date: Mon Jan 7 05:44:00.376 2008 -->
I will reprogram the PSM address for htdc00 as soon as come in this morning. So it can read out properly.  
PS: When a fan in these power supplies goes out, they will not overheat since the have an overtemp circuitry bilt-in to protect them from overheating.
<!-- Author: Roberto Davila :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=255848' target=_top>255848</a>) -->





<!-- Date: Mon Jan 7 06:03:16.100 2008 -->
ICICLE in ProcMon turned red. Inverstigating..
<!-- Author: Eunsin :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=255848' target=_top>255848</a>) -->
<!-- Comment: Mon Jan  7 06;10;38 comment by...Eunsin -->
<pre>I saw an error message popped up on solenoid2 machine:

System Error
C:\Dynamics\NAC.EXE
na_rcv_cb : memory allocation failed.

I cleared it and restart the ICICLE.
But could not connect &lt;_node&gt; RTserver.</pre>


<!-- Comment: Mon Jan  7 06;20;53 comment by...Eunsin -->
I killed ICICLE and restarted it, but it failed. 
No connection to RTserver.


<!-- Comment: Mon Jan  7 06;26;29 comment by...Eunsin -->
In this case what are we supposed to do? Can't find an instruction..








<!-- Comment: Mon Jan  7 07;27;22 comment by...Eunsin -->
We paged Steve and he will come over here..



<!-- Comment: Mon Jan  7 07;41;02 comment by...bauer -->
Steve Hahn was called, and will be in to help restore RT server communication
<!-- Date: Mon Jan 7 07:33:20.967 2008 -->
Run <A HREF=/java/cdfdb/servlet/RunSummary?RUN_NUMBER=255755>255755</A>
<HTML>Run <A HREF=http://www-cdfonline.fnal.gov/java/cdfdb/servlet/RunSummary?RUN=255755 target=_runSummary>255755</A> has not yet been checked for goodrun status; please do so.</HTML>
<!-- Author: RunControl -->
<!-- Comment: Mon Jan  7 07;49;27 comment by...bauer -->
This run has CAL marked as 'other', but we (shift crew at the end of that run) were not convinced that this is correct. Experts need to review status of this run.
(XFT was also marked as 'other', cuz of some XFT errors, but XFT expert declared this was ok, ie see
<a href=
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2008&action=view&page=10&frame=2&anchor=04:45:52.231'>
here</a>



<!-- Date: Mon Jan 7 07:51:17.456 2008 -->
Done TO. for crate/s:  
    b0pcal01   auto hrr issued.
<!-- Author: Eunsin :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=255848' target=_top>255848</a>) -->


<!-- Date: Mon Jan 7 07:55:25.163 2008 -->
<TABLE BORDER=2 CELLSPACING=1 CELLPADDING=1 BGCOLOR=WHITE>
<TR BGCOLOR=YELLOW><TH>RunNumber</TH>
<TH>DataType</TH>
<TH>PhysicsTable</TH>
<TH>Begin</TH>
<TH>End</TH>
<TH>LiveTime</TH>
<TH>L3Accepts</TH>
<TH>DelivLumi nb<SUP>-1</SUP></TH>
<TH>LiveLumi nb<SUP>-1</SUP></TH>
<TH>GR</TH>
<TH>SC</TH>
<TH>RC</TH></TR>
<TR><TD><A HREF=/java/cdfdb/servlet/RunSummary?RUN=255846 target=_runSummary>255846</A> x3E766</TD>
<TD>BEAM</TD>
<TD><FONT SIZE=-1>PHYSICS_5_01 [3,1016,713]</FONT></TD>
<TD ALIGN=CENTER>23:56:59</TD>
<TD ALIGN=CENTER>02:05:37</TD>
<TD ALIGN=CENTER>01:17:55</TD>
<TD ALIGN=RIGHT>     464,498</TD>   <TD ALIGN=RIGHT>    600.08</TD>
<TD ALIGN=RIGHT>    359.27</TD>
<TD ALIGN=CENTER>1</TD>
<TD ALIGN=CENTER>1</TD>
<TD ALIGN=CENTER>1</TD></TR>

<TR><TD><A HREF=/java/cdfdb/servlet/RunSummary?RUN=255847 target=_runSummary>255847</A> x3E767</TD>
<TD>BEAM</TD>
<TD><FONT SIZE=-1>PHYSICS_5_01 [3,1016,713]</FONT></TD>
<TD ALIGN=CENTER>02:09:33</TD>
<TD ALIGN=CENTER>02:29:08</TD>
<TD ALIGN=CENTER>00:17:39</TD>
<TD ALIGN=RIGHT>      78,300</TD>   <TD ALIGN=RIGHT>     86.44</TD>
<TD ALIGN=RIGHT>     76.19</TD>
<TD ALIGN=CENTER>0</TD>
<TD ALIGN=CENTER>1</TD>
<TD ALIGN=CENTER>1</TD></TR>

<TR><TD><A HREF=/java/cdfdb/servlet/RunSummary?RUN=255848 target=_runSummary>255848</A> x3E768</TD>
<TD>BEAM</TD>
<TD><FONT SIZE=-1>PHYSICS_5_01 [3,1016,713]</FONT></TD>
<TD ALIGN=CENTER>02:32:44</TD>
<TD ALIGN=CENTER></TD>
<TD ALIGN=CENTER>04:40:07</TD>
<TD ALIGN=RIGHT>   1,487,570</TD>   <TD ALIGN=RIGHT>  1,199.46</TD>
<TD ALIGN=RIGHT>  1,044.46</TD>
<TD ALIGN=CENTER></TD>
<TD ALIGN=CENTER></TD>
<TD ALIGN=CENTER>1</TD></TR>

<TR><TD>Totals</TD>
<TD> </TD>
<TD> </TD>
<TD> </TD>
<TD>07:55:01</TD>
<TD ALIGN=CENTER>06:15:42</TD>
<TD ALIGN=RIGHT>     2,030,368</TD> <TD ALIGN=RIGHT>  1,885.98</TD>
<TD ALIGN=RIGHT>  1,479.92</TD>
<TD> </TD>
<TD> </TD>
<TD> </TD></TR>

</TABLE>
<!-- Author: End of Shift Report -->




<!-- Date: Mon Jan 7 07:59:06.470 2008 -->
<font color=red>Shift Summary: </font><pre>Inherit Run 255846...along with some of its problems 
 
--Running with  
 PHA HV in Yellow. Crate 02 S109 Ch14 has over voltage = 101.73% 
 
-HadCal TDC crate b0htd00 is giving an alarm: 
Channel 6 reads 5, rather than 0=OK Fan 
--&gt;Dervin comes in and replaces PS 
 
Run 255847 is without  b0htd00 crate! Run marked bad for CAL 
 
Two outstanding issues: 
1) it is apparently NOT possible for this individual crate  
to be masked off in PSM! Needs to be investigated in the morning! 
 
2) The new power supply needs to have its address reprogrammed so that  
the PSM monitoring properly recognizes it. Right now PSM is NOT properly  
reading out its voltage/status. This also must be done in the morning. 
--&gt; Roberto says he is on it when he comes in 
 
 
00:41:04  BMU HV trip  
 
 
Continuing to get "too large event fragment" errors all night 
 
ACE gets ICICLE error in ProcMon....tries restarting it,  
cannot connect to RT server...Steve Hahn will come in to restore it 
</pre> 
<br><b>End of Shift Numbers</b>
<table><tr><td width=60% align=left>
<b>CDF Run II <p></b>                       
<pre>
Runs                   255846, 255847, 255848
Delivered Luminosity   1906.9 nb-1  
Acquired Luminosity    1492.1 nb-1  
Efficiency             78.2
   
</td></tr></table></pre>
<!-- Author: bauer -->