AIPS NRAO AIPS HELP file for VLATECR in 31DEC18



As of Tue Oct 16 10:35:33 2018


VLATECR: Procedure to calibrate ionospheric delay

INPUTS

INNAME                             Input UV file name (name)
INCLASS                            Input UV file name (class)
INSEQ             0.0     9999.0   Input UV file name (seq. #)
INDISK            0.0        9.0   Input UV file disk unit #
SUBARR                             Subarray to correct
                                     (0 => all)
APARM                              Switches
                                     (1) if > 0 correct for
                                         dispersive delay
                                     (2) Follow ionosphere
                                         factor
           VLATECR is defined in the VLAPROCS run file.

HELP SECTION

VLATECR
Type: Procedure
Use:  Automatically download IONEX files needed to correct the
      atmospheric Faraday rotation and optionally dispersive
      delay with TECOR.  Then runs TECOR.  See EXPLAIN TECOR
      for more information on these corrections.  To perform the
      automatic download the system must have one of the
      following commands: wget, curl or ncftpget, and an NX
      table.
      VLATECR is defined in the VLAPROCS run file.
Adverbs
  INNAME.....Input UV file name (name).      Standard defaults.
  INCLASS....Input UV file name (class).     Standard defaults.
  INSEQ......Input UV file name (seq. #).    0 => highest.
  INDISK.....Disk drive # of input UV file.  0 => any.
  SUBARR.....Subarray to correct.            0 => all.
  APARM......Miscellaneous settings and switches.
             (1) Enable (> 0.5) or disable (<= 0.5) dispersive
                 delay corrections.
             (2) In principle, it is thought that the ionosphere
                 remains approximately fixed wrt the Sun.  Thus, the
                 task should predict which ionosphere is now in the
                 direction of the source by applying a time correction
                 to the apparent longitude while interpolating between
                 the table values, which are only given every two
                 hours.  This sometimes seems in fact to do odd
                 things.  This parameter allows you to do only a
                 fraction of the time correction, from epsilon to 1.0.
                 0 -> 1; < 0 -> 0.  A correction of zero is equivalent
                 to a model in which the ionosphere rotates with the
                 earth.

EXPLAIN SECTION

VLATECR: Procedure that corrects the atmospheric Faraday rotation
         using TECOR.  This procedure automatically downloads the
         IONEX files from the CDDIS archive.
DOCUMENTOR: Amy Mioduszewski
RELATED PROGRAMS: VLAPROCS, TECOR

VLATECR is designed to make the use of TECOR easier.  It uses
the header and the NX table to calculate what files to download
from CDDIS.  It uses the CDDIS site in the US (cddis.gsfc.nasa.gov)
and downloads the jplg or codg version of the IONEX files.  Then it
runs TECOR using these files.  For simplicity (files from multiple
days must to have the same prefix), all the files are renamed with
the jplg prefix.  The IONEX files are left in the /tmp area of your
computer, so you can copy them for your records or ignore them.

See EXPLAIN TECOR for more information.

NOTE: The IONEX files can take up to a week to be available at
CDDIS.

This procedure is defined in VLAPROCS, type RUN VLAPROCS to load
VLAPROCS.

To run VLATECR:
   1) The dataset must have a correct observation date in the header;
      if it is wrong correct it with PUTHEAD.
      -> there is a weak test on the validity of the observation date;
         the observation year must be <= to the creation year.
   2) The dataset must have an NX table; run INDXR to create.
   3) The system must have one of the following commands: wget, curl or
      ncftpget.  VLATECR will test for the existence of these commands
      in the order given above and will use the first one it finds.
      Mac OS - will probably have curl; wget and ncftpget seem to be
      available in Fink.
   4) /tmp directory must exist on your computer
   5) Your computer must allow link to the Internet, some computers may
      have firewalls such that the above commands exist, but will not work.

AIPS