<!-- Title: Owl shift. Thu Oct 12, 2000 -->
<!-- Leader: Rick Tesarex -->
<!-- Ace: Peter Wittich, Dave Am -->
<!-- Co1: Antoni Munar -->
<!-- Co2: Jonatan Piedra -->
<!-- Co3: Nigel Lockyer (SOS1) -->
<!-- Co4: Dave Toback (SOS2) -->
<!-- Co5: &nbsp; -->
<!-- Notes: -->
<pre>Continuing run from evening shift (third trigger table from 
run plan): 
 
   Trig Type: COMMISSIONING_A[1,47] 
   SvxSet: (none) 
   TS Flags:  non-Myron 
   Output Type: hdwevb, 1 L3 subfarm (8) 
   CCAL (all), PCAL (all), WCAL (all) 
   CMP00,CMU00,CMX00,IMU01 
   COT 1-3,6-14,16-19 
   XFT 0-5 
 
</pre>


<!-- Date: Thu Oct 12 01:14:07 2000 -->
<pre>During run 101126, YMon started getting: 
 
   Invalid superlayer or wire for this hit (sl 6, wire 12) 
 
and YMON froze and had to be killed.  We don't see any other 
Merlin errors.</pre>
<!-- Author: Dave  :: (run 101126) -->


<!-- Date: Thu Oct 12 01:36:28 2000 -->
<pre><br><b>Solenoid Status:</b> 
<br>At the beginning of the shift, Bob Kephart stopped by and 
gave a summary of the solenoid status.  My notes read as follows: 
<ul> 
  <li>Solenoid cold for couple of days</li> 
  <li>Current in the solenoid ramped up as high as 1000A.</li> 
  <li>Solenoid is off. 
</ul> 
The technicians were working on fixing various minor  
instrumentation problems throughout the day (20+ hrs) and are tired.  Work on the solenoid instrumentation is to resume on the 
day shift. 
<br></pre>
<!-- Author: R.J. Tesarek -->


<!-- Date: Thu Oct 12 01:41:28 2000 -->
<br><b>Control Room HV monitor:</b> 
<br>Began shift with problems in the HV monitor to the right 
of the ACE station;  the GUI display on the upper screen did 
not respond to mouse clicks on the ON-STANDBY-OFF sections  
of the screen.   
<p>Alan Sill and Willis Sakamoto restarted IFix on the NT  
machine and we now get reasonable responses. 
<br>
<!-- Author: R.J. Tesarek -->


<!-- Date: Thu Oct 12 01:50:32 2000 -->
Ended run 101126 after 105142 events.  Bit 15 rate : 5.6 Hz, 
bit 23: 17.2.  Data rate was 22.8 Hz. 
 
<p>Next run will have SVX, SVT and CLC included and switch to Myron mode, no L1 early. 
 
<p> Got a BUSY timeout from the SVT crates 1,2, and 6. Will try to remove SVT. 
 
<p>Appears to work now, run 101128.
<!-- Author: Peter Wittich :: (run 101126,101128) -->


<!-- Date: Thu Oct 12 01:54:50 2000 -->
<p>Timed out in SVX_VRB_02, after 9800 events. Halt-recover-run 
appears to have worked.
<!-- Author: Peter :: (run 101128) -->
<!-- Comment: Thu Oct 12 01;59;56 comment by...Peter Wittich -->
<p>Another timeout, VRB_SVX_02, after 22k events, this time with a reformatter error.  Try another couple of HRRs.  Didn't work that time.


<!-- Date: Thu Oct 12 02:20:21 2000 -->
Remove the SVX for now.  Other run parameters unchanged.  Having problems in the partition stage, so we rebooted the tsi00 crate. Still no luck, so we cleaned the EVB.  Appears to be working now.
<!-- Author: Peter Wittich :: (run 101129) -->
<!-- Comment: Thu Oct 12 02;24;45 comment by...Peter Wittich -->
For run 101129, get busy timeout after 4517 events in 
CMX_WEST_00 crate.  Got a couple of reformatter errors and an "undefined" error. HRR did not work, so we end the run.

<!-- Comment: Thu Oct 12 02;44;05 comment by...dave -->
<pre>Trying to start from scratch: new run control process, cleaned
up evb, rebooted tsi00, and did SYSRESET on muon crates included
above.  Got a timeout during the partition phase, but got to
cold start.  Did abt/reset anyway, logged onto cmx00 to look for
error messages, and retried.  This time we got to cold start.

