<!-- Title: Eve shift. Fri Oct 20, 2000 -->
<!-- Leader: Henry Frisch -->
<!-- Ace: Nancy Lai -->
<!-- Co1: Konstantin Anikeev -->
<!-- Co2: Elena Vataga -->
<!-- Co3: Doug Benjamin -->
<!-- Co4: Dave Toback -->
<!-- Co5: Slaweck Tkaczyk -->
<!-- Notes: -->
<pre>Waiting for shot- detector ready to go (in principle)</pre>


<!-- Date: Fri Oct 20 16:34:26 2000 -->
<pre>Begin a new run after reseting b0cot05. 
SVX reformatter errors are not currently present.</pre>
<!-- Author: patrick :: (run 102065) -->


<!-- Date: Fri Oct 20 17:01:29 2000 -->
<pre>Process to set New COT thresholds : 
To be done after ColdStart and BEFORE Activate. 
ssh cdfdaq@b0dau30 
setcv/setcv -f def 
setcv/setcv cr will display the current thresholds.  
SL1-7 should be 250mv SL8 350mv 
 </pre>
<!-- Author: Dan -->


<!-- Date: Fri Oct 20 17:24:04 2000 -->
<pre>Run 102067: purpose to just run with high (~100 Hz) trigger 
rate as we wait for actual collisions. 
 
We are using COMMISSIONING_ZERO_BIAS (1,58) with  
L3 subfarms 0,1,5,6,7,9,10,11,12 and full crate set.   
 
Got busy condition from svx02 at 35K events.  Try HRR.  Works. 
 
A snapshot of trigger rates: (Count/Average rate(Hz)>/rate(Hz) 
 
Fred: 
 
L1_SUM_ET_10/0		491	7.8	5.5 
L1_JET_PLUG_2/0		5	0.1	0.6 
L1_PHOTON_PLUG		0	0.0	0.0 
L1_2_JET_4/0		1,483	14.8	12.3 
L1_2_JET_4/0		16	0.1	0.3 
L1_MIN_BIAS		0	0.0	0.0 
L1_ZERO_BIAS/5...	6,709,755	47,657.2	47,658.8 
 
Fred Prescaled: 
 
L1_ZERO_BIAS/5...	15,665	98.2	98.4 
 
</pre>
<!-- Author: Nancy :: (run 102067) -->
<!-- Comment: Fri Oct 20 23;02;13 comment by...Nancy -->
<pre>Note: the first "L1_2_JET_4/0" with 1,483 events is the lower
of the di-jet trigger bits and the second is the higher of the
trigger bits.  We are only concerned with the higher-order bit 
because that is the one that actually tells us if we have two
or more objects.  Hence the average rate here is 0.1 Hz.</pre>
<!-- Date: Fri Oct 20 17:45:13 2000 -->
<pre>Accelerator Status: Waiting for shot- also waiting for experts 
to come in to work on Tev. RF PS anode supply. Stack has been 
dwindling - 30 mA at 17:45. 
 
Detector Status:  
COT: All but 6 
Cal: All 
SVX: All 
SVT: All 
Muon: All 
XFT: All 
XTRP: ALL 
L1CAL: All 
L2CAL: All 
Run Config: Early Myron, Partition 0, L3 =58 
 
Plan:  
 
1.Get CLC z information 
2. CLC gate work 
3. CLC Trigger-BC timing 
During 1 an d2, shift runs with COMMISSIONING_ZERO_BIAS (2,58) 
4) COMMISIONING_MIN_BIAS (include CLC crate) tag (2,58) 
5) Create a new trigger for this store (Alexei)) 
6) Run with the new trigger table (a few k events) 
 
</pre>
<!-- Author: Henry -->


<!-- Date: Fri Oct 20 17:54:59 2000 -->
<pre>We are stopping this run to: 
 
1. Do the svx calibration. 
 
2. Test the new Level 3 executable with CdfTracks in Level3 - yay!! 
 
156K events taken.</pre>
<!-- Author: Nancy for Kirsten and Petar :: (run 102067) -->


