[daip] FITLD broken?

[Amy Mioduszewski]

Hi Adam,

Can't be since I loaded some hardware correlator data on the weekend and it was 
fine.  Also that looks like one of the partially processed files (rather than 
the correlator job files), is that correct?

Amy

Adam Deller wrote:
> Hi Amy,
> 
> An example can be found at
> 
> /home/marathon2/data/1023+0038/bd141a/BD141A_UG_HPOL4IF8MHZ16CH_1.6515GHZ00
> 
> Although I suspect any and all VLBA hardware correlator data is
> probably affected.
> 
> Cheers,
> Adam
> 
> On Wed, Jun 16, 2010 at 10:09 AM, Amy Mioduszewski <amiodusz at nrao.edu> wrote:
>> Yea, Eric made some changes.  Point me at the data you are using.  Although
>> I cannot promise too much since I am taking Thurs/Friday off.
>>
>> Amy
>>
>> Adam Deller wrote:
>>> Hi Amy,
>>>
>>> Running from version 'NEW' works.  Running from 'TST' does not.  I
>>> notice they have different adverbs, so obviously some code surgery has
>>> been done somewhere.
>>>
>>> Cheers,
>>> Adam
>>>
>>> On Wed, Jun 16, 2010 at 9:22 AM, Amy Mioduszewski <amiodusz at nrao.edu>
>>> wrote:
>>>> Ack, and Eric isn't here.  Can you test it in version 'new'?
>>>>
>>>> Thanks!
>>>>
>>>> Amy
>>>>
>>>> Adam Deller wrote:
>>>>> Hi,
>>>>>
>>>>> There is something very strange going on with FITLD for VLBA data in
>>>>> AIPS - it is scrambling the SU table for some files (but not all).  I
>>>>> have checked out this particular file (you can see it at
>>>>>
>>>>>
>>>>> /home/marathon2/data/1023+0038/bd141a/BD141A_UG_HPOL4IF8MHZ16CH_1.6515GHZ00)
>>>>> using fv and see a sensible looking SU table.  However, as soon as I
>>>>> load it into AIPS with FITLD the SU table reads:
>>>>>
>>>>>      1    5.0000000000D+05    1.4176255806D+02     3.9039125519D+01
>>>>>  2.0000000000D+03    1.0792773795D+02    4.5395855014D+01
>>>>>      2    5.0000000000D+05    1.5612327792D+02    -8.8208229444D-01
>>>>>  2.0000000000D+03    1.3016422419D+02    7.9956464878D+00
>>>>>      3    5.0000000000D+05    1.5591154583D+02     4.0463333333D-01
>>>>>  2.0000000000D+03    1.2979993496D+02    9.2488222431D+00
>>>>>      4    5.0000000000D+05    1.5271527786D+02    -2.0054371833D+00
>>>>>  2.0000000000D+03    1.2689149360D+02    6.4704735040D+00
>>>>>
>>>>> where the columns are channel bandwidth, RA epoch (deg), Dec epoch
>>>>> (deg), Epoch (years), RA apparent (deg) and Dec apparent (deg).  You
>>>>> can see that the apparent source positions have changed by many
>>>>> degrees - something is amiss.  I tried running FITLD from 31DEC09 but
>>>>> got the same result.  This is data from the hardware correlator from
>>>>> late 2008.
>>>>>
>>>>> Cheers,
>>>>> Adam
>>>>>
>>>
>>>
>>
> 
> 
>