Started a run successfully, run 101130.</pre>


<!-- Comment: Thu Oct 12 02;57;57 comment by...Peter -->
<pre>Got a BUSY timeout from CMX00 again.  HRR did not work. 
"No New Events" message in CMX00 console.  Removing CMX00 
from the configuration.</pre>
<!-- Comment: Thu Oct 12 03;05;06 comment by...Peter Wittich -->
Got an immediate DONE timeout from PCAL 04 in the next
run.  Reboot. 
<!-- Date: Thu Oct 12 02:52:15 2000 -->
<pre><br><b>MCR:</b> 
<br>MCR phoned to let us know that there will be no beam for 
at least the next 2 hours due to QPM (Quench Protection Monitor) problems. 
<br></pre>
<!-- Author: R.J. Tesarek -->
<!-- Comment: Thu Oct 12 02;55;10 comment by...RJT -->
QPM problem is located at D2.




<!-- Date: Thu Oct 12 03:18:03 2000 -->
<pre>New Run without CMX00.</pre>
<!-- Author: Peter Wittich :: (run 101132) -->


<!-- Date: Thu Oct 12 03:56:28 2000 -->
<br><b>CMP Trip:</b> 
<br>Notice CMP HV trip.  Bring CMP HV back up, first to STANDBY 
then to ON.   
<br> 
<br><font color="0000AA"><b>Comments:</b> 
 <ul> 
  <li>The HV monitor doesn't seem to retain a continuous display  
      of the status for individual detectors (ON, STANDBY, OFF). 
      This would probably be a nice feature.</li> 
  <li>An audio alarm would also be nice to attract the attention 
      of the sleepy owl shift crew.</li> 
 </ul> 
</font> 
<br>
<!-- Author: R.J. Tesarek -->


<!-- Date: Thu Oct 12 03:59:05 2000 -->
<pre>Run 101132 finally died with 176628 events, with a DONE 
timeout on PCAL04.  Tried HHR, but only bot about 20 more  
events, and then froze again.</pre>
<!-- Author: dave :: (run 101132) -->


<!-- Date: Thu Oct 12 04:29:45 2000 -->
<pre>Moving on to calibrations, took QIE run 101133 containing all 
*CAL crates, with following error: 
 
--> pcal00, slot 14, fail 10 (no fitting) 
 
Next, took LED calibration (run 101134).  Get following error: 
 
--> Strange (but not fatal) Run Configuration selections: 
    Not using Error Handler 
 
even though I think I am.  I'm using LED_ALL config.  Run ended 
without any other errors. 
 
Moved onto XEF calibration.  When turning on HV for Xenon, crate 
two, ch 02W drew 0 mA at full voltage (2850V).  On starting run 
(101135), get same error handler message above, but run finishes 
without error. 
 
</pre>
<!-- Author: dave :: (run 101133-101135) -->
<!-- Comment: Thu Oct 12 04;59;43 comment by...dave -->
<pre>Take another QIE run (101136) including the CLC (no beam yet).
In addition to pcal00,slot14 problem above, get the following:

--> clc00, slot 4-8, fail 10 (no fitting)

Run control failed to receive the CLC acknowledgement, although
it did not report any errors.  Logging onto the clc00, we saw:

   Messenger  FER_messenge   e55be0 200 SUSPEND      1692b4
      e55900 3d0004     0
   Readout_CalFER_calib      b96fc0 200 SUSPEND    76650000  
      89ccf8      0     0

Will reboot and try again (run 101137).  Get the following 
(same hanging):

   receive    clcreceive     ea4ef8 200 PEND+T       2759a4  
      ea4ac0      46  1646
   Messenger  FER_messenge   e55d40 200 READY        2759a4  
      e558a8  3d0004     0
   Readout_CalFER_calib      bb3dc8 200 SUSPEND       4afec  
      8b9d30       0     0
   Mon_III    FER_monitorI   ddd370 220 DELAY        27891c  
      ddd2d0       0    43

as well as:

   0xe55d40 (Messenger): Heap Error: 'Internal Inconsistency' 
      at 8b9ef0 (count = 33)

Rebooted CLC, tried to run alone (no *CAL), run 101138, but
same problem.


</pre>


