Start of Shift Notes:  

Continue taking data through the shift .
 Lum=19E30 and Stack=126E10 

Busy time out for crate b0svx06 associated to error in evb b0eb22. 

From the error log: 
SCPU-P1-E-VrbReadFailed: Error reading  
VRB in slot 16 for event 1898730.VRB_BUS_ERROR:  
Alignment or VME bus error. 
Transferred 0 bytes before the error. 
SCPU-P1-E-EventIdMismatch:  
VRB ID for event 1898731 is 0 instead of 11 (slot 16).

As usual TOF heartbeat alarm appeared 
-> usual procedure 
-> iFix problems 
-> rebooting computer 
-> everything is fine again

The Hourlies

A block of error seen in TrigMon, DCAS vs ADMEM comparison. Paged Carla. She's investigating the problem right now.

The errors occur in a cluster of events in a short range of time. 
All towers involved are in PCAL5. The same problem happened 
about a week ago, and it went away by itself.
It appears to be ok at the moment.
If it comes back, reboot the crate - check with Calorimeter people first.

abort gap losses basically between 15 - 20 kHz

abort gap losses still fluctuate between 15 and 20 kHz

Automatic HRR issued for Done TO in crate b0cot17.  
From the error log: 
(MLE) b0cot17:Messenger:3:36:14 AM->TDC Invalid Header evt 4123342 slot 18: exp/fnd mod 487/487 rol
7/4 l2b 2/2 

(MLE) b0cot17:Messenger:3:36:14 AM->Event 4123342: Bunchcounters in slot 3 (BC=62) and slot 18
(BC=0) disagree (L2B=2) 

same same

Long sequence of L3 REFORMAT ERROR.  
The reformatter rejected total rate is 0.01%. 
The Rejection rate of node 267 chain 1 is 1.  
From the error log: 
Error on L3 node b0l3267 (partition 1) 
Found same CrateId twice! 
CrateId     PartId      EvtId       Tracer Word 
0x00000079  0x00000001  0x0044150b  0x001b0179 


Error on L3 node b0l3267 (partition 1) 
VRB word not consistent with the existing one. 
Bank Name   Bank Type   Default     Faulty 
0x44504d54  0x00000003  0x00000309  0x000000a9 
Error during reformatting! 
Exact position not identifiable! 

4:00 - 5:00 .......

Halt the run since losses are at 20 kHz and MCR is moving the collimator 

abort gap losses touch 20 kHz: 

collimator movement 
-> usual standby procedure

These collimator movements took this time really long - almost 1 hour!!! 
detectors are in on-state again

5:00 - 6:45 : including collimator movements

L3 reformat error from node 267 partition 1 again.  
From the error log: 
Reject rate: 9.181 percent 
VRB word not consistent with the existing one. 
Bank Name   Bank Type   Default     Faulty 
0x44504d54  0x00000003  0x0000720b  0x000000f6 
Error during reformatting! 
Exact position not identifiable! 

6:45 - 7:30: stormy abort gap losses till the end

1) Continue taking data throgh the shift @ L=19E30 with
default table. 


2) 1:20 AM, Co noticed some errors in Trigmon, DCAS vs ADMEM, paged expert. Carla called back, the
errors occur in PCAL5 in a short period time and went away by itself.  


3) 5:40 AM abort gap loss exceeds 20K, called MCR to move the collimator to reduce the loss. After
playing  almost an hour,  

the loss is reduced to 16K. 

4) 6:30 AM Resuming the run.  

5) 7:45 AM, MCR called, they are ready to do separator scan. End the run. Leave CLC on, put COT off
and the rest to standby.  

 

Runs                   179156
Delivered Luminosity   468 nb-1  
Acquired Luminosity    403.4 nb-1  
Efficiency             86.2