<!-- Date: Fri Oct 20 17:59:26 2000 -->
<pre>Run 102068: fails because of a failed to pick up tcl error error 
at L3.</pre>
<!-- Author: Nancy :: (run 102068) -->
<!-- Comment: Fri Oct 20 18;08;10 comment by...Nancy -->
<pre>The exact error is:

Partition:0 Run number: 102068 (0x18eb4)
(MLE) b0l3gate2:main:5:56:05 PM->Error on L3 node b0l3gate2
(partition 0) Fri Oct 20 17:56:04 2000 l3proxy
in Config (L3ProxyPartition.cc:1009)
@L3_PACKAGE_FAIL - failed to distribute TCL package
</pre>
<!-- Date: Fri Oct 20 18:05:39 2000 -->
<pre>Run 102069 works!  Only 1K events are needed and after half a  
minute, we stop the run at 3.6K events.  Will do another run 
after changing the chip bitstream (now turning dps on).  This  
run is dps off.</pre>
<!-- Author: Nancy and Petar. :: (run 102069) -->



<!-- Date: Fri Oct 20 18:15:55 2000 -->
<pre>MCR estimates several more hours for shot</pre>
<!-- Author: Henry -->


<!-- Date: Fri Oct 20 18:17:53 2000 -->
<pre>Run 102070: dps on for svx.  2.2K events taken.  Calibration 
is done for the svx.</pre>
<!-- Author: Nancy & Petar :: (run 102070) -->


