<!-- Title: Day shift. Mon Jul 30, 2001 -->
<!-- SciCo: Craig Blocker -->
<!-- DAQAce: Andras Zsenei -->
<!-- MonAce: Alexei Sedov -->
<!-- CO: Bob Orr -->
<!-- OpManager: Kevin Burkett -->
<!-- Notes: -->
<pre>Shift Plan 
========== 
 
1.  Continue to take data. 
2.  Rob Roser will find a replacement flow transducer 
    for the solenoid. 
3.  Call Jonathan Lewis to work on -1 in trigger DB problem.</pre>


<!-- Date: Mon Jul 30 08:29:25 2001 -->
Paused the run (flying wire).
<!-- Author: Andras :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=121964' target=_top>121964</a>) -->


<!-- Date: Mon Jul 30 08:31:17 2001 -->
<pre>Flying wire.</pre>
<!-- Author: Alexei Sedov -->


<!-- Date: Mon Jul 30 08:33:15 2001 -->
<pre>Our rate is pretty low: around 10 Hz. I guess the trigger  
table was tuned for the luminosities observed at the end of  
the last time we had collisions.</pre>
<!-- Author: Andras :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=121964' target=_top>121964</a>) -->



<!-- Date: Mon Jul 30 09:28:24 2001 -->
Flying wire
<!-- Author: Alexei Sedov -->
<!-- Comment: Mon Jul 30 09;31;52 comment by...Andras -->
<pre>Paused run 121964.</pre>


<!-- Date: Mon Jul 30 10:12:38 2001 -->
2 DTOs from imu00. Second HRR works. 
<!-- Author: Andras :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=121964' target=_top>121964</a>) -->
<!-- Comment: Mon Jul 30 10;14;25 comment by...Andras -->
<pre>It looks like the DTOs from imu00 are correlated with the
CMP trips! Does it make sense???</pre>


<!-- Date: Mon Jul 30 10:16:40 2001 -->
<pre>Several peaks in B0PLOS & B0ALOS. Looked like flying wires but time is wrong and there were 3 of them (peaks). </pre>
<!-- Author: Alexei Sedov -->
<!-- Comment: Mon Jul 30 10;27;46 comment by...Alexei Sedov -->
Also there were CMP trips (COT is on stand by all the time).


<!-- Date: Mon Jul 30 10:29:31 2001 -->
<pre>Flying wire.</pre>
<!-- Author: Alexei Sedov -->
<!-- Comment: Mon Jul 30 10;31;47 comment by...Andras -->
<pre>Run 121964 paused.</pre>


<!-- Date: Mon Jul 30 10:45:26 2001 -->
<pre>This morning (around 8:45 am), cdfsoftb0 release is switched to 
the new release, 3.18.0int3b.  SVXMon has a problem getting  
started, but others seem to be ok.</pre>
<!-- Author: Kaori -->
<!-- Comment: Mon Jul 30 11;42;15 comment by...Hartmut -->
<pre>The SVXMon startup problem is fixed.</pre>
<!-- Date: Mon Jul 30 11:01:57 2001 -->
<pre>Beam is lost. Everything is on stand by.</pre>
<!-- Author: Alexei Sedov -->
<!-- Comment: Mon Jul 30 11;10;27 comment by...Alexei Sedov -->
<pre>I tried to put CMU in "stand by" several times but only 4-th or 5-th attempt was successful.  </pre>
<!-- Date: Mon Jul 30 11:02:08 2001 -->
<pre>Stopped the run because MCR is planning to end the store. 
We got 376519 events.</pre>
<!-- Author: Andras :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=121964' target=_top>121964</a>) -->




<!-- Date: Mon Jul 30 11:45:50 2001 -->
Cal QIE - Run 121974  
Some warnings about Raw ped low or Sigma high and the following:  
      <br>
(MLE) b0wcal03:Readout_Calib:11:23:55 AM->ADMEM=19 QIE=5 Fail 14: Sigma(off) big      (4.3691316) (0) (1)  <br>
(MLE) b0ccal00:Readout_Calib:11:23:58 AM->ADMEM=20 QIE=12 Fail 14: Sigma(off) big      (1.1948838) (0) (0) 
      <br>
