<!-- Title: Day shift. Mon Jul 11, 2005 -->
<!-- SciCo: Beate Heinemann -->
<!-- DAQAce: Svenja Richter  -->
<!-- MonAce: Greg Williams -->
<!-- CO: Athanasios Staveris -->
<!-- OpManager: Bob Wagner -->
<!-- Notes: -->
<pre>No beams expected for the entire shift since they had lost the entire stack. There will be a 2 hour access starting around 9am probably. L2 experts will work on their system.</pre>


<!-- Date: Mon Jul 11 08:38:20.346 2005 -->
I've turned on East CMX wedges 18-19 and 20 in prep for the access at ~9:00.  If 18-19 trips go ahead and reset it as often as you care to (it likely won't trip).
<!-- Author: Dale Stentz -->
<!-- Comment: Mon Jul 11 09;50;23 comment by...Dale and Phil -->
We're done with our work (see summary 
<a href=
'/cgi/elog/elog.pl?nb=2005&action=view&page=575&frame=2&anchor=09:45:08.028'>below</a>).<br><br>
Our instructions are to keep these wedges on for the rest of the access - feel free to turn on all CMX if you take a quiet time cosmic run and set it to stand-by once MCR wants to put beam in the Tev.
<!-- Date: Mon Jul 11 08:38:34.478 2005 -->
The latest version of YMon (cdfsoftb0 version 6.1.0o) has a 
problem with CESDMonitor which crashes when YMon trys to get sarted 
with cosmic run.  I set the CO monitor startup script so that the previous version of YMon (cdfsoftb0 6.1.0m) starts up automatically. 
This version runs fine cosmic or physics.  YMon expert will be 
notified.
<!-- Author: kaori :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200790' target=_top>200790</a>) -->


<!-- Date: Mon Jul 11 09:08:46.412 2005 -->
<pre>iFix alarm:  Node Unreachable error:   
 
The Gamma High Voltage Alarm was red on the upper screen.  I clicked the "D" and brought up the Gamma voltage sources picture.    The red alarm turned back to green.  
The Gamma bars on the lower screen turned red for about one minute and then turned green again.   </pre>
<!-- Author: Greg -->


<!-- Date: Mon Jul 11 09:13:51.982 2005 -->
The access has just started at 9.05am. It will be 2.5 hours.
<!-- Author: Beate -->

<!-- Date: Mon Jul 11 09:34:19.009 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200790">200790</A>
 Terminated at 2005.07.11 09:33:58
<!-- Author: RunControl -->


<!-- Date: Mon Jul 11 09:34:39.734 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200790">200790</A>
TERMINATE: end run
<!-- Author: Fabrizio  x2080 -->



<!-- Date: Mon Jul 11 09:41:40.358 2005 -->
The CMX work is done. Details will follow.
<!-- Author: Phil Schlabach -->


<!-- Date: Mon Jul 11 09:45:08.028 2005 -->
<h3>CMX access summary</h3> 
<p> 
We went in to try to resegment the HV on the NE miniskirt.  Wedges 18-19 on the east have been tripping with varying rates and was taken out on Saturday when it became to fast. 
</p> 
We segmented the HV so that we can pin-point the problem better and perhaps (as was the case on the SW CMX miniskirt) make the weak sections more robust aginst trips.   
<br><br> 
Other access news: Phil observed that the blue motor generator #3 on the SE corner was making a high pitch sound (perhaps a bit hot as well) and has alterted others of this.
<!-- Author: Phil Schlabach and Dale Stentz -->
<!-- Comment: Mon Jul 11 11;11;21 comment by...Dale and Phil -->
<a href=
'/cgi/elog/elog.pl?nb=2005&action=view&page=575&frame=2&anchor=10:00:34.516'>Via the trips below</a> we decided to re-configure the HV further.  (Note: this is basically what we wanted - find the bad section and isolate it down to a small as possible.)<br><br>Details + instructions to follow.
<!-- Comment: Mon Jul 11 13;00;32 comment by...Phil and Dale -->
Summary:<br><br>We were lucky and added the bad section to a smaller section and thus only need to make one other change to identfy the bad section (and we did so).  Sure enough it triped a couple of times after making the needed changes.  This section, NE CMX iFIX wedge 20, represents only 5 degrees in phi and can be removed (i.e. turned off) with no effect on data quality, etc.  <br><br>  Formal instructions will be posted when we are closer to actual data taking.  Further details are posted in the <a href=
'/cgi/elog/det-system-elog.pl?nb=cmx&action=view&page=9&frame=2&anchor=12:51:53'>
CMX e-log</a>.
<!-- Date: Mon Jul 11 09:46:06.350 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200793">200793</A>
ACTIVATE: RunSet: SVT_B0SVT09_STANDALONE 
<!-- Author: Radu -->




