[daip] FITLD ZABORS on DiFX data

Walter Brisken wbrisken at nrao.edu
Tue Mar 11 15:13:38 EDT 2008


I have encountered a problem when using FITLD on some software correlator 
data.  I'm not sure if it is a bad FITS file or a problem in FITLD, but 
FITLD is probably the best diagnostic of the problem.

The FITS file in question is

/home/parallax/ZABORS.FITS

The last few lines that FITLD produces are:

FITLD1: Current file has     2724 visibilities
FITLD1: File ref. freq:     1612.23 MHz
FITLD1: Found 3C345            at   0/14:33:43 src #   1
FITLD1:                                        fqid #   1
FITLD1: Found W75N             at   0/14:49:56 src #   2
AIPS 1: Resumes
>FITLD1: UV table spanned time:   0/14:33:43 -  0/15:05:28
FITLD1:     2724 vis. written
FITLD1: PHINI: 'PC_FREQ_1' COLUMN HAS NO VALUES
FITLD1: PHINI: 'PC_REAL_1' COLUMN HAS NO VALUES
FITLD1: PHINI: 'PC_IMAG_1' COLUMN HAS NO VALUES
FITLD1: PHINI: 'PC_RATE_1' COLUMN HAS NO VALUES
FITLD1: PHINI: 'PC_FREQ_2' COLUMN HAS NO VALUES
FITLD1: PHINI: 'PC_REAL_2' COLUMN HAS NO VALUES
FITLD1: PHINI: 'PC_IMAG_2' COLUMN HAS NO VALUES
FITLD1: PHINI: 'PC_RATE_2' COLUMN HAS NO VALUES
FITLD1: ZABORS: signal 11 received
FITLD1: ABORT!


I don't suspect the PHINI lines are relevant as I see those whenever I 
don't populate the pulse cal values (this expt didn't observe with them), 
and in the past all such files loaded fine.  I make the PH table since the 
monitor data does have state counts.

If its not too much trouble, could someone push this FITS file through 
FITLD running in a debugger?

Thanks,

Walter




More information about the Daip mailing list