2004 CDF E-Log -- Day shift. Sat Feb 14, 2004
SciCo DAQ Ace Monitoring Ace CO (Operations Manager)
Young-Kee Kim Ian Vollrath Alison Lister Jared Yamaoka Mary Convery


Start of Shift Notes:  

Taking data with store 3231. 
Luminosity 25E30. 
Running conditions: 
 * COT SL1,2 off 
 * COT SL3,4,5 lower voltage 
 * XFT SL2 - Masked 
 * XFT SL4 - 3 miss instead of 1 miss 
This store will last anothe ~20 hours.
Sat Feb 14 08:33:07
 - alison
Sat Feb 14 09:34:13
 - alison
Sat Feb 14 10:15:39 Abort Gap Loss increases slowly. It's around 15.5kHz. MCR called. They will move a collimator. - Young-Kee
-- Sat Feb 14 12:06:31 comment by...rainer --  it looks like we have not cycled the HV to standby as in earlier occasions. Did MCR ever give us a 'risk assessment' of the severity of collimator moves, (are there minor and major ones if you can tell beforehand etc.), or is this up to us ? I would advocate to take the silicon to STANDBY in any collimator move until we have a better feeling how safe of a modification of the beam condition this is. my understanding is we are moving steel the beam's way and there is always the possibility of human error (moving the collimator too far in etc). but maybe they do this all the time without us noticing ? I think this needs clarification by ops and standing orders should be developed for shift crew.

until further notice, please put the silicon to STANDBY if collimator moves are announced.
-- Sat Feb 14 12:30:54 comment by...convery --  There were instructions on the white board to put silicon and wire chambers (COT, muons, showermax) to standby for collimator moves, but perhaps it should have been specifically pointed out to the shift crews.
I talked to Ron Moore last week and his feeling was that it is safer to go to standby for collimator moves.
-- Sat Feb 14 12:34:04 comment by...rainer --  OK, thanks. I got a similar impression. the loss of efficency is well invested in Si (and other's) safety.
-- Sat Feb 14 13:02:07 comment by...ian --  

speaking for this shift crew: we were well aware of the instructions on the white board and
intended to put these guys to standby but were instructed by rob roser not to since the collimator
move was at e0, apparently resulting in (virtually) no chance of problems reaching us.

-- Sat Feb 14 13:25:25 comment by...rainer --  I apologize to the shift crew. I guess I need to have a word with mt head of operations.
Sat Feb 14 10:48:04
 - Jared
-- Sat Feb 14 10:52:02 comment by...Jared --  
Some sample event displays made since the COT change.

-- Sat Feb 14 11:40:58 comment by...Larry Nodulman --  So what is the yellow circle in there?
-- Sat Feb 14 12:04:44 comment by...Andrei Loginov --  
Well, I have a guess - could it be XFT hits?
If one could go to the Hit mode and click on these
yellow creatures we would know for sure.

Or just zoom on this region and put another picture.

-- Sun Feb 15 02:28:36 comment by...Cheng-Ju --  Any COT wire that has been masked on in the XFT shows up in the event display as a yellow dot. We have masked on all the wires in SL2 (over 2000 wires). That's why we have a yellow circular band there.
Sat Feb 14 10:48:45 MCR called. They moved a vertical collimater E03V by ~30 mils. The proton abort gap losses went down from 15.5kHz to 9kHz. - Young-Kee
Sat Feb 14 10:52:23
 - alison
Sat Feb 14 11:01:29 
got an evb vrb error: 

Attention!!!. Event Builder SCPU_CANT_RESET_VRB Error !!! 
 THE BAD VRB CRATE is: b0eb16 
 THE BAD VRB MODULE is in SLOT: 10 

halted the run. reset vrb slot 10 of b0eb16. resumed running.
 - ian :: (run 179104)
Sat Feb 14 11:17:56 
evb error: 

Host b0eb15.fnal.gov, task tRec_0 
SCPU-P1-E-VrbHeader: Dump of header words for event 4658918 from VRB in slot 12: 

hrr worked.
 - ian :: (run 179104)
Sat Feb 14 11:40:48 
got a: 

Done Timeout: PCAL_07 

and rc was stuck in halt state. shepherded b0pcal07 successfully. back running.
 - ian :: (run 179104)
Sat Feb 14 11:41:25
 - alison
Sat Feb 14 12:37:18
 - alison
Sat Feb 14 13:11:27
ObjectMon: TrackMonitor. Track Phi Red.
 - Jared
Sat Feb 14 13:32:53
 - alison
Sat Feb 14 14:35:57
 - alison
Sat Feb 14 14:57:43
JpsiMonitor before and after COT change.
 - Jared
-- Sat Feb 14 15:01:01 comment by...Jared --  
EDIT: JpsiMonitor after COT change.
Sat Feb 14 14:59:35
JpsiMonitor before COT change.
 - Jared
Sat Feb 14 15:35:11
 - alison
Sat Feb 14 15:45:55
 - Jared
-- Sat Feb 14 15:49:08 comment by...Jared --  
Left plot 179056 (before). Right plot 179104 (after).
Sat Feb 14 15:55:24
Run Number Data Type Physics Table Begin Time End Time Live Time L1 Accepts L2 Accepts L3 Accepts Live Lumi, nb-1 GR SC RC
179104 x2BBA0 BEAM PHYSICS_2_01 [4,416,424] 05:40:12 09:46:28 534,849,552 8,051,912 1,518,178 798.521 1
Totals 15:55:01 09:46:28 534,849,552 8,051,912 1,518,178 798.521
 - End of Shift Report
Sat Feb 14 15:57:21 Shift Summary: 
Took data with store 3231. 
Luminosity is now 18E30. 
Proton abort gap losses gradually went up to 15kHz.  By moving a collimator, it went to to 9kHz. 
Compared COT tracking resolution with J/psi mass (see e-log).

End of Shift Numbers
CDF Run II 

Runs                   179104
Delivered Luminosity   612.0  
Acquired Luminosity    582.9  
Efficiency             95.2%
 - Young-Kee