The consumer did not want to finish (and the log file was not 
 finished). Stopped it manually after 10 minutes. The log file 
was terminated and looked reasonable. The data made it to the 
database.  
<!-- Author: Andras :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=121974' target=_top>121974</a>) -->


<!-- Date: Mon Jul 30 11:50:03 2001 -->
<pre>Redid Cal QIE. This time I was patient enough to wait for the 
consumer to finish (15 minutes!!!!). Consumer log file looks 
OK. The RC logfile contains: 
 
(MLE) b0ccal08:Readout_Calib:11:34:31 AM->ADMEM=20 QIE=2 Fail 14: Sigma(off) big      (1.2928035) (3) (1)  
 
(MLE) b0ccal06:Readout_Calib:11:34:30 AM->ADMEM=16 QIE=13 Fail 14: Sigma(off) big      (1.6051589) (3) (0) 
</pre>
<!-- Author: Andras :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=121977' target=_top>121977</a>) -->


<!-- Date: Mon Jul 30 12:09:19 2001 -->
Had couple COT heart beat alarms. Experts are working.
<!-- Author: Alexei Sedov -->


<!-- Date: Mon Jul 30 12:09:50 2001 -->
<pre>SMXQIE calibration ok (consumer log file, rc log file look ok, 
data made it to the database). This consumer was pretty slow 
as well. This is bad because MCR has informed us that they are  
starting their studies so the quiet time is ending...</pre>
<!-- Author: Andras :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=121982' target=_top>121982</a>) -->


<!-- Date: Mon Jul 30 12:20:25 2001 -->
<pre>TOF calibration. On the web page it says that b0wcal00,b0wcal01, 
b0wcal03, b0wcal04, b0wcal05, b0wcal07 will have error  
messages that are known, but I saw b0wcal02 and b0wcal06 as 
well!: 
 
(MLE) b0wcal02:Messenger:12:12:41 PM-&gt;QIE calibration failed 
(b0wcal02) QIE calib: slot 06, qie 08:Warn 10: Slope low          , val 03.0596, cap 0, rng0. 
(MLE) b0wcal02:Readout_Calib:12:12:41 PM-&gt;ADMEM=9 QIE=0 Fail 14: Sigma(off) big      (16.882593) (0) (0) 
(b0wcal02) QIE calib: slot 09, qie 00:Fail 14: Sigma(off) big     , val 16.8826, cap 0, rng0. 
(b0wcal02) QIE calib: slot 09, qie 02:Fail 10: No fitting         , val 00.0000, cap 0, rng0. 
(b0wcal02) QIE calib: slot 09, qie 04:Fail 14: Sigma(off) big     , val 14.6615, cap 0, rng0. 
(b0wcal02) QIE calib: slot 09, qie 06:Fail 14: Sigma(off) big     , val 17.9495, cap 0, rng0. 
(b0wcal02) QIE calib: slot 09, qie 08:Fail 14: Sigma(off) big     , val 14.5848, cap 0, rng0. 
(b0wcal02) QIE calib: slot 09, qie 10:Fail 10: No fitting         , val 00.0000, cap 0, rng0. 
(MLE) b0wcal06:Messenger:12:12:41 PM-&gt;QIE calibration failed 
(MLE) b0wcal06:Readout_Calib:12:12:40 PM-&gt;ADMEM=9 QIE=0 Fail  4: Raw ped high        (465.645) (0) (0) 
(b0wcal06) QIE calib: slot 09, qie 00:Fail  4: Raw ped high       , val 465.6450, cap 0, rng0. 
(b0wcal06) QIE calib: slot 09, qie 02:Fail  4: Raw ped high       , val 432.2600, cap 0, rng0. 
(b0wcal06) QIE calib: slot 09, qie 04:Fail 10: No fitting         , val 00.0000, cap 0, rng0. 
</pre>
<!-- Author: Andras :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=121983' target=_top>121983</a>) -->
<!-- Comment: Mon Jul 30 12;36;29 comment by...Andras -->
<pre>We had to stop the consumer because it is now 20 minutes
that we are waiting for it to finish. The log file does not
look good and we can't see the data in the database.</pre>


