[daip] Problems with DBCON - 31DEC15
gcastell
gcastell at iafe.uba.ar
Mon Apr 20 11:21:33 EDT 2015
To whom it may concern,
I am working on two GMRT data sets obtained on February 15 and 17 (in
fact, I also have a third data set observed on 18Feb, please see below).
I am having difficulty combining the first two data sets using DBCON in
31DEC15 AIPS version.
The inputs that I used are the following:
AIPS 1: INNAME 'J1731feb15' dataset obtained Feb15
AIPS 1: INCLASS 'SPLIT'
AIPS 1: INSEQ 1
AIPS 1: INDISK 1
AIPS 1: IN2NAME 'J1731feb17' datase obtained Feb17
AIPS 1: IN2CLASS 'SPLIT'
AIPS 1: IN2SEQ 1
AIPS 1: IN2DISK 1
AIPS 1: REWEIGHT 0 0
AIPS 1: OUTNAME 'J1731feb1517'
AIPS 1: OUTCLASS ' '
AIPS 1: OUTSEQ 0
AIPS 1: OUTDISK 1
AIPS 1: DOPOS 1 1
AIPS 1: 1 1
AIPS 1: 1 1
AIPS 1: 1 0
AIPS 1: DOARRAY -1
AIPS 1: FQCENTER 1
The message from DBCON is:
localh> DBCON1: Task DBCON (release of 31DEC15) begins
localh> DBCON1: Scaling u,v,w of data set 1 by 1.0263917E+00
localh> DBCON1: Scaling u,v,w of data set 2 by 1.0263917E+00
localh> DBCON1: UV DATA TYPES ARE INCOMPATIBLE
localh> DBCON1: Purports to die of UNNATURAL causes
Both inputs files are single source data set, their headers are:
AIPS 1: Image=J1731-34 (UV) Filename=J1731feb15 .SPLIT . 1
AIPS 1: Telescope=GMRT Receiver=GMRT
AIPS 1: Observer= User #= 353
AIPS 1: Observ. date=14-FEB-2015 Map date=31-MAR-2015
AIPS 1: # visibilities 576457 Sort order TB
AIPS 1: Rand axes: UU-L-SIN VV-L-SIN WW-L-SIN BASELINE TIME1
AIPS 1:
----------------------------------------------------------------
AIPS 1: Type Pixels Coord value at Pixel Coord incr
Rotat
AIPS 1: COMPLEX 3 1.0000000E+00 1.00 1.0000000E+00
0.00
AIPS 1: STOKES 2 -1.0000000E+00 1.00 -1.0000000E+00
0.00
AIPS 1: FREQ 41 5.9204167E+08 1.00 7.8125000E+05
0.00
AIPS 1: IF 1 1.0000000E+00 1.00 1.0000000E+00
0.00
AIPS 1: RA 1 17 32 03.415 1.00 3600.000
0.00
AIPS 1: DEC 1 -34 45 16.603 1.00 3600.000
0.00
AIPS 1:
----------------------------------------------------------------
AIPS 1: Coordinate equinox 2000.00
AIPS 1: Rest freq 533.333 Vel type: RADIO wrt YOU
AIPS 1: Alt ref. value 0.00000E+00 wrt pixel 1.00
AIPS 1: Maximum version number of extension files of type NX is 1
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 AN is 1
AIPS 1: Maximum version number of extension files of type FG is 4
and for the 17Feb data:
AIPS 1: Image=J1731-34 (UV) Filename=J1731feb17 .SPLIT . 1
AIPS 1: Telescope=GMRT Receiver=GMRT
AIPS 1: Observer= User #= 353
AIPS 1: Observ. date=16-FEB-2015 Map date=08-APR-2015
AIPS 1: # visibilities 419578 Sort order TB
AIPS 1: Rand axes: UU-L-SIN VV-L-SIN WW-L-SIN SUBARRAY TIME1
AIPS 1: ANTENNA1 ANTENNA2
AIPS 1:
----------------------------------------------------------------
AIPS 1: Type Pixels Coord value at Pixel Coord incr
Rotat
AIPS 1: COMPLEX 3 1.0000000E+00 1.00 1.0000000E+00
0.00
AIPS 1: STOKES 2 -1.0000000E+00 1.00 -1.0000000E+00
0.00
AIPS 1: FREQ 41 5.9204167E+08 1.00 7.8125000E+05
0.00
AIPS 1: IF 1 1.0000000E+00 1.00 1.0000000E+00
0.00
AIPS 1: RA 1 17 32 03.415 1.00 3600.000
0.00
AIPS 1: DEC 1 -34 45 16.603 1.00 3600.000
0.00
AIPS 1:
----------------------------------------------------------------
AIPS 1: Coordinate equinox 2000.00
AIPS 1: Rest freq 533.333 Vel type: RADIO wrt YOU
AIPS 1: Alt ref. value 0.00000E+00 wrt pixel 1.00
AIPS 1: Maximum version number of extension files of type NX is 1
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 AN is 1
AIPS 1: Maximum version number of extension files of type FG is 5
I do not understand "the incompatibility in the uv" that DBCON found.
Looking for an answer to my problem, I tried to combine the 17Feb data
set with a third data set taken on 18Feb. Using the same
inputs as above, except that the first and second files are now
J1731feb17.SPLIT.1 and J1731feb18.SPLIT.1, the message from DBCON is:
localh> DBCON1: Task DBCON (release of 31DEC15) begins
localh> DBCON1: Scaling u,v,w of data set 1 by 1.0263917E+00
localh> DBCON1: Scaling u,v,w of data set 2 by 1.0263917E+00
localh> DBCON1: RA DOES NOT MATCH, BUT NOT DOING SHIFTS!
localh> DBCON1: UVPGET: RANDOM PARMS NOT ALL THERE: 0 1 2 4 -1 -1
-1 -1 -1
localh> 3 5 -1
This is completely different to the former DBCON message. Probably it
is indicating a new problem
with the data sets used this time.
Just in case, the header corresponding to the file named
J1731feb18.SPLIT.1 is
AIPS 1: Image=J1731-34 (UV) Filename=J1731feb18 .SPLIT . 1
AIPS 1: Telescope=GMRT Receiver=GMRT
AIPS 1: Observer= User #= 353
AIPS 1: Observ. date=17-FEB-2015 Map date=17-APR-2015
AIPS 1: # visibilities 450240 Sort order TB
AIPS 1: Rand axes: UU-L-SIN VV-L-SIN WW-L-SIN SUBARRAY TIME1
AIPS 1: ANTENNA1 ANTENNA2
AIPS 1:
----------------------------------------------------------------
AIPS 1: Type Pixels Coord value at Pixel Coord incr
Rotat
AIPS 1: COMPLEX 3 1.0000000E+00 1.00 1.0000000E+00
0.00
AIPS 1: STOKES 2 -1.0000000E+00 1.00 -1.0000000E+00
0.00
AIPS 1: FREQ 41 5.9204167E+08 1.00 7.8125000E+05
0.00
AIPS 1: IF 1 1.0000000E+00 1.00 1.0000000E+00
0.00
AIPS 1: RA 1 17 32 03.415 1.00 3600.000
0.00
AIPS 1: DEC 1 -34 45 16.603 1.00 3600.000
0.00
AIPS 1:
----------------------------------------------------------------
AIPS 1: Coordinate equinox 2000.00
AIPS 1: Rest freq 533.333 Vel type: RADIO wrt YOU
AIPS 1: Alt ref. value 0.00000E+00 wrt pixel 1.00
AIPS 1: Maximum version number of extension files of type NX is 1
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 AN is 1
AIPS 1: Maximum version number of extension files of type FG is 3
I really appreciate your help to solve these problems, because I have
not any idea what is wrong. Both DBCON results
are a surprise for me. I know that originally GMRT data had problems to
concatenate LTB and LTA sidebands, and that a couple
of scripts were written to deal with this. However, from the header of
my three data sets you can see that IF=1, so I
suspect that the LTA and LTB bands are not the cause that DBCON doesn't
work.
Thank you very much in advance,
Best Regards,
Gabriela Castelletti
More information about the Daip
mailing list