<!-- Date: Fri Oct 20 18:30:22 2000 -->
<pre>Run 102071: running back with COMMISSIONING_ZERO_BIAS(2,58) 
(actually, it had been switched back to this after the  
"Failed to distribute TCL package" error. 
 
We have the same crate set and the same run configuration  
settings as for 102067.</pre>
<!-- Author: Nancy :: (run 102071) -->


<!-- Date: Fri Oct 20 18:32:50 2000 -->
<table><tr><td><a href=/cgi/elog/elog.pl?nb=2000&action=view&page=-406&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/elog.pl?nb=2000&action=view&page=-406  width='250' align='top'></td><td>One more plot from famous event 2 (run 101978). Et in almost all of the bons is above 100GeV !!! (few more event in this run that we looked at are Ok though)</a></td></tr></table>
<!-- Author: K Anikeev -->


<!-- Date: Fri Oct 20 18:35:49 2000 -->
<table><tr><td><a href=/cgi/elog/elog.pl?nb=2000&action=view&page=-407&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/elog.pl?nb=2000&action=view&page=-407  width='250' align='top'></td><td>This was supposed to be the first picture ... Anyways, this is event #2 from run 101978. This is LEGO plot for ADC counts. Obviously some problem with EventDisplay (Dmitry contacted about it.)</a></td></tr></table>
<!-- Author: K Anikeev -->


<!-- Date: Fri Oct 20 18:39:24 2000 -->
<pre>There are a number of errors that appear on the Error Handler. 
An example error spewed out is
(MLE) b0l3gate2:main:6:24:55 PM->Error on L3 node b0l3023 (partition 0) Fri Oct 20 18:24:54 2000 l3_node 
  in refoInt_reformatProc (l3_refevt.c:584) 
  @L3_REFORMAT_ERROR 
 
RAWREF Error - UTILSILDEC - with code 36 (n= 1,1)  -- START 
 Line  -  288  in File: src/library/rr_rawevt.c 
 Buffer Position: 7981 
 
 Specific Message: 
 Detector ID not known (yet?). 
 
 
 Error location code: 0x00001030 
 
 
 Crate Id?: 0x00000000 
 
 Error during scanning MINI structure! 
 Last Unit prob. worked on (all counts from 0): 
  SCPU: 1 
  VRB : 0 
  LINK: 3 
  MINI: 0 
 
 Event Buffer dump (7961 until posi+2=7983) 
 0x00240423  0x06260725  0x03280027  0x032a0729  0x002c052b  0x05310230 
 0x01350332  0x03370636  0x04390538  0x053f053e  0x00410740  0x00430642 
 0x06480347  0x024b0349  0x054d084c  0x0050034e  0x03520851  0x07570256 
 0x007f0058  0x0000c1c1  0x2c2be3c3  0x012085f9  0x15011000 
 
 
 NOTE: Event is rejected! 
 
RAWREF Error - UTILSILDEC - with code 36 (n= 1,1) -- FINISHED: L<  815 
 
See the error log for more details. 
 
Ivan says that events were rejected due to data rejection  
from a single crate. 
 
</pre>
<!-- Author: Nancy :: (run 102071) -->
<!-- Comment: Mon Oct 23 09;18;34 comment by...SCN -->
<pre>This is a "nibble shift" in a Vrb channel reading out 
B4 wedge East Phi = 2 Layer =3.  

0x2c2be3c3  0x012085f9 -Byte Swap-> c3e32b2c f9852001
Shift Odd Nibbles left 1 Byte    -> e3232bfc 89250001

Probable cause is GLINK SYNCH problem (in turn caused by
CDF CLOCK glitch) clocking out 1/2 bytes too early in the VRB</pre>
<!-- Date: Fri Oct 20 18:46:53 2000 -->
<pre>Working on b0dap19 becomes impossible after a while due to 
TrigMon eating up all memory: 
 
  PID USER     PRI  NI  SIZE  RSS SHARE STAT  LIB %CPU %MEM   TIME COMMAND 
12802 cdfdaq    16   0  618M 206M  3748 R       0 79.0 81.9  19:36 TrigMon 
 
... 
</pre>
<!-- Author: Arnd -->
<!-- Comment: Fri Oct 20 18;55;36 comment by...Arnd -->
<pre>OK, it finally died five minutes later, with about 1 GB used ...</pre>


<!-- Date: Fri Oct 20 19:30:55 2000 -->
<pre>Run 102071: At ~230K events, get  
busy condition from svx02....tried HRR and then 
got done timeout from the same crate.  Tried another HRR  
.... get done timeout again. 
 
The rate was 98Hz before the run ended.</pre>
<!-- Author: Nancy :: (run 102071) -->


<!-- Date: Fri Oct 20 19:39:18 2000 -->
<pre>Run Control died after the busy condition: 
 
SIGSEGV 11 (*) segmentation violation 
... 
 
Restart run control.</pre>
<!-- Author: Nancy :: (run 102071) -->


<!-- Date: Fri Oct 20 19:46:23 2000 -->
<pre>Run 102072: Running with the exact same configuration as for 
run 102071 with a new instance of run control.</pre>
<!-- Author: Nancy :: (run 102072) -->


<!-- Date: Fri Oct 20 19:57:26 2000 -->
<pre>MCR called- TeV RF folks think it's stable enough for a shot- 
say they are starting shot setup. We're running ZERO_BIAS 
while waiting.</pre>
<!-- Author: Henry -->


<!-- Date: Fri Oct 20 20:15:34 2000 -->
<pre>IFIX program was updated with no entry e-log or communication 
with sci-co. Username Kelly was logged into machine. We logged 
the user out and restarted ifix.</pre>
<!-- Author: DB/ST -->


<!-- Date: Fri Oct 20 20:28:23 2000 -->
<pre>Earlier today we updated the calibration bank names of the  
beam loss counters from: 
 
FLAC to FDAC, and FLAP to FDAP 
 
These are now consistant with what is in CDF4152. 
 
Also the channel id for the FDAD bank has been modified. 
 
Changes as requested by Koji Terashi. 
 
</pre>
<!-- Author: Frank Chlebana -->


<!-- Date: Fri Oct 20 20:28:53 2000 -->
<pre>Channel 13 says Tev RF problems NOT fixed now... Hope springs 
eternal, but slowly...</pre>
<!-- Author: Henry -->


<!-- Date: Fri Oct 20 20:31:58 2000 -->
<pre>Run 102072 was ended so that Bill can put in svt 1, 2, and 6, after he loaded the meyera version of fer, which prevents svt 
crates from sending info to the vrb. 
 
Run 102073 has started.  Still running with  
COMMISSIONING_MIN_BIAS (2,58) - the rate is 98.7 Hz.</pre>
<!-- Author: Nancy :: (run 102073) -->


<!-- Date: Fri Oct 20 20:43:20 2000 -->
<pre>Doug Benjamin points us to MCR log: I've added it to the 
Personal Toolbar Folder. Last entry is: 
 
"20:35:17-  The APS repairmen report burnt smells from the supply. John Van Bogaert has been called in, and Mark Champion is also being called again."</pre>
<!-- Author: Henry -->


<!-- Date: Fri Oct 20 21:06:42 2000 -->
<pre>Run 102073: just got a busy condition from svx02 at  
around 140K events.  Did a  
HRR and it successfully recovered.</pre>
<!-- Author: Nancy :: (run 102073) -->
<!-- Comment: Fri Oct 20 21;21;57 comment by...Nancy -->
We have stopped run 102073 so that Arnd can test the change he 
made to the COT11 readout time.
<!-- Date: Fri Oct 20 21:09:40 2000 -->
<pre>For this and previous runs, the readout rate was about 70 Hz, 
with about 25% dead time caused almost completely by the 
readout. It was likely caused mostly by b0cot11 which was 
readout with a delay of 10ms - I changed this to 4ms (still 
very conservative), to have a more realistic load. 
</pre>
<!-- Author: Arnd :: (run 102073) -->



<!-- Date: Fri Oct 20 21:43:58 2000 -->
<pre>Run 102074 begins - the readout rate increased from about 70 Hz 
to about 95 Hz.   
 
What is trigger bit 12?  It is triggering at 0.1 Hz prescaled 
at the moment. It has no name associated with it.</pre>
<!-- Author: Arnd & Nancy :: (run 102074) -->


<!-- Date: Fri Oct 20 22:04:55 2000 -->
<pre>Called MCR: "replacing charred componenents; at least an hour 
before retrying". </pre>
<!-- Author: Henry -->


<!-- Date: Fri Oct 20 22:21:19 2000 -->
<pre>Jean S. set the Silicon Power Supply Control window on b0dap25 
so that we can keep an eye on it.  I will let the owl shift ace 
and psycho know about it, but I put it here as a reminder. 
 
The run 102074 is still going strong (cue image of Energizer 
bunny) .... 314K events now.  Trigger rate of zero bias prescaled 
is 114Hz.</pre>
<!-- Author: Nancy :: (run 102074) -->


<!-- Date: Fri Oct 20 22:28:47 2000 -->
<pre>MCR called- they are calling it quits for tonight. They will 
make a decision tomorrow morning about when the next shot is. 
Sorry...</pre>
<!-- Author: Henry -->


<!-- Date: Fri Oct 20 22:58:40 2000 -->
<pre>Ended Run 102074 so that we can move on to testing other  
trigger tables; we've probably worked the  
COMMISSIONING_ZERO_BIAS table to death by now.  440K events  
taken.  We had 110 items in the run (green "crate" buttons, 
although not all of them are actual crates). 
I think this is a new REAL record.  :)  (I took all of Dan's 
crate settings + 3 svt crates.) 
 
