[evlatests] Holography Phase Oddities

[Bryan Butler]

FWIW, it's not the executor that is doing this, it's obs2script.

again - i'll be poking at what obs2script is doing here, probably over 
the weekend but at least by next monday.

	-bryan


Rick Perley wrote:
>     Finally -- an annoying feature of the new system was found.  The 
> file I submitted was in stop times.  I had added 10 or 20 seconds to 
> each holography scan, in order to give the system a little extra time to 
> get reorganized (and also to see what would happen).  What happened was 
> this:
>           The executor ignored all my commanded stop and start times.  
> On its own accord, it decided not to honor my requested extra time for 
> each holographic scan, and essentially made up a new file with no padded 
> time added -- it executed each holography scan in the minimum time 
> possible (10 seconds per requested point).  However, this override did 
> not happen for the calibration scan -- the full duration was given, even 
> though the scan was not at the time requested.  Because of the removal 
> of the extra times, the file ended 4 minutes and 40 seconds early.  For 
> reasons unclear to me, the final calibrator observation never took 
> place.  Instead, the system lingered at the final holographic position 
> for 80 seconds, then decided to close up shop (so to speak), without the 
> final calibration scan being observed. 
> 
> 
> _______________________________________________
> evlatests mailing list
> evlatests at listmgr.cv.nrao.edu
> http://listmgr.cv.nrao.edu/mailman/listinfo/evlatests