[daip] [!7466]: AIPS - RLDLY not properly workin

[Thomas Krichbaum]

Thomas Krichbaum updated #7466
------------------------------

RLDLY not properly workin
-------------------------

           Ticket ID: 7466
                 URL: https://help.nrao.edu/staff/index.php?/Tickets/Ticket/View/7466
           Full Name: Thomas Krichbaum
               Email: tkrichbaum at mpifr-bonn.mpg.de
             Creator: User
          Department: AIPS Data Reduction
       Staff (Owner): Eric Greisen
                Type: Issue
              Status: Open
            Priority: Default
                 SLA: NRAO E2E
      Template Group: Default
             Created: 21 October 2015 10:00 AM
             Updated: 02 November 2015 03:39 PM
      Resolution Due: 02 November 2015 10:09 AM 



Hi Eric,

yes this sounds all very useful. Is it possible to also write on
the MSGSERV a sort of summary of the averaging process. If there
is a lot of scatter in the delays/phases per IF the user could be warned.

Minor comments inserted below

On 11/01/2015 09:28 PM, Eric Greisen wrote:
> I propose making the following changes:
> 
>         Added APARM for control parameters:
>         APARM(1)   SNRMIN, 0 _ 5 which was the previous fixed value

SNR=5 is not very high, so I guess one one  can set also higher values to avoid marginal detections ?

>         APARM(2)   > 0 do not write CL table when have 1 cal scan

in the help file please clarify, that this will write an SN table in any case

>         APARM(3)   Max delay error in ns allowed to be included in
>                    averaging, 0 -> 1000000.

yes, this should allow removing outliers, though the cross-delay should
be much smaller than the default.

>         The task now always writes an SN table.
yes, great.

>         IFs with failed solutions now get delay and phase of 0 not
>         magic blanks to avoid deleting data.

yes, this should help.

> 
> I do not understand the request that the CL table out be allowed to over-write
> an existing table.  The task is applying GAINUSE to the data and then applying the
> extra correction to that version.  It is not doing anything as complex as CLCAL.

this is a misunderstanding, I meant not to over-write an existing CL table. What I meant
was that I could specify an output table in the case the CL+1 does already exist.
So I wanted to write instead to CL+2. But if you create an SN table, the gainuse
command in CLCAL will give control over that.

> 
> Low SNRs (< 5) are already cutoff but I am adding control over that.  I also added
> a control over max delay rms to be included in case that is useful.
> 
> The data missing in a subarray can be handles with the SUBARRAY adverb and the
> options in CLCAL.

good
> 
> Do you think this will help?

yes, thank you very much.

kind regards,
Thomas


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