<!-- Title: 11:23:45  Mon Jun 18 2001 -->
<!-- Crewchief: Andy F. -->
<!-- Op1: Jean -->
<!-- Op2: Mary -->
<!-- Op3: &nbsp; -->
<!-- Op4: &nbsp; -->
<!-- Op5: &nbsp; -->
<!-- Op6: &nbsp; -->
<!-- Notes: -->
<pre>1) investigate wedges in new crates 
2. integrate with CDF 
3. debug problem ladders</pre>


<!-- Date: Mon Jun 18 11:55:55 2001 -->
<table><tr><td><a href=/elog/notebooks/silicon/Mon_Jun_18_2001_115545.ps align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-104  align='top'></td><td>This plot shows what happened yesterday at about  12.30 to SB0W3 (12 o'clock wedge) Layer 3 and 4 The current on layer-4 was really erratic and high, reaching 1 mA. Spikes on this layer are losely correlated with dips on other layers e.g. L3. We were having colliding beams at the time.  Silicon was turned off at 16.30 for flying wire test.</a></td></tr></table>
<!-- Author: Saverio -->
<!-- Comment: Tue Jun 19 00;45;16 comment by...Sav -->
<pre>What is the little noise that starts around 21:00 ?</pre>
<!-- Date: Mon Jun 18 13:09:15 2001 -->
<pre>SB3W0 tested for CDF integration--OK!</pre>
<!-- Author: ADF -->
<!-- Comment: Mon Jun 18 18;16;31 comment by...ADF -->
<pre>Also tested SB3W2, SB3W3, and SB5W2; all are
basically Ok but need some ladders turned off
(see PC e-logs.)

</pre>


<!-- Date: Mon Jun 18 18:18:34 2001 -->
<pre>All interlock enables down; SVX/ISL 5V switch is off. 
 
Plan: Off until OWL shift.  In OWL shift, test flying 
wires waters if there are still flying wires.  Otherwise, 
await flying wireless run to run integrated with CDF.</pre>
<!-- Author: ADF -->



<!-- Date: Tue Jun 19 00:47:01 2001 -->
<table><tr><td><a href=/elog/notebooks/silicon/Tue_Jun_19_2001_004631.ps align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-106  align='top'></td><td>Starting from 21:00 these detectors were in stand-by</a></td></tr></table>
<!-- Author: Saverio -->


<!-- Date: Tue Jun 19 05:55:59 2001 -->
<pre>Night activities (ooooooooooooooooouuuuuuuuuuuu): 
------------------------------------------------- 
 
I treated the silicon according to Andy's instructions (more  
or less): 
 
At the begin of the owl shift they just lost the beam, but around  
1:50 or so we had a new store in the machine. The first 5 hours  
were dedicated to flying wires. During the first of these  
occasions I checked carefully the beamlosses which were very  
constant and around 5kHz.  
 
After the second flying wire I put  
all 8 SVX wedges to SB, I left ISL off due to the large event  
size (here I'm not sure whether that is correct). 
 
Getting integrated after rebooting four VRBs which had  
suspended messengers: svx03,05,06,07. Afterwards we had  
tons of L3/EVB problems with one intermittent svx06 hardware  
reset.  
 
For the next flying wire I biased SB1W0, which didn't show any  
change in bias currents, nor did it trip. 
 
Therefore, I biased all the SVX wedges. I encountered the  
following peculiarities: 
when I first tried to turn wedges on from SB, they would turn on,  
but the bias voltages stayed at 2V! And also: SB1W3 had L2,3,4  
in SB although they are supposed to be off. I changed the file  
this morning and changed it back, telling Andy to restart the  
GUI, but this has probably not happened. I restarted the GUI.  
Now everything should be fine, also the default bias voltages  
appear now when I go to ON. But I don't understand in which 
 strange  mode the GUI was! 
SB0W3, L2 shows a very high current, I ramped it up by hand and  
watched the current. Could only reach ~18V instead of 30V. 
 
During the last flying wire all 8 SVX wedges were biased (more  
or less) and nothing apparently bad happened to them. Now we  
were even on while the COT was only in SB :) 
 
More or less meaningfull data since run 118119 I would say. 
</pre>
<!-- Author: Petra -->


<!-- Date: Tue Jun 19 17:07:33 2001 -->
<h1>New Wedges</h1>almost...<P> 
I configured the HDWDB for b0fib04 with the ladders 
Andy gave me.  On our first and only attempt we had 
failed to initialize SB3W0-3 and SB4W3-2.  Don't use 
this crate just yet, without supervision...
<!-- Author: SCN -->


