<!-- Title: 08:55:15  Mon Oct 30 2000 -->
<!-- Crewchief: Tara (morning) -->
<!-- Op1: Anyes -->
<!-- Op2: Andy -->
<!-- Op3: Mircea (evening) -->
<!-- Op4: Tania -->
<!-- Op5: &nbsp; -->
<!-- Op6: &nbsp; -->
<!-- Notes: -->
<pre>Beam today.  Take data, run Matt's program, store ntuples, find beam.</pre>


<!-- Date: Mon Oct 30 08:59:18 2000 -->
<pre>Here is a summary of where we got to last week on the tracking 
and beam determination.   On Alan's suggestion, I put it here 
directly in the logbook, in case the .html files I created 
(tracking.html and beam.html) are wiped from the public area. 
 
</pre>
<!-- Author: Ronan, Tara -->


<!-- Date: Mon Oct 30 09:00:14 2000 -->
<pre>Changed the hardware data base from NN to readall  
in preparation for a calibration with DPS on. 
</pre>
<!-- Author: Anyes -->

<!-- Date: Mon Oct 30 09:08:48 2000 -->
<pre>
Mon Oct 30 09:13:03 CST 2000
From the SVX Power Supply Demon
DVDD 0 26 switched from OFF to ON
</pre>
<!-- Author: SVX Power Supply spy Demon -->



<!-- Date: Mon Oct 30 09:12:31 2000 -->
<table><tr><td><a href=/elog/notebooks/barrel4/Mon_Oct_30_2000_091221.ps align=top><img src=/elog/gifs/ghost64.gif  width='56' align='top'></td><td>This plot shows the (biased) residuals to a least square circle fit through 4 and 5 hit track candidates.  Units on the x axis are cm.  This plot was made from about 100,000 triggers taken from Run 102330 to 102343.  Two features are visible. The first is a narrow Gaussian like structure with a width of about 100 microns.  This is evidence for tracks, though the width suggests we are dominated by multiple scattering which is large for 100 MeV protons. The larger Gaussian with a width of about a mm is likely due to good tracks with an additional noise hit which pulls the fit. It is not just random combinations since running the program on  data without beam produced very few candidates. </a></td></tr></table>
<!-- Author: Ronan  -->

<!-- Date: Mon Oct 30 09:16:46 2000 -->
<pre>
Mon Oct 30 09:21:02 CST 2000
From the SVX Power Supply Demon
DVDD 0 26 switched from ON to OFF
</pre>
<!-- Author: SVX Power Supply spy Demon -->



<!-- Date: Mon Oct 30 09:18:53 2000 -->
<table><tr><td><a href=/elog/notebooks/barrel4/Mon_Oct_30_2000_091848.ps align=top><img src=/elog/gifs/ghost64.gif  width='56' align='top'></td><td>From the curvature of the fitted tracks, we can plot the transverse momentum spectrum (x-axis in units of GeV) It is very very low!! Most tracks have a pt below 100 MeV. </a></td></tr></table>
<!-- Author: Ronan -->


<!-- Date: Mon Oct 30 09:20:11 2000 -->
<table><tr><td><a href=/elog/notebooks/barrel4/Mon_Oct_30_2000_092005.ps align=top><img src=/elog/gifs/ghost64.gif  width='56' align='top'></td><td>Blow-up of low momentum part of spectrum</a></td></tr></table>
<!-- Author: Ronan -->

<!-- Date: Mon Oct 30 09:20:34 2000 -->
<pre>
Mon Oct 30 09:25:02 CST 2000
From the SVX Power Supply Demon
DVDD 0 26 switched from OFF to ON
</pre>
<!-- Author: SVX Power Supply spy Demon -->



<!-- Date: Mon Oct 30 09:23:10 2000 -->
<table><tr><td><a href=/elog/notebooks/barrel4/Mon_Oct_30_2000_092250.ps align=top><img src=/elog/gifs/ghost64.gif  width='56' align='top'></td><td>Finally, we can attempt to 'see the beam'.   This plot shows a superposition of all tracks with pT above 100MeV.  (Turn your head through 90 degrees... silicon is at 12 o clock.)  Some evidence for the beam is visible at or about (0,0) </a></td></tr></table>
<!-- Author: Ronan -->


<!-- Date: Mon Oct 30 09:24:13 2000 -->
<table><tr><td><a href=/elog/notebooks/barrel4/Mon_Oct_30_2000_092406.ps align=top><img src=/elog/gifs/ghost64.gif  width='56' align='top'></td><td>Using those tracks below 100 MeV, it is clear they do NOT come directly from the beam but are probably a product of conversions  in the beam pipe or the silicon.</a></td></tr></table>
<!-- Author: Ronan -->


