<!-- Title: Owl shift. Sun Nov 16, 2003 -->
<!-- SciCo: Beate Heinemann -->
<!-- DAQAce: Eli Ben-Haim -->
<!-- MonAce: Massimo Casarsa -->
<!-- CO: Subir Sarkar -->
<!-- OpManager: Steve Hahn -->
<!-- Notes: -->
<pre>Planning to do cosmic hig rate running for COT (SVX off) and normal cosmic running with COT and SVX on. L2 pulsar experts running test but XTRP crate causes problems.</pre>

<!-- Date: Sun Nov 16 00:05:47.241 2003 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=174155">174155</a>
ACTIVATE: End cosmic run (busy TO from b0mutr00)
<!-- Author: alex x2080 -->


<!-- Date: Sun Nov 16 00:07:04.365 2003 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=174155">174155</a>
TERMINATE: End cosmic run.
<!-- Author: alex x2080 -->



<!-- Date: Sun Nov 16 00:08:26.027 2003 -->
Trying to page XTRP expert
<!-- Author: beate -->

<!-- Date: Sun Nov 16 00:16:35.413 2003 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=174156">174156</a>
ACTIVATE: Ending cosmic run		
<!-- Author: alex x2080 -->


<!-- Date: Sun Nov 16 00:16:36.633 2003 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=174156">174156</a>
TERMINATE: Ending cosmic run

<!-- Author: alex x2080 -->


<!-- Date: Sun Nov 16 00:21:19.289 2003 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=174157">174157</a>
ACTIVATE: Starting a cosmic notrack test run
<!-- Author: alex x2080 -->


<!-- Date: Sun Nov 16 00:23:59.237 2003 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=174157">174157</a>
TERMINATE: End run
<!-- Author: alex x2080 -->


<!-- Date: Sun Nov 16 00:33:40.593 2003 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=174158">174158</a>
ACTIVATE: new try
<!-- Author: alex x2080 -->


<!-- Date: Sun Nov 16 00:34:13.074 2003 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=174158">174158</a>
TERMINATE: ending run on scanner manager SM_SCPU_TIMEOUT Error

<!-- Author: alex x2080 -->
<!-- Comment: Sun Nov 16 01;34;03 comment by...Eli -->
We followed the instructions and cleaned the event builder. We tried to start the run again. During configuration, the partition State Monitor on L3Display became red. We did Abort -> Reset -> Restart L3 Proxy. L3 seams to be OK now.
<!-- Date: Sun Nov 16 00:34:14.809 2003 -->
We are slightly confused about which cosmic trigger table to use. Following Steve Hahn's message from yesterday we lean towards COSMICS[11,349,403]. However, the white board has a different L2 tag (284). We reckon that the white board instruction is not up to date and follow Steve's elog instructions from 11/15 at 16.44 .
<!-- Author: Beate -->
<!-- Comment: Sun Nov 16 08;20;01 comment by...Steve Hahn -->
<p>You were absolutely right.  I've corrected the white board
(which was my fault).  Tnanks.</p>
<!-- Date: Sun Nov 16 00:48:18.963 2003 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=174159">174159</a>
TERMINATE: Ending cosmic test run.
<!-- Author: alex x2080 -->


<!-- Date: Sun Nov 16 00:53:21.371 2003 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=174160">174160</a>
ACTIVATE: include trigger_scalers
<!-- Author: alex x2080 -->


<!-- Date: Sun Nov 16 00:55:43.986 2003 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=174160">174160</a>
TERMINATE: end run
<!-- Author: alex x2080 -->



<!-- Date: Sun Nov 16 01:09:46.829 2003 -->
Rainer called to tell us that he can be paged again and wants us to run cosmics and monitor at SVXMON.
<!-- Author: Beate -->
<!-- Comment: Sun Nov 16 01;15;13 comment by...rainer -->
keep the silicon biased over night - of course in the very unlikely event of beam, page me and turn to STDBY. it would be good to have a long cosmics run with SVXMon active some time during tonight or tomorrow morning.

