<!-- Title: Eve shift. Sun Dec 11, 2005 -->
<!-- SciCo: Beate Heinemann -->
<!-- DAQAce: Wojciech Fedorko/Ai Nagano -->
<!-- MonAce: Lester Pinera -->
<!-- CO: Gianluca Introzzi -->
<!-- OpManager: Greg Feild -->
<!-- Notes: -->
<pre>Tevatron is stacking, but quiet time until 7pm. We plan to do non-quiet time calibrations and L2 torture, and hope for shot setup!</pre>


<!-- Date: Sun Dec 11 16:09:39.724 2005 -->
MCR consider it unlikely that they will have a big enough stack for a shot this evening: currently the stack is 29E10.
<!-- Author: Beate -->


<!-- Date: Sun Dec 11 16:10:35.075 2005 -->
TM2 Events Pending Timeout Error, Trigger rates problem, HRR
<!-- Author: ai :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208699' target=_top>208699</a>) -->


<!-- Date: Sun Dec 11 16:13:56.799 2005 -->
Jianrong Deng was here and talked to Phil Schlabach to figure out the CMX TDC problems: it looks like there is an oscillating preamp in wedge 8. They are looking into that together with the pager carrier. Good news is that the trigger problem is fixed.
<!-- Author: Beate -->


<!-- Date: Sun Dec 11 16:16:21.286 2005 -->
Busy timeout b0tsi03
<!-- Author: ai :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208699' target=_top>208699</a>) -->


<!-- Date: Sun Dec 11 16:19:25.354 2005 -->
I restarted VOICE Alarms.
<!-- Author: ai -->

<!-- Date: Sun Dec 11 16:21:18.537 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208699">208699</a>
 Terminated at 2005.12.11 16:20:57
<!-- Author: RunControl -->


<!-- Date: Sun Dec 11 16:22:34.203 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208699">208699</a>
TERMINATE: for SVT test
<!-- Author: Young-Jang -->


<!-- Date: Sun Dec 11 16:28:25.075 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208701">208701</a>
 Activated at 2005.12.11 16:28:20
<!-- Author: RunControl -->


<!-- Date: Sun Dec 11 16:30:18.558 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208701">208701</a>
ACTIVATE: RunSet: ACE_COSMICS_ALL  Trigger: COSMICS [15,730,598] 
<!-- Author: ai & wojtek x2080 -->


<!-- Date: Sun Dec 11 16:30:19.509 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208703">208703</a>
ACTIVATE: RunSet: SVT_500HZ 
<!-- Author: annovi -->



<!-- Date: Sun Dec 11 16:36:49.535 2005 -->
TM2 Events Pending Timeout Error
<!-- Author: ai :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208701' target=_top>208701</a>) -->


<!-- Date: Sun Dec 11 16:40:51.396 2005 -->
<pre>noticed COT was on STDBY default is to have it off so we ramp it down</pre>
<!-- Author: Wojtek -->


<!-- Date: Sun Dec 11 16:42:50.885 2005 -->
Readout error, RXPT Error b0cot02, HRR
<!-- Author: ai :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208701' target=_top>208701</a>) -->
<!-- Comment: Sun Dec 11 16;47;09 comment by...ai -->
again
<!-- Comment: Sun Dec 11 16;51;23 comment by...ai -->
Readout error for b0cot17
<!-- Date: Sun Dec 11 16:43:13.933 2005 -->
<pre>ODH ALARM for collision and assembly hall 
cryo on the phone</pre>
<!-- Author: Wojtek -->
<!-- Comment: Sun Dec 11 16;43;49 comment by...Beate -->
Cryo guys is going to check it out.


<!-- Comment: Sun Dec 11 16;54;47 comment by...Beate -->
He checked it and thinks it is a bad reading: it says "trouble ok" on the reading. So, he will by pass it now.
<!-- Date: Sun Dec 11 16:44:01.974 2005 -->
TM2 Events Pending Error
<!-- Author: ai :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208701' target=_top>208701</a>) -->
<!-- Comment: Sun Dec 11 16;57;14 comment by...ai -->
again, HRR
<!-- Date: Sun Dec 11 16:48:21.938 2005 -->
Trigger rates problem
<!-- Author: ai :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208701' target=_top>208701</a>) -->



<!-- Date: Sun Dec 11 16:52:28.089 2005 -->
Done Timeout b0cot13, b0cot14, b0cot15, b0cot16, b0cot17 bocot00 b0cot02
<!-- Author: ai :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208701' target=_top>208701</a>) -->


