<!-- Title: Eve shift. Wed Nov  1, 2000 -->
<!-- Leader: Jimmy Pr -->
<!-- Ace: Ben K. -->
<!-- Co1: Saverio D'A -->
<!-- Co2: Stefano G. -->
<!-- Co3: Dave T. (SOS) -->
<!-- Co4: &nbsp; -->
<!-- Co5: &nbsp; -->
<!-- Notes: -->
<pre>Organised chaos in progress</pre>


<!-- Date: Wed Nov 1 16:32:32 2000 -->
<pre>Myron mode. 
L2 processors not included. 
Greg is playing with timing. 
Events: 54 K</pre>
<!-- Author: Ben :: (run 102993) -->


<!-- Date: Wed Nov 1 16:33:50 2000 -->
<pre>Beam Shower Counters: 
calibrated ADMEMs in slot 10 and slot 11 of CLC crate. 
All channels are calibrated OK with the exception of: 
Channel 3/Slot 10 
Channel 5/Slot 10 
 
Channel 3 is unused. 
 
It is OK for now.</pre>
<!-- Author: M. Gallinaro, R. Tesarek -->


<!-- Date: Wed Nov 1 16:56:37 2000 -->
SOS noticed that the CMX had an alarm around 4:30PM  using the  
global alrams page on IFIX. There seemed to be a trip on  21  
west. We reset. At 14:50, there are two more trips in 18 and 19 
(flashing red alarm on the CMXDetector.grf) in the east. We 
also periodically see  a sigh  which says 
 
 
"HVMON++  does not seem to be running check the local PC"
<!-- Author: Dave Toback & Kevin Burkett -->


<!-- Date: Wed Nov 1 17:03:40 2000 -->
<table border=0><td><tr><td bgcolor=#e0e030><pre>After many minutes of searching, I have determined at least  
some of the ongoing activities at the start of this shift: 
 
1) Greg et al working on calorimeter L1 trigger timing 
2) CLC experts working on ADMEM calibration (now complete) 
3) COT HV system disabled - Aseet was working on this and distracted. He returned the system to its prior state and will come in in the evning to work on some program development 
4) SVX - experts are working on message passing software (between RC and the Front-end crates) 
5) The solenoid was off (a couple of hours turned into 5) - presently ramping to 4500A and then to 4650A 
6) CMX has tripped twice in the last 45mins and we paged expert</pre></td></tr></td></table>
<!-- Author: J. Proudfoot -->


<!-- Date: Wed Nov 1 17:18:56 2000 -->
<pre>Switch to Asychronous mode on crates: 
all COT, CMU, PCAL 4. 
 
Turn off myron mode. 
 
Tried Reset+Partition -> failed to book any partition. 
Tried ABT+RST+Partition -> failed to book any partition. 
 
Tried ABT+RST+close partition + select partition 
 
okay. 
Events: 1000  
Rate: slow ~ 20 Hz logging 
Stop to get faster table 
</pre>
<!-- Author: Ben :: (run 102994) -->


<!-- Date: Wed Nov 1 17:28:05 2000 -->
<pre>Released L2CAL crates after VME hang-up studies. 
Earlier this morning, Rick and I found out why DCAS towers phi=13, eta=22 and 23 were always giving an energy of 0x3ff:  
the cable was plugged in backward! After fixing the problem, 
we took a quick cosmic run which confirmed that the problem was gone!</pre>
<!-- Author: Monica Tecchio -->


<!-- Date: Wed Nov 1 17:30:44 2000 -->
<pre>Switch to COMMISSIONING_HIGHRATE with 70 instead of 67. 
Much faster - 99 % dead-time 
Using 4 level 3 sub-farms. 
 
Stop run to add more sub-farms -> 14 
 
Bad idea ... 
</pre>
<!-- Author: Ben :: (run 102995) -->


<!-- Date: Wed Nov 1 17:33:21 2000 -->
<pre><pre> 
    At ~17:00 pm CMX wedges 18, 19 East side tripped. 
    They were reset and brought back to their values.  
 
     </pre></pre>
<!-- Author: Abraham Gallas -->