<!-- Date: Mon Jul 11 09:59:03.020 2005 -->
Working on pcal02, please ignore the power cycles.
<!-- Author: m mattson (ADMEM) -->


<!-- Date: Mon Jul 11 10:00:34.516 2005 -->
CMX NE 20 just triped - this is the section that we suspected (wanted) to go bad.  It recovered on the reset - will watch it for a bit.
<!-- Author: Dale -->
<!-- Comment: Mon Jul 11 10;14;50 comment by...Dale -->
Another trip (15 minute time constant?)
<!-- Date: Mon Jul 11 10:07:16.522 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200794">200794</A>
ACTIVATE: RunSet: SVT_B0SVT09_STANDALONE 
<!-- Author: Radu -->


<!-- Date: Mon Jul 11 10:13:42.682 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200795">200795</A>
ACTIVATE: RunSet: SMQIECALIB 
<!-- Author: Svenja  x2080 -->




<!-- Date: Mon Jul 11 10:15:18.148 2005 -->
IMU access report: Basically, we couldn't find any noise on the offending channels in SE BMU. I noticed the fan located on the SE corner wasn't turning and the motor was quite hot to the touch. I left it unplugged. As for the noise around SE80, we can't find it so we can't fix it. It also should have absolutely no effect upon data. 
 
Also noted, someone left a broken off key in the IMU01 crate - its functional just confusing.  
<!-- Author: Sunny and Dan -->

<!-- Date: Mon Jul 11 10:26:28.771 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200795">200795</A>
TERMINATE: SM QIE calib successful
<!-- Author: Svenja  x2080 -->
<!-- Comment: Mon Jul 11 10;45;29 comment by...m mattson -->
Plug SMXR okay (almost too good...)
<!-- Date: Mon Jul 11 10:28:45.263 2005 -->
While partitioning the spike run, we got a Scanner Manager Error because of b0 eb24 was rebooted or hung. We were asked by the pop-up to clean upp evb.
<!-- Author: Svenja -->

<!-- Date: Mon Jul 11 10:32:58.236 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200796">200796</A>
 Activated at 2005.07.11 10:31:58
<!-- Author: RunControl -->


<!-- Date: Mon Jul 11 10:32:59.793 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200796">200796</A>
ACTIVATE: RunSet: ACE_CALORIMETER_MINIMAL  Trigger: SUMET5 [5,622,540] 
<!-- Author: Svenja  x2080 -->


<!-- Date: Mon Jul 11 10:34:46.026 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200796">200796</A>
 Terminated at 2005.07.11 10:34:13
<!-- Author: RunControl -->


<!-- Date: Mon Jul 11 10:34:47.394 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200796">200796</A>
TERMINATE: spike run worked
<!-- Author: Svenja  x2080 -->
<!-- Comment: Mon Jul 11 10;45;03 comment by...m mattson -->
L1 rate 70 Hz, so the L1 cables are back on
<!-- Date: Mon Jul 11 10:37:28.641 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200797">200797</A>
ACTIVATE: RunSet: ACE_QIE with FRAM download, for pcal crates
<!-- Author: Svenja  x2080 -->




<!-- Date: Mon Jul 11 10:50:46.710 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200797">200797</A>
TERMINATE: finished
<!-- Author: Svenja  x2080 -->



<!-- Date: Mon Jul 11 10:53:44.884 2005 -->
Work done on pcal02, slot 16, ch 11.  This channel has been dead for the last week.  We were being extra paranoid, since this is actually a replacement CAFE, which failed within 24 hours of being put in the hall.<p> 
The ADMEMs in slots 14 and 16 were swapped (the problem followed the ADMEM), and the CAFE of channel 11 (now in slot 14) was replaced.  This new CAFE passed all tests.  SMXR and spike runs are normal, so we no longer need access to the crate downstairs.  Calib-and-FRAM download finished okay, so the repair work is finished.
<!-- Author: m mattson, s richter -->
<!-- Comment: Mon Jul 11 12;57;23 comment by...m mattson -->
<br>This problem was seen as PEM 8W channel 11 in the calibrations, and I think eta 15 of the YMon plots (dead channel).
<!-- Date: Mon Jul 11 10:55:54.892 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200801">200801</A>
ACTIVATE: RunSet: ACE_QIE 
<!-- Author: Svenja  x2080 -->


<!-- Date: Mon Jul 11 10:57:18.015 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200801">200801</A>
TERMINATE: Cal QIE calib successful
<!-- Author: Svenja  x2080 -->


