<!-- Title: Owl shift. Sat Sep 29, 2001 -->
<!-- SciCo: P. Azzi, Bob W. -->
<!-- DAQAce: Koji Sato -->
<!-- MonAce: Juan Pablo Fernandez -->
<!-- CO: F. Yoshiaki,L. Moneta -->
<!-- OpManager: Dave Ambrose -->
<!-- Notes: -->
<pre>Store 727 colliding.  
Take data with Physics_0_01[43,207]</pre>


<!-- Date: Sat Sep 29 00:30:12 2001 -->
Inherited Run 127848 at around 300k event. 
<BR> 
Done TimeOut(CMX_01) at event 444679, hit HRR. Two Busy TOs right  
after this HRR successively, two HRRs recovered the run. 
We are running fine now. 
<BR> 
Run condition : 
<PRE> 
  Physics_0_01[43, 207].
  everything in. 
  CMP with top, north and south walls off. 
  LOSTP is around 28kHz. 
  total deadtime is around 1%, Fred 290Hz, L1A 290Hz, L3 60Hz. 
  reformatter errors 0.5% 
  luminosity 4.0E30 
</PRE>  
<!-- Author: Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=127848' target=_top>127848</a>) -->


<!-- Date: Sat Sep 29 00:39:20 2001 -->
<pre>Losses are stable now, but high ~25K. 
Called MCR: they will pull the collimator another mm.</pre>
<!-- Author: Pat -->


<!-- Date: Sat Sep 29 00:45:37 2001 -->
Done Timeout from CMX_01 at event 1023532. 
HRR recovers this.
<!-- Author: Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=127848' target=_top>127848</a>) -->


<!-- Date: Sat Sep 29 00:53:01 2001 -->
<pre>CMX and CPR tripped as a consequence of the flying wire 
(did not have time to put it on stdby after the warning; 
need to set it 1 minute in advance)</pre>
<!-- Author: Juan Pablo :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=127848' target=_top>127848</a>) -->
<!-- Comment: Sat Sep 29 00;57;32 comment by...Juan Pablo -->
<pre>the message was set to warn us about flying wire just 1 minute
in advance (set to two; I can do it on 1 minute but I do not 
want to risk the system; 2 minutes is safe enough)</pre>
<!-- Date: Sat Sep 29 00:54:01 2001 -->
Put Silicon standby.
<!-- Author: Juan Pablo/Koji -->
<!-- Comment: Sat Sep 29 01;01;35 comment by...JP&K -->
<pre>The reason being the fact that the losses are above the
limit (20KHz); the beam is stable though but those losses...</pre>
<!-- Comment: Sat Sep 29 02;11;57 comment by...Pat -->
<pre>Called MCR again: moving collimators did not work, the Tev specialist will try something else. If this fails they might scrape again. 
 </pre>
<!-- Date: Sat Sep 29 00:58:13 2001 -->
Ended run 127849 at 1063612 because we'll keep silicon standby 
for some time. 
<BR> 
Warmstarting a new run.
<!-- Author: Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=127849' target=_top>127849</a>) -->


<!-- Date: Sat Sep 29 01:00:39 2001 -->
l3 failed warmstart. Abort the run.
<!-- Author: Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=127849' target=_top>127849</a>) -->



<!-- Date: Sat Sep 29 01:12:33 2001 -->
Tried warmstart again. 
'L3 Manager Error!'(Orange window) pops up, saying  
<PRE> Attention!! L3CalibTag not found Error!!!. 
We RECOMMEND the following steps: 
- Please page L3 Filter software expert (Farrukh) immediately. 
</PRE> 
Paged L3 software. 
Kirsten called back, told us to try coldstart and if this fails  
page L3 farm. 
Ended 127850 and Trying Coldstart 127851.
<!-- Author: Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=127851' target=_top>127851</a>) -->
<!-- Comment: Sat Sep 29 01;40;12 comment by...Koji -->
We tagged run 127850 'potentially good', but Kirsten told me 
that data should be just junc due to no calibration.
<!-- Comment: Tue Oct  9 18;18;22 comment by...Rob Snihur -->
I checked the used_sets of calibrations for run 127850:
on the surface, no observed problem.
At some point, I should compare the CIDs of each table
to those of another known good run taken during this shift.
<!-- Date: Sat Sep 29 01:19:36 2001 -->
Coldstarting 127851 succeeded, but got 'RXPT Error'(Orange window) in Activating and TSI00 turned red. 
<BR> 
Aborted and Tryed coldstart again(127852). 
Succeeded in activating, but got BTO from VRB_SVX_02 after 12, 17 and 22 events.  
Tying cleaning up event builder.  
<!-- Author: Koji/JuanPablo :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=127852' target=_top>127852</a>) -->