<!-- Date: Wed Nov 1 17:34:48 2000 -->
<table border=0><td><tr><td bgcolor=#e0e030><pre>All RCs are hosed right now due to Trigger DB errors. 
Found Alexei at home and he suggested we set an environmental. 
It doesn't work. 
 
Alexei is on his way here ... 
 
We have been down for 30 minutes due to this problem. </pre></td></tr></td></table>
<!-- Author: Ben -->


<!-- Date: Wed Nov 1 17:39:07 2000 -->
<pre>After we contacted Alexei, he arrived within 10 minutes, and is 
now looking at the problem.</pre>
<!-- Author: Ben -->


<!-- Date: Wed Nov 1 17:47:53 2000 -->
<pre>Following up on the CMX  error: 
 
 
HVMON++ DOES NOT SEEM TO BE RUNNING! CHECK THE LOCAL PC. 
 
 
        Abraham Gallas took a look and said that he said that it 
does seem to be running. He said call JC and  see what the deal 
is. JC said call Margueritte Vittone. We can't seem to get in 
touch with her. Sent mail and called her office</pre>
<!-- Author: Dave Toback -->


<!-- Date: Wed Nov 1 17:54:10 2000 -->
<table><tr><td><a href=/cgi/elog/elog.pl?nb=2000&action=view&page=-491&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/elog.pl?nb=2000&action=view&page=-491  width='250' align='top'></td><td>Results from the SM delay scan:<br> Solid is CPR mmf=1/mmf=2, dashed is CPR mmf=0/mmf=1<br> Dotted is CES wire mmf=0/mmf=1.  No ph in mmf=0 till 66.<br> Scale does not really seem to be ns.</a></td></tr></table>
<!-- Author: Larry N. -->


<!-- Date: Wed Nov 1 17:58:14 2000 -->
data
<!-- Author: {Quick_Entry} -->


<!-- Date: Wed Nov 1 18:02:24 2000 -->
<pre>I just fixed some of the bugs in the online TriggerDB code. 
The code should not have "open cursor" error messages anymore. 
Also if you will get an error "no connection to TriggerDB" 
check that $TRIGGERDB_SID is set to cdfonprd or some other  
valid db instance </pre>
<!-- Author: Alexe Varganov -->


<!-- Date: Wed Nov 1 18:22:00 2000 -->
<pre>COMMISSIONING_HIGH_RATE 67  
Events : 60 K 
Rate   : 230 Hz 
sub-farms: 14 
  </pre>
<!-- Author: Ben :: (run 102996) -->


<!-- Date: Wed Nov 1 18:24:35 2000 -->
<pre>Level 3 transition failed on ColdStart. 
SOme red on the L3 display: b0l3022 is dead. 
 
Clean up L3 
</pre>
<!-- Author: Ben :: (run 102997) -->


<!-- Date: Wed Nov 1 18:33:55 2000 -->
<pre>Same error: 
On L3 Display after ColdStart, the following are red: 
l3014,l3019,l3gate2,l3u02,l3u03. 
 
Also, a large CSL error box popped up saying that events from  
run 102988 could not be logged since it was the same as the 
previous run number. 
 
L3 was paged, and Ivan is looking into it.</pre>
<!-- Author: Ben :: (run 102998) -->


<!-- Date: Wed Nov 1 18:54:52 2000 -->
<pre>Ivan found no problems with Level 3. 
It looked like there was a communication problem between  
processors and output nodes. 
 
It fixed itself.</pre>
<!-- Author: Ben -->


<!-- Date: Wed Nov 1 18:57:00 2000 -->
<pre>Load TS0 only table into smxr "5" in ccal04 (Wedge 14W) 
and into smxr "3" in ccal04 (wedge 15W) as requested by my  
Argonne colleagues this afternoon.</pre>
<!-- Author: J. Proudfoot :: (run 103000) -->


<!-- Date: Wed Nov 1 19:01:14 2000 -->
<pre>DOne TImeout from COT_W_03. 
EVB: Error reading VRB in slot 10 for event 1. 
Doing VISIONDemo readout, we see space in slot 17. 
This gap was not in run configuration so we edit RC config. 
 