<!-- Date: Mon Jul 11 11:00:10.141 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200803">200803</A>
ACTIVATE: RunSet: CALIB_CLC_QIE 
<!-- Author: Svenja  x2080 -->


<!-- Date: Mon Jul 11 11:00:58.451 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200803">200803</A>
TERMINATE: CLC QIE calib successful
<!-- Author: Svenja  x2080 -->


<!-- Date: Mon Jul 11 11:03:29.941 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200804">200804</A>
ACTIVATE: RunSet: CALIB_QIE_FWD 
<!-- Author: Svenja  x2080 -->


<!-- Date: Mon Jul 11 11:04:51.341 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200804">200804</A>
TERMINATE: BSC QIE calib successful
<!-- Author: Svenja  x2080 -->


<!-- Date: Mon Jul 11 11:06:01.218 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200805">200805</A>
ACTIVATE: RunSet: CALIB_RP_SMQIE 
<!-- Author: Svenja  x2080 -->


<!-- Date: Mon Jul 11 11:07:20.948 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200805">200805</A>
TERMINATE: Roman Pot QIE calib successful
<!-- Author: Svenja  x2080 -->


<!-- Date: Mon Jul 11 11:08:09.937 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200806">200806</A>
ACTIVATE: RunSet: BOTHPLUGS_NORMAL 
<!-- Author: Svenja  x2080 -->



<!-- Date: Mon Jul 11 11:16:44.358 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200806">200806</A>
TERMINATE: Bothplugs_normal calib successful
<!-- Author: Svenja  x2080 -->


<!-- Date: Mon Jul 11 11:19:53.621 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200807">200807</A>
ACTIVATE: RunSet: BOTHPLUGS_MM_C 
<!-- Author: Svenja  x2080 -->


<!-- Date: Mon Jul 11 11:21:03.824 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200807">200807</A>
TERMINATE: Bothplugs_MM_C calin successful
<!-- Author: Svenja  x2080 -->


<!-- Date: Mon Jul 11 11:22:08.407 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200808">200808</A>
ACTIVATE: RunSet: BOTHPLUGS_MM 
<!-- Author: Svenja  x2080 -->


<!-- Date: Mon Jul 11 11:23:52.060 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200808">200808</A>
TERMINATE: Bothplugs_MM calib successful
<!-- Author: Svenja  x2080 -->



<!-- Date: Mon Jul 11 11:36:12.927 2005 -->
No network access to the outside world. Stephan Lammel informed the network guys in CD they are working on the problem. We have no estimate yet for how long it will take.
<!-- Author: Beate -->
<!-- Comment: Mon Jul 11 11;51;08 comment by...Beate -->
Network seems okay again.
<!-- Date: Mon Jul 11 11:42:02.184 2005 -->
Access is over. 
<!-- Author: Beate -->





<!-- Date: Mon Jul 11 12:59:37.694 2005 -->
Silicon Cooling Alarm.  Silicon experts here & cooling experts paged by sci-co.
<!-- Author: Greg -->
<!-- Comment: Mon Jul 11 13;07;34 comment by...Greg -->
Both SVX & L00 cooling alarms were on - and the iFix SVX Cooling System indicated a compressor was turned off.  
<!-- Comment: Mon Jul 11 13;11;06 comment by...Greg -->
The alarms have cleared (lights are back "on") and the compressor is now turned on in the iFIX display.
<!-- Comment: Mon Jul 11 13;46;38 comment by...Jennifer :-), Ulrich H. -->
Greg's observation is correct. The silicon power supplies were switched off by a compressor trip in the SVX chiller. We switch it on again and wait for the temperatures to stabilize. More details can be found 
<a href=
'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=257&frame=2&anchor=13:43:27'>
here</a>.
<!-- Date: Mon Jul 11 13:01:51.067 2005 -->
<pre>Although network access offsite is restored, there is a 
serious problem with networking to village. Note that this 
may make some of our support (pager carriers etc) have to 
drive to CDF to work on problems. 
 
Date: Mon, 11 Jul 2005 12:22:56 -0500 
From: Luz Jaquez <ljaquez@fnal.gov> 
To: PPD_ALL_HANDS@FNAL.GOV 
Subject: Network outage to the village! 
 
 Hello, 
 
I've just been informed by Data communication group that the network fiber 
between FCC and the village has been cut by a trencher.  There current 
estimate for repair is 1 to 2 days. 
 
Allen</pre>
<!-- Author: jj -->


<!-- Date: Mon Jul 11 13:06:31.322 2005 -->
We got a COT heartbeat alarm. It cleared within half a minute or so.
<!-- Author: Svenja -->
<!-- Comment: Mon Jul 11 13;08;02 comment by...Greg -->
again


