Date: Thu, 26 Jul 2012 12:38:43 -0400 (EDT)
From: Jun-Hui Zhao 
To: Claudia J. Cyganowski 
Subject: Re: miriad questions

Hi Claudia,
    For recent data, the antenna positions read directly from
the file 120711_03:23:40/antennas. The reference antenna position
should be zero. In early data, the antenna position is decoded
from the baselines, so the calculation requires reference antenna.
    I have tried all the tested observing modes for your 2012 MAR 16 data
but not successful. Looks like that observation used a peculiar
observing mode. I will take a close look next week after
submit a NRAO proposal.
    Jun-Hui


On Thu, 26 Jul 2012, Claudia J. Cyganowski wrote:

> Hi Jun-Hui,
>
> I also have a few other questions, mostly related to antenna positions.
 (1) Recently, antenna 6 has not been on pad 1 (or even in the array).
> The smalod mirhelp documentation (copied below) implies that the default
> assumes antenna 6 is on pad 1.  Does this mean that if antenna 2 is on pad
> 1, I need to specify the refant, e.g.
> smalod in='120711_03:23:40' out=g14_x rxif=0 sideband=2 refant=2
> ?
>
> Keyword: refant
>          The reference antenna. Default is 6. The reference antenna needs
>          to be present while the antenna positions are being decoded
>          from baseline vectors stored in SMA MIR data. The geocentrical
>          coordinates for the antennas can be retrieved from SMA sybase.
>          For double checking the antenna positions, one can login to
>          d2o.sma.hawaii.edu (IP:128.171.116.111) and use the following
>          command:
>          dBValue -d hal9000-newdds -v dsm_dds_hal_x_v11_d -t "2004-11-16
> 00:00:0
>          dBValue -d hal9000-newdds -v dsm_dds_hal_y_v11_d -t "2004-11-16
> 00:00:0
>          dBValue -d hal9000-newdds -v dsm_dds_hal_z_v11_d -t "2004-11-16
> 00:00:0
>          If the reference antenna is not the default value 6, one may need
>          If the reference antenna is not the default value 6, one may need
>          to give the reference antenna here.
>          For 4GHz data, it uses the reference antenna given in the
>          antenna table.
>
>
> (2) I have some tracks for which improved baseline solutions became
> available later.  What is the recommended approach for applying these?
> E.g. should I delete the antenna file attached to the dataset and copy
> over the new antenna file before running smalod?  Should I load the data
> with the original antennas file, then copy over the new antennas file and
> run uvedit?  (From the SMA miriad guide, it seemed like either would work,
> so I'm wondering which is preferred.)
>
> Also, I have some data taken during a move, so that I need to apply new
> positions to some antennas but not to others.  What is the recommended
> method for doing this?
>
> (3) When loading a recent dataset, I get a lot of messages about source
> ids (copied below).  I haven't seen messages like these before--what do
> they mean?
>
> Thanks very much,
> Claudia
>
> Warning: Mars has the source id (2) different from that (1) of 3c279
> but their coordinates are the same:
>  RA=12:56:11.1651  Dec= -5:47:21.5245
> Warning: found the next integration for Mars of id=2 at inhset=269 with
> coordinates:
>  RA=11:39:58.6416  Dec=  2:49:04.5162
> Update the coordinates for Mars of id=2
> Warning: Neptune has the source id (9) different from that (4) of cygob_7a
> but their coordinates are the same:
>  RA=20:32:45.5434  Dec= 40:39:36.6174
> Warning: found the next integration for Neptune of id=9 at inhset=927 with
> coordinates:
>  RA=22:20:54.8515  Dec=-10:56:10.9591
> Update the coordinates for Neptune of id=9
> Warning: bllac has the source id (10) different from that (4) of cygob_7a
> but their coordinates are the same:
>  RA=20:32:45.5434  Dec= 40:39:36.6174
> Warning: found the next integration for bllac of id=10 at inhset=1528 with
> coordinates:
>  RA=22:02:43.2912  Dec= 42:16:39.9756
>  RA=22:02:43.2912  Dec= 42:16:39.9756
> Update the coordinates for bllac of id=10
> Warning: MWc349a has the source id (11) different from that (10) of bllac
> but their coordinates are the same:
>  RA=22:02:43.2912  Dec= 42:16:39.9756
> Warning: found the next integration for MWc349a of id=11 at inhset=1546
> with coordinates:
>  RA=22:02:43.2912  Dec= 42:16:39.9756
> Update the coordinates for MWc349a of id=11
> sources found in the file........
> 3c279                 id=  1 RA=12:56:11.1651 DEC= -5:47:21.5245
> Mars                  id=  2 RA=11:39:58.6416 DEC=  2:49:04.5162
> MWC349a               id=  3 RA=11:40:00.0767 DEC=  2:48:53.9247
> cygob_7a              id=  4 RA=20:32:45.5434 DEC= 40:39:36.6174
> cygob_7b              id=  5 RA=20:34:13.2486 DEC= 41:08:13.4921
> 2015+371              id=  6 RA=20:34:15.7274 DEC= 41:08:13.4921
> cygob_8               id=  7 RA=20:15:28.7292 DEC= 37:10:59.5093
> cygob_9               id=  8 RA=20:34:10.6119 DEC= 41:06:56.9174
> Neptune               id=  9 RA=22:20:54.8515 DEC=-10:56:10.9591
> bllac                 id= 10 RA=22:02:43.2912 DEC= 42:16:39.9756
> MWc349a               id= 11 RA=22:02:43.2912 DEC= 42:16:39.9756
> uranus                id= 12 RA=00:00:00.0000 DEC=  0:00:00.0000
>
> ##########################################################################3