ALso do a Bus reset on COT_W_03. 
 
Try again... 
</pre>
<!-- Author: Ben :: (run 102999) -->
<!-- Comment: Wed Nov  1 21;08;37 comment by...Arnd -->
<pre>That's not completely correct: the crate map showed a gap, which
should not be there, so we did a sysreset, and the TDC
recovered.
</pre>
<!-- Date: Wed Nov 1 19:07:52 2000 -->
<pre>Next run attempt: 
b0tsi00 fails to acknowledge PARTITION. 
 
Logging in to b0tsi00, we see : 
TM_reset 0:  
(list of memory errors ) 
 
Had a suspended FER_messenger process. 
 
reset b0tsi00. 
 
 </pre>
<!-- Author: Ben -->


<!-- Date: Wed Nov 1 19:14:18 2000 -->
<pre>I called Randy Keup about the HVMON++ problem. I resynchronized 
the Dimension4 timing on IFix in the control room and on the   
muon  PC downstairs. It seems to be fixed now.</pre>
<!-- Author: Dave Toback -->


<!-- Date: Wed Nov 1 19:33:47 2000 -->
<pre>b0tsi00 activate failed.  
 
Synchronization problem ??? 
 
ABT+COLDSTART  -->  
	Busy condition 
	Warning: there was an event skipped in trigger manager 
 
HRR  -->  
	dumps another 20 events 
 
... 
 
</pre>
<!-- Author: Ben :: (run 103000) -->
<!-- Comment: Wed Nov  1 19;53;44 comment by...Frank Chlebana -->
<pre>

(MLE) b0tsi00:Messenger:6:58:04 PM->TS failed when trying to Run (State 2)

</pre>
<!-- Date: Wed Nov 1 19:34:12 2000 -->
<pre>THe only drastic thing left to do is to 
cleanup the EVB</pre>
<!-- Author: Ben -->


<!-- Date: Wed Nov 1 19:46:14 2000 -->
<pre>Events: 150 K 
L1 trigger rate:  1.7 M Hz min bias 
rate to tape: 340 Hz. 
 
Tried to end run, but it resulted in EVB failure to ack end. 
 
From the EH log file:  
 
