<!-- Title: 08:50:35  Mon Oct  2 2000 -->
<!-- Crewchief: Noah Wallace -->
<!-- Op1: Naho Tanimoto -->
<!-- Op2: &nbsp; -->
<!-- Op3: &nbsp; -->
<!-- Op4: &nbsp; -->
<!-- Op5: &nbsp; -->
<!-- Op6: &nbsp; -->
<!-- Notes: -->
<pre>Timing and analyzing yesterdays runs.</pre>


<!-- Date: Mon Oct 2 09:02:44 2000 -->
<table><tr><td><a href=/elog/notebooks/barrel4/Mon_Oct__2_2000_090240.ps align=top><img src=/elog/gifs/ghost64.gif  width='56' align='top'></td><td>caen low voltage plots </a></td></tr></table>
<!-- Author: Noah B. Wallace -->


<!-- Date: Mon Oct 2 09:19:16 2000 -->
<pre>Runs taken yesterday evening 
 
fcdfsgi2> cat /cdf/data03/s1/hardware/svxii/data/RUN_LIST 
 
10.01    Data files written with standalone RC, SEVB. 
 
17:11   A20001001165804.test 
		Readall, 396 off, DPS off, CalCont, East-3 off	 
 
21:57	  A20001001215536.test 
	  Sparse, Thr=5, DPS on, 396 off, CalCont, Wedge East-3 on 
	  Correct size!  (after rc restart) 
 
23:08	  A20001001230124.test 
	  item 2: Readall, Myron, DPS off, 396 off 
 
23:33	  A20001001233228.test 
	  item 4: Sparse, DPS on, 396 off, Myron mode. 
	  got XPT BUSY time-out for svx-02 crate 
	  stopped getting data at ~3000 events, speed ~100ev/sec 
 
</pre>
<!-- Author: Vladimir Nagaslaev -->


<!-- Date: Mon Oct 2 10:28:25 2000 -->
<pre>There is at least one layer 4 ladder that was  
giving dropped readout - EOR 
c2c4s and in earlier runs you may have found 
 the layer 3 ladder on  
wedge 2 west which had extra words before the first chip id. 
 Layer 4 on wedge 3 west was dropping bit 3 hence the channel 
 numbers out of order (hardware has now been fixed).  
Would be nice if the error handler would make an intelligent 
 attempt when getting channels out of order to 
ascertain whether a certain bit is being dropped and report that. 
Also instead of printing out VRB 13 .... can we instead get a 
message like barrel , layer, side .... ?" 
 
Mary's e-mail reported by</pre>
<!-- Author: Saverio -->


<!-- Date: Mon Oct 2 11:23:41 2000 -->
<pre>Vrb Reset Timing 
 
Tested on b0svx02, 6 Vrbs in SRC crate, sending reset, waiting 
a variable time, and trying a VME read. 
SVX MODE 
Vrb Reset w/ value 0 does not bus error on subsequent read 
if delay is > 0.5 mSecs (did not try faster) 
Vrb Reset w/ value 1 bus errors unless delay >= 1.5 mSecs 
 
CAL MODE 
Value 0 -> delay >= 1.5 mSecs 
Value 1 (irrelevant for CAL Mode?) delay >= 5 mSecs 
 
</pre>
<!-- Author: SCN -->


<!-- Date: Mon Oct 2 13:33:22 2000 -->
<pre>Turned on Voltages but not Bias</pre>
<!-- Author: SCN -->


<!-- Date: Mon Oct 2 15:13:18 2000 -->
<pre>Steve Blusk is testing Interlocks...He tripped the East and I powered 
down the West...</pre>
<!-- Author: SCN -->


<!-- Date: Mon Oct 2 15:50:24 2000 -->
<pre>Finished analyzing the four runs from last night: 
165804, 230124, 215536 and 233228 (1000 events each). 
The rz files are in the usual  /cdf/data03/s1/hardware/svxii 
area.</pre>
<!-- Author: Naho, Ashkan -->


<!-- Date: Mon Oct 2 21:17:14 2000 -->
<pre>Integrated with the rest of CDF for testing with chips 
powered on but biases off since about 5 pm.  Accelerator 
has tried for collisions but apparently not yet succeeded.   
We have taken the conservative approach and left biases off 
(despite clean beam conditions) until they decide that the 
accelerator is correctly cogged -- which may not be this 
shift, if things go like they have been so far...</pre>
<!-- Author: Alan Sill -->