<!-- Comment: Thu Oct 12 11;23;30 comment by...W.Badgett -->
<pre>The Error Handler does not participate in the Run unless 
the box "UseErrorHandler" is checked.   Not a good idea 
to run without the Error Handler.</pre>
<!-- Date: Thu Oct 12 05:13:54 2000 -->
<pre>COT calibration with crates 1-3, 6-14, 16-19.</pre>
<!-- Author: Peter Wittich :: (run 101139) -->


<!-- Date: Thu Oct 12 05:16:32 2000 -->
<table><tr><td><a href=/cgi/elog/elog.pl?nb=2000&action=view&page=-324&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/elog.pl?nb=2000&action=view&page=-324  width='250' align='top'></td><td>TOF pmt readout through CLC electronics; ADC pedestals for  TOF PMT #384. (offline look at Run #11894)  </a></td></tr></table>
<!-- Author: Ivan Furic -->


<!-- Date: Thu Oct 12 05:26:43 2000 -->
Re-tried CLC QIE calibration, first deleting the CLC receiver process from the crate.  Still get the "Internal Inconsistency" error message from the CLC console.  We punt on this for now.	
<!-- Author: Peter Wittich -->


<!-- Date: Thu Oct 12 05:50:22 2000 -->
<p>Start a new run, back to the previous configuration as listed at the beginning of the shift.  Cosmic ray data, no SVX or SVT, CLC included, trigger table COMMISSIONING_A. 
 
<p>Event ID mismatch coming from b0cmx00 (crate 85), as before. 
 
<p>Rick resets the clock, let's try this again...works.
<!-- Author: Peter Wittich :: (run 101141) -->
<!-- Comment: Thu Oct 12 05;57;18 comment by...Peter Wittich -->
Got an "undefined error" in CMX00 after 22K events, which stops
stops the run.  HRR does not work.  Remove this crate, for the 2nd time this evening.

<!-- Comment: Thu Oct 12 06;09;36 comment by...RJT -->
D0 PCC module was found in with a RF lock LED on.  This was the 
situation at the beginning of the shift.


<!-- Date: Thu Oct 12 06:16:02 2000 -->
<p>Next run, without CMX, went for 36 K events until it died (not sure why).  Tried a HRR, at which point I got a BUSY CONDITION from PCAL WEST 04.  Ending the run, start a new one. 
 
<p> A few more "Undefined error" error messsages in the merlin window.
<!-- Author: Peter Wittich :: (run 101143) -->


<!-- Date: Thu Oct 12 06:37:40 2000 -->
Next run again dies with "Unknown error" from PCAL04.  Also getting reformatter errors from COT EAST 19.  Maybe this is the cause.
<!-- Author: Peter Wittich :: (run 101144) -->


<!-- Date: Thu Oct 12 06:50:56 2000 -->
<pre>Started a new run, see if  I can reproduce this error. 
 
</pre>
<!-- Author: Peter :: (run 101145) -->
<!-- Comment: Thu Oct 12 07;05;15 comment by...Peter Wittich -->
<p>Same error, and from the b0pcal04 console, I see the following error message:

<pre>Data size = 4460
TRACER_enableDone: Front End Fatal Error (-1): Tracer done not set
Runtime Error 0, event 37954: Tracer FIFO more than half full 
Got error message through error_q 
</pre>

This must be the "undefined error message" that we see in the merlin window.  As a test, we will remove the PESD_05 bank from this crate and see if that makes a difference.
<!-- Date: Thu Oct 12 06:52:52 2000 -->
<br><b>CMP HV trip:</b> 
<br>Again a HV trip for the CMP.  Reset according to the procedure used last time. 
<br>
<!-- Author: R.J. Tesarek -->



<!-- Date: Thu Oct 12 07:10:45 2000 -->
<pre><br><b>MCR:</b> 
<br>Phoned MCR to get an idea about the status of the work 
underway at D2.  Learn that a Kautzsky valve is being replaced 
under TeV controlled access.  Also apparently Tevatron is  
experiencing compressor problems at C2.  If the Kautzsky work is 
successful, Tevatron may be up later today.  If not, this may 
mean a week down time. 
<br></pre>
<!-- Author: R.J. Tesarek -->


<!-- Date: Thu Oct 12 07:20:16 2000 -->
<p>Started next run, having removed PESD bank from crate pcal04. 
 
