[daip] [!9732]: AIPS - R-L delay calibration: rldly & crsfring

[Matthew Lister]

R-L delay calibration: rldly & crsfring
---------------------------------------

           Ticket ID: 9732
                 URL: https://help.nrao.edu/staff/index.php?/Tickets/Ticket/View/9732
           Full Name: Yuri Kovalev
               Email: yyk at asc.rssi.ru
             Creator: User
          Department: AIPS Data Reduction
       Staff (Owner): Eric Greisen
                Type: Issue
              Status: Open
            Priority: Default
                 SLA: NRAO E2E
      Template Group: Default
             Created: 29 January 2017 03:17 PM
             Updated: 30 January 2017 05:19 PM
                 Due: 01 February 2017 05:19 PM (2d 0h 0m)
      Resolution Due: 07 February 2017 05:19 PM (8d 0h 0m)



Hi Eric,

I've had mixed success with RLDLY and CRSFRING, for some VLBA segments they both 
work, others neither. In the last dataset I reduced (from BL193) CRSFRING 
worked. The one prior to that it didn't. The behavior has been too erratic to 
identify any pattern, and the AIPS error messages are generally uninformative. 
I'm sorry I can't contribute anything more productive/helpful at the moment.

- Matt



On 01/30/2017 11:51 AM, Yuri Y. Kovalev wrote:
> Dear Eric,
>
> Following your recommendation some years ago I switched from crsfring to rldly 
> and it was fine. At some later point (a year or more ago) rldly started to 
> give wrong results, similar to this 
> ftp://jet.asc.rssi.ru/outgoing/yyk/2cm/BL229AD_RLDLY/POSSM_CROSS_RLDLY.PS
> Matt Lister had similar problems. I wonder if he can add anything to this?
>
> If you are interested to see the whole procedure, this file describes it:
> ftp://jet.asc.rssi.ru/outgoing/yyk/2cm/BL229AD_processing/BL229AD_Mk5C.SCRIPT
>
> Cheers,
> Yuri
>
> On Mon, 30 Jan 2017, NRAO Helpdesk wrote:
>
>> I am surprised the CRSFRING still works - if it does.  RLDLY was intended to 
>> replace what it did in one nice neat package rather than through a horrible 
>> kludge of a script which included a task written just to do a part of that 
>> job.  On the other hand, if RLDLY was broken in 2015, why did you not tell us 
>> in 2015?  I have consulted with an experienced polarization user (down the 
>> hall) and he tells me RLDLY works just fine to this day.  I will try to see 
>> what is wrong in your case but it is clearly not a general situation.
>>
>> Eric Greisen
>>
>>
>>
>>
>>
>> Ticket Details
>> ---------------------------------
>> Ticket ID: 9732
>> Department: AIPS Data Reduction
>>
>> Support Center: https://help.nrao.edu/index.php?/Tickets/Ticket/View/9732
>>


------------------------------------------------------
Staff CP:  https://help.nrao.edu/staff