Start of Shift Notes:  

Store 3261 (luminosity 2.0E31) and run 179473 (Silicon in, COT in degraded config) in
progress.

trigger inhibit from TOF system (HV bars turned blinking red) 
cleared itself after 30 seconds 
global alarms for TOF shows wrong button description

requested plot by MCR. Rainer and me agree that it looks pretty flat

I have to end the run and reset since c16 subfarm lost tbe monitoring (gold).  
Event funnel crashed on the processor node.

Hourlies (1515-1700)
-in addition to the PAGC spikes a slow rise is also seen

total hits appear to have increased one or two times compared to the reference plots. Is this correct?

same comment, especially layer 3

Automatic HRR issued due to L2 TO, following almost 10 "dumping CLIST data" error. 

I also cheched the suspect (dead/noisy) channels for the IMU, 
this is the layout I have found: 
("-" means that a channel left the list;"+" that it joined it) 
WEST: L0:-1+2	L1:+2	L2:+2	L3:-3+2 
EAST: L0:-1	L1:-1	L2:-2	L3:-2 
so apparently the west detector has 8 'new' suspect channels, 
compared to the reference plots taken about one year ago.

Note that our eLog from previous shift has multiple plots
showing the E0 loss monitor and the correlation. There is some
commonality in the readout system between the CDF abort gap
losses and the E0 variable however. This is why MCR asked for
plot of temperatures in the readout crate.

The proton global phase noise monitor is the first truly
independent variable that proved to the MCR that this is
not an instrumentation problem.

Tevatron expert has identified one more variable that 
correlates with abort gap pulsations. Look at 
T:PGPN (Proton Global Phase Noise) - it can be  
plotted from data logger .Inst2  .  
Ops are contacting TeV RF experts to look further.

Tevatron has turned off the longitudinal dampers to see 
if abort gap oscillation goes away. If no change, TeV will 
turn dampers back on.

I might note that Rick Vidal told me to ask Tevatron to
check state of the longitudinal dampers at 11:30 a.m. this
morning. I did not....

SCPU_TRACER_EVENT_ID_ Error in the Hardware EVB due to FER crate XFT_FINDER_04. Automatic HRR
issued twice.  

Hourlies from 1700-1900
abort gap losses fall slowly

Did abort gap pulsations go away??

Tevatron helix studies: 

ramping down voltages to standby state (except CLC [on] and COT [off]

At the end of the ALPHA clustering test run, rc was stuck and I had to close and restarted it.
For this reason I couldn't select "potentially good run". We tried to mark it good but we were not
allowed.  

Marked Bad, explanation:
SVX  \
ISL   |
L00   | Alpha Clustering Test Run without Silicon
SVT  /

Hourlies (1900-2100)

huge broad spikes are due to the HELIX STUDIES

 
SVX over current trip DVDD, barrel 4 wedge 3 
   - ACE try to reset but gets "Handshake no responds from FIB" 
   - page Silicon, Pete calls back, will login remote to check 
   - BIAS trips too, barrel 4 wedge 3 

I do not currently know when store 3261 will end.
My guess is 

that TeV Run Coordinator will let it go until early Sunday 
morning. However, if store is ended before 0800 Sunday or 
if it terminates itself during owl shift, here is plan. 
(Please pass to owl SciCo and Aces..) 

0) Page Ops if store terminates abnormally. 
1) Do Silicon checkout if appropriate. 
2) Do quiet time and non-quiet time calibrations. 
* D0 has asked for 1 hour controlled access so we 
  should have plenty of quiet time. * (CDF currently 
  has no short access requests.) 
3) Test PHYSICS_HIGHLUM_2_03[1,432,436] with no beam 
   and AAA_SHOTSETUP configuration. Run for 5 minutes, 
   there should be at least 1.7 MHz of MB_XING in the 
   trigger rate but probably nothing else. 
4) Take cosmics while waiting for shot setup. 
5) For next shot setup, page ops when final protons being 
   loaded and Silicon Primary and SPL when pbars start to 
   be loaded. 
6) Start next store with PHYSICS_HIGHLUM_2_03[1,432,436] 
   if it was tested successfully in item #3.

DVDD of B4W3L0 and B4W3L1 tripped 
shortly after that also their bias tripped 

the normal procedure for Si trip recovery DIDN'T work 
paged Si expert - > solved problem (the how is unfortunately secret ;-)

Hourlies 2100-2315

Store 3261 still in progress luminosity dropped from
2.0E31 to 1.?E31 

   - continued data taking with new low lum trigger table (COT in degraded 
      config, Silicon on) 
   - sikes in proton abort gap loss traced by MCR to timing problem with 
      longitudinal dampers 
   - MCR opened helix at 19:00 done about 30 min later 
   - took Alpha Clustering Test data 
   - took Silicon dmode calibrations 
   - resumed data taking with new low lum trigger table (COT in degraded 
      config, Silicon on) 
   - SVX over current DVDD/BIAS trip 
   - plug HV problem 

Plan is to continue data taking until end of store 
   - about 1 hour access after store, no CDF requests 
   - see JJ's owl shift plan above

Runs                   179473, 179474, 179475, 179480
Delivered Luminosity   0.504 fb^-1  
Acquired Luminosity    0.344 fb^-1  
Efficiency             68.2

plug (PEM,PHA,PSH)hardware problems (HV went yellow) and while trying the power cycle procedure
several times we lost communication (HV went grey) 

-> after doing the three recovery steps in the third floor the plug is back to normal!

ending again

the second time did not work because ladders might trip on DVDD first, but the second time it usually works. alternatively, the monitoring ace could have put the whole wedge to OFF and ON as written in the instructions in front of the PSGui computer, as was then finally done. but it is also true that resetting single ladder trips is a faster way - the penalty being that one has to recover maybe twice.  (entry outside this shift's time range ) - Rainer