<!-- Date: Tue Jun 19 17:59:12 2001 -->
<pre>Want to add B3W0, B3W2, B3W3, B4W1, B4W2, B4W3, 
B5W2, B5W3 to integrate into CDF. 
 
</pre>
<!-- Author: ADF -->


<!-- Date: Tue Jun 19 18:10:00 2001 -->
<pre>Plan! 
 
	1. Lester finishes pipecap test 
	2. Retest standalone (SVXDAQ) the two problem wedges 
that Steve flagged. 
	3. Use NEW ladder set (using b0fib04, all VRB's) ONLY 
		(i.e. do not use b0fib03) 
	3.5 Turn on new set barrel-by-barrel (SVX ON or POWER ON 
              don't work yet).  Barrels 3,4,5 
	4. First flying wire: keep ISL ON, ramp SVX to SBY 10 
minutes before FW. (i.e. Pause run, ramp SVX, FW, raise SVX, 
resume run) 
	5. If that works, keep SVX biased through flying wires 
	6. Turn everything OFF, interlocks off, 5V switches OFF 
	    at 0300. </pre>
<!-- Author: ADF -->
<!-- Comment: Wed Jun 20 04;16;25 comment by...Petra -->
<pre>I guess Andy means: do not use fib00, shich is the SVX one; 
fib03 is the ISL crate!</pre>
<!-- Date: Tue Jun 19 18:32:49 2001 -->
<P> 
We tried to estimate the instantaneous hit rate that the silicon detectors will see during a flying wire. We learned the following. 
 
<P> 
There are 3 separate wires located around the ring. When they fly, they go across and back. This means that each time the wires fly there are actually 6 independent events. The MCR guys said that they get a measure of the emittance for each of the 36 bunches when the wires fly. So, we calculate that the time over which the losses occur must be at least 6*36*2=432 crossings where the 2 comes from the fact that it takes at least 2 measurements per bunch to get an emittance (it is probably more of course but 2 is conservative). We assume that the losses are constant with time during these 432 crossings. They will be higher when the wire is in the middle of the beam than at the edges, but we have assumed only 2 bins so that washes out. 
 
<P> 
The ACNET variables ALOSS and PLOSS are not designed to make fast time scale loss measurements. They measure luminosity per bunch over long time scales and spend a lot of their time calculating rather than measuring. So, the old run I acnet loss variables have been resurrected, LOSSP and LOSSPB. They make a direct measurement of the losses using a rate meter with a 0.5s time constant. They update faster than once per second. During today's store, they've measured several flying wire events and show peak losses of about 25kHz. That number does vary from fly to fly, but we can't see if it falls linearly with beam intensity because the intensity hasn't changed that much. 
<P> 
These losses are measured from the beam shower counters which are scintillators directly around the beam pipe. They probably shadow about as much as L0 does. 
 
<P>To estimate the instantaneous rate at the silicon, we assume that the 25kHz measurement means that 25k particles where counted all originating during the 432 crossings when wires were flying. That should be conservative since the 25kHz is measured in less than a second so the number of particles will be less than 25k. 
 
<P> 
25,000 particles over 432 crossings is about 60 particles per crossing, or 5 per wedge, or 1 per ladder. This is small enough that we think there is enough safety factor to handle variations in loss normalization, angular distribution, showering, etc and still stay below the max multiplicities we'll get out of normal collisions. 
<P> 
A reasonable, cautious approach to follow based on this is to turn SVXII to standby for the next one or two flys but leave ISL biased. If ISL does not trip during these flys then we can leave SVXII biased for subsequent flys.  
<!-- Author: David and Doug and Andy -->
<!-- Comment: Wed Jun 20 04;26;04 comment by...Petra -->
<pre>wasn't it sufficient, that SVX was biased during the last 
FW of last night?</pre>
<!-- Date: Tue Jun 19 21:31:26 2001 -->
<pre>Voltage trigger is incorporated into the PS GUI. The GUI gives an ALERT message, if channel reported, as OFF, but DVDD, AVDD or DOIM voltage is above 1 V for longer than 30 sec. The same time delay is set for Current ALERT messages.</pre>
<!-- Author: Andrew -->
<!-- Comment: Wed Jun 20 04;27;45 comment by...Petra -->
<pre>is it possible to have no DTERM alarms please? This is not
 connected to anything and the alarms are just annoying...</pre>
<!-- Comment: Wed Jun 20 22;13;56 comment by...Andrew -->
<pre>I have masked SB0W5 DTerm channel, which was alarming on the current. Matt suggested to keep an eye on DTerm channels as well.
I am going to modify alarm message to make it not so annoying </pre>
<!-- Date: Tue Jun 19 21:51:56 2001 -->
<pre>Put the following into CDF integration, with the noted  
ladders off: 
 
Wedge         Ladders Off 
B3W0          None 
B3W2          None 
B3W3          L0, L4 
B4W1          L2 
B4W2          L2 
B4W3          L3 
B5W2          None 
B5W3          L2, L4 
 
 These are in CAENvolts.dat  
 
 Also had a lot of trouble with B0W3 L2 Vbias overcurrent, 
should probably remove from CAENvolts.dat . 
 
 Does anyone know how to change which ladders come on 
when you press "SVX" or "POWER"? 
 
</pre>
<!-- Author: ADF -->
<!-- Comment: Tue Jun 19 21;52;26 comment by...ADF -->
<pre>Steve Nahn put them into the HWDB.</pre>


<!-- Date: Tue Jun 19 23:27:40 2001 -->
<pre>New Silicon Integrated run: 
 
Configuration: 
SB3W0 SB3W2 SB3W3 
SB4W1 SB4W2 SB4W3 
SB5W2 SB5W3 &lt;- this last one has L2 (S3) off. 
 
IB0W1 L0,4 on 
IB0W0 L0,1,2,3 are on 
 
Run number  118153 
Calibration: 118159 DPS off</pre>
<!-- Author: Sav -->
<!-- Comment: Wed Jun 20 04;29;52 comment by...Petra -->
<pre>what is (S3) ???</pre>
<!-- Comment: Wed Jun 20 10;01;27 comment by...Sav -->
<pre>Layer-2 is "our" construction layer-2
but in software it is "Silicon-3" because of the presence of L00
</pre>
<!-- Date: Tue Jun 19 23:32:50 2001 -->
<pre>Calibration DPS on Run 118160</pre>
<!-- Author: Sav -->


<!-- Date: Wed Jun 20 03:53:56 2001 -->
<pre>Used a short access tonight and turned PS crate 5 on (including  
the SOC) and raised DVDD for SB0W2, layer4. I ran this ladder  
for a short test and still find RO errors (details see PC elog). 
 
Crate 5 is included in the CAEN.map file. 
 
When the GUI got restarted we found SB0W5 has a DTERM current of  
186mA and IB0W0 cannot get its DOIM voltages down anymore,  
they are high at 1.7V (2VDOIM) and 0.56 (5VDOIM).</pre>
<!-- Author: Petra -->






<!-- Date: Wed Jun 20 04:40:49 2001 -->
<table border=0><td><tr><td bgcolor=#e0e030><pre>IMPORTANT: do not use the global switches for the west side SVX  
in the PS GUI for the time being; since now even crate 5 is  
powered up, you would turn on even those wedges which are not  
checked out yet!</pre></td></tr></td></table>
<!-- Author: Petra -->


<!-- Date: Wed Jun 20 04:43:48 2001 -->
<pre>A couple of PS Gui things which might be nice to have: 
1) A "read new CAENvolts.dat file" button. 
2) A "print" button on the Full Status display.</pre>
<!-- Author: Amit -->