We are starting Run 102075 with the COMMISSIONING_MIN_BIAS (2,58) 
trigger table.  Same crateset as before.  But 102075 ends in 
error from the tsi00 on "Activate".   
 
Try Run 102076.... upon "Activate", the crate b0l1gl00 (PreFred/ 
Fred crate) is deep yellow and the tsi00 and tsi02 and the  
svx crates are light yellow.  The fer crates read out  
"No new event....." all the time.  There are absolutely no  
events.  I think I will try to do another run, but it might be 
a function of the trigger table.</pre>
<!-- Author: Nancy :: (run 102076) -->



<!-- Date: Fri Oct 20 23:06:16 2000 -->
<pre>The global level 1 (Fred/PreFred) crate seems to hang on the  
"Partition" transition.  I see that b0l1gl00 has a corrupt heap. 
I am rebooting it.</pre>
<!-- Author: Nancy :: (run 102076) -->
<!-- Comment: Fri Oct 20 23;12;48 comment by...Nancy -->
<pre>It doesn't respond to a software (VxWorks) reboot - I have 
marched over to the trigger room and hit the Reset button on the
MVME in the crate.</pre>


<!-- Date: Fri Oct 20 23:38:59 2000 -->
<pre>L3 ends in error .... I did all the standard checks and  
everything was ok, but then I stopped and started the L3 proxy 
for good measure (or call it superstition, whatever you will)... 
hopefully it will partition successfully this time.... 
 