<!-- Date: Mon Oct 30 09:25:44 2000 -->
<pre>1) Been playing with the Layer 0 power to test 
initialization failures being reported to Run Control 
when a ladder fails to initialize and we are using  
pedestal downloading.  Seems to be ok now - we will 
fail to initialize if we do not see the data from the broker, 
or if chip initialization fails, or what not. 
 
2) Taking a special Run for Jean - 102784.  No Ped Subtraction, 
DPS On, READ ALL, BW 4, Standard (38 ns) SRC timing. 
Presumably this should give us a new noise/hot/dead map 
to compare against, and provide "pedestals" to be subtracted offline for the next shot. 
 
</pre>
<!-- Author: SCN -->
<!-- Comment: Mon Oct 30 09;32;33 comment by...SCN -->
<pre>SEVB died after ~ 1600 Events.  Will try again.</pre>
<!-- Comment: Mon Oct 30 09;52;45 comment by...SCN -->
<pre>Re-try run after restarting SEVB, Run #102786</pre>
<!-- Comment: Mon Oct 30 10;09;17 comment by...SCN -->
<pre>Run Ended Succssfully - 13 kEvents</pre>
<!-- Date: Mon Oct 30 09:31:37 2000 -->
<table><tr><td><a href=/elog/notebooks/barrel4/Mon_Oct_30_2000_093134.ps align=top><img src=/elog/gifs/ghost64.gif  width='56' align='top'></td><td>With the higher momentum tracks, the beam position can be fitted in the x and y co-ordinates. It looks like the x position is at  +900 +- 100 microns. The y position is less well determined to be +3500 +- 500 microns. The width of the beam, including the effect of multiple scattering in the stainless steel beampipe, is approximately 600 microns. </a></td></tr></table>
<!-- Author: Ronan -->



<!-- Date: Mon Oct 30 09:35:18 2000 -->
<table><tr><td><a href=/elog/notebooks/barrel4/Mon_Oct_30_2000_093409.ps align=top><img src=/elog/gifs/ghost64.gif  width='56' align='top'></td><td>The tails in the above plot are interesting.   They are not just due to noise or random combinations of hits in the silicon.  Here we plot positive and negative tracks whose z position lies under the first or second z-segmented silicon.  Three features are noteworthy:  1. Positively charged tracks populate both the central peak and the tails.  Identifying these regions as due to beam collisions and scatters respectively,  this is reasonable behaviour for positive tracks which can come either from the interaction region or from protons which are knocked out of the stainless steel beampipe.   In contrast, negative tracks come predominantly from the  beam interaction region.   They do not come from the halo or pipe-interaction region.  2. The ratio of peak to tails is higher under the first z segmentation.  This allows us to approximately locate the z co-ordinate of the beam. (Note the overall efficiency to find tracks in the second z segment is lower due to more hot and dead channels there.)  3. The position of the beam in x is independent of the z position (within the resolution).  So the beam isn't horribly off axis. All good news for the SVT ...... </a></td></tr></table>
<!-- Author: Ronan -->


<!-- Date: Mon Oct 30 09:39:12 2000 -->
<pre>About the SEVB death 
 
Here's what the Crates were saying: 
FER_readOutVRB(): Error 0xffffffff from SEVB Send globalCount = 5080 
error: socket is not open                                            
 
Here's the last Messages from the SEVB for the run  
in which it died... (My Comments in <I> italics </I>) 
 
== RAWREF Error Handler Initialisation -- FINISHED == 
 
Connecting to CSL on b0dau32, key 4000 
processor queue = 64 
* EventCollector has been CREATED 
subevent queue size = 64 
MGR: running 
* EventCollector has STARTED 
sending ack for /partition-5/ack subject (result = SUCCESS) 
Got transition: Activate 
sending ack for /partition-5/ack subject (result = SUCCESS) 
<I> Run Starts Here </I> 
events: 0 
events: 1000 
ACE_ASSERT: file Token.cpp, line 205 assertion failed for 'my_entry.runable_'.Aborting... 
 
 
</pre>
<!-- Author: SCN -->


<!-- Date: Mon Oct 30 09:40:56 2000 -->
<pre>The code which sits on top of Matt's ntuples and finds stand-alone  
tracks and the beam position will be made available today 
so that people on shift (and offline) can run it as a tool. 
</pre>
<!-- Author: Ronan, Tara -->