<!-- Comment: Sun Nov 16 01;24;23 comment by...rainer -->
I am confused as to whether the two 10K dmod runs were taken with solenoid on as part of the program described <a href=
'/cgi/elog/elog.pl?nb=2003&action=view&page=953&frame=2&anchor=20:30:43.023'>
here.</a>  To be sure, I would like to request re-taking these some time tonight or tomorrow morning. you need to substitute your favourite COSMICS trigger table which might have changed. Also don't forget to propagate the runs into the database  <a href='http://www-cdf.lbl.gov/~igv/Sicalib/job.html'> here </a> as was likely forgotten by the previous shift crew. These guys likely had their hands full debugging L3.

<!-- Comment: Sun Nov 16 01;52;49 comment by...Beate -->
Sure, we'll take them again.
<!-- Date: Sun Nov 16 01:28:49.194 2003 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=174161">174161</a>
TERMINATE: abort due to b0svt05 failed config transition, shepharding b0svt05 failed twice
<!-- Author: alex x2080 -->
<!-- Comment: Sun Nov 16 01;43;13 comment by...Eli -->
L3 proxy died again. We repeated Abort -> Reset -> Restart L3 Proxy. The problem seam to be related to crate b0svt05. We will exclude it from the next run.
<!-- Date: Sun Nov 16 01:37:35.956 2003 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=174162">174162</a>
TERMINATE: abort as b0svt05 turned red in config tramsition
<!-- Author: alex x2080 -->


<!-- Date: Sun Nov 16 01:41:26.466 2003 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=174163">174163</a>
ACTIVATE: starting cosmic notrack excluding b0svt05
<!-- Author: alex x2080 -->
<!-- Comment: Sun Nov 16 01;44;08 comment by...Eli -->
This time L3 proxy does not die.
<!-- Date: Sun Nov 16 01:43:01.573 2003 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=174163">174163</a>
TERMINATE: end run
<!-- Author: alex x2080 -->
<!-- Comment: Sun Nov 16 01;51;29 comment by...Eli -->
L3 proxy died again. We recovered.
<!-- Date: Sun Nov 16 01:49:06.150 2003 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=174164">174164</a>
TERMINATE: abort as level 3 Proxy turns red, reset to start stated for cleaning up L3 
<!-- Author: alex x2080 -->




<!-- Date: Sun Nov 16 01:57:24.882 2003 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=174165">174165</a>
ACTIVATE: try to start with l2pulsar
<!-- Author: alex x2080 -->


<!-- Date: Sun Nov 16 01:57:25.563 2003 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=174165">174165</a>
TERMINATE: abort, found tracer in b0l2pu00 disabled, enable tracer now
<!-- Author: alex x2080 -->



<!-- Date: Sun Nov 16 01:59:17.240 2003 -->
<pre>Update of out plan (when pulsar tests are finished): 
1) take Silicon DMOD runs
2) take cosmic runs with table COSMICS[11,349,403]: SVX and COT on 
3) take all other calibrations 
4) take high data volume cosmic run (SVX off, COT on) 
</pre>
<!-- Author: Beate -->

<!-- Date: Sun Nov 16 02:02:39.655 2003 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=174166">174166</a>
ACTIVATE: next try with pulsar
<!-- Author: alex x2080 -->


<!-- Date: Sun Nov 16 02:03:13.581 2003 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=174166">174166</a>
TERMINATE: we don't get more than 23 events, l2 time out
<!-- Author: alex x2080 -->


<!-- Date: Sun Nov 16 02:15:36.911 2003 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=174167">174167</a>
ACTIVATE: begin cosmic test run
<!-- Author: alex x2080 -->


<!-- Date: Sun Nov 16 02:15:37.921 2003 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=174167">174167</a>
TERMINATE: end run, only 23 events then stuck 
<!-- Author: alex x2080 -->


<!-- Date: Sun Nov 16 02:20:12.000 2003 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=174168">174168</a>
ACTIVATE: try one more run
<!-- Author: alex x2080 -->


<!-- Date: Sun Nov 16 02:24:08.627 2003 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=174168">174168</a>
TERMINATE: run gets stuck on 23rd events (L2A), HHR don't help
<!-- Author: alex x2080 -->
<!-- Comment: Sun Nov 16 02;24;48 comment by...alex -->
cleaning up EVB

<!-- Date: Sun Nov 16 02:32:28.783 2003 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=174169">174169</a>
TERMINATE: Level 3 proxy died in comfig transition
<!-- Author: alex x2080 -->


<!-- Date: Sun Nov 16 02:44:04.240 2003 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=174170">174170</a>
ACTIVATE: Starting cosmic run after cleaning up L3 and EVB
<!-- Author: alex x2080 -->