<p>This run is now at 70k events.  Removing the PESD seems to have fixed the problem.
<!-- Author: Peter Wittich :: (run 101146) -->
<!-- Comment: Thu Oct 12 07;28;29 comment by...Peter Wittich -->
Busy condition timeout from XFT_FINDER crates 00, 02, 04. 96584 events.  end run.
<!-- Date: Thu Oct 12 07:22:00 2000 -->
Looking at what is going on with calibrations taken this night. 
 
I notice that there are some consumers hanging around 
<pre> 
ps -auux --cols 180 | grep consumers 
 /cdf/code-common/cdfonline/proxy/consumers/Consumers.config cdfdaq   14329  0.0  0.1  2300 1208 ?        S    Oct11   0:00  
csh -f /cdf/people1/cdfdaq/consumers/runCLCDModeConsumer 2 b0dau32 oracle 
 
cdfdaq   14424  0.3 13.6 360036 140952 ?     S    Oct11   1:53 /cdf/people1/cdfdaq/consumers/Linux2-KCC_3_3/CLCDModeConsumer /cdf/people1/cdfdaq/consumers/runCLCDModeConsumer_2.tcl 
 
cdfdaq   16682  0.0  0.1  2300 1212 ?        S    05:24   0:00 csh -f /cdf/people1/cdfdaq/consumers/runQiePed 1 b0dau32 onoci_prd 
 
cdfdaq   16777  0.0  3.5 65732 36712 ?       S    05:24   0:02 /cdf/people1/cdfdaq/consumers/Linux2-KCC_3_3/QiePed /cdf/people1/cdfdaq/consumers/runQiePed_1.tcl 
 
</pre> 
 
Other consumers are just sitting there: 
<pre> 
[stdenis@b0dap30 ~]$ tail ~cdfdaq/consumers/log/runQiePed_1_2000-10-12_05:24:17.log 
level1 bytes 0 -7 : 255 255 255 255 255 255 255 255  
 
exiting APPConsumerInputModule::initIOSystem 
***** 
***** Opened output file: calib.dat 
***** 
 
Entering APPConsumerInputModule::nextEvent 
APPConsumerInputModule::nextEvent :about to request an event 
APPConsumerInputModule::nextEvent :about to receive event 
 
</pre> 
 
 for example is just waiting for events.  i see nothing on the database to indicate the led's were run. 
<p> 
We have seen this before and believe that the problem is that any given event only goes to 3 consumers at most.  If the monitors are running, then there are more than 3 consumers and the calibration consumer has 1 in N chance of failing in this way. 
Hence, it can miss the one event.  Here is an example of what is probably happening when we miss the event: 
<pre> 
[stdenis@b0dap30 ~]$ tail ~cdfdaq/consumers/log/runQiePed_1_2000-10-12_05:24:17.log 
level1 bytes 0 -7 : 255 255 255 255 255 255 255 255  
 
exiting APPConsumerInputModule::initIOSystem 
***** 
***** Opened output file: calib.dat 
***** 
 
Entering APPConsumerInputModule::nextEvent 
APPConsumerInputModule::nextEvent :about to request an event 
APPConsumerInputModule::nextEvent :about to receive event 
</pre> 
<pre> 
[stdenis@b0dap30 ~]$ tail ~cdfdaq/consumers/log/runQiePed_0_2000-10-12_04:09:28.log 
Warning : Returned TSID > 0 
Successfully wrote RAW data for PHAPed 
In writeDB 
Container empty 
ERROR: Could not write RAW data for CLAPed 
Entering APPConsumerInputModule::terminateIOSystem 
Exiting APPConsumerInputModule::terminateIOSystem 
 
 *** Break *** segmentation violation 
Abnormal termination caused by signal: 6 
</pre> 
<p> 
 
<font color=red><b>As an administrative step, we request that the following procedures be followed when a calibration run is done: 
<ul> 
<li> stop all monitoring consumers be stopped before a calibration run: trigmon, ymon, event disply etc. </li> 
<li> make an entry in the elog stating that you have done this</li> 
<li> tail the log file: 
   <ul> 
   <li></font><font color=green>ls -art ~cdfdaq/consumers/log 
        </font><font color=red> 
        The latest log files show up at the end of the list.       
   <li><font color=green>tail -f ~cdfdaq/consumers/log/&lt the file &gt </font><font color=red> and see if you observe that the consumer terminates with some error summaries and no core dumps or "waiting for event". 
    </ul> 
  <li> Look at the run list to see if the calibration made it to the database.  You can get this from the Calibrations item in the ACE help page:<a href="/ops/ace2help/acecalibrations.html"> or by clicking here</a></li> 
   <li>Look at the results with DBANA</li> 