<!-- Date: Tue Oct 3 00:30:45 2000 -->
<pre>Optimism triumphs over pessimism: collisions verified by LumMon 
group actually appeared, and we took several runs integrated 
with the rest of CDF and with silicon biased (see main shift 
e-log for details).  Ran event display and SVXMon, but no obvious 
indications of tracks or collisions ... (probably need to  
complete the step[ of subtracting pedestals and suppressing hot 
and noisy channels to be able to see anything clearly). 
 
Accelerator plan is to run with this store all night and not 
to do any further tuning, so will turn monitoring of power 
supplies over to CDF shift crew until 8 am meeting.  Data being 
taken in sparse mode (no neighbors), dps on, with threshold=5. 
One task for tomorrow's shift is to identify runs taken tonight  
integrated with CDF and to run SVXMon on them... if events are 
also taken in Myron mode tonight, will have to do further  
processing to see if any evidence of collisions shows up vs.  
trigger number.  (Ease of doing this will depend on whether 
this is done w/ hardware event builder or software event builder.)</pre>
<!-- Author: Alan Sill -->


<!-- Date: Tue Oct 3 04:21:58 2000 -->
<pre>The relevant Myron mode run with beam (DPS, threshold 5, 
sparse) is (or at least was last night) in  
fcdfsgi2:/cdf/data08/_APHYSR.0000/*100188* 
 
I looked with evd (cf mail to cdf_silicon_monitor), 
but no obvious track-to-calorimeter tower matching. 
 
I asked Peter Wilson to suggest a better trigger for us 
at the 8:00 am meeting, e.g. with Et>1 GeV in central 
crates that roughly map to the B4 phi-space.  For in 
the run mentioned above, the calor threshold was  
minimal, and hence most events have been triggered 
simply by noise -- one can see their hot channels too :( 
</pre>
<!-- Author: Petar -->


<!-- Date: Tue Oct 3 08:02:09 2000 -->
<pre>On the job trying to run the hv script without success.  
 
Apparently we're to analyze the overnight intergrated runs.</pre>
<!-- Author: Noah -->


<!-- Date: Tue Oct 3 08:14:10 2000 -->
<table><tr><td><a href=/elog/notebooks/barrel4/Tue_Oct__3_2000_081405.ps align=top><img src=/elog/gifs/ghost64.gif  width='56' align='top'></td><td>Note power supply trip 00:15 tuesday morning.</a></td></tr></table>
<!-- Author: Noah -->
<!-- Comment: Tue Oct  3 08;36;07 comment by...Noah -->
This is a short run from Wednesday morning.


<!-- Comment: Tue Oct  3 09;50;12 comment by...Saverio -->
This is a short run from Tuesday morning.After that the PS 
was run from another account different from svxii.
<!-- Date: Tue Oct 3 08:37:31 2000 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=barrel4&action=view&page=-34&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=barrel4&action=view&page=-34  width='250' align='top'></td><td>This is the 24 hours ending 10/02/2000 23:59</a></td></tr></table>
<!-- Author: Noah -->
<!-- Comment: Tue Oct  3 08;40;38 comment by...Noah -->
This image is obviously broken.
<!-- Date: Tue Oct 3 08:40:10 2000 -->
<table><tr><td><a href=/elog/notebooks/barrel4/Tue_Oct__3_2000_084008.ps align=top><img src=/elog/gifs/ghost64.gif  width='56' align='top'></td><td>Another attempt to add the graphic</a></td></tr></table>
<!-- Author: Noah  -->



<!-- Date: Tue Oct 3 09:14:15 2000 -->
<pre>the following files were written last night: 
 
100177 (18751) 22:08  22:10 physics cosmics Cosmics table 5 
 
100173 (1874d) 21:24 21:41 physics other Colliding beams. Using COMMISSIONING_TABLE_2  
 
100184 (18758) 23:28 00:03 physics other Colliding beams. COSMICS TABLE 5 
 
100188 (1875c) collsions myron mode no pedestal subtraction.  
 
 </pre>
<!-- Author: Noah and Yamashita -->