<!-- Date: Sat Sep 29 01:24:01 2001 -->
Cleaned up EVB. 
Nothing seemed wrong as far as we know from checking with 'Ace Control for EVB/L3'.  
<!-- Author: Koji/Juan Pablo -->
<!-- Comment: Sat Sep 29 01;28;15 comment by...Koji -->
Found in the log for run 127852 :
<PRE>(MLE) b0l3gate1.fnal.gov:main:1:16:53 AM->Host b0eb10.fnal.gov, task tsmDisp
SM-P0-E-TmSendFailure: I/O error 7 sending Partition Flushed to Trigger Manager.
</PRE>

Anyway, in the case of eb10 failing, the instruction is to 
cleanup EVB.
I hope this would work.
<BR>
Coldstarting a new run(127853).


<!-- Date: Sat Sep 29 01:35:19 2001 -->
<pre>Run 127853 started all right with PHYSICS_0_01[43,207]. 
We got no error or warnings. 
<PRE> 
Silicon on standby. We still have 30kHz LOSTP. 
Total deadtime around 1%, Fred 290Hz, L1A 290Hz,  L3 60Hz. 
and no errors!!! ... and no errors!!! ... and no errors!!! ... 
and no errors!!!... and no errors!!! ... and no... !!! ...  
and... !!!... an...!!! ... a...!!! ...!! ...! ...</pre>
<!-- Author: Juan Pablo and Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=127853' target=_top>127853</a>) -->
<!-- Comment: Sat Sep 29 02;06;03 comment by...Koji -->
The 1% deadtime consists of 90% readout and 10% of busy.
<!-- Date: Sat Sep 29 01:49:20 2001 -->
Had Yoshiaki(CO) check monitor plots. 
<BR> 
He confirmed that plots look as usual, and also comments that 
in run 127850(without-L3Calib-run) histograms came with strange 
shapes. 
<BR> 
So we're happy with current data taking.
<!-- Author: Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=127853' target=_top>127853</a>) -->


<!-- Date: Sat Sep 29 01:52:09 2001 -->
<pre>everything (CPR,CMX,CMP-bottom and COT) to stdby right on time and ... the wire flies ... 
 
</pre>
<!-- Author: Juan Pablo  :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=127853' target=_top>127853</a>) -->


<!-- Date: Sat Sep 29 01:56:09 2001 -->
<pre>CMX_01 gives BTO but H/R/R saves our souls...</pre>
<!-- Author: Juan Pablo and Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=127853' target=_top>127853</a>) -->


<!-- Date: Sat Sep 29 02:02:04 2001 -->
Done time out from CMX_01 at event 544916. HRR works.
<!-- Author: Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=127853' target=_top>127853</a>) -->



<!-- Date: Sat Sep 29 02:08:43 2001 -->
<pre>DTO from level2decision00 H/R/R saves our souls</pre>
<!-- Author: Juan Pablo and Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=127853' target=_top>127853</a>) -->