<!-- Comment: Mon Jul 30 12;39;24 comment by...vaia -->
<pre>The log file indicates that that run never received an event
and of course never made it to teh database.
That is why we tried a new run which aparently
works. </pre>
<!-- Date: Mon Jul 30 12:38:59 2001 -->
<pre>Retried the TOF calibration and this time it worked. Log file 
looks reasonable and it made it to the database.</pre>
<!-- Author: Andras :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=121984' target=_top>121984</a>) -->



<!-- Date: Mon Jul 30 13:07:51 2001 -->
<pre>Failed to do muon calibrations. Always getting DTOs before 
finishing. There are also some other messages, like: 
 
(MLE) b0imu00:Messenger:12:56:13 PM-&gt;VISIONread/write failed in slot 20 
57'56" 1 crate/s: b0imu00(80),  Done TO.[RXPT] 
 
Usually DTOs come after that sort of message, but not always. 
I tried to increase the DTO by a factor of 10, but it did 
not help.</pre>
<!-- Author: Andras -->


<!-- Date: Mon Jul 30 13:09:24 2001 -->
<pre>Restarted RC as Arnd requested (to pick up the fix for the 
negative prescales).</pre>
<!-- Author: Andras -->


<!-- Date: Mon Jul 30 13:18:21 2001 -->
<table border=0><td><tr><td bgcolor=#e0e030>Attention! The software event builder default output format has changed from TRYBOS to ROOT. Any calibrations or runs taken with sevb from now on will generate events in that format. 
 
If you find problems with this new version, please let me know (x6593 or pager 630-218-9536 or piccoli@fnal.gov). It's easy to switch back to TRYBOS if that is necessary. 
 
To switch back to TRYBOS one simply has to edit the file $PROXY_DIR/../sevb/RunSoftEvb, and comment/uncomment lines as indicated, stop and start sevb from the proxy window. 
</td></tr></td></table>
<!-- Author: Luciano -->
<!-- Comment: Mon Jul 30 19;35;52 comment by...Tony Vaiciulis -->
<pre>See note in next shift, 19:31. Reverted back to trybos.
</pre>
<!-- Comment: Tue Jul 31 12;36;28 comment by...dan -->
Also, it appears that 2x during the weekend - a DTO happened, perhaps due to high beam losses. If the frequency of DTO becomes an issue I'll remove the card....
<!-- Comment: Tue Jul 31 12;36;58 comment by...dan -->
err disregard this :p

<!-- Date: Mon Jul 30 13:48:09 2001 -->
<pre>Tried to reintegrate SVT and the last four subfarms of Level3. 
Got BTOs after 21 events. We cleaned up L3 and EVB. Afterwards 
the run started ok, but L2 people came and they are taking away 
half of the crates...</pre>
<!-- Author: Alexei and Andras -->


<!-- Date: Mon Jul 30 13:59:31 2001 -->
<pre>To keep RC warm for after-L2-tests-done we started new run with 
what we have (i.e. muons, ccal, wcal, cot, xft, l3, hevb), 
the trigger table is COSMICS_NOTRACKS[3,165]. Run started. 
The rate looks pretty low for a Calib Continuous (L3 nodes 
are cyan and waiting for input...). Strange...</pre>
<!-- Author: Alexei and Andras :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=121995' target=_top>121995</a>) -->
<!-- Comment: Mon Jul 30 14;05;34 comment by...Andras -->
<pre>Finally the Trigger Supervisor Rate window came up and showed
us that we are running at 100Hz. Is it reasonable?</pre>

<!-- Comment: Mon Jul 30 14;08;14 comment by...Andras -->
<pre>Ending the run at 90k events.</pre>