<!-- Date: Sun Nov 16 02:48:10.267 2003 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=174170">174170</a>
TERMINATE: end this run
<!-- Author: alex x2080 -->


<!-- Date: Sun Nov 16 02:53:59.273 2003 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=174171">174171</a>
ACTIVATE: start new run including pulsar
<!-- Author: alex x2080 -->


<!-- Date: Sun Nov 16 03:02:26.391 2003 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=174171">174171</a>
TERMINATE: Ending cosmic run.
<!-- Author: alex x2080 -->


<!-- Date: Sun Nov 16 03:02:27.925 2003 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=174172">174172</a>
TERMINATE: Level3 proxy dies again in config transition
<!-- Author: alex x2080 -->



<!-- Date: Sun Nov 16 03:04:43.891 2003 -->
L3 proxy dies systematically during config transition although all 8 available subfarms are enabled.
<!-- Author: Eli -->


<!-- Date: Sun Nov 16 03:41:11.693 2003 -->
HV problem in CEM wedge 17 east. Expert gave detailed instructions to Ace how to fix it. 
<!-- Author: Beate -->


<!-- Date: Sun Nov 16 03:42:39.717 2003 -->
Cannot run with XTRP. Have not managed to get hold of any XTRP expert. Continue to try though.
<!-- Author: Beate -->

<!-- Date: Sun Nov 16 04:12:28.955 2003 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=174173">174173</a>
 Activated at 2003.11.16 04:11:39
<!-- Author: RunControl -->


<!-- Date: Sun Nov 16 04:19:28.022 2003 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=174173">174173</a>
ACTIVATE: Cosmics run with silicon and cot.
<!-- Author: Eli -->



<!-- Date: Sun Nov 16 04:27:19.700 2003 -->
<pre>Problem with CEM HVs: 
 - wedge 17E all towers but 7R and 9R, 
 - wedge 6W tower -9R. 
Expert was paged. Following his instructions I reset HVs of such channels. Then I restarted also the redout program.</pre>
<!-- Author: Massimo -->


<!-- Date: Sun Nov 16 04:30:21.803 2003 -->
We were trying to start a cosmics run with silicon. After selecting the run configuration (COSMICS_SILICON_TAPE, or any other configuration that includes silicon crates), windows pop-up every second saying we have to restart SVXMon. We obey, but it persists. We paged silicon. The problem was solved after opening the ConsumerMonitor proxy viewerthen clicking on 'Mode'.
<!-- Author: Eli -->


<!-- Date: Sun Nov 16 04:56:48.248 2003 -->
<h3> Would somebody *please* fix this RunControl/Consumer issue?</h3> 
 
Got paged because of several windows popping up in  run control making it impossible to take cosmics with silicon. This sounds awfully familiar and has already been amply noted <a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2003&action=view&page=953&frame=2&anchor=19:48:25.244'> 
here </a> and 
<a href= 
'/cgi/elog/elog.pl?nb=2003&action=view&page=956&frame=2&anchor=18:42:11.190'> 
here  </a>. It is no doubt fallout from <a href= 
'/cgi/elog/elog.pl?nb=2003&action=view&page=952&frame=2&anchor=13:24:34.179'> 
 here </a> and does not seem to have been addressed successfully so far.  <p> 
The <b> symptom </b> is 50 windows/minute telling that consumer monitor has restarted and SVXMon needs restarting which does not help. The rate of the windows popping up is so high that nothing can be done until one disables/beats into submission the ConsumerMonitor Proxy. This is what I told the Aces to do. <p> 
 