</ul> 
 
 </b></font>  This may help the situation.  </font>
<!-- Author: rick st. denis -->
<!-- Comment: Thu Oct 12 07;39;09 comment by...Rick St. Denis -->
These procedures may be found <a
href="/ops/ace2help/calibration/Overall.html#procedures"> on the ACE help page</a>
<!-- Comment: Thu Oct 12 11;30;53 comment by...W.Badgett -->
<pre>NB: Consumers can be automagically terminated at end of 
run time if the "EndRunTerminate" box is checked in the 
Consumer definition within Run Control.</pre>
<!-- Date: Thu Oct 12 07:30:25 2000 -->
        Here's my nightly list of notes. These are 
either known problems which could probably be added 
to the known problems page, or new things I found  
and don't know what to do with. 
 
 
- Interlock light is broken.  
 
- Slow controls page -> HV summary gives an error  
when pulling up the menu. Is this right?  Same with 
Global alarms? There is a note from Steve about  
database entries being wrong on 10/2. Steve: Is  
this still true? Its not clear what to check here  
still.  
 
- SVX Cooling: Errors in Alarm list. Are these OK? 
Lots of Red on ISL Main Cooling system.  SVX/L00  
Trips (SVX interlock state) :  SVX experts say that 
any alarms (flashing or not red boxes)  in BHW2,  
BHW3, L00W, BHE2, BHE3 can be ignored for the  
commissioning run. BHW1 and BHE1 are Barrel 4 and  
need monitoring. If red or flashing red, contact  
expert. Lots of ISL trips. 
 
- Cryo System:  
 
        CRYO Alarms page has a fair amount of red  
on it. What is the "expert call in list"  
spreadsheet? Are those errors? 
  
        Solonoid cooldown page: Actual Supply  
temperature varies wildly from 53 degrees to 213  
or so. Is this OK? Notes say its supposed to be  
within a few degrees of setting. It's not. Is this 
OK? 
 
 
        Compressor page: LABS  has all **** since  
it's not there. BABS is at 67, the notes say it's  
supposed to be closer to 130. 
 
 
- Flammable Gas menu:  
        02 Analyzer: NWA Disabled?  
        Mixing/Regenerate: 50/50 mixing: Lots of  
Red here ok?  
        Device status: Notebook says for now  
ignore the fact that Compressor #1 and #2 are in  
the alarm state because they are off (also in red). 
Fix this???  
        Mix Shed In: Nitrogen heater being off and 
red a problem? 
 
 
- Racks:  
 
        Tracetek Leak Location: Lots of red with  
Leaks here? Is this ok?  
        Tracetek Controls: Timer disabled and  
Actions bypassed ok? - Water:  
        Alarms: Lots of Red here. Tripped Digital  
alarms. Also WTR_TE81 goes red intermittently.  
        ECW: Pump  6 should be Red?? 
        Chilled Water: Pump 4 and Pump 1 Red? 
        Cooling Pond water: VP-1 should be red? 
        
 
- APACS: Lots of red here. Is this  ok?  
  
<!-- Author: Dave Toback -->



<!-- Date: Thu Oct 12 07:45:56 2000 -->
<pre>Ended run 101147 to add in SVX again.  Run 101148 appears to 
be working.  It is using the COMMISSIONING_A[1,47], but should 
switch to [1,46] (with reconstruction) next.</pre>
<!-- Author: dave :: (run 101148) -->
<!-- Comment: Thu Oct 12 08;07;06 comment by...Peter -->
<p>Run 101148 gets done timeout at 24465 events from COT17.
Tried HRR, got 1 event, then same error.

<p>Mapped crate, saw that slot 11 had dropped out.  did a crate_reset, and now it's back.
<!-- Date: Thu Oct 12 07:57:14 2000 -->
<font color=red>Shift Summary: </font><pre>Owl Shift Summary 
~~~~~~~~~~~~~~~~~ 
Plan: 
 1.  Run with MIN BIAS, 2tower-Et>4, NO BIAS triggers and as much 
     of the detector as possible (Myron Mode). 
 2.  Attempt to run with Muon Trigger  
 3.  Calibrations (QIE, LED, XEF, COT, CLC) 
 4.  Repeat 2 with as large a system as possible. 
 
