[evlatests] Re: EVLA Tests July 18, 2005

[Bryan Butler]

since the EVLA executor runs on UTC start times, indeed i used the MST 
in the time comment that observe/jobserve writes to set the start time 
of the entire observation.  but that only sets the start time of the 
first source.  subsequent source start times are set by the LST stop 
time of the previous source.  so, if you had multiple sources, then 
things would get synch-ed by the second source, i think.  if you had 
only the one source, then i am a bit confused, since an MDT start time 
would put your start time an hour into the future.  i'd have to look at 
the actual script to figure that one out.  can you send it along to me, 
along with the OBS file?

	-bryan


On 7/18/05 14:51, Mark Claussen wrote:
> Bryan,
> 
> I have been looking a little more about this, and I 
> think I understand a little better.   The time in the .obs
> file was actually an MDT, not an MST.  I have tested 
> this, and (as I'm sure you know, but I didn't), obs2script
> must use the date and the time from the obs file
> comment line, not the LST day number and LST.  I had
> edited this by hand, and had put in an MDT time, not MST.
> This doesn't explain how we were able to track 3C84 and
> get fringes if the script uses the same times in the
> subarray.execute(time) for source tracking as for script
> control.   The az/el from the acu was essentially the same
> as the VLA, and we did get fringes.... 
> 
> Mark
> _______________________________________________
> evlatests mailing list
> evlatests at listmgr.cv.nrao.edu
> http://listmgr.cv.nrao.edu/mailman/listinfo/evlatests