Until NOW this was HARMLESS (apart from other non Silicon issues I might be blissfully unaware of as I am no consumer or proxy expert) since a) we are running cosmics at low L1 rate and b) the magnetic field was off. <BR>Since b) is no longer the case, (very) theoretically we are right now not protected any more against high occupancy/stuck cellid failures which  might lead to resonances and are spotted by SVXMon and mitigated by a sequence of HRRs plus corresponding error message sent to RC which presumably uses that Proxy link. <BR> However it is my understanding that the risk taken is very low since the L1 rate is very low and several conditions including higher L1 rate need to be present in order to constitute a danger. so I am willing to run this cosmics run with this safety feature DISABLED. We also in the meantime commissioned a resonance detector which will pull an SRC error (from b0svx02) in the unlikely event of having synchronous trigger conditions. 
<p> 
<b> Instruction for Aces </b> 
I would like to ask the ACEs: to regularly check the sanity of the trigger by looking for reasonable low ( ~ 50 Hz) L1rate and therefore no hot triggers and low deadtime < a few %.   
Also, should b0svx02 pull error put the DAQ in halt and page me. 
<p> After this run and the dmod  calibrations which are necessary now to debug the detector after the muon wall incident and the friday power cut I will consider removing the silicon from standard CDF datataking/cosmics until this feature has been addressed or a better understanding on my part has been gained that it is absolutely harmless to run in this mode. 
<p> 
And while we are at it  it  would also be nice to know about the status of the <b>trigger inhibits </b>  - at least b0trin00 which seem to be faulty since Friday as well.  I admit I don't know what its status is, whether we migrated to the new system or stil lcan use the old one  and I  maybe should but I was already searching for this b0trin00 crate because the CPU probably needs a reboot but could not find it and it is also not my business. But I would not even know who to page, nor do the aces .... 
  
  
<!-- Author: Rainer -->


<!-- Date: Sun Nov 16 04:57:21.060 2003 -->
<center><a href='/cgi/elog/elog.pl?nb=2003&action=view&page=-12042&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/elog.pl?nb=2003&action=view&page=-12042' width='300'></a><a href='/cgi/elog/elog.pl?nb=2003&action=view&page=-12043&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/elog.pl?nb=2003&action=view&page=-12043' width='300'></a><a href='/cgi/elog/elog.pl?nb=2003&action=view&page=-12044&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/elog.pl?nb=2003&action=view&page=-12044' width='300'></a><a href='/cgi/elog/elog.pl?nb=2003&action=view&page=-12045&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/elog.pl?nb=2003&action=view&page=-12045' width='300'></a></center>
<!-- Author: sarkar -->
<!-- Comment: Sun Nov 16 05;07;28 comment by...rainer -->
looks good, thanks. try to run like this until 7pm or so, do the dmod and  silicon is happy data taking wise. please keep silicon biased until I will come in but remove it for COT high occupancy tests, L2 torture or the like. if in doubt, page me.

<!-- Comment: Sun Nov 16 05;10;56 comment by...rainer -->
sorry, I meant 7 AM .... 


<!-- Date: Sun Nov 16 05:23:53.516 2003 -->
XTRP expert called back. Told him that we don't need him right now and he can sleep for a bit longer. He will come in at 8am. 
<!-- Author: Beate -->


<!-- Date: Sun Nov 16 05:24:03.892 2003 -->
It took us a while to establish that the Pulsar hardware is working fine. We had to exclude the following problem crates to get RC going: b0svt05, pcal07-08, trigger_inhibit and xtrp. We also had to frequently clean up L3 proxy and HEB.  The L3 proxy and HEB problems do not appear to be Pulsar related. We encountered the same type of problems with and w/o the Pulsar. The Pulsar crate is now running with all the available CDF crates (including silicon). 
  
  
<!-- Author: Cheng-Ju & Burkard -->
<!-- Comment: Sun Nov 16 05;33;18 comment by...rainer -->
is the pulsar read out, i.e. reformatter errors are gone ?


<!-- Comment: Sun Nov 16 12;23;28 comment by...Cheng-Ju -->
<pre>We are still disabling the Pulsar readout.  This will be the
default running mode until DAQ/L3 experts are convinced that
the problem is fixed.</pre>
<!-- Date: Sun Nov 16 05:54:53.989 2003 -->
The crates bpcal07 and bpcal08 cannot be included. This problem had already been noted by previous shiftcrew but expert was not paged. Cannot find any reason why not. Paged calo and SVT expert now: are looking into the problems.
<!-- Author: Beate -->
<!-- Comment: Sun Nov 16 06;33;02 comment by...m mattson -->
<br>I'm rather upset at being woken up by the Cal ADMEM pager.  I don't blame the owl shift.  I blame the evening shift, for leaving <b>no documentation in the e-log</b> about why pcal07 and 08 were excluded.  I looked at the error log of a couple of runs, and I see squat.  The only thing I can do is rely on the observations of people running rc, which was not done during the evening shift.<p>
The current DAQ ACE said they could try starting a new run with 07 and 08, but they would prefer to take cosmics longer.  That's fine with me, as long as some point (maybe during the next shift?) someone can write down what the problems are.