Nope - b0l3021 and b0l3023 are dead.  I am cleaning up the  
Level 3 farm.</pre>
<!-- Author: Nancy :: (run 102076) -->


<!-- Date: Fri Oct 20 23:54:57 2000 -->
<pre>Run Control dies.  Started it up again.</pre>
<!-- Author: Nancy -->


<!-- Date: Sat Oct 21 00:01:42 2000 -->
<pre>Despite cleaning up the Level 3 farm, partition still fails  
on L3.
<!-- Author: Nancy -->


<!-- Date: Sat Oct 21 00:02:55 2000 -->
<font color=red>Shift Summary: </font><pre>wing Shift, Thursday Oct 19, 2000 
 
Accelerator Status: Beam studies: they will be coalescing a single bunch 
later in the evening. 63 mA in stack(!); stacking at 3.2 mA/hr. 
Shot setup will begin first thing in the morning; if all went really well 
could be as early as 11am; MCR says 4pm may be more likely. 
 
Detector Status: 
 
COT 01-05, 07-19 
CAL all 
SVX FIB_00,FIB_02,fib_04,fib_06,vrb_svx_00->05, isl_06->08 
Muon: CMU00,CMP00,CMX00,IMU00,IMU01,MUSC00,MUTR00,CMU01 
XFT:DAQ_XFT*_00->05 
XTRP:DAQ_XFT*_XTRP_OO 
SVT: b0svt01,02,06; b0l2de01 
CLC: clc00 
L1CAL00-05 
L2CAL00-05 
L3: Farms 9-12 
 
Plan: 
1) Get CLC z information with CLC in standalone partion, with Lummon running; 
2) Time in CLC gate:  kill losses (sidebands); keep an ey on coinc. rate 
(acnet) 
During 1 and 2 shift runs with COMMISSIONING_ZERO_BIAS 
3) Take  COMMISSIONING_MIN_BIAS run before changing timing 
4) CLC Trigger/BC timing (Carla and Greg) 
5) Take  COMMISSIONING_MIN_BIAS run (include CLC crate) 
6) Create a new trigger for this store 
with  prescales from measured rates (Alexei V.) 
7) Run with new table 
All runs with Early Myron, L3, 58, Partion 0. 
 
Story of the shift- waiting for shot, running COMMISSIONING_ZERO_BIAS (2,58) 
while waiting. Much like United Airlines- flight finally cancelled after 
lots of delays due to equipment. 
 
We conclude sensible thing to do is just to cycle among the triggers on 
the white board; end long run (440K events, 110 items booked), and start 
on MIN_BIAS. Troubles with L3 starting over, as midnight overtakes us 
and Owlies come in. 
 
Accelerator has decided on a meeting tomorrow morning (time not decided) to 
decide what to do next. No shot tonight; schedule unknown until tomorrow's 
meeting. 
 
 
</pre> 
<br><b>End of Shift Numbers</b>
<table><tr><td width=60% align=left>
<b>CDF Run II <p></b>                       
<pre>
Runs                   102065-102076
Delivered Luminosity   0  pb-1
Acquired Luminosity    0  pb-1
Efficiency             100%
   
</td></tr></table></pre>
<!-- Author: Henry -->