<!-- Comment: Mon Jul 11 13;11;29 comment by...Greg -->
again
<!-- Comment: Mon Jul 11 13;13;24 comment by...Greg -->
again
<!-- Comment: Mon Jul 11 13;16;11 comment by...Greg -->
again
<!-- Comment: Mon Jul 11 13;24;12 comment by...Greg -->
again
<!-- Comment: Mon Jul 11 13;27;20 comment by...Greg -->
again
<!-- Comment: Mon Jul 11 13;33;08 comment by...Greg -->
again
<!-- Comment: Mon Jul 11 13;38;29 comment by...Greg -->
again
<!-- Comment: Mon Jul 11 13;49;43 comment by...Greg -->
again
<!-- Comment: Mon Jul 11 14;11;35 comment by...Greg -->
again
<!-- Comment: Mon Jul 11 14;18;02 comment by...Greg -->
again
<!-- Comment: Mon Jul 11 14;20;37 comment by...Greg -->
again
<!-- Date: Mon Jul 11 13:08:25.279 2005 -->
<table border=0><td><tr><td bgcolor=#e0e030><pre>Having problems with the cdfonprd run database --  
please do not start any applications for now... 
No RunControl, cardEditor, etc. 
 
Fix in progress...    
 
</pre></td></tr></td></table>
<!-- Author: W.Badgett -->







<!-- Date: Mon Jul 11 13:25:53.321 2005 -->
I am not sure if it has already been turned off, but the wireless system was plugged in during the access.
<!-- Author: m mattson -->





<!-- Date: Mon Jul 11 13:42:15.752 2005 -->
<table border=0><td><tr><td bgcolor=#e0e030><pre>Apologies for the database hang-up -- we will  
probably have to "bounce" the database (shutdown  
and restart) to fix the problem. 
 
Please standy by... 
</pre></td></tr></td></table>
<!-- Author: W.Badgett -->




<!-- Date: Mon Jul 11 13:57:27.710 2005 -->
MCR called: they are going to inject some beam.. There is still no stack at all though. So, it's gonna be a while until we take data.  
We are currently still having problems with the DB and this is being worked on. Currently we cannot do much.
<!-- Author: Beate -->


<!-- Date: Mon Jul 11 14:08:33.469 2005 -->
<center><a href='/cgi/elog/elog.pl?nb=2005&action=view&page=-11781&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/elog.pl?nb=2005&action=view&page=-11781' width='300'></a><a href='/cgi/elog/elog.pl?nb=2005&action=view&page=-11782&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/elog.pl?nb=2005&action=view&page=-11782' width='300'></a><a href='/cgi/elog/elog.pl?nb=2005&action=view&page=-11783&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/elog.pl?nb=2005&action=view&page=-11783' width='300'></a></center>
<!-- Author: Steve Hahn -->
<!-- Comment: Mon Jul 11 14;09;42 comment by...W.Badgett -->
Ignore this posting -- the problem was not with 
Icicle, but on the database side.

<!-- Comment: Mon Jul 11 14;12;14 comment by...Steve Hahn -->
<p>Errors associated with ICICLE dying and generating heartbeat
alarm on VNODE1.  This is more as an excercise for the aces: I
used ALT-PRINT SCREEN and Paint to save these as GIF files and
then inserted them into the e-log.  Note I have the debug 
message, the error message, and where the ICICLE log stopped--all useful information.  However, it turned out the culprit
was Bill, who has somehow crashed CDFONPRD; this disagreed with
ICICLE in the extreme.</p>
<!-- Comment: Mon Jul 11 14;19;59 comment by...W.Badgett -->
I hereby rescind my "Ignore this posting" directive.
<!-- Date: Mon Jul 11 14:08:54.174 2005 -->
<table border=0><td><tr><td bgcolor=#e0e030><pre>Estimate about 20 minutes for database to come  
back... 
 
</pre></td></tr></td></table>
<!-- Author: W.Badgett -->






<!-- Date: Mon Jul 11 14:18:12.821 2005 -->
The cdfonprd database is being restarted now...  
<!-- Author: W.Badgett -->


