[daip] gain missing in APCAL

[Amy Mioduszewski]

On 09/15/2014 02:46 AM, Arnaud Collioud wrote:
> Hi Amy,
>
>> Good news, I replicated your error.  :)
>
> Great! At least we can say this is not machine-dependent...
>
>> I compared GC/4 and TY/4 between the data set that didn't work and the one that did (the only difference seems to be that I used UVCOP to copy IFs 1-4, rather than FITLD), and the GC tables are identical, I wrote them out and did a "diff".  The TY tables are different (different sources IDs, which is weird, but I can't figure out why that would cause this).  But since I can replicate the problem that means I can run the debugger and get to the bottom of it.
>
> OK. Good luck with that!
>
>> However, Eric has changed ANTAB so that it no longer works with multiple subarrays.  He said that ANTAB should be run before USUBA because the input file has no information about subarrays and people can get into trouble using it.  I tried ANTAB then USUBA with your data, USUBA assigns different TY entries to different subarrays.  But it gave a similar APCAL error to what you are getting so can't really tell if it is working.  I don't ever use subarrays, so I couldn't really argue with him.  But if there is a good reason for going the USUBA then ANTAB route I will ask him to change it back, or at least to allow multiple subarrays if people are setting the SUBARRAY input.
>
> Does it mean that the SUBARRAY adverb in ANTAB task is useless?
> For the moment, in the doc, it is still written:
>       SUBARRAY
>      ...The subarray to calibrate. Run ANTAB separately for each subarray in the uv-data file. (<-- what I am actually doing)
>
> I have no argument against running ANTAB first...as long as, USUBA does a great job to assign subarrays and update tables.
>
It did appear to assign the different Tsys to different subarrays, although I 
didnt' look close enough to see if it did it right.

> I could not test either because when I try running ANTAB (after FITLD, VLBAMCAL and INDXR, but before USUBA), I have the following message:
>    ANTAB1: Task ANTAB  (release of 31DEC14) begins
>    ANTAB1: NXREAD: INCREASE PARAMETER MAXNX
>    ANTAB1: Purports to die of UNNATURAL causes
> I suppose I have to change MAXNX in ANTAB.FOR. Is it safe to do it (and which value should I put)? How could I then recompile ANTAB? (I used the binary installation...)
>

Eric fixed this problem.  If you do a midnight job you should get this fix.

> Cheers,
> Arnaud
>
>
>
>
>
>