<!-- Date: Sun Dec 11 16:53:56.040 2005 -->
Readout error b0cot17,HRR
<!-- Author: ai :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208701' target=_top>208701</a>) -->


<!-- Date: Sun Dec 11 16:54:03.143 2005 -->
<pre>Solenoid trip field and current look ok 
it cleared in ~30s 
</pre>
<!-- Author: Wojtek -->
<!-- Comment: Sun Dec 11 16;55;57 comment by...Beate -->
The cryo guys also checked out the solenoid trip and says it is okay again. It got a "bad reading" but is now fine. It is strange that this and the ODH alarm happened nearly simultaneously. We will keep watching it. 
<!-- Date: Sun Dec 11 16:55:57.598 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208704">208704</a>
ACTIVATE: RunSet: SVT_500HZ 
<!-- Author: annovi -->




<!-- Date: Sun Dec 11 16:55:59.756 2005 -->
<pre>PSM alarm for 1rr12e_4 
I think this is also a fluke 
</pre>
<!-- Author: Wojtek -->
<!-- Comment: Sun Dec 11 17;04;55 comment by...wojtek and ai -->
<pre>we went to 1st floor: CSX folks are working on it crate is off
</pre>
<!-- Date: Sun Dec 11 17:00:59.323 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208704">208704</a>
TERMINATE: ending
<!-- Author: annovi -->



<!-- Date: Sun Dec 11 17:01:16.282 2005 -->
<pre>We put in a patch to allow SVTSPYMON to save the beam position from run to run. The patch was required since the SVT code migration is on going.</pre>
<!-- Author: Laura & Alberto -->