<!-- Date: Mon Jul 11 14:18:33.759 2005 -->
<p>The other continuing problem is heartbeat alarms from COT1 
on VNODE1.  I've been trying to run both the network status  
display and the task manager networking display in the hopes of 
catching something, but it's been inconclusive at best.  It  
appears that the networks used bandwidth on VNODE1 may increase 
from 0.5-1.0% to up to 2.0% very briefly during these occasions. 
This certainly doesn't provide an explanation.</p> 
<p>Another thing 
I notice on the network display is that VNODE1 keeps trying to 
connect to CDFS6, and seems to succeed momnetarily at which 
point the bandwidth goes down from 1.0% to 0.5% or less, on a 
pretty regular basis.  I thought CDFS6 was a spare; I'm not even 
sure if we're using it.  I will look into this.</p>
<!-- Author: Steve Hahn -->
<!-- Comment: Mon Jul 11 14;54;59 comment by...Steve Hahn -->
<p>Just had a long and interesting talk with Mark Knapp.  Today
he and Jim Loskot have been looking into the issue of "network
timers"--apparently, the equivalent of heartbeats at the iFIX
system level.  iFIX documentation states these should be the
same on every node, but they found them different on each CDFS*
node.  They have now set them all the same, and several false
alarms and unfilled data field problems have gone away.  They
want to keep it this way for a while and make sure the situation
is improved and not degraded.  However, if this pans out, it 
means we should also change these setting on <b>every</b> iFIX
node (which requires bringing down iFIX on each node).  Again,
it may result in much better response.</p>
<!-- Date: Mon Jul 11 14:22:29.610 2005 -->
<table border=0><td><tr><td bgcolor=#e0e030><pre>The CDF online production database is back up!  (woo-hoo) 
 
Please resume your normal activities!</pre></td></tr></td></table>
<!-- Author: W.Badgett -->

<!-- Date: Mon Jul 11 14:29:10.333 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200820">200820</A>
ACTIVATE: RunSet: ACE_TOF_QIE_NEW 
<!-- Author: Svenja x2080 -->


<!-- Date: Mon Jul 11 14:29:11.724 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200820">200820</A>
TERMINATE: TOF QiE calib successful
<!-- Author: Svenja x2080 -->


<!-- Date: Mon Jul 11 14:30:48.051 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200821">200821</A>
ACTIVATE: RunSet: SMQIECALIB 
<!-- Author: Svenja x2080 -->


<!-- Date: Mon Jul 11 14:32:31.800 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200821">200821</A>
TERMINATE: SMX QIE calib successful
<!-- Author: Svenja x2080 -->


<!-- Date: Mon Jul 11 14:34:14.037 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200822">200822</A>
ACTIVATE: RunSet: ACE_LED_ALL 
<!-- Author: Svenja x2080 -->


<!-- Date: Mon Jul 11 14:35:04.541 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200822">200822</A>
TERMINATE: CEM LED calib successful
<!-- Author: Svenja x2080 -->



<!-- Date: Mon Jul 11 14:35:04.373 2005 -->
<pre>The problem with the database happened immediately  
after a rundb "schema cut" -- added two columns  
to RUNSETS table IGNORESVT and IGROREXTRP for the L2 pulsar  
trigger bypass system.    For some reason after cut,  
the RUNDB package of stored database procedures could  
not be recompiled.   The DBAs do not understand why  
this happened...</pre>
<!-- Author: W.Badgett -->

<!-- Date: Mon Jul 11 14:37:40.835 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200823">200823</A>
ACTIVATE: RunSet: COTCALIB_ACE 
<!-- Author: Svenja x2080 -->


<!-- Date: Mon Jul 11 14:37:42.938 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200823">200823</A>
TERMINATE: COT calib successful
<!-- Author: Svenja x2080 -->



<!-- Date: Mon Jul 11 14:38:45.388 2005 -->
I made some small modifications in the L2 control and decision nodes, which I hope will reduce (or remove) the rate at which that system reports errors (as seen by the l2ctrl client turning red).  
<!-- Author: Daniel Whiteson -->

<!-- Date: Mon Jul 11 14:39:55.773 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200824">200824</A>
ACTIVATE: RunSet: XEF_ALL 
<!-- Author: Svenja x2080 -->


<!-- Date: Mon Jul 11 14:41:06.199 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200824">200824</A>
TERMINATE: CEM XEF calib successful
<!-- Author: Svenja x2080 -->



<!-- Date: Mon Jul 11 14:41:06.428 2005 -->
<pre>The fer (FrontEndReadout and RunControl) package has  
ascended to version v3_95, and rundb package to v2_3n. 
The changes are: 
 
   . Add XTC2 testing functionality to the TDCTest run type --  
     provided by Matthew Jones 
 
   . Add support for the SVT and XTRP bypass system for  
     two L2 pulsar b0l2de01 crate cards 
 
Note there are two new expert options in the RunSettings  
window: 
 
     IgnoreXtrp   =  if checked, L2Pulsar bypasses XTRP info 
     IgnoreSvt    =  if checked, L2Pulsar bypasses SVT info 
 
Also there is a facility in the hdwdb, CARDS.CLKMODE  
field -- which can "permanently" disable the XTRP and SVT  
paths, if necessary. 
 
