AIPS HELP file for TIORD in 31DEC22
As of Fri Dec 1 13:04:46 2023
TIORD: Checks for time/baseline ordering, displays failures
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 #
DOALL -1.0 1.0 > 0 -> ignore adverbs below
SOURCES Source name
QUAL -10.0 Calibrator qualifier -1=>all
CALCODE Calibrator code ' '=>all
STOKES Stokes selection
TIMERANG Time range to examine
SELBAND Bandwidth to select (kHz)
SELFREQ Frequency to select (MHz)
FREQID Freq. ID to select.
SUBARRAY 0.0 1000.0 Sub-array, 0=>all
BIF Low IF number to examine
EIF Highest IF number to examine
BCHAN 0.0 First channel included
ECHAN 0.0 last channel included
DOCALIB -1.0 101.0 > 0 calibrate data & weights
> 99 do NOT calibrate weights
GAINUSE CL (or SN) table to apply
DOPOL -1.0 10.0 If >0.5 correct polarization.
PDVER PD table to apply (DOPOL>0)
BLVER BL table to apply.
FLAGVER Flag table version
DOBAND -1.0 10.0 If >0.5 apply bandpass cal.
Method used depends on value
of DOBAND (see HELP file).
BPVER Bandpass table version
SMOOTH Smoothing function. See
HELP SMOOTH for details.
PRTLIMIT Print no more than PRTLIMIT
messages for time, antenna,
baseline errors, resp.
BADDISK Disks to avoid for scratch
Task: This task will check UV data to see if it is actually in time
and baseline order and will print any failure points.
Normally, all of the calibration adverbs should be set at 0 or
blank - you can use DEFAULT TIORD followed by setting FLAGVER
TO -1 and setting INDISK and doing GETNAME - but they are
included to diagnose cases that arise only when they are
applied. The visibility number is that after the application
of the data selection adverbs, calibration, flagging, etc. and
so will not match those in PRTUV unless all adverbs are set to
TIORD also check the baseline code which in AIPS is supposed to
be 256*A1 + A2 with A1 < A2. Any with the opposite will be
displayed (up to 100 printed lines) and all will be counted.
The task also checks baseline number order in case you care and
reports up to 10 such problems at the end.
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.
DOALL......> 0 -> use the simplest I/O to the uv file rather than the
calibration routines which put their own imprint on
<= 0 -> use the adverbs below. Note that if DOCAL or DOBL
are true, if DOBAND > 1, or FLAGVER >= 0 then the
data out of order are mentioned and skipped so no
real information other than the fact of out of order
SOURCES....Sources to be examined. ' '=> all; if any starts with
a '-' then all except ANY source named.
QUAL.......Qualifier of source to be examined. -1 => all.
CALCODE....Calibrator code of sources to examined. ' '=> all.
STOKES.....Specifies which STOKES parameters are found by the
calibration routines: ' ' => 'FULL'
'I','Q','U','V', 'IV', 'IQU', 'IQUV'
'RR','LL', 'RL', 'LR', 'RRLL', 'RLLR', 'RLRL'
'VV','HH', 'VH', 'HV', 'VVHH', 'VHHV', 'VHVH'
'HALF', 'CROS', and 'FULL' have sensible interpretations
depending on the Stokes present in the data. The last in
each of the 3 rows above == 'FULL'. Note that many
combinations of polarizations in the input and values
above are not supported.
TIMERANG...Time range of the data to be examined. In order: Start
day, hour, min. sec, end day, hour, min. sec. Days
relative to reference date.
SELBAND....Bandwidth of data to be selected. If more than one IF is
present SELBAND is the width of the first IF required.
Units = kHz. For data which contain multiple
bandwidths/frequencies the task will insist that some form
of selection be made by frequency or bandwidth.
SELFREQ....Frequency of data to be selected. If more than one IF is
present SELFREQ is the frequency of the first IF required.
Units = MHz.
FREQID.....Frequency identifier to select (you may determine which is
applicable from the OPTYPE='SCAN' listing produced by
LISTR). If either SELBAND or SELFREQ are set, their values
override that of FREQID. However, setting SELBAND and
SELFREQ may result in an ambiguity. In that case, the task
will request that you use FREQID.
SUBARRAY...Sub-array number to examine. 0=>all.
BIF........First IF to examine. 0 -> 1.
EIF........Last IF to examine. 0 -> max.
BCHAN......First channel to examine. 0=>all.
ECHAN......Highest channel to examine. 0=>all higher than BCHAN
DOCALIB....If true (>0), calibrate the data using information in the
specified Cal (CL) table for multi-source or SN table for
single-source data. Also calibrate the weights unless
DOCALIB > 99 (use this for old non-physical weights).
GAINUSE....version number of the CL table to apply to multi-source
files or the SN table for single source files.
0 => highest.
DOPOL......If > 0 then correct data for instrumental polarization as
represented in the AN or PD table. This correction is
only useful if PCAL has been run or feed polarization
parameters have been otherwise obtained. See HELP DOPOL
for available correction modes: 1 is normal, 2 and 3 are
for VLBI. 1-3 use a PD table if available; 6, 7, 8 are
the same but use the AN (continuum solution) even if a PD
table is present.
PDVER......PD table to apply if PCAL was run with SPECTRAL true and
0 < DOPOL < 6. <= 0 => highest.
BLVER......Version number of the baseline based calibration (BL) table
to apply. <0 => apply no BL table, 0 => highest.
FLAGVER....specifies the version of the flagging table to be applied.
0 => highest numbered table.
<0 => no flagging to be applied.
DOBAND.....If true (>0) then correct the data for the shape of the
antenna bandpasses using the BP table specified by BPVER.
The correction has five modes:
(a) if DOBAND=1 all entries for an antenna in the table
are averaged together before correcting the data.
(b) if DOBAND=2 the entry nearest in time (including
solution weights) is used to correct the data.
(c) if DOBAND=3 the table entries are interpolated in
time (using solution weights) and the data are then
(d) if DOBAND=4 the entry nearest in time (ignoring
solution weights) is used to correct the data.
(e) if DOBAND=5 the table entries are interpolated in
time (ignoring solution weights) and the data are then
IMAGR uses DOBAND as the nearest integer; 0.1 is therefore
BPVER......Specifies the version of the BP table to be applied
0 => highest numbered table.
<0 => no bandpass correction to be applied.
SMOOTH.....Specifies the type of spectral smoothing to be applied to
a uv database . The default is not to apply any smoothing.
The elements of SMOOTH are as follows:
SMOOTH(1) = type of smoothing to apply: 0 => no smoothing
To smooth before applying bandpass calibration
1 => Hanning, 2 => Gaussian, 3 => Boxcar, 4 => Sinc
To smooth after applying bandpass calibration
5 => Hanning, 6 => Gaussian, 7 => Boxcar, 8 => Sinc
SMOOTH(2) = the "diameter" of the function, i.e. width
between first nulls of Hanning triangle and sinc
function, FWHM of Gaussian, width of Boxcar. Defaults
(if < 0.1) are 4, 2, 2 and 3 channels for SMOOTH(1) =
1 - 4 and 5 - 8, resp.
SMOOTH(3) = the diameter over which the convolving
function has value - in channels. Defaults: 1,3,1,4
times SMOOTH(2) used when input SMOOTH(3) < net
PRTLIMIT...Specifies the maximum number of lines of print for
(1) Time ordering errors (0 -> 100)
(2) Antenna (baseline code) errors (0 -> 100)
(3) Baseline ordering errors (0 -> 10)
BADDISK....The disk numbers to avoid for scratch files (sorting