[daip] stress test failed at FRING

[Eric Greisen]

Emmanuel Momjian wrote:
> Hi Eric,
> 
> This morning (June 5) the operators ran the stress test script as usual, 
> and the script failed while running FRING and reported the following:
> 
> FRING1: NO DATA FOUND: CHECK ADVERB VALUES
> FRING1: AVERT RETURNS FATAL ERROR
> FRING1: Purports to die of UNNATURAL causes
> 
> I noticed that yesterday you have updated something in FRING:
> 
> 14139.  June 4, 2013              FRING                   Eric
>         AVERT ignored the "no data found" error condition.  Changed it
>         to issue a message on this and added an error code to be
>         returned by the routine.  Error less than zero means no
>         integration time parameter which may not be fatal, but errors
>         greater than zero including no data found (converted from -1
>         to 10 in AVERT) are fatal and tasks should quit.  Changed
>         FRING and RLDLY to add this argument and a response to errors
>         greater than zero.
>         Moved nowhere.
> 
> 
> I have checked the data in AIPS, and both UVPRT or LISTR are showing 
> that there are data. I tried running FRING manually and it kept 
> reporting the same message and failed. However, FRING is running 
> successfully on the older files of the stress test taken on May 30. 
> Therefore, it is not clear if this update is the reason for the failure 
> of the stress test or not.
> 
> Also, on the June 5 data, I am able to run BPASS successfully, so there 
> is data according to BPASS.
> 
> As I am at the AAS meeting I thought of letting you know about this 
> issue via email. I will back in office on Monday, and I can do more 
> checks on the data of June 5 if the above noted information are 
> insufficient or if you need more details.
> 
> Meanwhile, if you need to access one of June 5 stress test AIPS files, 
> you can use the file with catalog number 436, AIPS user number 13 (the 
> file is 13JUN051343.X BAND.2) on evan.
> 
> Thanks,
> Emmanuel

Thanks for the quick response - I looked at the code I putbck and the 
error was obvious.  I have fixed it, preped a new MNJ, run the MNJ on 
evan, and run with good results the FRING on the data set mentioned above.

ERic