</pre>
<!-- Author: W.Badgett -->
<!-- Comment: Mon Jul 11 14;41;57 comment by...W.Badgett -->
<pre>Also:  The new test summary bank XTCC now works , although 
it still appears as a generic StorableBank in the event stream, 
rather than XTCC_StorableBank

</pre>

<!-- Comment: Mon Jul 11 15;14;56 comment by...Sakari -->
The SVT and XTRP bypass system is currently feeding a copy L2 crate b0l2pu01. The bypass system and the RunSettings for it will be tested with the copy L2 system.

The RunSettings were correctly enabling/disabling the SVT/XTRP transmitters in b0l2de01.
<!-- Comment: Mon Jul 11 15;37;37 comment by...Ted -->
once this is fully tested in beam, then we can make it also available to the default L2 system (i.e. b0l2pu00).
<!-- Comment: Mon Jul 11 17;10;35 comment by...Sakari -->
Also L2 SVT RX firmware was rolledback one version in the default system (b0l2pu00) to get rid of the errors in the input diagnostics, which were caused by the latest version.
<!-- Date: Mon Jul 11 14:43:20.610 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200825">200825</A>
ACTIVATE: RunSet: CALIB_MUON_ALL1 
<!-- Author: Svenja x2080 -->


<!-- Date: Mon Jul 11 14:43:21.791 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200825">200825</A>
TERMINATE: Muon calib successful
<!-- Author: Svenja x2080 -->


<!-- Date: Mon Jul 11 14:44:28.318 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200826">200826</A>
ACTIVATE: RunSet: TOF_TAC_CALIB 
<!-- Author: Svenja x2080 -->


<!-- Date: Mon Jul 11 14:53:34.256 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200826">200826</A>
TERMINATE: TOF TAC calib successful
<!-- Author: Svenja x2080 -->




<!-- Date: Mon Jul 11 14:57:55.985 2005 -->
<table><tr><td><a href=/elog/notebooks/2005/Mon_Jul_11_2005_Day.145750.ps align=top><img src=/cgi/elog/elog.pl?nb=2005&action=view&page=-11785  align='top'></a></td><td>CAL calibration</td></tr></table>
<!-- Author: staveris -->
<!-- Comment: Mon Jul 11 15;18;52 comment by...m mattson (ADMEM) -->
<br>Was paged about the cal calibrations.  No cause for alarm.  The black entries are noisier than we would like, but still would not harm data quality.  The extra noise is hardware (PMT/base) realated, not read out electronics.
<!-- Date: Mon Jul 11 15:00:02.986 2005 -->
<table><tr><td><a href=/elog/notebooks/2005/Mon_Jul_11_2005_Day.150000.ps align=top><img src=/cgi/elog/elog.pl?nb=2005&action=view&page=-11787  align='top'></a></td><td>CAL calibration QIE</td></tr></table>
<!-- Author: staveris -->
<!-- Comment: Mon Jul 11 15;20;29 comment by...m mattson (ADMEM) -->
<br>The slopes are just over the limit of what shows up in the "bad" list.  That should still be acceptable.  My concern is mostly when the slopes go to zero, or are several error bars away from normal.
<!-- Comment: Mon Jul 11 15;21;23 comment by...m mattson (ADMEM) -->
<br>I was paged about this on Sunday as well.  The slopes are steady, and not getting worse.
<!-- Date: Mon Jul 11 15:04:54.259 2005 -->
<table><tr><td><a href=/elog/notebooks/2005/Mon_Jul_11_2005_Day.150452.ps align=top><img src=/cgi/elog/elog.pl?nb=2005&action=view&page=-11789  align='top'></a></td><td>roman pots calibration problem (?)</td></tr></table>
<!-- Author: staveris -->
<!-- Comment: Mon Jul 11 15;20;28 comment by...Beate -->
Talked to Koji Terashi. He is going to powercylce the crates and see whether that helps.
<!-- Comment: Mon Jul 11 15;42;40 comment by...K. Terashi -->
Powercycled the west alcove crate and did calibration again. Nothing changed unfortunately. The SMD corresponding to the second column seems to have more bad squid channels than before, though the problem is not too bad. We will probably need access to fix it.
<!-- Date: Mon Jul 11 15:09:44.272 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200833">200833</A>
 Activated at 2005.07.11 15:09:32
<!-- Author: RunControl -->


<!-- Date: Mon Jul 11 15:10:11.301 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200833">200833</A>
ACTIVATE: RunSet: ACE_CALORIMETER_MINIMAL  Trigger: SUMET5 [5,622,540] non-quiet time
<!-- Author: Svenja x2080 -->


<!-- Date: Mon Jul 11 15:10:54.137 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200833">200833</A>
 Terminated at 2005.07.11 15:10:28
<!-- Author: RunControl -->


