[evlatests] [Fwd: Problems with EVLA 14 and 16]

[Bryan Butler]

i believe this is fixed now - the usual form of subarray.execute, with 
look-ahead, is used for files with durations.

and rick's file was hosed, as barry points out, by being on the wrong 
day.  in the OBS file header, there is:
//* *** Observation day 60,391 at 02 30 00 LST, 2005.10.29 00:09:36 MST.
which is off by a day.  that header line is used by obs2script to get 
necessary day/time information.  GIGO.

	-bryan


On 10/28/05 10:47, Bryan Butler wrote:
> 
> 
> On 10/28/05 09:53, Barry Clark wrote:
> 
>> The first sequence, with script 390ptst.script is pretty explicable.
>> The script says it is to start at 53672.2983333, which is to say,
>> tonight at midnight instead of last night at midnight (Rich - it
>> would also help to put your times in UT instead of MDT.)
>>
>> The second, 390btst.script, file seems to clain to have run normally.  
>> Nothing
>> in the log says it wasn't.  I could believe in no fringe, because the 
>> synchronization between the EVLA and Modcomps is never done explicitly,
>> but there is nothing to say the antennas shouldn't have pointed.
>> Walter - putting your file in stop times would make it traverse a more
>> used and better debugged range of software.  Bryan - I think an 
>> implementation using the ususal form of subarry.execute, rather than 
>> defeating the look-ahead feature, would be better.
> 
> 
> this is a by-product of basically doing no testing on files in 
> durations.  if memory serves, i disabled the array.wait() in normal 
> files long ago (except for the very last one) - just never translated it 
> over to durations files.  i will sleuth it and fix it.
> 
> in theory it should still work as-is though, seems to me.
> 
>     -bryan
> 
> 
> _______________________________________________
> evlatests mailing list
> evlatests at listmgr.cv.nrao.edu
> http://listmgr.cv.nrao.edu/mailman/listinfo/evlatests