(MLE) b0l3gate1.fnal.gov:Sender:7:28:51 PM->End 
(MLE) b0dap15.fnal.gov:AWT-EventQueue-0:7:25:41 PM->Some of the following clients are in error: 
(MLE) b0dap15.fnal.gov:AWT-EventQueue-0:7:25:41 PM->stateManager.inErrorState(): Problems with client /eventBuilder 
(RC) End -> ERROR 
(MLE) b0l3gate1.fnal.gov:main:7:28:52 PM->Host b0eb10.fnal.gov, task tsmHot 
SM-P0-E-ScpuUnresponsive: One or more SCPUs failed to respond to Delete Partition. Check SCRAMNet. 
(</pre>
<!-- Author: Ben :: (run 103002) -->


<!-- Date: Wed Nov 1 19:51:08 2000 -->
<pre>Tried to start a new run but EVB fails to respond. 
Nothing is printed to the EVB scrolling message display. 
 
CLeanup EVB. 
</pre>
<!-- Author: Ben -->


<!-- Date: Wed Nov 1 19:53:18 2000 -->
<pre>CMX  East 18 and 19 tripped again.  I tried to reset twice but 
they tripped again.  Abe Gallas is coming in to take a look.	</pre>
<!-- Author: Dave Toback -->



<!-- Date: Wed Nov 1 19:56:21 2000 -->
<pre>For run  103001 we have the following error messages. 
 
(MLE) b0dau32.fnal.gov:csl_driver:7:00:21 PM->Logger partition 0 is in unknown state: 4. 
 (INITIAL 0,CONNECTED 1,ACTIVE_IDLE 2,ACTIVE 3,COMPLETED 4,BUSY_STATE 5,ERROR_STATE 6)  
 
</pre>
<!-- Author: Frank Chlebana :: (run 103001) -->


<!-- Date: Wed Nov 1 20:01:22 2000 -->
<pre>Added in SVT, L2 decision1 after rebooting. 
 
Changed trigger table to SUM_ET_10, L3: 67  
 
Nice rate: 
288 Hz trigger rate. 
250 Hz logging rate. 
dead-time : 14 %. 
 
Events: 45 K. 
 
Stopped to incorporate CAL changes. 
 
</pre>
<!-- Author: Ben :: (run 103003) -->


<!-- Date: Wed Nov 1 20:08:15 2000 -->
<pre>Silicon cooling trip. While our on-shift experts sorts this out 
we called pager number listed on instructions by SVX alarms. NO response in a few minutes so repeated page.</pre>
<!-- Author: J. Proudfoot -->
<!-- Comment: Wed Nov  1 20;16;01 comment by...J. Proudfoot -->
Jean was on her way here when she received the page


<!-- Date: Wed Nov 1 20:19:02 2000 -->
<pre>Cafe Delays set for CAL did not appear to be updated in RC 
after a PARTITION+COLDSTART. 
 
We restarted to RC to guarantee the mosts recent HDWDB entries. 
 
Is there another way ? Should these changes be able to be picked 
 up on COLDSTART ? How are the timing studies done with  
parameters being changed only before COLDSTART. 
 
 </pre>
<!-- Author: Ben -->
<!-- Comment: Thu Nov  2 12;27;49 comment by...W.Badgett -->
<pre>Normally they should be automatically updated.   However, 
if the SQL-plus user did not commit right away, they may 
have been missed.</pre>
<!-- Date: Wed Nov 1 20:22:01 2000 -->
<pre> Around 19:45 we had a trip in 18, 19 wedges East side.  
 Dave T reset them twice but they still tripped again  
 in the ramping up. We turned them off wait a moment  
 and put them in standby. I reduced the ramping up rate  
 to 30 V/sec for these guys. Meanwhile we got a trip  
 in 21 West, we reset it and now is fine. 
</pre>
<!-- Author: Abraham Gallas, Dave Toback -->


<!-- Date: Wed Nov 1 20:23:24 2000 -->
<pre>Rate: 250 Hz 
SUMET_10 
L3 subfarms: 4 
 
Dead time:  40 %  (64% busy, 34% readout) 
 
 
</pre>
<!-- Author: Ben :: (run 103007) -->


<!-- Date: Wed Nov 1 20:23:56 2000 -->
<pre>TOwer occupancy in West plug looks funny on trigsim.</pre>
<!-- Author: Ben :: (run 103007) -->


<!-- Date: Wed Nov 1 20:35:03 2000 -->
<pre>CAL tests of unmasking previous hot towers continue for 
another tower. 
Events: 35 K</pre>
<!-- Author: Ben :: (run 103008) -->


<!-- Date: Wed Nov 1 20:48:42 2000 -->
<pre>CAL unmasking 
Events: 40 K 
</pre>
<!-- Author: Ben :: (run 103009) -->


<!-- Date: Wed Nov 1 20:49:14 2000 -->
<pre>CAL unmasking 
3 K events</pre>
<!-- Author: Ben :: (run 103010) -->


<!-- Date: Wed Nov 1 21:01:43 2000 -->
<pre>Transition failed for ACTIVATE for /daq/tsi/ts. 
 
From b0tsi00:  
	Sent ack to RC: 0 ERROR ERROR 
	TS failed when trying to RUn (State 2) 
 
Try Abort + COLDSTART + ACTIVATE</pre>
<!-- Author: Ben :: (run 103011) -->



<!-- Date: Wed Nov 1 21:09:26 2000 -->
<pre>On ACTIVATE: 
Busy Condition PCAL W 4 
 
SKipping events problem on b0tsi00: 
 
Here are the messages from b0tsi00 and the EVB: 
 
b0tsi00-> Messenger: processStatechange Config 
Slot  2: 0024 001 TRACER__V2 
Slot  3: 0002 040 TS V2.0@ 
Slot  5: 0000 040 TS V2.0 
Slot  7: 0005 040 TS V2.0  
Slot  9: 0003 040 TS V2.0` 
Slot 11: 0007 040 TS V2.0 
Slot 13: 0006 040 TS V2.0 
Slot 15: 0008 040 TS V2.0 
Slot 17: 0004 040 TS V2.0? 
Slot 19: 0001 042 GL2 V1 
Messenger: processReadoutlist 
Reset TS slot 3 
Sent ack to Run Control: 0 READY SUCCESS 
Messenger: processStatechange Activate 
TM_wrap: ACTIVATE 
p_flag=1 
TM_wrap: call tm_start_flow 0 
Warning! There was an event skip between the event_id 0 and event_id 2 (show 
the last byte of event_id). 
Sent ack to Run Control: 0 ACTIVE SUCCESS 
Warning! There was an event skip between the event_id 1 and event_id 4 (show 
the last byte of event_id). 
Warning! There was an event skip between the event_id 3 and event_id 5 (show 
the last byte of event_id). 
Warning! There was an event skip between the event_id 4 and event_id 6 (show 
the last byte of event_id). 
  
 
EVB: 
----- 01 Nov 2000 20:57:36 CST ----- b0eb10.fnal.gov ----- tsmDisp 
SM--E-CantHearTm: Can't receive from Trigger Manager in SM_Disp_Trigger(). 
 
----- 01 Nov 2000 20:57:42 CST ----- b0eb10.fnal.gov ----- tsmDisp 
SM--E-CantHearTm: Can't receive from Trigger Manager in SM_Disp_Trigger(). 
 
----- 01 Nov 2000 20:57:48 CST ----- b0eb10.fnal.gov ----- tsmDisp 
SM--E-CantHearTm: Can't receive from Trigger Manager in SM_Disp_Trigger(). 
 
----- 01 Nov 2000 20:57:54 CST ----- b0eb10.fnal.gov ----- tsmDisp 
SM--E-CantHearTm: Can't receive from Trigger Manager in SM_Disp_Trigger(). 
 
----- 01 Nov 2000 20:58:00 CST ----- b0eb10.fnal.gov ----- tsmDisp 
SM--E-CantHearTm: Can't receive from Trigger Manager in SM_Disp_Trigger(). 
 
----- 01 Nov 2000 20:58:05 CST ----- b0eb10.fnal.gov ----- tsmDisp 
SM--E-CantHearTm: Can't receive from Trigger Manager in SM_Disp_Trigger(). 
 
----- 01 Nov 2000 20:58:11 CST ----- b0eb10.fnal.gov ----- tsmDisp 
SM--E-CantHearTm: Can't receive from Trigger Manager in SM_Disp_Trigger(). 
 
 
 
Will Try ABT+RST + PARTITION + COLDSTART + ACTIVATE 
</pre>
<!-- Author: Ben :: (run 103012) -->


<!-- Date: Wed Nov 1 21:10:38 2000 -->
<pre>ABT+RST ... worked. 
Events: 10 K</pre>
<!-- Author: Ben :: (run 103013) -->


<!-- Date: Wed Nov 1 21:16:11 2000 -->
<pre>All Crates timed out on ACTIVATE transition. 
 
-> Timed out waiting for r/o list 
... 
... 
... 
</pre>
<!-- Author: Ben :: (run 103015) -->


<!-- Date: Wed Nov 1 21:18:43 2000 -->
<pre>CAL unmasking 
Events:  15 K 
 
Note: This run was started w/ ABT+RST + ...</pre>
<!-- Author: Ben :: (run 103016) -->


<!-- Date: Wed Nov 1 21:19:31 2000 -->
<pre>CAL unmasking: 
10 K events</pre>
<!-- Author: Ben :: (run 103017) -->


<!-- Date: Wed Nov 1 21:20:15 2000 -->
<pre>After a few hours of testing, I am more or less convinced that 
the 'new and improved' asynchronous readout mode is working 
reliably. I made this the default by changing banksets for all 
'slow' crates (COT, muon crates, scalers, cal crates w. SMXR, 
...) to 'asynchronous'. I haven't seen any problems on the 
event builder side. 
 
Also, I reduced the readout delay in TDC crates from 3000 to 
2000. 
 
We ran with a sustained rate of about 340Hz to disk. At 250Hz, 
the dead time was below 15%, when running with 14 L3 subfarms, 
but without Silicon. The logging rate was according to Ben 
23MB/sec, but we didn't do further tests since people were 
(understandably) becoming impatient. 
</pre>
<!-- Author: Arnd -->


<!-- Date: Wed Nov 1 21:21:11 2000 -->
<pre>CAL unmasking: 
3 K events 
</pre>
<!-- Author: Ben :: (run 103018) -->


<!-- Date: Wed Nov 1 21:25:59 2000 -->
<pre>CAL unmasking: 
Events: 6 K</pre>
<!-- Author: Ben :: (run 103020) -->


<!-- Date: Wed Nov 1 21:32:15 2000 -->
<pre>CAL unmasking: 
Events: 7 K</pre>
<!-- Author: Ben :: (run 103021) -->


<!-- Date: Wed Nov 1 21:35:39 2000 -->
<pre>CAL unmasking: 
Events: 3 K</pre>
<!-- Author: Ben :: (run 103022) -->


<!-- Date: Wed Nov 1 21:36:45 2000 -->
<pre>Yet another trip on CMX West 21. This time I was able to reset  
it fine.</pre>
<!-- Author: Dave Toback -->


<!-- Date: Wed Nov 1 21:42:06 2000 -->
<pre>CAL unmasking: 
Events: 30 K</pre>
<!-- Author: Ben :: (run 103023) -->


<!-- Date: Wed Nov 1 21:48:37 2000 -->
<pre>Same routine, but this time error: 
 
b0tsi00 failed to ACTIVATE: 
from b0tsi00, we see: 
 
Messenger: processStatechange Activate 
TM_wrap: ACTIVATE 
p_flag=1 
TM_wrap: call tm_start_flow 0 
Activate Failed 
Sent ack to Run Control: 0 ERROR ERROR 
TS failed when trying to Run (State 2) 
Messenger: processStatechange Abort 
Sent ack to Run Control: 0 IDLE SUCCESS 
Messenger: processStatechange Reset 
TM_reset partition 0 
TM_wrap: END, call tm_stop_partition 0 
p_flag after end 1 
TM_wrap: END  end 
     ts pollster stops ...  partition 0 at slot 3 
 
     RUN SUMMARY: partition 0 
 0 event(s) loaded 
 0 unread event(s) 
 0 DONE Timeout(s) handled 
 0 time(s) flow stopped 
 0 time(s) partition flushed at request of SM 
 0 time(s) partition flushed at request of TM 
 0 event(s)  since last stop flow 
 0 event(s) processed since last stop flow 
 
  
</pre>
<!-- Author: Ben :: (run 103024) -->


<!-- Date: Wed Nov 1 21:49:17 2000 -->
<pre>Yet another 21West CMX trip. I reset and it's ok.	</pre>
<!-- Author: Dave Toback -->


<!-- Date: Wed Nov 1 21:52:36 2000 -->
<pre>CAL unmasking: 
Events:  42 K
 
Notes: 
Tried ABT+RST + PARTITION + COLDSTART --> and worked 
 
On this run, our COs were ramped up again to use YMON. 
 
</pre>
<!-- Author: Ben :: (run 103025) -->


<!-- Date: Wed Nov 1 22:00:49 2000 -->
<pre>Final CAL unmasking (for tonight) 
Events: 25 K 
</pre>
<!-- Author: Ben :: (run 103026) -->


<!-- Date: Wed Nov 1 22:02:22 2000 -->
<pre>Aseet is taking down the COT HV conttrol system to work on 
improving it</pre>
<!-- Author: J. Proudfoot -->


<!-- Date: Wed Nov 1 22:17:08 2000 -->
<br><b>Unmasking Party:</b> 
<br>Sequentially unmasked all but three of the masked EM 
trigger towers.  The CAFE delay was reset to 0 for the above 
unmasking party.  Below is a summary of the results: 
<pre> 
 eta phi cal    date     Who         comment 
------------------------------------------------------------ 
  5   1  PEM  11/01/00  RJT,SR    ADMEM cable (0x080) 
 13   3  CEM  11/01/00  RJT,SR    ADMEM cable (0x3ff) 
  7   4  CEM  08/21/00  CHEF      Bit 5 stuck 
  9  12  CEM  11/01/00  RJT,SR    Bit 3 stuck on. (ADMEM) 
  2  13  PEM  10/17/00  PA,RJT    Initial mask 
  2  14  PEM  10/17/00  PA,RJT    Initial mask 
  3  15  PEM  08/21/00  FC        Unknown. 
 15  18  CEM  11/01/00  PA,RJT    ADMEM cable (0x3ff) 
 13  22  CEM  11/01/00  RJT,SR    ADMEM cable (0x318) 
 19  22  PEM  10/17/00  RJT,SR    ADMEM cable (0x008) 
  9  23  CEM  11/01/00  RJT,SR    ADMEM cable (0x0e7) 
 19  22  PEM  10/17/00  RJT,SR    Hot PMT eta=15,phi=45 (East) 
 12  23  CEM  11/01/00  RJT,SR    ADMEM cable (0x21c) 
</pre> 
During the unmasking we discovered 4 towers which appeared to 
be ok.  These towers remain unmasked: 
<pre> 
  eta   phi 
------------- 
   23    6 
    6   10 
   11   11 
    9   16 
</pre> 
The final DIRAC trigger mask is copied below. 
<pre> 
EM Trigger Towers eta-phi map 
     |P|P|P|P|P|P|C|C|C|C|C|C|C|C|C|C|C|C|P|P|P|P|P|P| 
eta  | | | | | | | | | | |1|1|1|1|1|1|1|1|1|1|2|2|2|2| 
     |0|1|2|3|4|5|6|7|8|9|0|1|2|3|4|5|6|7|8|9|0|1|2|3| 
phi  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
 00  | | | | | | | | | | | | | | | | | | | | | | | | | 
 01  | | | | | |*| | | | | | | | | | | | | | | | | | | 
 02  | | | | | | | | | | | | | | | | | | | | | | | | | 
 03  | | | | | | | | | | | | | |*| | | | | | | | | | | 
 04  | | | | | | | |*| | | | | | | | | | | | | | | | | 
 05  | | | | | | | | | | | | | | | | | | | | | | | | | 
 06  | | | | | | | | | | | | | | | | | | | | | | | | | 
 07  | | | | | | | | | | | | | | | | | | | | | | | | | 
 08  | | | | | | | | | | | | | | | | | | | | | | | | | 
 09  | | | | | | | | | | | | |*| | | | | | | | | | | | 
 10  | | | | | | | | | | | | | | | | | | | | | | | | | 
 11  | | | | | | | | | | | | | | | | | | | | | | | | | 
 12  | | | | | | | | | | | | | | | | | | | | | | | | | 
 13  | | |*| | | | | | | | | | | | | | | | | | | | | | 
 14  | | |*| | | | | | | | | | | | | | | | | | | | | | 
 15  | | | |*| | | | | | | | | | | | | | | | | | | | | 
 16  | | | | | | | | | | | | | | | | | | | | | | | | | 
 17  | | | | | | | | | | | | | | | | | | | | | | | | | 
 18  | | | | | | | | | | | | | | | |*| | | | | | | | | 
 19  | | | | | | | | | | | | | | | | | | | | | | | | | 
 20  | | | | | | | | | | | | | | | | | | | | | | | | | 
 21  | | | | | | | | | | | | | | | | | | | | | | | | | 
 22  | | | | | | | | | | | | | |*| | | | | |*| | | | | 
 23  | | | | | | | | | |*| | |*| | | | | | |*| | | | | 
</pre> 
<br><i>This leaves only 2.4% of the remaining EM trigger 
towers masked.</i> 
<br> 
CAFEDELAY reset to 45ns after unmasking session completed. 
<br>
<!-- Author: R.J. Tesarek, S. Rolli -->


<!-- Date: Wed Nov 1 22:19:28 2000 -->
<pre>Yet another trip in CMX21West. Came back ok.</pre>
<!-- Author: Dave Toback -->


<!-- Date: Wed Nov 1 22:43:36 2000 -->
<pre>Yet another CMX 21West trip that was reset ok.  Paged an expert</pre>
<!-- Author: Dave Toback -->


<!-- Date: Wed Nov 1 22:45:47 2000 -->
Expert said, next ti
<!-- Author: {Quick_Entry} -->


<!-- Date: Wed Nov 1 22:47:14 2000 -->
CMX  expert called. Said, "next time it trips, let it sit off 
for 15 minutes then try resetting again." 
<!-- Author: Dave Toback -->


<!-- Date: Wed Nov 1 23:37:37 2000 -->
<pre>XEF calibration. 
Some trouble selecting and setting ALL voltages on with one switch. 
HOwever, could turn on voltages by half-circle. 
 
</pre>
<!-- Author: Ben :: (run 103033) -->


<!-- Date: Wed Nov 1 23:47:09 2000 -->
<font color=red>Shift Summary: </font><pre>Progress on many fronts.  
Understood CLC/Calor L1 timing issues 
About half of the work needed on masking/unmasking trigger towers 
was done. 
Preliminary work done for plug source scan</pre> 
<br><b>End of Shift Numbers</b>
<table><tr><td width=60% align=left>
<b>CDF Run II <p></b>                       
<pre>
Runs                   102993-103033
Delivered Luminosity   0  pb-1
Acquired Luminosity    0  pb-1
Efficiency             100 !
   
</td></tr></table></pre>
<!-- Author: J. Proudfoot -->


<!-- Date: Wed Nov 1 23:53:50 2000 -->
<p>Xenon calibrations:<br> 
Run 102033 - 444 events<br>Run 102034 - 444 events <br> 
Both run have been technically successfull and are written in the database.<br> 
Both give identical list of channels with no signal:<br> 
 1W eta =2 phi = 1<br> 
 2W ALL CHANNELS<br> 
 7W ALL CHANNELS<br> 
  13W eta = 9 phi = 0 <Br> 
0E eta = 8 phi = 0 -- This is new wrt 10/26, was there on 10/30 May be due to low statistics ?<br> 
6E eta = 1 phi = 0<br> 
7E ALL Channels<br> 
21E eta = 0 phi = 0<br> 
23E eta = 2 phi = 1<br> 
23E eta = 4 phi = 1<br> 
<br> 
Run 103034 has one "noise" hit at 140 percent on 4W PMT 3.<br>  
<!-- Author: Stefano and Saverio :: (run 102034) -->


<!-- Date: Wed Nov 1 23:54:41 2000 -->
<pre>Attempt to do another XEF calibration with new dedicated calibration CSL on b0dap11. 
 
Set CSL to b0dap11 on RC to check. Run works, but I see no  
log files in the CSL log area. Did RC send it to the right one ? 
 
 
 </pre>
<!-- Author: Ben :: (run 103034) -->
<!-- Comment: Thu Nov  2 00;51;27 comment by...mako -->
<pre>No, the events were apparently sent to the CS/L running
on b0dau32...</pre>
<!-- Date: Thu Nov 2 00:01:30 2000 -->
<pre>Did some 2 runs for plug source scans. Setting ADMEM into  
source monitoring mode is integrated into Run Control, but 
this is not the case for the SMQIE's. Therefore I manually set 
bit D11 in the SMXR status register after initialisation (I did 
check that this bit was not later cleared by Run Control). 
We tested using the software event builder, but only saw a rate 
of 50 Hz. therefore, we switched to the Hware event builder and  
checked by logging into the crate that the data taking rate  
was 100Hz. There were several test runs during this. The two 
good runs are 103041 and 103042. Since I have never looked at 
source monitoring data, I make no promises on what is being  
read out of the SMXRs.</pre><font color=red><cite>(Entry started on Thu Nov  2 00:01:26 2000)</cite></font>
<!-- Author: J. Proudfoot -->