From bcotton@cv3.cv.nrao.eduThu Jan 30 15:37:01 2003
Date: Thu, 9 Jan 2003 19:10:45 -0500 (EST)
From: Bill Cotton <bcotton@cv3.cv.nrao.edu>
To: "VLBI Observers (Aspen only)" <vlbiobs@cv3.cv.nrao.edu>
Cc: Bill Cotton <bcotton@cv3.cv.nrao.edu>, jwrobel@cv3.cv.nrao.edu
Subject: Re: BC135

VLBI Observers (Aspen only) writes:
 > 
 > 
 > On Thu, 9 Jan 2003, Bill Cotton wrote:
 > 
 > >   Thanks, four sessions have been approved.  The version of sched here
 > > in C'ville is rather outdated.  I'm not sure about the times in the
 > > schedule in any case as sched insisted that I give it a date.
 > 
 > I believe the different scan times are due to the fact that I replaced
 > the calendar date with today's LST date, 59364. So if you're satisfied
 > that nothing has been compromised, we'll run with it as it stands.

   I really don't understand the times.  When you ran sched, the times
were closer to what I would have expected - starting at nearly
23:00:00 (but still off by a day).  I tried fine tuning the schedule
based on the times I was getting here but in your version several
observations got hit by long slews.

   However, I understand that the times the schedule is to run can
vary by up to half an hour.  Does this mean that that up to a full
hour is simply lost?  If this is the case, I should schedule an extra
hour on each end and then you just start the schedule whenever, and
stop 8 hours later.  Then I'll not be able to predict exactly what I'm
going to get, but at least I get the full 8 hours.

   Do I need to redo the schedule???

 > 
 > Have also made the b, c and d directories. Please let us know if
 > you want to update or revise your coordinates at some point. Also, if
 > you could write a note about what kind of interval between observations
 > you'd like, that would be helpful for the operators. They're usually
 > the ones to select which dynamics to run on any given day.

   The interval between observations shoould be about 3 months.

Thanks,
Bill