<!-- Comment: Mon Jul 30 15;33;36 comment by...Alexei & Andras -->
<pre>We spent the rest of the run figuring out why it was only 100Hz.
It all came down to the XFT crates (running with everything
except the XFT gave us rates around 380Hz (at the start of a
run!)). Jim Patrick advised us to reboot the culprits. After
rebooting all the XFT crates our rate went up to 310Hz (L3
being limited to 380Hz).</pre>
<!-- Date: Mon Jul 30 14:31:32 2001 -->
<pre>Stopped the run to reboot output Ethernet switch 
on the third floor. 
 
We see two connections to b0l3u04d  on CSL display. 
One of them is dead.   </pre>
<!-- Author: Boris.  -->



<!-- Date: Mon Jul 30 15:37:11 2001 -->
<pre>It looks like that we have taken no run usingthe software 
event builder after we changed its version. 
We tested it past Saturday but we have to make sure 
it is not crashing now. 
Please take a DAQ run using software event builder and some calibration. 
IF you see any problem page me at 218-9500 
and I will try to notify Luciano Piccoli before he leaves for the day. 
 
</pre>
<!-- Author: vaia -->


<!-- Date: Mon Jul 30 15:37:17 2001 -->
<pre>Tony Vaiciulis asked us to restart Run Control to pick up  
some changes...</pre>
<!-- Author: Andras -->


<!-- Date: Mon Jul 30 15:53:19 2001 -->
<pre>Changed RunSectionInterval from 30 to 50 for all  
current Run configurations.  (Per Tony V's orders)</pre>
<!-- Author: W.Badgett -->
<!-- Comment: Mon Jul 30 18;42;13 comment by...Tony Vaiciulis -->
<pre>The bunch crossing trigger in TFRD is currently incremented
every 0.59 seconds. The reformatter previously was declaring
a new run section every 30 increments of the TFRD bunch
crossing trigger counter. This parameter was changed from 30 to
50 to make the time of each run section equal to about 30
seconds (0.59 * 50).</pre>
<!-- Date: Mon Jul 30 16:00:46 2001 -->
<font color=red>Shift Summary: </font><pre>Shift Summary 
============= 
 
BEAM          We inherit a store at 1.5E29 and continue taking data 
              with run 121964.  Ended store and run at 11:00 with 
	      376519 events.  They will do Tevatron studies for two 
	      to three shift and then do a shot sometime tomorrow. 
 
CALIBRATIONS  We got quiet time while they work on a sextupole, so 
              we do calibrations. 
	       
SOLENOID      Rob Roser says that they have replaced the flow transducer. 
              After seeing it is stable for several hours, they ramp 
	      up the solenoid.  It comes to full power and we will 
	      leave it there for now. 
	       
L2            Level 2 people take advantage of the beam down time 
              to continue their studies. 
	    
TRIGGER DB    Jonathan Lewis and Alexei Vargonov sent email that 
              the -1 problem in the trigger DB should be fixed.</pre> 
<br><b>End of Shift Numbers</b>
<table><tr><td width=60% align=left>
<b>CDF Run II <p></b>                       
<pre>
Runs                   121964-122015
Delivered Luminosity   1.46/nb  
Acquired Luminosity    1.33/nb  
Efficiency             91%
   
</td></tr></table></pre>
<!-- Author: Craig Blocker -->


<!-- Date: Mon Jul 30 16:01:08 2001 -->
<pre>Started a new run. Hmm, now the rate is around 220Hz and L3 is 
green, so maybe the last CSL slowed it down?</pre>
<!-- Author: Andras :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=122015' target=_top>122015</a>) -->


<!-- Date: Mon Jul 30 16:01:15 2001 -->
<table><tr><td><a href=/cgi/elog/elog.pl?nb=2001&action=view&page=-1717&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/elog.pl?nb=2001&action=view&page=-1717  width='300' align='top'></td><td>Luminosity summary</a></td></tr></table>
<!-- Author: Alexei Sedov -->


<!-- Date: Mon Jul 30 16:20:52 2001 -->
<table><tr><td><a href=/cgi/elog/elog.pl?nb=2001&action=view&page=-1718&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/elog.pl?nb=2001&action=view&page=-1718  width='300' align='top'></td><td>Losses</a></td></tr></table><font color=red><cite>(entry outside this shift's time range )</cite></font>
<!-- Author: Alexei Sedov -->