<!-- Date: Wed Jun 20 06:26:16 2001 -->
<pre>I just saw that SB1W6 also has non zero DOIM voltages  
although it is off!</pre>
<!-- Author: A sleepy night owl -->


<!-- Date: Wed Jun 20 07:37:52 2001 -->
<pre>we had a SWT rack trip, something with DRIP... 
rack reset by Rob R.</pre>
<!-- Author: Petra -->


<!-- Date: Wed Jun 20 07:38:34 2001 -->
<pre>Silicon off in awaitement(???) of Tevatron activities. 
All enables off and 5V off.</pre>
<!-- Author: Petra -->



<!-- Date: Wed Jun 20 16:52:03 2001 -->
<pre>Date: Wed, 20 Jun 2001 10:27:07 -0700 
From: Igor Volobouev &lt;IVolobouev@lbl.gov&gt; 
To: Saverio D'Auria &lt;dauria@fnal.gov&gt; 
Cc: Igor Volobouev &lt;igv@fnal.gov&gt;, dadominguez@lbl.gov, 
     Anna Slaughter &lt;slaughte@fnal.gov&gt; 
Subject: Re: new data - calibration 
  
Hi Saverio, 
  
The file on fcdfsgi2 which corresponds to the calibration run 118160: 
/cdf/data08/_ICALIR.0000/ir01cd90.0001cali 
contains only 14 events. I presume, there were more in the actual run. 
Since I don't have an account on b0dau32, could somebody please try to 
figure out what happened? 
  