<!-- Date: Sat Sep 29 02:45:24 2001 -->
We've reached 1M egvents in run 127853 and this run has been running for more than one hour. 
<BR> 
<BR> 
The perventage of BUSY deadtime grew up to about 20-25% of the  
total. 
<BR> 
L3 monitor looks as usual except for that output nodes stay in 
'Output' state for longer than usual (not that they're always green). 
<BR> 
Event numbers in  L3 summary and consumer receiver display  
are well consistent and total data rate is 16MB/s, which I believe is well within CSL capability. 
<BR> 
Anyway total deadtime stays 1-2% and I think this is all right.
<!-- Author: Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=127853' target=_top>127853</a>) -->


<!-- Date: Sat Sep 29 03:01:25 2001 -->
Busy timeout from VRB_SVX_2 at event 1321337. 
HRR works.
<!-- Author: Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=127853' target=_top>127853</a>) -->


<!-- Date: Sat Sep 29 03:07:46 2001 -->
BTO from VRB_SVX_02 at event 1415481 and HRR works.
<!-- Author: Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=127853' target=_top>127853</a>) -->


<!-- Date: Sat Sep 29 03:10:17 2001 -->
DTO from VRB_SVX_02 and HRR works. Event number 1425447.
<!-- Author: Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=127853' target=_top>127853</a>) -->


<!-- Date: Sat Sep 29 03:10:35 2001 -->
<pre>PEM alarm cleared itself</pre>
<!-- Author: Juan Pablo and Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=127853' target=_top>127853</a>) -->


<!-- Date: Sat Sep 29 03:15:39 2001 -->
BTO from VRB_SVX_02 at event 1515916 and HRR works.
<!-- Author: Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=127853' target=_top>127853</a>) -->


<!-- Date: Sat Sep 29 03:22:03 2001 -->
event 158453, BTO(VRB_SVX_02) -> HRR.
<!-- Author: Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=127853' target=_top>127853</a>) -->


<!-- Date: Sat Sep 29 03:30:52 2001 -->
MCR calls. they are beginning scraping. 
<BR> 
We ended run 127853, and putting everything on standby.
<!-- Author: Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=127853' target=_top>127853</a>) -->
<!-- Comment: Sat Sep 29 03;42;55 comment by...Koji -->
During 'End' transition in RC, we again got orange window saying 'RXPT error!', for which I don't yet find a description in the 
E-Log.
<BR>
Since we could clear this RXPT error previous time by cleaning up
EVB and also because we got recommendations to cleanup EVB in BTOs messages from VRB_SVX_02, we're cleaning up EVB.
<BR>
Also we cleaned up L3 farms.

<!-- Date: Sat Sep 29 03:34:37 2001 -->
<pre> 
 
MCR called.  
They will start scraping the beam.  
Looses will go even higher.   
Everything is on stdby. 
 
</pre>
<!-- Author: Juan Pablo Fernandez  -->






<!-- Date: Sat Sep 29 04:06:50 2001 -->
<a href=  
'/cgi/elog/elog.pl?nb=2001&action=view&page=711&frame=2&anchor=14:44:19'>the reason </a> for losses  
to be that high are already known ; 
  
after waiting for a while to D0 (?) they have just started scraping ... 
<!-- Author: Juan Pablo and Patrizzia -->


<!-- Date: Sat Sep 29 04:08:18 2001 -->
<pre>SVX B4 W3 L1 gave a vbias overcurrent 
reseting trip</pre>
<!-- Author: Juan Pablo -->


<!-- Date: Sat Sep 29 04:08:40 2001 -->
MCR has not yet started scraping. 
<BR> 
I've tried two times (run 127854 and 127855) going through 
ColdStart->Activate->End transition loop, 
to see if we still get RXPT error in run control transitions. 
<BR> 
The error message pops up everytime we end the run. 
This doesn't affect starting our runs. 
<BR> 
To be sure, I paged L1 Decision/TSI. 
<BR><BR> 
Bill (for FRED) called back, and told me that we can live with 
this error, until they fix this. 
Thank him so much for waking up!!
<!-- Author: Koji -->
<!-- Comment: Sat Sep 29 09;32;06 comment by...patrick -->
This very often happens at end run. The ERROR line
comes on before all events have been processed.
This causes the RXPT error. It is nothing to worry about!
<!-- Date: Sat Sep 29 04:13:01 2001 -->
They finished scraping and losses are quite stable now(they called us). 
LOSTP around 11kHz. 
<BR> 
We're putting everything up.  
<!-- Author: Koji/Juan Pablo/Pat -->


<!-- Date: Sat Sep 29 04:18:24 2001 -->
<pre>During the end-run transition, it doesn't generally make  
sense to have errors reported from the RXPT.  However,  
sometimes it is possible. 
 
Does the run continue happily in the Active state, the  
next time you take a run? 
 
Can you tell which crate(s) causes the problem?   Have  
a look at the RXPT GUI. 
 
Which RXPT signal is the problem?  Done timeout?  Busy  
timeout?   Error condition?</pre>
<!-- Author: W.Badgett -->
<!-- Comment: Sat Sep 29 06;51;34 comment by...Koji -->
Sorry I didn't notice this question. I noticed this just now.
<BR>
Now Heather is using trigger crates, I cannot check things.
She will make an entry later on what she notices from now.
<BR>
Anyway until the end of the store, we didn't have any apparent problem in cold-starting runs or taking runs.
<BR>
What I found unusual was that during run 127853, we had a shift 
in BUSY deadtime/Total deadtime percentage of 5 to 20%.
(The error showed up itself at the end of run 127852 for the first time).
<BR>
Sorry for what small information I can give you....
Please wait for Heather's entry.
<!-- Date: Sat Sep 29 04:21:23 2001 -->
Everything up. 
<BR> 
fib04 failed in Coldstart. 
<PRE>(MLE) b0fib04:Messenger:4:16:33 AM->Error Initializing HDI Slot 13 Chan 9: SVX B 
4W3 
(MLE) b0fib04:Messenger:4:16:33 AM->Statechange failed 
</PRE> 
<BR> 
Checked that this channel is ON in Silicon GUI. 
<BR> 
Trying Coldstart again(127857).
<!-- Author: Koji/Juan Pablo :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=127857' target=_top>127857</a>) -->


<!-- Date: Sat Sep 29 04:22:58 2001 -->
CMX tripped. 
<BR> 
WE LOST BEAM!  
<!-- Author: Koji -->


<!-- Date: Sat Sep 29 04:26:51 2001 -->
We put everything on standby after loss was lost. 
<BR> 
We're starting quiet time calibrations.
<!-- Author: Koji/Juan Pablo -->


<!-- Date: Sat Sep 29 04:32:40 2001 -->
<pre>svx b2 w3 (l1) had external trip 
reset</pre>
<!-- Author: Juan Pablo -->


<!-- Date: Sat Sep 29 04:34:57 2001 -->
Took Cal QIE. 
<BR> 
Already in database.
<!-- Author: Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=127858' target=_top>127858</a>) -->


<!-- Date: Sat Sep 29 04:38:08 2001 -->
<table><tr><td><a href=/cgi/elog/elog.pl?nb=2001&action=view&page=-2491&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/elog.pl?nb=2001&action=view&page=-2491  width='300' align='top'></td><td>svrad losses in numbers : SVRAD0 : 1.15; SVRAD1 : 0.59; SVRAD2 : 1.40; SVRAD3 : 1.13 </a></td></tr></table>
<!-- Author: Juan Pablo -->


<!-- Date: Sat Sep 29 04:49:20 2001 -->
Cal LED calibration done.
<!-- Author: Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=127860' target=_top>127860</a>) -->
<!-- Comment: Sat Sep 29 04;54;40 comment by...Koji -->
In database now.
<!-- Date: Sat Sep 29 04:51:13 2001 -->
<center><a href='/cgi/elog/elog.pl?nb=2001&action=view&page=-2494&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/elog.pl?nb=2001&action=view&page=-2494' width='300'></a><a href='/cgi/elog/elog.pl?nb=2001&action=view&page=-2493&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/elog.pl?nb=2001&action=view&page=-2493' width='300'></a></center>
<!-- Author: Juan Pablo Fernandez -->
<!-- Comment: Sat Sep 29 04;54;50 comment by...Juan Pablo -->
<pre>luminosity and losses for this owl's shift

+ suffered from high losses due to the new magnet settings that
were required in order to align the beam w.r.t. our silicon
detector (those hight losses forces as to turn silicon to stdby)

+ got scraping to reduce the losses

+ and then (after few minutes with low losses) got beam lost
(r.i.p.)</pre>


<!-- Date: Sat Sep 29 04:58:44 2001 -->
Went downstairs to turn on Xenon flasher and found message in 
iFix control window "HVMON++ is intentionally down for now. 
Check back later".  Turning ON the HV was disabled and I couldn't
make XENON flash.
<BR> 
Paged Vaia.
<!-- Author: Koji -->
<!-- Comment: Sat Sep 29 05;11;44 comment by...Koji/Juan Pablo -->
Vaia was not the one to page for this.  So sorry, Vaia.
<BR> Paged CEM pager.


<!-- Comment: Sat Sep 29 05;49;22 comment by...Koji -->
No reply from CEM pager.
<BR>
Talked with Dave and decided to move on with other calibrations.

<!-- Date: Sat Sep 29 05:12:53 2001 -->
SMQIE calibration finished.  Already in database.
<!-- Author: Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=127861' target=_top>127861</a>) -->


<!-- Date: Sat Sep 29 05:27:54 2001 -->
<center><a href='/cgi/elog/elog.pl?nb=2001&action=view&page=-2495&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/elog.pl?nb=2001&action=view&page=-2495' width='300'></a><a href='/cgi/elog/elog.pl?nb=2001&action=view&page=-2496&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/elog.pl?nb=2001&action=view&page=-2496' width='300'></a></center>
<!-- Author: Juan Pablo and Koji -->
<!-- Comment: Sat Sep 29 05;29;58 comment by...Juan Pablo and Koji -->
<pre>Looking at the YMon and TrigMon plots:

 calorimeter occupancy and the calorimeter spike occupancy
(under the calorimeter expert menu) in YMon. </pre>

<!-- Comment: Sat Sep 29 05;36;04 comment by...Juan Pablo and Koji -->
<pre>This corresponds to the most recent Rick's run (127862)
L1 accept rate is 120-130 Hz</pre>


<!-- Date: Sat Sep 29 05:39:51 2001 -->
<center><a href='/cgi/elog/elog.pl?nb=2001&action=view&page=-2499&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/elog.pl?nb=2001&action=view&page=-2499' width='300'></a><a href='/cgi/elog/elog.pl?nb=2001&action=view&page=-2500&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/elog.pl?nb=2001&action=view&page=-2500' width='300'></a></center>
<!-- Author: Juan Pablo and Koji -->
<!-- Comment: Sat Sep 29 05;42;04 comment by...Juan Pablo and Koji -->
<pre>WHA spike occupancy and DCAS em/had tower occupancy</pre>


<!-- Date: Sat Sep 29 05:42:51 2001 -->
Took TOF QIE calib.  
<!-- Author: Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=127863' target=_top>127863</a>) -->
<!-- Comment: Sat Sep 29 05;46;00 comment by...Koji -->
Appeared in the database.
<!-- Date: Sat Sep 29 05:45:32 2001 -->
TOF TAC calib.
<!-- Author: Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=127864' target=_top>127864</a>) -->




<!-- Date: Sat Sep 29 05:55:18 2001 -->
After paging the list of people interested in a short access, noone was available to come.  
Called MCR to tell them noone is going on access: their plan is to go into shot setup after quench recovery. 
<i>....oooops....</i> cryo reminded us we should pump the watt can. 
<!-- Author: Pat -->


<!-- Date: Sat Sep 29 06:01:27 2001 -->
CLC calibration failed (as usual). 
<PRE> 
(MLE) b0clc00:Messenger:7:48:34 PM->QIE calibration failed 
48'51"   
</PRE> 
Luminosity monitor starts to show 181E30 instantaneous luminosity. 
Resetting clc00 put it 0.
<!-- Author: Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=127865' target=_top>127865</a>) -->


<!-- Date: Sat Sep 29 06:11:12 2001 -->
COT calibration done. 
Already in database (status:BAD).
<!-- Author: Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=127866' target=_top>127866</a>) -->


<!-- Date: Sat Sep 29 06:15:01 2001 -->
Muon calibration done.
<!-- Author: Koji :: (run <a href='/java/cdfdb/servlet/RunSummary?RUN_NUMBER=127867' target=_top>127867</a>) -->


<!-- Date: Sat Sep 29 06:18:28 2001 -->
Heather is working here with all trigger and calorimeter crates.  
<!-- Author: Koji -->



<!-- Date: Sat Sep 29 07:02:31 2001 -->
Noticed that we don't have CEM, CHA, WHA and GAM. 
I must have forgotten to re-login to pisabox. 
<BR> 
Went downstairs to do that.
<!-- Author: Koji -->


<!-- Date: Sat Sep 29 07:15:01 2001 -->
<ul>Oh yeah Bill, can I give you some information about that stupid RXTP error window popping up in RC.<br><br> 
<li>yesterday morning Monica and I were running with our usual setup - all cal (pcal,ccal,wcal) L1cal,L2cal,L3 config with several different tables and for every end in RC we saw this stupid gui 
<br><br> 
to be more specific, this morning: (please don't ask why I was doing all of this switching between tables - it will be in the L2 log) 
<br> 
->these runs were with alpha in tagging, 6 L3 farms, an old prom in CLIQUE to look for sync errors with cosmics, no files being written to look area 
<li>127870: L2_rate[2,205], get  RXTP gui, TSI00 pink on activate, all b0l1cl crates show error.  I abort and CS 
<li>127871: still using L2_rate[2,205] BTO from TSI00 around ev 25.  HRR and get BTO from TSI00 around ev 31.  RXPT shows pcal07 done, get stupid RXPT gui 
<li>127872: Cosmics_NoTracks[3,205]  get BTO from TSI00, RXPT shows TSI03 as busy. HRR and stick at ev 38.  check of EVB shows no problems, so don't cleanup, just end (get RXPT gui) and reset 
<li>127873: Cosmics_NoTracks[3,205] ran fine after reset/partition, end get RXPT gui and all crates I'm using are shown in error  
<li>127875: Cosmics_NoTracks[3,205] get a new CSL gui -> CSL not logging error when I was in the idle state on my way to start this run.  Says to ignore this error if I'm not in activate.  I'm not so I ignore.  end run and get RXPT gui again, again error in all crates 
<li>127876: L2_TORTURE[3,188] runs fine, end and get RXPT gui with error in all crates 
<li>in the process of running 127876 with L2_TORTURE[3,188]. 
<br> 
unless specifically stated, I only did a coldstart between each run, not reset or anything like that.  I didn't cleanup EVB/L3.  hope this is good enough   
</ul>  
<!-- Author: hray -->
<!-- Comment: Sat Sep 29 07;18;12 comment by...hray -->
something to note: Monica and I never run (rarely) with L3Manager, because it takes so long to partition/coldstart, and not having the most recent calibrations doesn't affect the tests we need to do at L2.  Is it possible this is what always gives us that evil RXPT gui?
<!-- Comment: Sat Sep 29 09;18;25 comment by...hray -->
<ul>
<br><br>
<li>127877: L2_TORTURE[3,188] runs fine, end and see RXPT gui with errors in all crates
<li>127878 same above table, same above run, again see RXPT gui with errors in all crates at end
<li>127879: same above table, BTO from TSI00 at 5K, busy in TSI03, get SM error, cleanup EVB, eb12 doesn't respond, reset that CPU and cleanup EVB again.
<li>127880: same above table, 2 cn in L3 turn orange (09 and 13 on gui)
</ul>
<!-- Date: Sat Sep 29 07:15:16 2001 -->
<pre>Tevatron ramping</pre>
<!-- Author: Juan Pablo Fernandez -->



<!-- Date: Sat Sep 29 07:24:07 2001 -->
Cryo is ready to ramp up the solenoid.   
<!-- Author: Pat -->


<!-- Date: Sat Sep 29 07:58:19 2001 -->
<table><tr><td><a href=/cgi/elog/elog.pl?nb=2001&action=view&page=-2501&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/elog.pl?nb=2001&action=view&page=-2501  width='300' align='top'></td><td>L3 issues:  got SM error, end run and cleanup EVB, but I forgot to  be in Start state.  Try to run and EVB won't pass partition.  So I cleanup EVB again.  This time EVB12 (the one for L1/L2) CPU is stuck so I press reset button on CPU, cleanup again and cross my fingers</a></td></tr></table>
<!-- Author: hray -->


<!-- Date: Sat Sep 29 07:59:47 2001 -->
<pre>TOF alarm that cleares itself 
(this subdetector is OFF anyway) 
</pre>
<!-- Author: Juan Pablo -->


<!-- Date: Sat Sep 29 08:08:48 2001 -->
Cryo called. Solenoid is at full current.
<!-- Author: Erik -->


<!-- Date: Sat Sep 29 08:23:12 2001 -->
MCR called, they are going into shot setup now <font color=red><cite>(entry outside this shift's time range )</cite></font>
<!-- Author: Carsten -->