<!-- Date: Mon Jul 11 15:10:55.105 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200833">200833</A>
TERMINATE: monitors not running yet
<!-- Author: Svenja x2080 -->



<!-- Date: Mon Jul 11 15:16:58.268 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200834">200834</A>
 Activated at 2005.07.11 15:16:28
<!-- Author: RunControl -->


<!-- Date: Mon Jul 11 15:16:59.306 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200834">200834</A>
ACTIVATE: RunSet: ACE_CALORIMETER_MINIMAL  Trigger: SUMET5 [5,622,540] 
<!-- Author: Svenja x2080 -->



<!-- Date: Mon Jul 11 15:17:18.295 2005 -->
L2 decision timeout.
<!-- Author: Svenja :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200834' target=_top>200834</a>) -->
<!-- Comment: Mon Jul 11 15;17;41 comment by...Svenja -->
again.


<!-- Comment: Mon Jul 11 15;18;55 comment by...Svenja -->
L2 decision rate had dropped to 0. I issued HRR as the Active button went red in RC

<!-- Comment: Mon Jul 11 15;19;07 comment by...Svenja -->
again

<!-- Comment: Mon Jul 11 15;19;25 comment by...Svenja -->
again



<!-- Date: Mon Jul 11 15:21:16.059 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200834">200834</A>
 Terminated at 2005.07.11 15:21:03
<!-- Author: RunControl -->



<!-- Date: Mon Jul 11 15:21:54.340 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200834">200834</A>
TERMINATE: we were not taking any events and had a lot of L2 decision TO. Resetting the run and doing it again.
<!-- Author: Svenja x2080 -->


<!-- Date: Mon Jul 11 15:26:04.131 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200835">200835</A>
 Activated at 2005.07.11 15:24:35
<!-- Author: RunControl -->


<!-- Date: Mon Jul 11 15:26:05.366 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200835">200835</A>
ACTIVATE: RunSet: ACE_CALORIMETER_MINIMAL  Trigger: SUMET5 [5,622,540] 
<!-- Author: Svenja x2080 -->



<!-- Date: Mon Jul 11 15:26:58.844 2005 -->
iFIX expert J.C. Yun restarted iFIX about 30 minutes ago, and since that time there have been no further COT heartbeat alarms. 
<!-- Author: Greg -->


<!-- Date: Mon Jul 11 15:28:26.383 2005 -->
<table><tr><td><a href=/elog/notebooks/2005/Mon_Jul_11_2005_Day.152822.ps align=top><img src=/cgi/elog/elog.pl?nb=2005&action=view&page=-11791  align='top'></a></td><td>PLUG LASER:TIMING PROBLEM</td></tr></table>
<!-- Author: staveris -->
<!-- Comment: Mon Jul 11 16;42;34 comment by...Min-Jeong -->
Steve Hahn asked me to look into this problem, but this time I am not the person who can diagnose the problem, so I transfer it to Willis and Howard. My first guess is that the problem might be caused by the PLUG Laser calibration system.
<!-- Comment: Mon Jul 11 20;29;31 comment by...Willis -->
The plug laser calibration shift time history indicates the
shift above is for this one run. If this continues, then the
east plug laser timing will be shifted.
<!-- Date: Mon Jul 11 15:29:35.692 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200835">200835</A>
 Terminated at 2005.07.11 15:29:08
<!-- Author: RunControl -->


<!-- Date: Mon Jul 11 15:30:31.844 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200835">200835</A>
TERMINATE: having problems with L2 decision timeouts.
<!-- Author: Svenja x2080 -->



<!-- Date: Mon Jul 11 15:32:59.711 2005 -->
<center><a href='/cgi/elog/elog.pl?nb=2005&action=view&page=-11792&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/elog.pl?nb=2005&action=view&page=-11792' width='300'></a><a href='/cgi/elog/elog.pl?nb=2005&action=view&page=-11793&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/elog.pl?nb=2005&action=view&page=-11793' width='300'></a></center>
<!-- Author: Greg -->
<!-- Comment: Mon Jul 11 15;34;47 comment by...Greg -->
Icicle crashed with the above message.  I was able to restart it with no problem.  

<!-- Date: Mon Jul 11 15:35:12.757 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200836">200836</A>
ACTIVATE: RunSet: CALIB_RP_SMQIE 
<!-- Author: Svenja x2080 -->


<!-- Date: Mon Jul 11 15:35:38.578 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200836">200836</A>
TERMINATE: RP calib successful
<!-- Author: Svenja x2080 -->




<!-- Date: Mon Jul 11 15:38:18.426 2005 -->
<pre>Forgot to mention this earlier:  Had to disable the  
readout of XTC2 mezzanine card on the TDC in slot 12 of  
b0cot19, since it was giving copious configuration errors. 
</pre>
<!-- Author: W.Badgett -->