Thanks, 
Igor        </pre>
<!-- Author: Saverio -->


<!-- Date: Wed Jun 20 16:52:54 2001 -->
<pre>Date: Wed, 20 Jun 2001 13:10:37 -0500 (CDT) 
From: Steven Nahn &lt;nahn@cdfsga.fnal.gov&gt; 
To: Saverio D'Auria &lt;dauria@fnal.gov&gt; 
Cc: Igor Volobouev &lt;IVolobouev@lbl.gov&gt;, dadominguez@lbl.gov, 
     Anna Slaughter &lt;slaughte@fnal.gov&gt;, Steven Nahn &lt;nahn@fnal.gov&gt;, 
     Petra Merkel &lt;petra@fnal.gov&gt;, lmiller@fnal.gov 
Subject: Re: new data - calibration 
  
This is beacuse that Fib is not updated with the latest firmware, is 
my guess.  (Looks like a "c4" problem). 
------------------------------------------------ 
"Saverio D'Auria" writes 
  
&gt; 
&gt;Igor, you are right ! 
&gt;we had a lot of errors in this run, as you can see from the extract 
&gt;from the error report. 
&gt; 
&gt;(MLE) b0dap62.fnal.gov:sevb:11:31:44 PM-&gt;Reformatter error: 
&gt;Returning code: 38; position: 36 
&gt;Line: 299; file: src/library/rr_rawevt.c 
&gt;Description: @L3_REFORMAT_ERROR 
&gt; 
&gt;RAWREF Error - UTILSILDEC - with code 38 -- START 
&gt; Line -  299 in: src/library/rr_rawevt.c 
&gt; Buffer position: 34 
&gt; Error count: 5 of 5 
&gt; Reject rate: -99.000 percent 
&gt; 
&gt; Detector ID not known (yet?). 
&gt; FIB id found: 
&gt;  0xc4e42144                    
&gt;  0xc4e42144 
&gt; 
&gt; [...] 
&gt; 
&gt;(EOR) SoftEVB: 5016 started, 5007 completed, 14 assembled, 14 dispatched, 
&gt;0 timed out events 
&gt;(EOR) SoftEVB: 20054 valid, 8 missing, 0 repeated, 0 invalid, 0 discarded, 
&gt;0 early, 0 late subevents (client events) 
&gt;(EOR) CSL: Normal end; 14 events received, 14 sent to loggers, 14 logged. 
&gt;(EOR) CSL: stream 0, 0 events received, 0 events logged. 
&gt;(EOR) CSL: stream 1, 0 events received, 0 events logged. 
&gt;(EOR) CSL: stream 2, 0 events received, 0 events logged. 
&gt;(EOR) CSL: stream 8, 14 events received, 14 events logged. 
&gt;(EOR) CSL: stream 9, 0 events received, 0 events logged. 
&gt;(EOR) CSL: errors, 23 bad events. 
&gt;(EOR) End of Run System Summary  </pre>
<!-- Author: Saverio -->


<!-- Date: Wed Jun 20 17:33:27 2001 -->
<table border=0><td><tr><td bgcolor=#e0e030><p><font color="red"> <b>We need to take Calibrations with the  
previous configuration </b></font><br> if we want to analyze the data taken last night !<br> The DPS-on calibration went wrong.<br></td></tr></td></table>
<!-- Author: Saverio -->


<!-- Date: Wed Jun 20 18:24:38 2001 -->
<pre>Summary 
 
GUI work all day, combined with very iffy beam  
(studies) 
 
Also much energy expended on BSC's and flying wires; 
will write more fully later. 
 
Hoping for beam this evening.</pre>
<!-- Author: ADF -->


<!-- Date: Wed Jun 20 18:29:24 2001 -->
<pre>Plan! 
 
1. Finish GUI work.  Let Andrew finish what he is working 
on. 
 
2. Take calibration run of first set of SVX wedges 
(which failed last night) 
 
3. Switch over to second (East) set of SVX wedges, which 
has been fully standalone tested.  Feel free to X-out anything 
that gives trouble (with an appropriate note in the 
logbook.)  This will require the "obvious" change to 
the inclusion of crates in the run, and also a change to 
the "powerset" configuration of the gui (which Andrew is 
working on now.) 
 
4. take calibration with the new set of silicon 
 
5. Take data with new SVX set (and old ISL wedges-B0W0 and B0W1) 
integrated into CDF 
 
	If Colin or Steve want to do something they have 
priority. 
</pre>
<!-- Author: ADF -->