<!-- Title: Owl shift. Wed Nov  8, 2000 -->
<!-- Leader: Alan Sill -->
<!-- Ace: Giulia Manca -->
<!-- Co1: &nbsp; -->
<!-- Co2: &nbsp; -->
<!-- Co3: &nbsp; -->
<!-- Co4: &nbsp; -->
<!-- Co5: &nbsp; -->
<!-- Notes: -->
<pre>Quiet running.</pre>


<!-- Date: Wed Nov 8 00:23:06 2000 -->
<pre>CMP Bottom D3 Tripped ~00:15.  Reset.</pre>
<!-- Author: K Burkett -->


<!-- Date: Wed Nov 8 00:51:27 2000 -->
<pre>First run with the same trigger table as before   
(COMMISSIONING_COSMIC_ZEROBIAS[1,70]) just to see how 
things go; 
b0cot06 not responding in partition;I took it off to reboot it. 
Run goes smoothly. b0cot11 gives Done TimeOut after 151515 evts, 
HRR doesn't work. 
I stop so I can add also b0cot06 and see if it's working now.</pre>
<!-- Author: giulia :: (run 103821) -->


<!-- Date: Wed Nov 8 01:03:55 2000 -->
<pre>New run started with all the crates we had before; 
(right now). 
Why do I see events in the output nodes before  
activating (respectively 8,8,8,4) ?</pre>
<!-- Author: giulia :: (run 103822) -->
<!-- Comment: Wed Nov  8 01;15;45 comment by...giulia -->
<pre>Few errors in the clc (Bunch counter mismatch);
initial frequency 110 Hz, I notice it's slowly 
decreasing already...Let's see if it gets worse.</pre>


<!-- Date: Wed Nov 8 01:25:38 2000 -->
<table><tr><td><a href=/cgi/elog/elog.pl?nb=2000&action=view&page=-536&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/elog.pl?nb=2000&action=view&page=-536  width='250' align='top'></td><td>This is the decreasing in the events rate after 142k evts; it appears as the rate has been dropped of something  which seems like 12 Hz indeed..</a></td></tr></table>
<!-- Author: giulia -->


<!-- Date: Wed Nov 8 01:44:48 2000 -->
<pre>Each time I open a window form the RC main window it takes ages  
to appear completely and gives a message: 
 
Editing RunSet: GREG_COSMIC_11-2 
Exception occurred during event dispatching: 
java.lang.OutOfMemoryError 
                                               