<!-- Date: Mon Oct 30 10:12:01 2000 -->
<pre>Put Chips back to Neighbor Mode.  Threshold = 5 comes from 
Cal Database.</pre>
<!-- Author: SCN -->
<!-- Comment: Mon Oct 30 10;14;13 comment by...SCN -->
<pre>Took Some Events for Fun - Run 102788, DPS, NN, Hot/Dead
implemented.</pre>


<!-- Date: Mon Oct 30 10:21:14 2000 -->
<pre>SEVB has trouble at "END" 
Here's log: 
 
 == RAWREF Error Handler Initialisation -- FINISHED == 
 
Connecting to CSL on b0dau32, key 4000 
processor queue = 64 
* EventCollector has been CREATED 
subevent queue size = 64 
MGR: running 
* EventCollector has STARTED 
sending ack for /partition-5/ack subject (result = SUCCESS) 
Got transition: Activate 
sending ack for /partition-5/ack subject (result = SUCCESS) 
events: 0 
events: 1000 
events: 2000 
events: 3000 
events: 4000 
events: 5000 
events: 6000 
events: 7000 
events: 8000 
events: 9000 
events: 10000 
events: 11000 
events: 12000 
events: 13000 
events: 14000 
events: 15000 
Got transition: End 
* EventCollector has STOPPED 
stopping timer 
/cdf/people2/piccoli/srtrel-lin/include/thread_util/private/Queue.ipp:446: failed assertion `count_sem.read () == (int)queue.size ()' 
Got shutdown event 
MGR: total of subevents:3033 
 
 
Looks like data is there: 
/logger/disk1/csl/05/ar019184.0001phys is the file, but it already went to FCC!</pre>
<!-- Author: SCN -->

<!-- Date: Mon Oct 30 16:20:49 2000 -->
<pre>
Mon Oct 30 16:25:02 CST 2000
From the SVX Power Supply Demon
DVDD 0 26 switched from ON to SB
DVDD 0 27 switched from ON to SB
DVDD 0 38 switched from ON to SB
DVDD 0 39 switched from ON to SB
DVDD 1 26 switched from ON to SB
DVDD 1 27 switched from ON to SB
DVDD 1 38 switched from ON to SB
DVDD 1 39 switched from ON to SB
DVDD 2 26 switched from ON to SB
DVDD 2 27 switched from ON to SB
DVDD 2 38 switched from OFF to SB
DVDD 3 27 switched from ON to SB
DVDD 3 38 switched from ON to SB
DVDD 3 39 switched from ON to SB
DVDD 4 26 switched from ON to SB
DVDD 4 27 switched from ON to SB
DVDD 4 38 switched from ON to SB
DVDD 4 39 switched from ON to SB
</pre>
<!-- Author: SVX Power Supply spy Demon -->



<!-- Date: Mon Oct 30 16:21:22 2000 -->
<pre>set  HV in stand-by before injection unstable beam.</pre>
<!-- Author: saverio -->

<!-- Date: Mon Oct 30 17:28:32 2000 -->
<font color="red"><pre> 
From SVX GUI-spy Demon: 
 The PS GUI is not running
 Demon run on: Mon Oct 30 17:33:00 CST 2000
 Last data file update:   Mon Oct 30 17:29:31 CST 2000
</pre></font>
<!-- Author: SVX PS Demon -->



<!-- Date: Mon Oct 30 17:28:32 2000 -->
<pre>Running SVXMon offline on Run 102343 in order to see what 
the pedestals really are.  
 
We also fixed the svxmon_offline script which was not  
identifying the format properly. </pre>
<!-- Author: Tania, Jean -->

<!-- Date: Mon Oct 30 17:54:31 2000 -->
<pre>
Mon Oct 30 17:59:04 CST 2000
From the SVX Power Supply Demon
DVDD 0 26 switched from SB to ON
DVDD 0 27 switched from SB to ON
DVDD 0 38 switched from SB to ON
DVDD 0 39 switched from SB to ON
DVDD 1 26 switched from SB to ON
DVDD 1 27 switched from SB to ON
DVDD 1 39 switched from SB to ON
DVDD 2 26 switched from SB to ON
DVDD 2 27 switched from SB to ON
DVDD 2 38 switched from SB to ON
DVDD 3 27 switched from SB to ON
DVDD 3 38 switched from SB to ON
DVDD 3 39 switched from SB to ON
DVDD 4 26 switched from SB to ON
DVDD 4 27 switched from SB to ON
DVDD 4 38 switched from SB to ON
DVDD 4 39 switched from SB to ON
</pre>
<!-- Author: SVX Power Supply spy Demon -->



<!-- Date: Mon Oct 30 17:58:28 2000 -->
<pre>SVXMon ran on 1000 events on file ar018fc7.0001phys.  
SVXMon running time 0 hrs 7 min 27 sec  
 
Output files =>  
Directory : /cdf/data05/s1/hardware/svxii/SVXMon_offline 
Log file  : 102343.log 
Root file : svxmontest.root_102343.root  
</pre>
<!-- Author: Tania -->


<!-- Date: Mon Oct 30 18:01:19 2000 -->
We have colissions, the beam is stable and we turned the bias  
high voltage on.    
 
 
<!-- Author: Mircea C, Tania M. -->


<!-- Date: Mon Oct 30 18:03:29 2000 -->
<pre>It is now possible for anyone to run some simple r-phi tracking 
on Matt's ntuples. Instructions are on the B4 shift how-to page. 
Basically, you run a kumac inside PAW where the appropriate 
Matt ntuple is given as an argument. The kumac runs the tracking 
algorithms (which might take a while!), and gives you an ntuple 
of track candidates and some sample histograms. An explanation 
of these is given in the instructions. 
 
 The code and the documentation are still under development so 
please send all problems to us ...  
</pre>
<!-- Author: Ronan and Tara -->


<!-- Date: Mon Oct 30 21:42:48 2000 -->
<pre>Set the broker off for 10287</pre>
<!-- Author: Mircea, Vladimir, Jean -->


<!-- Date: Mon Oct 30 22:10:55 2000 -->
We had some problems with the Fib crate 00. We tried to set the broker off, didn't work, reset the crate, didn't work, but finally after many trials and some magic tricks we did it... We are gods, as Alan S. would say. Now we are on the run 102827 with the broker OFF for all the crates... 
<!-- Author: Tania, Mircea, Vladimir,Jean -->
<!-- Comment: Mon Oct 30 22;18;24 comment by...Alan -->
Gods in training, maybe...


<!-- Date: Mon Oct 30 22:46:24 2000 -->
<pre>Started SiHitAnalyzer on Run 102825 which was in 
Myron Mode. (51672 L1A). Running on 5000 events. 
</pre>
<!-- Author: Tania -->


<!-- Date: Mon Oct 30 23:50:08 2000 -->
<table><tr><td><a href=/elog/notebooks/barrel4/Mon_Oct_30_2000_234934.ps align=top><img src=/elog/gifs/ghost64.gif  width='56' align='top'></td><td>SiHitAnalyzer ran on 102825. Ran analyse.kumac on hbook file. Selects 718 events. Plotted  Charge in cluster. See attached file.</a></td></tr></table>
<!-- Author: Tania, Mircea -->


<!-- Date: Mon Oct 30 23:55:46 2000 -->
<pre>Some more plots on Run 102825 are in /cdf/data05/s1/hardware/svxii/SiHitAnalyzer/Analysis : 
102825_mom.ps,102825_chargeinclus.ps,102825_residual.ps  
hbook file : hitdata_102825_0001.hbook (5000 events) contains 
ntuple for all events. Have fun!</pre>
<!-- Author: Tania, Mircea -->


<!-- Date: Tue Oct 31 01:11:23 2000 -->
<pre>Petar has added 2 files b4adcprime.kumac and latex_all.csh. 
b4adcprime.kumac which runs on hbook file produced with 
SiHitAnalyzer.  
 
To make plots for the 4 Myron mode buckets in PAW: 
o  b4adcprime Run# e.g.. b4adcprime#one 102825. 
 
o  To compile the produced eps files into one ps file use 
   latex_all.csh. Edit it to put flist="Run#" e.g.  
   flist="102825". This produces a ps file of the format 
   plots_102825.ps 
 
o  Remove the *.eps files  
 
Run # 102825 has been analysed and a ps file made. Take 
a look at the printout near the b0dap12 computer. 
</pre>
<!-- Author: Tania -->
<!-- Comment: Tue Oct 31 01;12;33 comment by...Mircea C -->
We left SVXMon running on b0dap06...



<!-- Date: Tue Oct 31 03:15:03 2000 -->
<pre>Checked SVXMon around 3 am.  There were occasional Vrb errors, 
but not really recently.  The SVXMon plots look OK.  Let it  
running... 
</pre>
<!-- Author: Petar -->
<!-- Comment: Tue Oct 31 03;16;15 comment by...Petar -->
I cut and pasted a few of the SVXMon VRB errors.  They can
be found in ~svxii/chip_occasional_errors_Oct31.log.