Opened 16 years ago

Closed 16 years ago

#45 closed defect (fixed)

F_int column not showing enough decimal places

Reported by: MatthewWhiting Owned by: MatthewWhiting
Priority: normal Milestone:
Component: Output Version: 1.1.6
Severity: normal Keywords:
Cc:

Description

When running on an image with large units (eg. Jy/beam) and weak sources (~few hundred uJy/beam), the F_int column just shows 0.000

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 Obj#           Name      X      Y     Z           RA          DEC     FREQ     w_RA    w_DEC   w_50   w_20 w_FREQ     F_int       F_tot      F_peak S/Nmax   X1   X2   Y1   Y2  Z1  Z2  Npix Flag   X_av   Y_av  Z_av X_cent Y_cent Z_cent X_peak Y_peak Z_peak
                                                                      [MHz] [arcmin] [arcmin]  [MHz]  [MHz]  [MHz]  [Jy MHz]   [Jy/beam]   [Jy/beam]                                    [pix]                                                                   
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    1 J123113-451450  829.0  801.0   0.0  12:31:13.85 -45:14:50.41 1420.000     0.33     0.20  0.000  0.000  0.000     0.000     0.00084     0.00011   6.22  827  831  800  802   0   0    11    E  829.0  801.0   0.0  829.0  801.0    0.0    829    801      0

The F_peak and F_tot columns seem to be fine, so just make F_int like them.

Change History (2)

comment:1 Changed 16 years ago by MatthewWhiting

Actually, maybe it's because the image is 2D and it doesn't do the integration just in 2D. Check this -- it should at least correct for the beam, even if there are no channels to integrate over.

comment:2 Changed 16 years ago by MatthewWhiting

Resolution: fixed
Status: newclosed

Yes, problem was that it didn't recognise a 2D image as it really had four axes (two of which had dimension 1).

Have instituted a series of small functions that check whether an image is really 2D, and added a flag to FitsHeader? that records that fact. Now seems to work. Checked in with [513].

Closing ticket.

Note: See TracTickets for help on using tickets.