AIPS HELP file for VLBATECR in 31DEC18
As of Wed Jun 20 22:27:26 2018
VLBATECR: Procedure to calibrate ionospheric delay
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)
VLBATECR is defined in the VLBAUTIL run file.
Use: Automatically download IONEX files needed to correct the
ionospheric dispersive delay with TECOR. Then runs TECOR.
See EXPLAIN TECOR for more information on this correction.
To do the automatic download the system must have one of
the following commands: wget, curl or ncftpget, and an NX
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.
VLBATECR: Procedure that corrects ionospheric dispersive delay
using TECOR. This procedure automatically downloads
the IONEX files from the CDDIS archive.
DOCUMENTOR: Amy Mioduszewski, NRAO
RELATED PROGRAMS: VLBAUTIL, TECOR
VLBATECR 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 details on the ionospheric correction.
This procedure is defined in VLBAUTIL, type RUN VLBAUTIL to load
To run VLBATECR:
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 or VLBAFIX to create.
3) The system must have one of the following commands: wget, curl or
ncftpget. VLBATECR will test for the existence of these commands
in the order given above and will 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.
VLBATECR should be run on data of 8 GHz and lower, and can be run
anytime before the last fringe fit and after VLBAFIX. For simplicity,
it is recommended that it be run right after VLBAFIX or VLBAEOPS, so
all corrections to the data are done before calibration.