[daip] MCUBE file size

Eric Greisen egreisen at nrao.edu
Wed Jun 22 15:42:18 EDT 2016


On 06/22/2016 01:32 PM, Eric Perlman wrote:
> Hi Eric,
>
> Thanks - and thanks also for putting up with me on this.
>
> Just to reiterate what I'm trying to do, I'm trying to assemble cubes to
> do an RM analysis in DOFARS ... knowing full well that since there are
> 128 channels of only 16kHz width in each band (C and L) what I will be
> able to get will be limited.  This was your recommended path.
>
> FQUBE seems to run, with these inputs:
>  >inp fqube
> AIPS 1: FQUBE:  Convert FREQ/FREQID image cubes into larger FREQID cube
> AIPS 1: Adverbs     Values                 Comments
> AIPS 1: ----------------------------------------------------------------
> AIPS 1: INNAME     'NGC4845_RM'            Input name(name).
> AIPS 1: INCLASS    'QCL001'                Input name(class).
> AIPS 1: INSEQ         1                    Input name(seq. #). 0=>high
> AIPS 1:                                    First sequence # in the set
> AIPS 1: INDISK        2                    Input disk drive #. 0=>any
> AIPS 1: IN2SEQ        2                    Last sequence # in set.
> AIPS 1: IN3SEQ        0                    Sequence # increment.
> AIPS 1: OUTNAME    'NGC4845_RM'            Output name(name).
> AIPS 1: OUTCLASS   ' '                     Output name(class).
> AIPS 1: OUTSEQ        0                    Output name(seq. #).
> AIPS 1:                                      0 => highest unique
> AIPS 1: OUTDISK       2                    Output image disk drive #
> AIPS 1:                                      0 => highest with space
> AIPS 1: DOALIGN       1                    Alignment control parm
> AIPS 1: DOKEEP        1                    > 0 keep all planes including
> AIPS 1:                                    fully blanked missing CG
>  >
>
> this is the header of the file it produced:
>
>  >imh
> LOGFILE FOR USER 1806 GETTING LARGE: USE PRTMSG AND CLRMSG NOW!
> AIPS 1: Image=NGC4845   (MA)         Filename=NGC4845_RM  .FQUBE .   1
> AIPS 1: Telescope=VLBA               Receiver=VLBA
> AIPS 1: Observer=BP191               User #= 1806
> AIPS 1: Observ. date=08-OCT-2015     Map date=22-JUN-2016
> AIPS 1: Minimum=-3.76577675E-03      Maximum= 3.81711102E-03 JY/BEAM
> AIPS 1: ----------------------------------------------------------------
> AIPS 1: Type    Pixels   Coord value     at Pixel     Coord incr Rotat
> AIPS 1: RA---SIN  1024    12 58 01.197     512.00 -0.001000    0.00
> AIPS 1: DEC--SIN  1024    01 34 32.420     513.00 0.001000    0.00
> AIPS 1: FQID       256   1.0000000E+00       1.00 1.0000000E+00    0.00
> AIPS 1: STOKES       1   2.0000000E+00       1.00 1.0000000E+00    0.00
> AIPS 1: FREQ         1   1.3920000E+09       1.00 2.5000000E+05    0.00
> AIPS 1: ----------------------------------------------------------------
> AIPS 1: Coordinate equinox 2000.00
> AIPS 1: Map type=NORMAL              Number of iterations=     100
> AIPS 1: Conv size= 0.00926 X 0.00371   Position angle=  -2.83
> AIPS 1: Rest freq   1392.000         Vel type: OPTICAL wrt YOU
> AIPS 1: Alt ref. value  0.00000E+00  wrt pixel    0.00
> AIPS 1: Maximum version number of extension files of type FQ is 1
> AIPS 1: Maximum version number of extension files of type HI is 1
> AIPS 1: Maximum version number of extension files of type CC is 128
>
> However, it gave warning messages like this:
>
> LOCALH> FQUBE1: FQUBCG: COULD NOT FIND FREQ 1.392000E+09 IN OLD CG TABLE
> LOCALH> FQUBE1: FQUBCG: COULD NOT FIND FREQ 1.392250E+09 IN OLD CG TABLE
> LOCALH> FQUBE1: FQUBCG: COULD NOT FIND FREQ 1.392500E+09 IN OLD CG TABLE
> (256 of these)
> and, as you can see it did not copy over the CC tables from the 2nd
> image (as that would have meant 256 of those).

Note it says CG not CC - the CG table contains the restoring Clean beam 
for each channel and is useful if one wants to do further smoothing. 
But after CONVL the Clean beam is essentially the same in all channels 
and so the info is meaningless.  Try a PRTAB on the FQ table of the 
FQUBE output.  You should see a list of the actual frequencies of each 
plane.  That is all that FARS and RMFIT will need.

Eric Greisen



More information about the Daip mailing list