[daip] [!KCC-499-67179]: aips - possible NX table issue

[Lynn D Matthews]

Lynn D Matthews updated #KCC-499-67179
--------------------------------------

possible NX table issue
-----------------------

           Ticket ID: KCC-499-67179
                 URL: https://help.nrao.edu/staff/index.php?/Tickets/Ticket/View/3721
           Full Name: Lynn D Matthews
               Email: lmatthew at haystack.mit.edu
             Creator: User
          Department: AIPS Data Processing
       Staff (Owner): -- Unassigned --
                Type: Issue
              Status: Open
            Priority: Default
      Template Group: Default
             Created: 19 August 2013 06:38 PM
             Updated: 19 August 2013 06:38 PM
                 Due: 20 August 2013 06:38 PM (1d 0h 0m)
      Resolution Due: 21 August 2013 06:38 PM (2d 0h 0m)



I have for the second time recently encountered a peculiar issue with the NX tables of single source (and single scan) data.

The single-source data were created by SPLIT. After then performing a task that creates a new NX table (e.g., CALIB or UVCOP), the resulting NX table erroneously breaks the scan into two pieces. For example:

Before UVCOP:
COL. NO.           1               2              3              4             5             6            7
     ROW      TIME            TIME INTER      SOURCE ID      SUBARRAY      START VIS      END VIS      FREQ ID
  NUMBER      D/HMS           D/HMS
       1      06:24:14.3      00:01:31.0          1              1             1           29900          1

After UVCOP:
COL. NO.           1               2              3              4             5             6            7
     ROW      TIME            TIME INTER      SOURCE ID      SUBARRAY      START VIS      END VIS      FREQ ID
  NUMBER      D/HMS           D/HMS
       1      06:24:13.8      00:01:30.0          1              1               1         29575          1
       2      06:24:59.8      00:00:00.0          1              1           29576         29900          1

I noticed this because the results of BPASS were affected. This problem is fixable by re-creating the NX table with INDXR and it does not seem to occur with all data sets. However, it goes away entirely in 31DEC11, so I thought it worth reporting.

Lynn Matthews

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