<!-- Comment: Sun Nov 16 06;52;55 comment by...m mattson -->
<br>When I tried to log into pcal07 and pcal08, both crates were not responding.  They were also un-pingable.  I'm not comfortable with minicom, but I think that wasn't working either.<p>
My suspicion is that the power supply for these crates are off.  If that's true, then basically anyone could go down in the hall and turn them on (east plug crates).  So the ACEs should check if there is a PSM problem in IFIX, and/or check Voltman (link from the Monitoring ACE page).  pcal07 would be at EPNE-1, and pcal08 at EPSE-1.

<!-- Comment: Sun Nov 16 07;35;07 comment by...Beate -->
Mike Lindgren called and is on his way in to manually reboot those two crates.
<!-- Date: Sun Nov 16 07:04:02.668 2003 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=174173">174173</A>
 Terminated at 2003.11.16 07:02:43
<!-- Author: RunControl -->


<!-- Date: Sun Nov 16 07:08:58.293 2003 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=174173">174173</A>
TERMINATE: Cosmics with silicon and cot. It ran very smoothly for more than 3 hours with 0% of total deadtime and 46.1Hz at L1 
<!-- Author: Eli 2080 -->




<!-- Date: Sun Nov 16 07:54:11.536 2003 -->
<font color=red>Shift Summary: </font><pre>- problem with XTRP: expert arrived in the morning, ran without XTRP all night 
- had to disable b0svt05: expert on his way in 
- had to disable pcal07 and pcal08. They appear dead and expert reckons they need rebooting. M. Lindgren is here now to do that 
- CEM HV failure in wedge 17E. Resetting it according to expert's instructions cured it. 
- tests of L2 pulsar crate were successful (after disabling XTRP, b0svt05 and b0pcal07+08) 
- problem with communication between RunControl and SVXMon made cosmic running impossible for a start: there were windows popping up all the time saying "consumer monitor has restarted and SVXMon needs restarting". Paged Silicon expert: he could help us to get it going. You can find instructions how to solve this in the future in the elog of this shift 
- ran cosmics with COT and SVX from 4.20-7am after getting around above problems. 
- tried to run SMX calibration (request by M. Lindgren) but difficulties with Software Eventbuilder: DAQ expert is helping now 
- outstanding issues: 
   o XTRP: expert will come in in the morning 
   o b0svt05: expert coming in 
   o pcal07,08: expert looking into it 
   o high rate cosmic running w/o SVX 
   o all calibrations (especially SMX and SVX dmod) 
</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 Nov 16 07:55:46.853 2003 -->
<TABLE BORDER=2 CELLSPACING=1 CELLPADDING=1 BGCOLOR=WHITE>
<TR BGCOLOR=YELLOW><TH>Run Number</TH>
<TH>Data Type</TH>
<TH>Physics Table</TH>
<TH>Begin Time</TH>
<TH>End Time</TH>
<TH>Live Time</TH>
<TH>L1 Accepts</TH>
<TH>L2 Accepts</TH>
<TH>L3 Accepts</TH>
<TH>Live Lumi, nb-1</TH>
<TH>GR</TH>
<TH>SC</TH>
<TH>RC</TH></TR>

<TR><TD>Totals</TD>                                                     
<TD> </TD>                                                              
<TD> </TD>                                                              
<TD> </TD>                                                              
<TD>07:55:01</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 Nov 16 07:58:37.899 2003 -->
Run <A HREF="/java/cdfdb/servlet/RunSummary?RUN_NUMBER=174176">174176</A>
 Terminated at 2003.11.16 07:57:12
<!-- Author: RunControl -->



<!-- Date: Sun Nov 16 08:07:49.213 2003 -->
<pre>went into the hall and manually reset crates pcal07 and pcal 08. 
I can log into them and run standalone programs now, so 
assume they are running ok for the moment.</pre>
<!-- Author: lindgren -->



<!-- Date: Sun Nov 16 08:27:54.483 2003 -->
We tried to get a plot from the voltman webpage. It was not possible. Instead of a plot we got an error message: 
<pre> 
This page contains information (application/x-java-vm) that can only be viewed with the appropriate plug-in 
</pre><font color=red><cite>(entry outside this shift's time range )</cite></font>
<!-- Author: Eli -->