<!-- Title: 01:53:43  Fri Apr  6 2001 -->
<!-- Crewchief: worm -->
<!-- Op1: &nbsp; -->
<!-- Op2: &nbsp; -->
<!-- Op3: &nbsp; -->
<!-- Op4: &nbsp; -->
<!-- Op5: &nbsp; -->
<!-- Op6: &nbsp; -->
<!-- Notes: -->
<pre>SLICON RULES!!</pre>


<!-- Date: Fri Apr 6 01:57:51 2001 -->
<pre>With some effort (hwdb java gui hung, b0dap12 crashed...etc etc) 
finally got chips all to BW=7, dynamic thresh = 0, read all. 
Was BW=5 (mostly), dynamic thresh = 1, NN before... 
 
Beginning run # 111381... 
</pre>
<!-- Author: dr worm -->


<!-- Date: Fri Apr 6 02:00:41 2001 -->
<pre>...forgot to say, had ace do a cold restart to make sure the new 
chip parms were loaded.  Will do same for next settings.</pre>
<!-- Author: dr worm -->


<!-- Date: Fri Apr 6 02:46:30 2001 -->
<pre>Run # 111383 is BW=3, read all... 
</pre>
<!-- Author: dr worm -->


<!-- Date: Fri Apr 6 03:22:22 2001 -->
<pre>Used wrong 'clone' button for these runs, so the L00 special ramp 
ped (14 for one of the HDIs) got reset to 6.  Oops!  Rather than 
reset (I think it was crate 0 slot 16 hdi 6 both chips), left at  
6 for scan and subsequent running; setting to 14 would (did) 
generate init failure on cold start (and this happened; set HDI  
7 ramp ped to 14-- before I/we realized it was 6 that was really 
the wonky one). 
 
Also in resetting to BW=5, changed thresh to 5 for the L00 HDIs 
that were at 0 before.  Why were they 0?   
 
Did a short run with BW=5 as the last point in the scan;  
run # 111384.  COT thresh scan now begins...</pre>
<!-- Author: dr worm w/ help from mary -->


<!-- Date: Fri Apr 6 04:33:41 2001 -->
<pre>Can't get siHitAnalyzer to work; old one does not run and 
I can't build a new one; anything that uses "ViewVector" is not 
compiling...(??).  So I can't look at the scan data... 
</pre>
<!-- Author: worm -->


<!-- Date: Fri Apr 6 06:36:00 2001 -->
<pre>Lost store about an hour ago... pump problem... no word yet on  
if we will get another shot.  Should be fixed about the time  
that the day crew comes in, so probably not. 
 
Put voltages to standby. 
 
Unrelated to the above; looked in detail at all the silicon 
voltage histories; B2W8 layer 3 is verry strange.  Please monitor 
when turning it on; if it starts to draw >300 microA again, tell 
me.  It is (was) at ~3 microA now. 
 
</pre>
<!-- Author: worm -->


<!-- Date: Fri Apr 6 06:40:57 2001 -->
<pre>After new trigger table and turning myron off... we get an 
initialization failure for FIB 1 slot 9 chan 5.  This (I think) 
is ISL B0W3.  Looked in chip editor to make sure I didn't screw  
up anything from earlier BW changes; all looks fine.  I had them 
try a few more times, and ACE also logged in and tried to reboot  
crate, no luck.  Allowed shift crew to take this crate out; no  
beam anyway... 
</pre>
<!-- Author: worm -->


<!-- Date: Fri Apr 6 11:30:27 2001 -->
<h4> Silicon stand-alone tracks and rough beamspot estimate.</h4> 
 
We've run the very simple tracking from the engineering run 
on some silicon data taken during shot 2.  The simple algorithm 
is described in the <A Href="/internal/ops/svxii/com_run/rphitrack.html" 
> 
Barrel 4 'How to' pages. </A> 
<p> 
 
<A Href="http://www-cdf.fnal.gov/internal/people/links/RonanMcnulty/ps305_3.ps"> 
The momentum distribution </A>  
of the track candidates is soft. 
(Recall that we concluded last time around that the peak 
below 200MeV has a large contribution from combinatorics  
in the tracking algorithm used.) 
 
<p> 
 
We've 
<A Href="http://www-cdf.fnal.gov/internal/people/links/RonanMcnulty/ps305_1.ps"> 
superimposed many track candidates, </A> 
each having 
a transverse momentum greater than 500 MeV. 
There is evidence that these stand-alone silicon tracks come 
from the beam! 
 
From this, we can do a rough fit for the beam position (just  
using silicon information) and obtain  
x=0+-0.15cm, y=0.3+-0.05cm. 
The <A Href=http://www-cdf.fnal.gov/internal/people/links/RonanMcnulty/ps305_2.ps> 
impact parameter distribution </A> for the tracks with 
pt>0.5GeV is very broad.  This is not unreasonable, bearing 
in mind that the default (geometric) alignment has been used 
rather than the survey results.
<!-- Author: Ronan & Tara -->


<!-- Date: Fri Apr 6 11:47:54 2001 -->
<pre>I have also found tracks using the Karlsruhu tracking 
package.  Kurt Rinnert has also widened the roads to 
find tracks and will reposit that code soon.  I'll post 
some plots as soon as that is done. 
 
95 tracks found in about 225 events.</pre>
<!-- Author: Matt and Kurt -->


<!-- Date: Fri Apr 6 13:01:14 2001 -->
<pre> 
Ronan and Tara's beamspot is consistent with what I found  
using 25 tracks before the usual and not-so-usual code problems. 
The alignment web page will be kept up to date with all the 
values. 
 
Svx beamline Statistics: 25 tracks 
 x0 -0.13635 +- 0.0165998 
 xs 0.00186099 +- 0.00168632 
 y0 0.363554 +- 0.0151989 
 ys -0.000117713 +- 0.000570424 
 
The Cot beamline found by Hartmut Stadie is also consistent 
x = -0.12+-0.006   y = 0.346+-0.007 
indicating probably less than 0.05 cm misalignments between 
the two. Within a day or two, he should have high statistics 
over several runs for the Cot beamline and we will put them  
in the database and post plots.   
 
If anyone develops an order 1K track sample, please pass it  
around.  Thanks. 
</pre>
<!-- Author: Ray -->