<!-- Date: Mon Jul 11 15:38:59.058 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200837">200837</A>
 Activated at 2005.07.11 15:38:27
<!-- Author: RunControl -->


<!-- Date: Mon Jul 11 15:39:00.763 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200837">200837</A>
ACTIVATE: RunSet: ACE_CALORIMETER_MINIMAL  Trigger: SUMET5 [5,622,540] 
<!-- Author: Svenja x2080 -->



<!-- Date: Mon Jul 11 15:39:05.680 2005 -->
<table><tr><td><a href=/elog/notebooks/2005/Mon_Jul_11_2005_Day.153902.ps align=top><img src=/cgi/elog/elog.pl?nb=2005&action=view&page=-11795  align='top'></a></td><td>SMX calibration problem</td></tr></table>
<!-- Author: staveris -->
<!-- Comment: Mon Jul 11 16;14;47 comment by...Larry  -->
See next shift for comment
<!-- Date: Mon Jul 11 15:39:52.113 2005 -->
<pre>Note that there is a new crate in the hardware  
database, and available to include in RunControl: 
 
    XFT_FINDER_07  b0xft07 
 
however, this crate is not ready to be used, so unless you  
are an expert, do NOT include this crate in any runs. 
</pre>
<!-- Author: W.Badgett -->


<!-- Date: Mon Jul 11 15:50:58.229 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200837">200837</A>
 Terminated at 2005.07.11 15:50:53
<!-- Author: RunControl -->


<!-- Date: Mon Jul 11 15:51:43.951 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=200837">200837</A>
TERMINATE: trying to include all available crates except silicon to fix L2 problem
<!-- Author: Svenja x2080 -->


<!-- Date: Mon Jul 11 15:55:14.534 2005 -->
<TABLE BORDER=2 CELLSPACING=1 CELLPADDING=1 BGCOLOR=WHITE>
<TR BGCOLOR=YELLOW><TH>Run Number</TH>
<TH>Data Type</TH>
<TH>Physics Table</TH>
<TH>Begin Time</TH>
<TH>End Time</TH>
<TH>Live Time</TH>
<TH>L1 Accepts</TH>
<TH>L2 Accepts</TH>
<TH>L3 Accepts</TH>
<TH>Live Lumi, nb-1</TH>
<TH>GR</TH>
<TH>SC</TH>
<TH>RC</TH></TR>

<TR><TD>Totals</TD>                                                     
<TD> </TD>                                                              
<TD> </TD>                                                              
<TD> </TD>                                                              
<TD>15:55:01</TD>                                                       
<TD ALIGN=CENTER>::</TD>                                                
<TD ALIGN=RIGHT></TD>                                                   
<TD ALIGN=RIGHT></TD>                                                   
<TD ALIGN=RIGHT></TD>                                                   
<TD ALIGN=RIGHT></TD>                                                   
<TD> </TD>                                                              
<TD> </TD>                                                              
<TD> </TD></TR>                                                         
                                                                        
</TABLE>
<!-- Author: End of Shift Report -->



<!-- Date: Mon Jul 11 15:59:02.320 2005 -->
<font color=red>Shift Summary: </font><pre>- no beams: Tevatron had some repairs to do and had lost entire stack. 
                                                                                          
- access work on CMX trips, PEM dead channel and BMU noise: 
   o PEM channel 11 got fixed 
   o CMX trips got further understood and the problem was isolated 
   o BMU noise was too small to be observed. Hope is that the problem 
     will either disappear or to become bad enough such that it can be 
     observed 
                                                                                          
- there was a Silicon cooling alarm due to a problem with the SVX chiller. 
Experts are watching the system. 
                                                                                          
- there was an unexpected downtime of the online database. This lasted for 
just over 1h. It went back to normal then. 
                                                                                          
- Bill Badgett upgraded the fer package to include more functionality 
                                                                                          
- there were frequent heartbeat alarms from the COT. 
                                                                                          
- we did all the calibrations and found some issues: 
 o some issues seen with Roman Pots. But are considered not problematic
 o time shift seen in hadron TDC's east => Min-Jeong Kim is looking into it 
 o SMX calibration being looked into by Mike Lindgren 
                                                                                          
- L2 experts are working on new problem with L2 Time-outs 
                                                                                          
</pre> 
<br><b>End of Shift Numbers</b>
<table><tr><td width=60% align=left>
<b>CDF Run II <p></b>                       
<pre>
Runs                   
Delivered Luminosity   0  
Acquired Luminosity    0  
Efficiency             0
   
</td></tr></table></pre>
<!-- Author: Beate -->