<!-- Date: Sun Dec 11 17:12:20.772 2005 -->
In the meantime at the daq station: looks like a bunch of cal and cot crates gave rxpt errors 
this was preceded by some b0cot13 Timeout on global TDC Done(MLE 
 
several HRR's were issued 
 
we are back running 
 
jere are some crates that reported trouble: 
 
RXPT Error for crate/s:  
    b0ccal10   b0ccal11   b0ccal12   b0ccal13   b0wcal05   b0wcal06   b0pcal08   b0pcal09   b0pcal10   b0cot13   b0cot14   b0cot15   b0cot16   b0cot17   
<!-- Author: wojtek and ai :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208701' target=_top>208701</a>) -->
<!-- Comment: Sun Dec 11 17;15;18 comment by...Wojtek -->
<pre>actually looking back at the messages Isee that there were more cot crates done TO:
COT_13
COT_14
COT_15
COT_16
COT_17


this was happening in concurrence with the supposed SOlenoid trip (? interesting ?)
</pre>

<!-- Date: Sun Dec 11 17:19:17.449 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208701">208701</a>
 Terminated at 2005.12.11 17:17:11
<!-- Author: RunControl -->


<!-- Date: Sun Dec 11 17:19:19.245 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208701">208701</a>
TERMINATE: for L2torture
<!-- Author: ai & wojtek x2080 -->


<!-- Date: Sun Dec 11 17:22:32.701 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208705">208705</a>
ACTIVATE: RunSet: L2TORTURE  Trigger: L2_TORTURE [16,729,599] 
<!-- Author: ai & wojtek x2080 -->



<!-- Date: Sun Dec 11 17:23:08.275 2005 -->
L2 Decision Timeout
<!-- Author: ai :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208705' target=_top>208705</a>) -->


<!-- Date: Sun Dec 11 17:34:05.918 2005 -->
<pre>CMX ramped down by Dale's request 
he asks us to ramp all the way up in ~5-6 min. 
He will call in ~1hr to ramp back to stdby</pre>
<!-- Author: Wojtek -->
<!-- Comment: Sun Dec 11 17;42;18 comment by...Wojtek -->
<pre>it's up
running cosmics
will do dmode calib in few minutes than cosmics or l2 again</pre>
<!-- Date: Sun Dec 11 17:36:13.122 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208705">208705</a>
TERMINATE: for SVT cosmic
<!-- Author: ai & wojtek x2080 -->
<!-- Comment: Sun Dec 11 17;37;53 comment by...wojtek -->
actually to check out csx

<!-- Date: Sun Dec 11 17:39:31.058 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208706">208706</a>
 Activated at 2005.12.11 17:39:11
<!-- Author: RunControl -->


<!-- Date: Sun Dec 11 17:39:32.842 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208706">208706</a>
ACTIVATE: RunSet: ACE_COSMICS_ALL  Trigger: COSMICS [15,730,598] 
<!-- Author: ai & wojtek x2080 -->
<!-- Comment: Sun Dec 11 17;55;46 comment by...Dale Stentz -->
Short Cosmic run shows CMX west wedge 8 is not oscillating.  All CMX is on and shows typical occupancy.  Either the HV cycle helped or it doesn't oscillate when the HV is all on.  We'll keep looking from afar for now.
<!-- Date: Sun Dec 11 17:40:08.856 2005 -->
L2 decision Timeout
<!-- Author: ai :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208706' target=_top>208706</a>) -->


<!-- Date: Sun Dec 11 17:47:41.929 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208706">208706</a>
 Terminated at 2005.12.11 17:46:42
<!-- Author: RunControl -->


<!-- Date: Sun Dec 11 17:47:42.795 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208706">208706</a>
TERMINATE: for silicon dmod calibration
<!-- Author: ai & wojtek x2080 -->



<!-- Date: Sun Dec 11 17:49:02.567 2005 -->
ramping si up for dmode calib  
<!-- Author: wojtek and ai -->
<!-- Comment: Sun Dec 11 17;52;17 comment by...wojtek -->
up


<!-- Date: Sun Dec 11 17:55:18.698 2005 -->
We changed CSX discriminator (1RR12E, crate 3, slot7) 
and tested it on cosmic run, seems OK. 
Previous discriminator was noisy.
<!-- Author: Akram, Vladimir -->



<!-- Date: Sun Dec 11 17:58:55.745 2005 -->
Stack is at 44.6E10 now. No news from MCR yet.
<!-- Author: Beate -->


<!-- Date: Sun Dec 11 18:01:22.175 2005 -->
problem going through partiton tsi00 01 02  evb2b csl errlog yellow 
rest pale 
try reset  
going through partiton I get: 
Invalid Run Settings 
Trigger Table COSMICS [14,*,*] is no longer valid for online use 
L3 Tag Set 540 is no longer valid for online use 
I probably should just use a current cosmics table but I'll talk to Si to confirm
<!-- Author: Wojtek -->
<!-- Comment: Sun Dec 11 18;13;25 comment by...Kirsten -->
Veronica retired several of the old trigger tables.  If you are using a saved run configuration it may be old and not using a current version of the L3 tagset.  You will need to pick a valid L3 tagset from the available ones.

<!-- Comment: Sun Dec 11 18;15;22 comment by...wojtek ai ankush -->
we did that - it works now

<!-- Date: Sun Dec 11 18:15:38.466 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208707">208707</a>
ACTIVATE: RunSet: SVXCAL_DPSON  Trigger: COSMICS [15,730,598] 
<!-- Author: ai & wojtek x2080 -->



<!-- Date: Sun Dec 11 18:18:59.225 2005 -->
<pre>CER_SVXMON_HALT_RECOVER_RUN_ERROR !!!  
  
 Stuck Cellid S/B0/W4/L4/C0-6 .  
 AUTO HRR will be issued   
</pre>
<!-- Author: wojtek :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208707' target=_top>208707</a>) -->

<!-- Date: Sun Dec 11 18:27:19.868 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208707">208707</a>
TERMINATE: for silicon dmod calib DPS off
<!-- Author: ai & wojtek x2080 -->



<!-- Date: Sun Dec 11 18:31:27.486 2005 -->
<pre> CER_SVXMON_HALT_RECOVER_RUN_ERROR !!!  
  
 Stuck Cellid S/B0/W4/L4/C0-6 .  
 AUTO HRR will be issued  </pre>
<!-- Author: Wojtek :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208708' target=_top>208708</a>) -->
<!-- Comment: Sun Dec 11 18;32;51 comment by...wojtek -->
noch eins
<!-- Comment: Sun Dec 11 18;41;51 comment by...wojtek -->
and one more while ENDing
<!-- Date: Sun Dec 11 18:31:31.647 2005 -->
<table><tr><td><a href=/cgi/elog/elog.pl?nb=2005&action=view&page=-21377&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/elog.pl?nb=2005&action=view&page=-21377  width='300' align='top'></a></td><td>silicon BIAS turned pink, unmarked</td></tr></table>
<!-- Author: ai -->
<!-- Comment: Sun Dec 11 18;39;50 comment by...ai -->
several channel in SVX turned to pink, unmarked. 
one channel (B4W5L4) BIAS is still flat.
<!-- Comment: Sun Dec 11 18;44;09 comment by...wojtek -->
<pre>so actually svx b3w11l2 is also flat and turns back to pink
plots to follow</pre>
<!-- Date: Sun Dec 11 18:36:23.225 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208708">208708</a>
TERMINATE: DMODE done
<!-- Author: ai & wojtek x2080 -->




<!-- Date: Sun Dec 11 18:40:30.608 2005 -->
cmx back to stdby
<!-- Author: Wojtek -->
<!-- Comment: Sun Dec 11 19;17;26 comment by...Dale -->
Thanks - <a href=
'/cgi/elog/elog.pl?nb=2005&action=view&page=1035&frame=2&anchor=17:39:32.842'>via above</a> the potenital high trigger rate problem seen after the smoke cleared from the TDC problem (<a href=
'/cgi/elog/elog.pl?nb=2005&action=view&page=1035&frame=2&anchor=16:13:56.799'>link</a>) has gone away.  Hard to say what killed it; even harder to say whether it will come back or not.  Best course of action is to take cosmics (actually anything that reads out the CMX crate info) and see what happens.  <br><br>Right now run 208707 shows nothing (that's good - CMX is at stand-by).<br><br>
The potential problem might cause a high trigger rate which will result in high deadtime (likely have to mark CMX bad as well).  The problem will be obvious via the YMon "Muon Slide" and even more obvious on the TrigMon "Low Pt CMX TrigData/TrigSim comparision" - west wedge 8 will overshoot all the other west side wedges.<br><br>
We'll keep our eye on it and may decided to come in for the start of the shot to make sure everything runs smothly.

<!-- Date: Sun Dec 11 18:45:10.186 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208709">208709</a>
ACTIVATE: RunSet: L2TORTURE  Trigger: L2_TORTURE [16,729,599] 
<!-- Author: ai & wojtek x2080 -->



<!-- Date: Sun Dec 11 18:47:29.789 2005 -->
l2 decision TO 
 
DT is 4.5%-not too bad 
L1A 41kHz L2A 276Hz  
this looks normal too me  
<!-- Author: wojtek :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208709' target=_top>208709</a>) -->
<!-- Comment: Sun Dec 11 18;48;00 comment by...Wojtek -->
another one hmm....


<!-- Comment: Sun Dec 11 18;50;46 comment by...Wojtek -->
<pre>I will try to crank the rate and see if it affects the l2decision TO rate</pre>
<!-- Date: Sun Dec 11 18:48:21.638 2005 -->
<center><a href='/cgi/elog/elog.pl?nb=2005&action=view&page=-21378&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/elog.pl?nb=2005&action=view&page=-21378' width='300'></a><a href='/cgi/elog/elog.pl?nb=2005&action=view&page=-21379&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/elog.pl?nb=2005&action=view&page=-21379' width='300'></a></center>
<!-- Author: ai -->


<!-- Date: Sun Dec 11 18:50:15.474 2005 -->
ramp si down
<!-- Author: wojtek -->



<!-- Date: Sun Dec 11 18:52:35.870 2005 -->
<pre>Called MCR: they will inject beam in 15-30 minutes but call us before. They don't know the schedule for the shot setup yet since it depends on the pbar guys and the pbar guys "don't know yet"</pre>
<!-- Author: Beate -->


<!-- Date: Sun Dec 11 18:56:57.508 2005 -->
L2 Trigger Rate problem, Trigger rate problem, HRR 
<!-- Author: ai :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208709' target=_top>208709</a>) -->
<!-- Comment: Sun Dec 11 19;02;00 comment by...wojtek -->
<pre>it was L2 decision timeout (the bulb in run control turned red
there was NO alarm red and yellow box about this also no alarm and no auto HRR event though auto HRR's are enabled- 
we should have had auto hrr someone please look at this....</pre>

<!-- Comment: Sun Dec 11 19;02;34 comment by...wojtek -->
<pre>again - exact same behavior</pre>

<!-- Comment: Sun Dec 11 19;05;21 comment by...ai -->
again


<!-- Date: Sun Dec 11 19:06:48.437 2005 -->
RPS and BSC are in somewhat weird state both bars are off so I presume this is fine for beam - the status says 'ON' though
<!-- Author: wojtek -->


<!-- Date: Sun Dec 11 19:07:55.662 2005 -->
<pre>MCR will inject beam in 10 minutes. We are ready for that. But no news on when we will get a shot. The stack is now at 55E10.</pre>
<!-- Author: Beate -->



<!-- Date: Sun Dec 11 19:25:20.577 2005 -->
1RR18E_1 alarmed
<!-- Author: ai -->


<!-- Date: Sun Dec 11 19:32:12.761 2005 -->
funny problem on the rc machine: 
b0dap73:124:~> setup fer 
we^?^?WARNING:  '/cdf/code-common/cdfonline/upsii_database' is not a directory 
ERROR: Found no match for product 'rfm' 
ERROR: Action parsing failed on "unsetuprequired(-j rfm)" 
setup-ppc: assuming PowerPC 603 processor 
b0dap73:125:~> whoami 
cdfdaq 
 
works on control01
<!-- Author: wojtek -->
<!-- Comment: Sun Dec 11 19;39;37 comment by...wojtek -->
works now (?)


<!-- Date: Sun Dec 11 19:41:03.028 2005 -->
l2 decision TO
<!-- Author: Wojtek :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208709' target=_top>208709</a>) -->
<!-- Comment: Sun Dec 11 19;44;00 comment by...ai -->
again


<!-- Date: Sun Dec 11 19:45:11.465 2005 -->
L2 trig rates problem
<!-- Author: ai :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208709' target=_top>208709</a>) -->
<!-- Comment: Sun Dec 11 19;45;58 comment by...ai -->
again


<!-- Date: Sun Dec 11 20:00:38.750 2005 -->
<pre>Hey Wojtek....did you remember to fill in the Silicon D-Mode Calibration Web forms ?</pre>
<!-- Author: Ankush -->
<!-- Comment: Sun Dec 11 20;03;44 comment by...Wojtek -->
I did however I didn't get email confirm...

<!-- Date: Sun Dec 11 20:09:25.835 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208709">208709</a>
TERMINATE: Ending the run to include b0l2pu02 (where the TX we plan to use to proxy b0ccal13 sits)
<!-- Author: ai & wojtek x2080 -->


<!-- Date: Sun Dec 11 20:18:12.717 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208710">208710</a>
TERMINATE: need to make the TX card active (and refresh from HDB)
<!-- Author: ai & wojtek x2080 -->



<!-- Date: Sun Dec 11 20:18:15.845 2005 -->
MCR plan to do studies for 2 hours and then go into shot setup. They are having some trouble with reverse protons right now but as soon as they have fixed that they'll start the studies.  
<!-- Author: Beate -->

<!-- Date: Sun Dec 11 20:22:18.976 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208711">208711</a>
TERMINATE: end

<!-- Author: ai & wojtek x2080 -->



<!-- Date: Sun Dec 11 20:26:07.142 2005 -->
We went to down stairs and RPS BSC turned on.  
<!-- Author: ai -->
<!-- Comment: Sun Dec 11 20;31;08 comment by...ai -->
We noticed RPS and BSC min voltage bars on ifix were down (this is not normal). We paged forward detector expert and he suggested that we look at CLC PC in first floor, specifically BSC1 RPS trigger should be 100%, (they weren't, so we turn them on )

<!-- Comment: Sun Dec 11 20;34;44 comment by...convery -->
This is from when the CLC CAEN was hung up and reset on the owl shift.

<!-- Date: Sun Dec 11 20:36:29.052 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208713">208713</a>
ACTIVATE: RunSet: L2TORTURE  Trigger: L2_TORTURE [16,729,599] 
<!-- Author: ai & wojtek x2080 -->



<!-- Date: Sun Dec 11 21:18:07.839 2005 -->
power codes of wireless network in 1RR04F and 1RR34F they were pluged in. Shotsetup check list says they shuold be unpluged. 
<!-- Author: ai -->
<!-- Comment: Sun Dec 11 21;18;33 comment by...ai -->
so we unpluged them

<!-- Date: Sun Dec 11 21:22:24.876 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208714">208714</a>
TERMINATE: ending to exclude b0ccal13 and seee if we could run with the emulator alone.
<!-- Author: ai & wojtek x2080 -->


<!-- Date: Sun Dec 11 21:23:04.512 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208715">208715</a>
ACTIVATE: RunSet: L2TORTURE  Trigger: L2_TORTURE [16,729,599] 
<!-- Author: ai & wojtek x2080 -->



<!-- Date: Sun Dec 11 21:23:04.052 2005 -->
<pre> 
This TX plan is quite heroic!  
Do we have any evidence that: 
 
a) CCAL13 is sending bad data to L2 
 
OR  
 
b) that we might have to take physics data 
   without the ccal13 crate included? 
 
If so, a summary (or plot) would be nice</pre>
<!-- Author: greg -->
<!-- Comment: Sun Dec 11 22;02;40 comment by...neu+konstantin+wojtek -->
<pre>A summary: 

   o We first did a fiber swapping exercise that confirmed that 
the problem is indeed isolated to ccal13.  These L2DecisionTOs in 
L2Torture are coincident with a bunch-counter mismatch on one of
our three XCES Rx pulsar boards.  We found that when we moved the 
fibers from the three XCES channels coming from ccal13 (E15-17) 
to a different Rx pulsar board, the BC mismatch always followed 
these three channels.  So - it is one of these channels in 
ccal13.  

   o With ccal13 included and sending data I loaded some patterns 
to see if these three channels were giving garbled packets.  I 
did not see any clear data corruption - except the BC mismatch
in the pulsar board.  I did this only a handful of times though.

  o We verified that we could actually run with l2pu02 included 
in the run, which houses the XCES Tx.  This was a problem earlier 
in the week.

  o We verified that we could run L2T without L2DecisionTOs if we
removed the three ccal13 input channels and replaced them with 
three fibers from the XCES Tx.  

As for whether this problem with ccal13 will occur when we take 
data - I do not know.  The ShowerMax group should comment on 
that.  We are prepared to run if ccal13 does not work for beam
data-taking - but this is not a solution, just a temporary fix 
to keep us up and running.  Data would not be good. 

One of us L2 trigger guys will be here for BOS in case this 
ccal13 problem occurs (or any other problem that affects L2).
</pre>
<!-- Comment: Sun Dec 11 22;34;53 comment by...greg -->
<pre>
Excellent job!  Thanks.</pre>
<!-- Date: Sun Dec 11 21:29:23.296 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208715">208715</a>
TERMINATE: succesfully verified that using a TX in b0l2pu02 (slot 10) to emulate b0ccal13 data
works.  Going to default system now
<!-- Author: anikeev/neu/wojtek x2080 -->


<!-- Date: Sun Dec 11 21:32:17.397 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208716">208716</a>
ACTIVATE: RunSet: L2TORTURE  Trigger: L2_TORTURE [16,729,599] L2_TORTURE, b0l2ccal13 is in, b0l2pu02 is out (but hot and ready to go)
<!-- Author: anikeev/neu/wojtek x2080 -->



<!-- Date: Sun Dec 11 21:36:38.559 2005 -->
<pre>Here is a brief history of the L2 v. CCAL13 problem: 
 
A while ago it was found that ccal13 could not be used 
in any kind of run.  It turned out that the problem was due  
to a loose fiber connection to the TRACER in the crate. 
There were no bad SMXR cards that we know of. 
 
Because we wanted to run L2 torture and cosmics without 
the disabled ccal13, the SMXR data to L2 was masked off 
so we could keep running. 
 
HOWEVER, before we discovered the loose TRACER fiber, we  
did suspect that the SMXR cards were bad so  some  
spare SMXR cards were swapped into the crate.  It is at  
this point that the DONE timeouts started occuring in 
the L2 torture runs. 
 
In summary - the original conrcern involving L2 and SMXR was 
due to the ccal13 crate being excluded from running due 
to the bad TRACER connection. 
 
Now, with the (questionable?) SMXR spares installed and 
a possible increase in L2 deadtime (??) when ccal13 is  
included in the run, I leave it to the L2 and SMXR experts 
to assess the current situation. 
 
Perhaps this helps ...</pre>
<!-- Author: greg -->
<!-- Comment: Sun Dec 11 23;37;50 comment by...byrum -->
The problem earlier in the week which turned out to be a tracer cable was with ccal05, not ccal13.   Ccal13 has always had a problem that reappears after long accesses or power outages.   We have never understood this problem and it usually takes a bit of time after an access before this crate settles down.   
<!-- Comment: Mon Dec 12 10;15;47 comment by...greg -->
<pre>argh!  you are right.</pre>
<!-- Date: Sun Dec 11 21:44:42.212 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208716">208716</a>
TERMINATE: l2 work done
we had request before from csx to run cosmics we'll do that now
<!-- Author: wojtek x2080 -->


<!-- Date: Sun Dec 11 21:49:05.872 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208717">208717</a>
ACTIVATE: RunSet: L2TORTURE  Trigger: L2_TORTURE [16,729,599] 
<!-- Author: wojtek x2080 -->



<!-- Date: Sun Dec 11 21:57:39.127 2005 -->
<table border=0><td><tr><td bgcolor=#e0e030><h3>NO Silicon for this store</h3> 
 
<p>If a shot comes in tonight, do NOT include Silicon.  I would like to assess the beam quality of this store before we run with Silicon.</p> 
 
<p>Thank you:-)</p></td></tr></td></table>
<!-- Author: Ankush - Your friendly neighbourhood Silicon SPL -->
<!-- Comment: Sun Dec 11 22;10;02 comment by...greg feild -->
<pre>Then certainly leave CCAL13 in run and in the 
Level 2 trigger, regardless of any problems it may cause,
so that we can gather diagnostic data and fix any 
lingering problems in these systems.  thanks.
</pre>
<!-- Comment: Sun Dec 11 22;17;31 comment by...Lester -->
OK, Great Ankush!  I'll make sure to include silicon! =)
<!-- Comment: Sun Dec 11 23;03;00 comment by...a voice from the past -->
he who joketh with the silicon might roast in sili-hell!
<!-- Date: Sun Dec 11 22:10:00.817 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208718">208718</a>
ACTIVATE: RunSet: COTCALIB_ACE 
<!-- Author: wojtek x2080 -->


<!-- Date: Sun Dec 11 22:10:02.035 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208718">208718</a>
TERMINATE: done COT calib
<!-- Author: wojtek x2080 -->



<!-- Date: Sun Dec 11 22:11:12.240 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208719">208719</a>
 Activated at 2005.12.11 22:10:11
<!-- Author: RunControl -->


<!-- Date: Sun Dec 11 22:11:13.616 2005 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208719">208719</a>
ACTIVATE: RunSet: ACE_COSMICS_ALL  Trigger: COSMICS [15,730,598] 
<!-- Author: wojtek x2080 -->




<!-- Date: Sun Dec 11 22:17:48.000 2005 -->
<pre>per request of COT expert we run COT calibrations 
since CO is not in the room I checked these and the script says they look ok: 
Make sure date is correct. 
 
COT Calibration 22:06:19 on 2005-12-11 
aveStart:                        209.35    
total numBad:                    363     - o.k. 
   numBad  cells:                  2       
   numBad cables:                  0       
   numBad slots:                   0       
 
aveDrift:                       0.083     
max number drifted in crate:    52        
total numDrifted:              143  
   number of drifted  cells        4       
   number of drifted cables        0      
   number of drifted  slots        0       
 
 
This calibration is o.k. 
*** Timing has drifted, constants updated (i.e new COMPLETE file written to DB)*** 
  
Out of the last 7 calibrations, constants have been updated 5 times 
 
 
 
Expert Only: 
file: /cdf/onln/home/cdfdaq/consumers/log/runCotCtt_0_2005-12-11_22:06:19.log 
 
Drifted Cells: 
crate  3 slot 13 asdq  1:  9 
crate  3 slot 13 asdq  7: 10 
crate 17 slot 12 asdq  0: 10 
crate 17 slot 12 asdq  4:  9 
 
 
Bad Cells: 
crate  2 slot  5 asdq  6: 12 
crate  3 slot 14 asdq  3:  9 
 
 
</pre>
<!-- Author: wojtek -->


<!-- Date: Sun Dec 11 22:28:49.017 2005 -->
TM2 error
<!-- Author: wojtek :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208719' target=_top>208719</a>) -->
<!-- Comment: Sun Dec 11 22;41;03 comment by...ai -->
again
<!-- Comment: Sun Dec 11 23;16;08 comment by...ai -->
again
<!-- Comment: Sun Dec 11 23;19;45 comment by...ai -->
again
<!-- Comment: Sun Dec 11 23;30;30 comment by...ai -->
again
<!-- Date: Sun Dec 11 22:38:04.682 2005 -->
<pre>Busy TO. for crate/s:  
    b0tsi03   </pre>
<!-- Author: Wojtek :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208719' target=_top>208719</a>) -->
<!-- Comment: Sun Dec 11 23;59;30 comment by...taichi -->
again.
<!-- Date: Sun Dec 11 23:05:44.011 2005 -->
<table><tr><td><a href=/cgi/elog/elog.pl?nb=2005&action=view&page=-21380&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/elog.pl?nb=2005&action=view&page=-21380  width='300' align='top'></a></td><td>Silicon pinky channel S_DVDD_B2W9L1</td></tr></table>
<!-- Author: ai -->




<!-- Date: Sun Dec 11 23:21:22.856 2005 -->
TOMcat in ProcMon alarmed.
<!-- Author: ai :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208719' target=_top>208719</a>) -->
<!-- Comment: Sun Dec 11 23;45;57 comment by...Lester -->
<pre>When logging into the b0web00 to try issuing a kitty command we got the following message :

WARNING:  '/cdf/code-common/cdfonline/upsii_database' is not a directory
WARNING:  '/cdf/code-common/products/upsii_database' is not a directory
WARNING:  '/cdf/code-common/cdfonline/upsii_database' is not a directory
WARNING:  '/cdf/code-common/products/upsii_database' is not a directory
WARNING:  '/cdf/code-common/cdfonline/upsii_database' is not a directory
WARNING:  '/cdf/code-common/products/upsii_database' is not a directory


after that I tried issuing the kitty command,but we get command not found.  This problem happened during the day and owl shifts today.  We are paging daq</pre>
<!-- Date: Sun Dec 11 23:41:09.623 2005 -->
<pre>MCR called: they will be shooting very soon!</pre>
<!-- Author: Beate -->



<!-- Date: Sun Dec 11 23:55:16.445 2005 -->
<font color=red>Shift Summary: </font><pre> 
- L2 guys worked on the CCAL13 crate problem. The hope is that the 
problem will, however, not appear during physics data taking. Chris 
Neu wants to be called when final protons are being loaded so 
that he can be here for the shot setup. 
 
- CMX muon TDC trigger and HV problems from earlier shift got resolved 
by the experts.  
 
- Silicon should NOT be included into the nxt store 
 
- expect the store soon (during owl shift): will be recycler-only.  
The stack in the recycler is 51E10.  
 
- Currently having Tomkat problem: expert looking into it.</pre> 
<br><b>End of Shift Numbers</b>
<table><tr><td width=60% align=left>
<b>CDF Run II <p></b>                       
<pre>
Runs                   0
Delivered Luminosity   0  
Acquired Luminosity    0  
Efficiency             0
   
</td></tr></table></pre>
<!-- Author: Beate -->

<!-- Date: Sun Dec 11 23:55:31.410 2005 -->
<TABLE BORDER=2 CELLSPACING=1 CELLPADDING=1 BGCOLOR=WHITE>
<TR BGCOLOR=YELLOW><TH>RunNumber</TH>
<TH>DataType</TH>
<TH>Physics able</TH>
<TH>Begin</TH>
<TH>End</TH>
<TH>LiveTime</TH>
<TH>L1Accepts</TH>
<TH>L2Accepts</TH>
<TH>L3Accepts</TH>
<TH>LiveLumi nb<SUP>-1</SUP></TH>
<TH>GR</TH>
<TH>SC</TH>
<TH>RC</TH></TR>
<TR><TD>Totals</TD>
<TD> </TD>
<TD> </TD>
<TD> </TD>
<TD>23:55:00</TD>
<TD ALIGN=CENTER>::</TD>
<TD ALIGN=RIGHT></TD>
<TD ALIGN=RIGHT></TD>
<TD ALIGN=RIGHT></TD>
<TD ALIGN=RIGHT></TD>
<TD> </TD>
<TD> </TD>
<TD> </TD></TR>

</TABLE>
<!-- Author: End of Shift Report -->



<!-- Date: Sun Dec 11 23:57:50.074 2005 -->
<P> 
Have put the following statement in the .cshrc file  
of account tomcat on b0web00: 
 
<blockquote> 
setenv PRODUCTS /cdf/onln/code/products/lnx/upsdb:/cdf/onln/code/cdfprod/upsdb:/cdf/onln/code/cdfsoft/products/upsdb 
</blockquote> 
 
This seems to iron out problems accessing the old  
/cdf/code-common disk. 
 
<P>  
<!-- Author: W.Badgett -->



<!-- Date: Mon Dec 12 00:03:37.053 2005 -->
Trigger Manager Error. HRR. 
<!-- Author: taichi :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=208719' target=_top>208719</a>) -->
<!-- Comment: Mon Dec 12 00;09;47 comment by...taichi -->
again.