[daip] FITLD antenna ordering

[Anna Bartkiewicz]

Dear Eric,
  Thank you for fixing the problem, I will try it tomorrow.
Today was also suprising for me that:
antname 'vlba'
and
antname 'vlba''
gave different results (error in both cases but different messages). How 
it should be properly 'vlba' or 'vlba''?

Greetings,

Ania


On Thu, 18 Mar 2010, Eric Greisen wrote:

> Mark Reid wrote:
>> Eric Greisen wrote:
>>> Mark Reid wrote:
>>>> Eric,
>>>>
>>>>     I tried running FITLD with the new antenna ordering parameter, but it 
>>>> doesn't seem to work.  Is there anything more than using the ANTNAME 
>>>> parameter that I needed to set?
>>>> 
>>>> The data set I tried it on is
>>>> 
>>>> VLBA_BR145AH_br145ah_6_100308T221619.idifits
>>>> 
>>>> which is publically available and currently on disk in Socorro on 
>>>> /home/ftp/e2earchive
>>>> 
>>>> I tried both
>>>>    ANTNAME='VLBA'
>>>> and
>>>>    antnam 'MK','BR','OV','KP','PT','LA','NL','FD','HN','SC'
>>>> 
>>>> and it gives the same output in PRTAN starting with BR, FD, ...
>>>> 
>>>> Note this data set has HN missing (the data set that started the 
>>>> discussion of fixing the ordering).
>>> 
>>> Thanks for letting me know - the code is fine but I forgot to order up the 
>>> recompile and relink.  The MNJ should fix this tomorrow.
>>> 
>>> Eric
>> 
>> Eric,
>> 
>> A new problem has crept up.  Running on the above data set, here is what 
>> happens:
>> 
>> FITLD1: Task FITLD  (release of 31DEC10) begins
>> FITLD1: Data with weight <  0.80 will be permanently flagged
>> FITLD1: UV data will be written in compressed format
>> FITLD1: Create LIST_6      .UVDATA.   3 (UV)  on disk  2  cno    5
>> FITLD1: Sky frequencies (MHz) before re-ordering occurs:
>> FITLD1: Incoming FREQID #   1
>> FITLD1: 22215.38  22231.40  22247.42  22263.44
>> FITLD1: CL table interval set at  1.00 minutes
>> FITLD1:            !!!!!!!!!!!
>> FITLD1: Digital corrections being performed
>> FITLD1: Total power corrected even if no zero-padding
>> FITLD1:            !!!!!!!!!!!
>> FITLD1: Current file has    38938 visibilities
>> FITLD1: File ref. freq:    22215.38 MHz
>> AIPS 1: Resumes
>>  >FITLD1: Found G095.30-0.94     at   0/17:22:46 src #   1
>> FITLD1:                                        fqid #   1
>> FITLD1:    10000 vis. written
>> FITLD1:    20000 vis. written
>> FITLD1:    30000 vis. written
>> FITLD1: UV table spanned time:   0/17:22:46 -  0/17:25:40
>> FITLD1: Rejected    251 records based on weights
>> FITLD1:    38687 vis. written
>> forrtl: severe (27): too many records in I/O statement, unit -5, file 
>> Internal Formatted Write
>> Image              PC        Routine            Line        Source
>> FITLD.EXE          081E89AC  Unknown               Unknown  Unknown
>> FITLD.EXE          081E7584  Unknown               Unknown  Unknown
>> FITLD.EXE          081C5A15  Unknown               Unknown  Unknown
>> FITLD.EXE          0819D2AC  Unknown               Unknown  Unknown
>> FITLD.EXE          0819D783  Unknown               Unknown  Unknown
>> FITLD.EXE          081B5382  Unknown               Unknown  Unknown
>> FITLD.EXE          0805F2EF  Unknown               Unknown  Unknown
>> FITLD.EXE          08054ED8  Unknown               Unknown  Unknown
>> FITLD.EXE          0804C4C0  Unknown               Unknown  Unknown
>> FITLD.EXE          0804B37D  Unknown               Unknown  Unknown
>> Unknown            00BE3E9C  Unknown               Unknown  Unknown
>> FITLD.EXE          0804B2B1  Unknown               Unknown  Unknown
>
> Curious - I ran this a bunch on your file and did not get this.  But I found 
> an error of just this sort in writing the new adverb info to the history 
> file.  The fix should arrive tomorrow.
>
> Eric
>