If I wave the mouse over that, it magically starts to appear  
piece  by piece (where the mouse pass). 
The top commmand  doesn't give any particular reason for such  
a behaviour..(or maybe I haven't noticed):  
here are the first lines: 
 
CPU states: 49.8% user, 50.1% system,  0.0% nice,  0.0% idle 
Mem:  257616K av, 232384K used,  25232K free,  48676K shrd,  16264K buff 
Swap: 652760K av,  46764K used, 605996K free                 58640K cached 
 
  PID USER     PRI  NI  SIZE  RSS SHARE STAT  LIB %CPU %MEM   TIME COMMAND 
23965 cdfdaq    10   0  1124 1124   640 R       0 92.2  0.4  1141m cslmon 
29859 cdfdaq     4   0  1196 1196   932 R       0  2.1  0.4   0:01 top 
 7048 cdfdaq     0   0  1820 1444   276 S       0  1.7  0.5  74:46 cpumon 
30652 csl        0   0 30608  19M  2160 S       0  1.1  7.6  32:57 java 
24271 cdfdaq     0   0 47624  46M  9628 S       0  0.7 18.4   2:42 netscape-commun 
14325 root       0   0 45264  43M  1380 S       0  0.5 17.3 103:28 X 
25964 cdfdaq     0   0 34040  33M  3324 S       0  0.5 13.2   2:57 java 
30879 csl        1   0 19540  12M  1192 S       0  0.3  4.7  16:37 java 
29446 cdfdaq     0   0  4624 4624  3064 S       0  0.3  1.7   0:00 kvt 
    1 root       0   0   124   72    60 S       0  0.0  0.0   0:09 init                        
 
rate seems constant on ~100 Hz now.</pre>
<!-- Author: giulia :: (run 103822) -->


<!-- Date: Wed Nov 8 02:12:45 2000 -->
<table><tr><td><a href=/cgi/elog/elog.pl?nb=2000&action=view&page=-537&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/elog.pl?nb=2000&action=view&page=-537  width='250' align='top'></td><td>Who to ask for money next year.</a></td></tr></table>
<!-- Author: AFS -->


<!-- Date: Wed Nov 8 02:22:59 2000 -->
<pre>I'm trying one run in Early Myron Mode just to see what 
 happens... (table COMMISSIONING_COSMIC_ZEROBIAS[1,71]).</pre>
<!-- Author: giulia :: (run 103823) -->


<!-- Date: Wed Nov 8 03:08:41 2000 -->
<em><font size=+1>Why it's important to cross-check your data from more than one source:</font></em><p> 
<table width=340 bgcolor=#ffffdd cellpadding=4 cellspacing=0 border=0><tr><td valign=top><A name="sidebar"> 
 <font face="geneva, helvetica, arial" size=4 color=#3366CC> 
 <b>Florida Call Goes South</b> 
 </font> 
 <font face="geneva, helvetica, arial" size=2> 
Nov. 7 &#151; In the highly competitive media sweepstakes to project the presidential race, things have sometimes been known to go wrong.<br>&nbsp;&nbsp;&nbsp;&nbsp; 
 
That happened in tonight&#0146;s close race, when a key victory for Al Gore turned, two hours later, into a key uncertainty.<br>&nbsp;&nbsp;&nbsp;&nbsp; 
 
News organizations, including ABCNEWS, called Florida for Gore shortly before 8 p.m. ET, based on exit poll results from the Voter News Service.<br>&nbsp;&nbsp;&nbsp;&nbsp; 
 
&#0147;We are no longer certain of our projection of Florida because we were told by the Voter News Service that there might be problems with the data,&#0148; explained Jeffrey Schneider, director of public affairs for ABCNEWS, close to midnight on Election Night. &#0147;While VNS is re-evaluating that data, we felt it prudent to place Florida back in the &#0145;too close to call&#0146; column.&#0148;<br>&nbsp;&nbsp;&nbsp;&nbsp; 
 
&#0147;It is one of those things that we don&#0146;t like to see happen,&#0148; said Carolyn Smith, ABCNEWS director of elections. &#0147;The key precincts that we rely on to substantiate exit poll data, didn&#0146;t substantiate it the way they should have &#0133; we decided we need to pull back and re-examine all of the data, which is what we&#0146;re doing.&#0148;<br>&nbsp;&nbsp;&nbsp;&nbsp; 
 
VNS, a news consortium that includes ABC, CBS, CNN, Fox, NBC and The Associated Press, processes exit poll data from some 70,000 voters. Early readings of exit polls, which have proven very accurate in past elections, signaled Gore as the winner. <br>&nbsp;&nbsp;&nbsp;&nbsp; 
 
But then word came that some results remained to be counted. That was enough for Texas Gov. George W. Bush, the Republican candidate, to challenge the call.<br>&nbsp;&nbsp;&nbsp;&nbsp; 
 
&#0147;I don&#0146;t believe some of these states that they called, like Florida,&#0148; he said tonight.<br>&nbsp;&nbsp;&nbsp;&nbsp; 
 
Florida&#0146;s 25 electoral votes are critical in this tight race. They likely will determine its winner.<br>&nbsp;&nbsp;&nbsp;&nbsp; 
 
It was not immediately clear what caused the confusion in exit poll counts from the state. ABCNEWS is currently re-evaluating the data.<br>&nbsp;&nbsp;&nbsp;&nbsp; 
 
Mark McKinnon, a senior media consultant for the Bush campaign, says the reversal in calls by news organizations is a serious concern since, he says, it could have discouraged republican voters in Florida too soon and prevented them from casting their votes. He believes the mix-up calls for a reevaluation of the exit-poll system.<br>&nbsp;&nbsp;&nbsp;&nbsp; 
 
&#0147;This is an unfortunate rush to judgement by the media,&#0148; McKinnon said. &#0147;We&#0146;re concerned that rush could have affected the voting in the northern Florida in the panhandle. I think there will be some real serious discussion about this. I hope there will be because it could have literally affected the vote there.&#0148;<br>&nbsp;&nbsp;&nbsp;&nbsp; 
 
GOP consultant Adam Goodman adds that exit polls do not take into account absentee ballots and so are not entirely foolproof. <br>&nbsp;&nbsp;&nbsp;&nbsp; 
 
The Republicans aren&#0146;t the only ones concerned about early misreporting of Florida&#0146;s results. Ed Rendell, the general chairman of the Democratic campaign told ABCNEWS he believes this proves media organizations should refrain from reporting projections until at least 75 percent of voting data is available.  
 
<br>&nbsp;&nbsp;&nbsp;&nbsp;<i>&#151; ABCNEWS.com</i> 
</td></tr></table> 
</font> 
<br>  
<p> 
<em><font color="#ff0000">Try 99.9%...</font></em>                                                                                        
<!-- Author: Your newsreader -->


<!-- Date: Wed Nov 8 03:15:34 2000 -->
<table><tr><td><a href=/cgi/elog/elog.pl?nb=2000&action=view&page=-538&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/elog.pl?nb=2000&action=view&page=-538  width='250' align='top'></td><td>The EVD doesn't show much and the EventBuilder Daqmon  looks like this, but I think I'm using a particular  trigger table, so I stop this run and I try a new one now. (Actually I just got DoneTimeOut from CotEast11, HRR deosn't work, I end the run after 320k events (it was run#103823) </a></td></tr></table>
<!-- Author: giulia -->
<!-- Comment: Wed Nov  8 03;20;02 comment by...giulia -->
<pre>(The gap in the middle is between the tow runs 103822-823)</pre>


<!-- Comment: Wed Nov  8 03;43;24 comment by...Alan -->
The mystery here is why the event rate changes by ~12 Hz either in the down <b>or</b> the up direction, as if something that accoounts for about that much of the total is cutting in and cutting out...<p>
We look through the Merlin displays, L3 info screens, etc. but can't find a cause-and-effect explanation for this.
<!-- Comment: Wed Nov  8 04;31;30 comment by...giulia -->
After the DoneTimeOut the login in b0cot11 gives about 2 thousands lines which look like these:

FISION: S_errno_EINVAL (0x16): VISIONread(): corrupt handle given
TDC_readyForReadoutNowait: VISIONread failed, word = -1, slot = 15      FISION: S_errno_EINVAL (0x16): VISIONread(): corrupt handle given
TDC_readAllFifo: slot = 5 error = 22 reading fifo register
FISION: S_errno_EINVAL (0x16): VISIONread(): corrupt handle given
TDC_readAllFifo: slot = 6 error = 22 reading fifo register
FISION: S_errno_EINVAL (0x16): VISIONread(): corrupt handle given               TDC_readAllFifo: slot = 17 error = 22 reading fifo register
TRACER_enableDone: Front End Fatal Error (-1): Tracer done not set
                                                                                                        
reset crate seems to work.
<!-- Comment: Wed Nov  8 04;39;06 comment by...G -->
sorry, the last 5 words are from me_I forgot to type the
end of line.
<!-- Date: Wed Nov 8 03:37:29 2000 -->
I wasn't seeing anything_ Switch to Normal Mode and  Commissioning ZeroBias as before
<!-- Author: giulia  :: (run 103824) -->


<!-- Date: Wed Nov 8 03:39:36 2000 -->
We decide to place a moratorium on posting non-CDF news into the logbook...
<!-- Author: Alan -->


<!-- Date: Wed Nov 8 03:43:15 2000 -->
<pre>CMP bottom tripped again.  Reset.</pre>
<!-- Author: K Burkett -->



<!-- Date: Wed Nov 8 04:12:28 2000 -->
<pre>COMMISSIONING_ZERO_BIAS is the only table which allows you 
to see something different from nothing, so I'm running with this.Event rate around 100 Hz, occasionally raises to 120/130  
 and then goes back. Is it normal? We will grab the plot  
when we'll have more events, it's more significant.. 
</pre>
<!-- Author: giulia :: (run 103825) -->


<!-- Date: Wed Nov 8 04:28:54 2000 -->
<table><tr><td><a href=/cgi/elog/elog.pl?nb=2000&action=view&page=-539&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/elog.pl?nb=2000&action=view&page=-539  width='250' align='top'></td><td>no comment...</a></td></tr></table>
<!-- Author: giulia -->
<!-- Comment: Wed Nov  8 05;21;21 comment by...g -->
maybe one yes: this is the most interesting event I found...Imagine the rest.


<!-- Date: Wed Nov 8 05:58:56 2000 -->
<table><tr><td><a href=/cgi/elog/elog.pl?nb=2000&action=view&page=-540&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/elog.pl?nb=2000&action=view&page=-540  width='250' align='top'></td><td>This is the final behaviour of the EVB event rate for  the run 103825</a></td></tr></table>
<!-- Author: G -->
<!-- Comment: Wed Nov  8 06;07;16 comment by...g -->
Run ended by RXPT error for doneTimeOut from b0cot11 after 681k
 evts; logged in the crate I saw that the slot 15 was giving 
problem, so I removed it from the readout of the crate.
Now we are running again (wow!), even if you have to watch the
 screen very carefully to realize it.
Run 103826, same trigger table COMM_COSMIC_ZEROBIAS (70),
partition 0.


<!-- Comment: Wed Nov  8 06;16;46 comment by...G -->
This is part of the error message from the crate:

TDC_readAllFifo: card  = 11 fifo emptied xTry = 5 iTry = 5 header = 0x0
TRACER_enableDone: Front End Fatal Error (-1): Tracer done not set
Runtime Error 19: TDC in slot 15 not ready for readout
No new event ...                                                       
<!-- Date: Wed Nov 8 06:12:02 2000 -->
<pre>Convertor node b0l4c12 has not been initialized in partition, 
 maybe someone is working on it upstairs...</pre>
<!-- Author: giu :: (run 103826) -->
<!-- Comment: Wed Nov  8 06;23;31 comment by...G -->
<pre>Rate pretty constant ~100 Hz</pre>


<!-- Date: Wed Nov 8 07:55:16 2000 -->
<font color=red>Shift Summary: </font><pre>Quiet running of zero bias trigger throughout shift. 
Slight event rate mystery, see above.  Rate seems to vary by  
discrete 12-Hz increments either up or down, possibly connected 
with COT errors (but maybe not). 
 
News agencies gave useless information throughout the night... 
 
</pre> 
<br><b>End of Shift Numbers</b>
<table><tr><td width=60% align=left>
<b>CDF Run II <p></b>                       
<pre>
Runs                   1023821 - 103826
Delivered Luminosity   0  pb-1
Acquired Luminosity    0  pb-1
Efficiency             100%
   
</td></tr></table></pre>
<!-- Author: AFS -->


<!-- Date: Wed Nov 8 07:56:30 2000 -->
<table><tr><td><a href=/cgi/elog/elog.pl?nb=2000&action=view&page=-541&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/elog.pl?nb=2000&action=view&page=-541  width='250' align='top'></td><td>Run 103826 ended after 740k evts; this is the plot of the event rate for the event builder. We talked with Frank and he agrees someone should  investigate this.</a></td></tr></table>
<!-- Author: giulia -->
<!-- Comment: Wed Nov  8 08;22;53 comment by...Frank Chlebana -->
Looking through the error log file there are no errors
reported from L3 or EVB.


<!-- Date: Wed Nov 8 07:58:21 2000 -->
<pre>Started another run with 12 L3 subfarms to figure out if the 
 EVB behaviour has something to so with it. 
We already figured out it has nothing to do with the EVD  
running. 
</pre>
<!-- Author: giulia :: (run 103827) -->