Execution: 
 Completed 1,3,4.  We were unable to find a configuration which included 
 any muon trigger. MCR phoned early in the evening to inform us of QPM  
 work at D2.  Below is a summary of the problems we ran into on shift. 
    o Muon        - CMP HV tripped twice. No beam. 
    o Calibration - CLC QIE calibration never went to completion. 
                    Calibration process suspended in the crate. 
    o Readout     - Various problem from time-to-time. 
 
   Run     Runtype        Trig Table    # Events     Comments 
  ---------------------------------------------------------------- 
  101126    cosmic      Commission.A    105k    Myron? 
  101128       "             "           22k    Myron? 
  101129       "             "            4k    Myron 
  101132       "             "          176k    Myron 
  101133  QIE calib(Cal)    --           -- 
  101134  LED calib         --           --      Errors (see e-log) 
  101135  XEF calib         --           --      Errors (see e-log) 
  101136  QIE calib(CLC)    --           --      Errors (see e-log) 
  101139  COT calib         --           -- 
  101143    cosmic      Commission.A     ??     Myron 
  101144       "             "           ??     Reformatter errors 
  101145       "             "           37k    Myron 
  101146       "             "           96k    PESD bank removed from pcal04 
  101148    cosmic           "         running  Non-Myron, no reconstr. 
</pre> 
<br><b>End of Shift Numbers</b>
<table><tr><td width=60% align=left>
<b>CDF Run II <p></b>                       
<pre>
Runs                   101126-101148
Delivered Luminosity     pb-1
Acquired Luminosity      pb-1
Efficiency             
   
</td></tr></table></pre>
<!-- Author: R.J. Tesarek -->



<!-- Date: Thu Oct 12 08:12:39 2000 -->
<pre>        Here's my nightly list of notes (third try  
in the log book). These are either known problems 
which could probably be added to the known problems  
page, or new things I found and don't know what to  
do with. 
 
        Here's my nightly list of notes (third try  
in the log book). These are either known problems 
which could probably be added to the known problems  
page, or new things I found and don't know what to  
do with. 
 
 
- Interlock light is broken.  
 
- Slow controls page -> HV summary gives an error  
when pulling up the menu. Is this right?  Same with  
Global alarms? There is a note from Steve about  
database entries being wrong on 10/2. Steve: Is  
this still true? Its not clear what to check here  
still.  
 
 
- SVX Cooling: Errors in Alarm list. Are these OK?  
Lots of Red on ISL Main Cooling system.  SVX/L00  
Trips (SVX interlock state) :  SVX experts say that 
any alarms (flashing or not red boxes)  in BHW2,  
BHW3, L00W, BHE2, BHE3 can be ignored for the  
commissioning run. BHW1 and BHE1 are Barrel 4 and  
need monitoring. If red or flashing red, contact  
expert. Lots of ISL trips. 
 
- Cryo System:  
 
        CRYO Alarms page has a fair amount of red  
on it. What is the 
<!-- Author: Dave Toback -->


<!-- Date: Thu Oct 12 08:13:15 2000 -->
<pre>Did a crate_reset for b0cot17 - the TDC in slot 11 then 
came back.</pre><font color=red><cite>(Entry started on Thu Oct 12 08:13:12 2000)</cite></font>
<!-- Author: Bill Orejudos -->


<!-- Date: Thu Oct 12 08:13:37 2000 -->
<pre> 
        Here's my nightly list of notes (fourth try  
in the log book). These are either known problems 
which could probably be added to the known problems  
page, or new things I found and don't know what to  
do with. 
 
 
- Interlock light is broken.  
 
- Slow controls page -> HV summary gives an error  
when pulling up the menu. Is this right?  Same with  
Global alarms? There is a note from Steve about  
database entries being wrong on 10/2. Steve: Is  
this still true? Its not clear what to check here  
still.  
 
 
- SVX Cooling: Errors in Alarm list. Are these OK?  
Lots of Red on ISL Main Cooling system.  SVX/L00  
Trips (SVX interlock state) :  SVX experts say that 
any alarms (flashing or not red boxes)  in BHW2,  
BHW3, L00W, BHE2, BHE3 can be ignored for the  
commissioning run. BHW1 and BHE1 are Barrel 4 and  
need monitoring. If red or flashing red, contact  
expert. Lots of ISL trips. 
 
- Cryo System:  
 
        CRYO Alarms page has a fair amount of red  
on it. What is the 
<!-- Author: Dave Toback -->