% -*- latex -*-
%-----------------------------------------------------------------------
%;  Copyright (C) 2019
%;  Associated Universities, Inc. Washington DC, USA.
%;
%;  This program is free software; you can redistribute it and/or
%;  modify it under the terms of the GNU General Public License as
%;  published by the Free Software Foundation; either version 2 of
%;  the License, or (at your option) any later version.
%;
%;  This program is distributed in the hope that it will be useful,
%;  but WITHOUT ANY WARRANTY; without even the implied warranty of
%;  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
%;  GNU General Public License for more details.
%;
%;  You should have received a copy of the GNU General Public
%;  License along with this program; if not, write to the Free
%;  Software Foundation, Inc., 675 Massachusetts Ave, Cambridge,
%;  MA 02139, USA.
%;
%;  Correspondence concerning AIPS should be addressed as follows:
%;          Internet email: aipsmail@nrao.edu.
%;          Postal address: AIPS Project Office
%;                          National Radio Astronomy Observatory
%;                          520 Edgemont Road
%;                          Charlottesville, VA 22903-2475 USA
%-----------------------------------------------------------------------
%Body of final AIPSletter for 31 December 2019

\documentclass[twoside]{article}
\usepackage{graphics}

\newcommand{\AIPRELEASE}{December 31, 2019}
\newcommand{\AIPVOLUME}{Volume XXXIX}
\newcommand{\AIPNUMBER}{Number 2}
\newcommand{\RELEASENAME}{{\tt 31DEC19}}
\newcommand{\OLDNAME}{{\tt 31DEC18}}
\newcommand{\NEWNAME}{{\tt 31DEC20}}
\newcommand{\Tsys}{${\rm T}_{\rm sys}$}
\newcommand{\THISYEAR}{2019}
\newcommand{\NEWYEAR}{2020}
\newcommand{\OLDYEAR}{2018}


%macros and title page format for the \AIPS\ letter.
\input LET98.MAC

\newcommand{\MYSpace}{-11pt}

\normalstyle

\section{General developments in \AIPS}

\subsection{Reduction of VLB,  VLA and ALMA data in \AIPS}

\AIPS\ continues to be the main software system for the reduction of
VLBI data from the VLBA and other telescopes.  Since 2010, there have
been numerous improvements to \AIPS\ that enable full calibration of
data from the Karl G. Jansky VLA and most imaging operations as well.
The one exception is the wide-band (bandwidth synthesis) deconvolution
algorithm (``MSMFS'') being developed in \CASA\ by Urvashi Rao
Venkata, for which there is no comparable function in \AIPS\@.
Calibrated $uv$ data may be exported from \AIPS\ in ``UVFITS'' format
for use in that program.  ALMA data may also be reduced in \AIPS,
although the package is not fully qualified to calibrate data from
linearly-polarized feeds.  Chapter 4 of the \AIPS\ Cookbook,
available via the \AIPS\ web site, was revised to describe the new
calibration operations.

\subsection{\Aipsletter\ publication}

We have discontinued paper copies of the \Aipsletter\ other than for
libraries and NRAO staff.  The \Aipsletter\ will be available in
PostScript and pdf forms as always from the web site listed above and
will be shipped with all distributions of \AIPS\@.  It will be
announced on the bananas and MNJ list servers and, usually, in the
NRAO e-News mailing.

\subsection{Current and future releases}

We have formal \AIPS\ releases on an annual basis.  We recommend a
full binary installation method for both the frozen and development
versions for MacIntosh OS/X (Intel chips only), and Linux (32- and
64-bit) systems, but all architectures can do a full installation from
the source files.  There are no longer binary versions available for
Solaris and Mac PPC chip architectures.  If you develop \AIPS\ code
locally {\it or have system managers that forbid the use of\/} {\tt
  rsync} or {\tt cvs}, you will need to do a source-level installation.
The current release is called \RELEASENAME\ and is now ``frozen.''  If
you took a development copy of this version at some earlier date, you
should use the ``Midnight Job'' (MNJ) to bring it up to date.  You need
to run a MNJ only once in \NEWYEAR\ to convert your copy of
\RELEASENAME\ into the frozen version.  However, when patches to
\RELEASENAME\ are announced in \NEWYEAR, you may apply them with the
MNJ\@.  This \Aipsletter\ is intended to advise you of corrections and
improvements in this release.

We have begun a new version, called \NEWNAME, which is now under
development by the \AIPS\ Group.  You may fetch and install a complete
copy of this version at any time.  Having fetched \NEWNAME, you may
update your installation whenever you want by running the MNJ\@.  This
uses {\tt cvs}, {\tt rsync}, and/or transaction files to copy all
changed text files and then to copy the binary files or to compile the
code selectively based on the code changes and compilations we have
done.  We expect users to take their source-only or binary version of
\NEWNAME\ \AIPS\ over the Internet (via \emph{anonymous} ftp).  Both
versions require you to copy the installation procedure {\tt
  install.pl} via {\tt ftp}; the source-only version also requires you
to ftp the 171-Mbyte {\tt   \NEWNAME.tar.gz} compressed tar file.
Binary installations use only {\tt rsync}, while locally compiled
versions also use {\tt cvs}.  Linux sites will almost certainly have
{\tt cvs} installed; other sites may have installed it along with
other GNU tools.  Secondary MNJs will still be possible using {\tt
  ssh} or {\tt rcp} or NFS as with previous releases.  We have found
that {\tt cvs} works very well, although it has one quirk. If a site
modifies a file locally, but in an \AIPS-standard directory, {\tt cvs}
will detect the modification and attempt to reconcile the local
version with the NRAO-supplied version.  This usually produces a file
that will not compile or run as intended.  Use a new name for the task
or put a copy of the task and its help file in a private disk area
instead.

\AIPS\ is now copyright \copyright\ 1995 through \THISYEAR\ by
Associated Universities, Inc., NRAO's parent corporation, but may be
made freely available under the terms of the Free Software Foundation's
General Public License (GPL)\@.  This means that User Agreements are no
longer required, that \AIPS\ may be obtained via anonymous ftp without
contacting NRAO, and that the software may be redistributed (and/or
modified), under certain conditions.  The full text of the GPL can be
found in the \texttt{15JUL95} \Aipsletter\ and is included with every
distribution in file {\tt \$AIPS\_ROOT/{\it release-name}/COPYING}\@.


\subsection{Installing a new version}

If compiling locally, new releases must be installed from the tar ball
for that release.  {\tt 31DEC15} and later versions contain
improvements to the code which should make local compilation more
reliable.  If using the binary installation, a full new installation
must also be done with {\tt rsync}.  When installing a new \AIPS\
release in a system that already has a previous release, we recommend
that {\tt install.pl} be used and that the previous release be left in
place, at least until the new installation has been verified.  If you
do this, then you will not have to re-edit the disk, printer, and tape
lists and can simply skip all those pages in the {\tt install.pl}
menus.  The old {\tt \$HOME/.AIPSRC} file may be left in place, but it
will need to be edited.  The lines giving the {\tt DOWNLOADED} and
{\tt UNPACKED} parameters should be cleared and the {\tt CCOMOPT} line
should be changed to point to the current release rather than the
previous one.  If you have made a special version of {\tt
  do\_daily.{\it host}}, you should preserve it under a new name and
restore it after the install. If you have an odd set of \AIPS\
versions, the {\tt \$AIPS\_ROOT/AIPSPATH.*SH} files may need to be
edited after the install to set the desired versions.  The file {\tt
  \$SYSLOCAL/UPDCONFIG} also needs to be edited to correct your e-mail
address(es).

{\tt 31DEC09} contains a change in the format of antenna files.
Previous releases will not understand the antenna coordinates for
arrays that were traditionally left-handed (VLBI primarily).  The
format change occurs automatically when any {\tt 31DEC09} or later
antenna-file specific code reads the file, after which older releases
will have difficulties.  {\tt 31DEC15} contains a change in the
headers of $uv$ data sets which will not be understood by previous
versions.  Note that the only version which we will patch for major
errors is \RELEASENAME; even \OLDNAME\ will no longer be changed.

%\section{Preview of coming attractions}

%The \NEWNAME\ release already contains a few changes that we decided
%were a bit risky or not needed in \RELEASENAME\@.

\section{Improvements of interest to users in \RELEASENAME}

In the latter half of \THISYEAR, new tasks appeared including {\tt
  UVADD} to compare two very similar $uv$ data sets, {\tt SYVSN} to
compare SysPower values to solution phases, {\tt XYMOD} to apply a
linear polarization point source model to a $uv$ data set, {\tt PPAPP}
to apply a {\tt PP} table from {\tt RLDIF} to a second data set, {\tt
  BLPLT} to plot {\tt BL} tables from {\tt BLCAL}, {\tt BPFLG} to flag
$uv$ data for high or low values in the bandpass table, and {\tt TADIF}
to compare selected columns from tables.  In the first half of 2019 only
one new task, {\tt FGPRT} appeared.  It prints a matrix of the number of
flags applying to each baseline.

Normally, bugs which appear in an \AIPS\ {\tt TST} version and then
are fixed in that same version before its release get little or no
discussion in the \Aipsletter\@.  Since a rather large number of sites
now install the {\tt TST} version of \AIPS\ during its development,
this is somewhat of an oversight.  We urge you to run the ``Midnight
Job'' at least once after \RELEASENAME\ is frozen to bring it up to
date and to fix all bugs of this sort.  We urge active sites to use
the MNJ and, when something odd occurs, to examine {\tt CHANGE.DOC}
using the cgi tool available from the \AIPS\ documentation web page
({\tt http://www.aips.nrao.edu/aipsdoc.html}).  Please do not
hesitate to contact us via the NRAO help desk ({\tt
  https://help.nrao.edu}) or via e-mail {\tt daip@nrao.edu} with any
questions or suspicions that there are problems.

\subsection{VLBI matters}

The VLB data reduction pipeline continued to get attention in the
reporting period.  Bugs affecting the saving of adverb values,
inserting the date string into full path names, and finding the correct
version of plot files were corrected.  The option to run {\tt CLIP}
before, or instead of, {\tt RFLAG} was added to both {\tt VLBARUN} and
{\tt VLBAMPHC}\@.  The option to run {\tt TYSMO} was added to {\tt
  VLBARUN} to replace bad system temperatures with nearby good ones.
The option to run {\tt UVFLG} to flag low elevation observations was
also added.  {\tt VLBAMPHC} was changed to copy flag table version 1
from the master file, avoiding the repetition of the {\tt UVFLG} options.
Both scripts run {\tt INPUTS} at the beginning so that the message file
contains the user's parameters.  The old pipeline script {\tt VLBAPIPE}
was removed to avoid user confusion.

\begin{description}
\myitem{DTSUM} was changed to apply the full suite of calibration
        adverbs to the data as they are read.  The flagging state of
        each scan is particularly relevant.
\myitem{APCAL} was corrected to close the {\tt FQ} table when an error
        occurs and to respond to error conditions more completely.
\end{description}

\subsection{UV data}

\begin{description}
\myitem{SNCOR} was changed to copy the input {\tt SN} table rather than
     changing (damaging) it in place.  {\tt VLBAUTIL} was changed to
     leave {\tt SNVER} zero so that all uses of {\tt SNCOR} get the
     highest version number.
\myitem{BPASS} was corrected to use the proper list of standard sources
     when finding the spectral index.  NaNs (not-a-number) are not
     likely to appear in the {\tt BP} solutions --- but they have ---
     prompting a routine to check for them.
\myitem{BPEDT} menu handling when there is only one time needed
     correcting.
\myitem{UVADD} is a new task to add, subtract, multiply, or divide two
     very similar $uv$ data sets.
\myitem{SYVSN} is a new task to compare SysPower values to solution
     table phases to measure the correlation of the two.  This might be
     a poor-man's water vapor radiometer.
\myitem{XYMOD} is a new task to compute a linear polarization point
     source model and then to subtract it from, divide it into, or
     replace a $uv$ data set.
\myitem{PRTAN} now offers the option of making a plot (file or TV) of
     the antenna locations.
\myitem{UVFLG} was corrected in the loop over subarray when flagging for
     shadowing.  It used antenna data for the highest subarray for all
     subarrays.  It also did way too much disk I/O\@.
\myitem{TIORD} was given the option to use direct disk access rather
     than going through the calibration routines.  The latter were found
     to skip data out of time order with no comment.  The calibration
     package was changed to issue a message about data being lost.
\myitem{UVCOP} was given the option to avoid scaling the $u, v, w$
     parameters for a change in reference frequency.  This scaling is
     wrong for holography data.
\myitem{RLDIF} and {\tt XYDIF} were changed to write a {\tt PP} table
     giving the correction phases when in spectral mode.  The ability to
     plot such tables was added to {\tt POSSM}\@.
\myitem{PPAPP} is a new task to apply the {\tt PP} table to additional
     data sets.
\myitem{TYAPL} was given the option to specify antennas which have bad
     {\tt SY} table values but would otherwise pass the {\tt CUTOFF}
     test.  They are given the average of the corrections for the good
     antennas.
\myitem{BLPLT} is a new task to plot {\tt BL} table values produced by
     {\tt BLCAL}.  It makes a {\tt BPLOT}-like plot with IF on the
     horizontal axis and all baselines to the selected antenna on the
     vertical axis.
\myitem{BPFLG} is a new task to flag visibility data for bad values in a
     bandpass table.  It does the {\tt FLAG ABOVE} and {\tt FLAG BELOW}
     operations of {\tt BPEDT} without all the plotting and interactive
     overhead.
\end{description}

\subsection{Imaging and Display}

{\tt IMAGR}, {\tt SCIMG} and {\tt SCMAP} were changed to correct the
residual image whenever the user has specified the Clean beam
dimensions.  The residual image is convolved (when possible) to the
resolution specified and the brightness units (``per beam'') corrected.
Bugs in the self-cal tasks preventing the interactive editing phase were
corrected.

\begin{description}
\myitem{TVWEDGE} and {\tt HUEWEDGE} were changed to allow the user to
        point to the left or right of the image to select a vertical
        wedge rather than a horizontal one.
\myitem{TVLABEL} was given the {\tt CBPLOT} option to add a Clean-beam
        plot to the label.  It was also added to tasks {\tt PLAYR}, {\tt
          TVSPC}, and {\tt TVIEW}.\@.
\myitem{TVIEW} was changed to plot a spectrum in the upper left corner
        when there is no ``reference'' image to be displayed there.
\myitem{UVPLT,} {\tt WIPER}, {\tt VPLOT}, and {\tt ANBPL} were corrected
        to retain proper source information even when selecting only one
        source from a multi-source data set.
\end{description}

\subsection{General}

The gfortran compiler versions 4.$x$, 7.$x$, and 8.$x$ have been noted
over the years to fail with the pseudo-array processor code when
employing dynamic memory with the base memory in a Fortran {\tt
  COMMON}\@.  Versions 5.$x$ and 6.$x$ did work with this coding.  To
allow users to compile \AIPS\ without worrying about versions of
gfortran, a major re-organization of the pseudo-AP code was undertaken.
In this re-write, the base memory is in the main routine of each AP
task.  Its name is then passed down to all subroutines, including the
``AP'' {\tt Q} routines, in call sequences.  The memory is still
allocated dynamically by a call to {\tt QINIT} and the resulting offset
is passed through the {\tt COMMON}\@.  Remarkably, this works with all
versions of gfortran and versions 6 and 7 were found to produce
identical results (including run time) in the {\tt Y2K} large test.

Apple Mac OS/X is rolling out a new version 10.15 that, famously, will
not run 32-bit load modules.  Fearing that our old Intel compiler was
producing same, we switched our {\tt MACINT} version to use gfortran
version 6.3.  Since then, we have had access to a brand new laptop
running 10.15.  It was found that the gfortran version runs nicely.
Surprisingly, we also found that an old {\tt 31DEC17} version ran
perfectly well also.  Thus, despite information to the contrary, all
binary versions of \AIPS\ should work on the new Mac OS\@.

\begin{description}
\myitem{\Cookbook} was updated on July 11, October 15, and November 25.
        The {\tt ABOUT} lists and tab completion and {\tt APROPOS} files
        were also updated at the same time.
\myitem{TADIF} is a new task which does a not very smart comparison of
        selected columns of two tables.  It may be used to determine
        what might be different between them when {\tt PRTAB} is too
        overwhelming.
\myitem{Compilation} requires a {\tt -c} most places but not in the {\tt
        Makefile} used to compile {\tt XAS}\@.  The compile procedures
        {\tt FC} and {\tt AIPSCC} were revised along with several {\tt
          FDEFAULTS.SH} and {\tt CCOPTS.SH} to correct this installation
        issue.
\end{description}

\vfill\eject
\section{\AIPS\ Distribution}

From the NRAO system logs, we count apparent MNJ accesses, downloads
of the tar balls, and {\tt rsync} accesses by unique IP address.
Since DSL and some university and other connections may be assigned
different IP addresses at different times, this will be a bit of an
over-estimate of actual sites.  However, a single IP address is often
used to provide \AIPS\ to a number of computers, so these numbers are
at the same time an under-estimate of the number of computers running
current versions of \AIPS\@.  In \THISYEAR, a total of 406 different IP
addresses downloaded the frozen form of \OLDNAME\ and 754 IP
addresses downloaded \RELEASENAME\ in tarball or binary form.  Fully
435 IP addresses accessed the NRAO cvs master.  Each of these has at
least installed some version of \AIPS, but with the change to the MNJ
we are unable even to guess how many sites have run the MNJ\@.  The
total number of unique IP addresses in these three lists was 1155.
The table below shows these numbers as a function of year since we
began recording them.  The plot of numbers versus time shows that 2019
exceeded 2018 by a bit, especially in the last half of the year.

\begin{center}
\begin{tabular}{|rrrrrrrrr|}
\hline
 & & & & & {\tt TST} & {\tt NEW} & & Total \\
\noalign{\vspace{-1mm}}
year & {\tt TST} name & {\tt NEW} name & \hspace{1em}{\tt TST} &
 \hspace{1em}{\tt NEW} & binary & binary &
 \hspace{1em}{\tt cvs} & unique \\
\hline
2004 & {\tt 31DEC04} & {\tt 31DEC03} &  808 & 196 &      &     &  797
 & 1276 \\
2005 & {\tt 31DEC05} & {\tt 31DEC04} &  832 & 246 &  299 &  48 &  982
 & 1460 \\
2006 & {\tt 31DEC06} & {\tt 31DEC05} &  806 & 191 &  402 &  94 & 1050
 & 1398 \\
2007 & {\tt 31DEC07} & {\tt 31DEC06} &  965 & 277 &  669 & 161 & 1385
 & 1811 \\
2008 & {\tt 31DEC08} & {\tt 31DEC07} & 1058 & 246 &  986 & 303 & 1667
 & 2107 \\
2009 & {\tt 31DEC09} & {\tt 31DEC08} & 1228 & 307 & 1082 & 478 & 1855
 & 2399 \\
2010 & {\tt 31DEC10} & {\tt 31DEC09} & 1228 & 307 & 1203 & 477 & 1914
 & 2416 \\
2011 & {\tt 31DEC11} & {\tt 31DEC10} & 1105 & 270 & 1064 & 424 & 1747
 & 2228 \\
2012 & {\tt 31DEC12} & {\tt 31DEC11} &  940 & 284 & 1028 & 396 & 1309
 & 1698 \\
2013 & {\tt 31DEC13} & {\tt 31DEC12} & 1014 & 307 &  990 & 443 & 1264
 & 1937 \\
2014 & {\tt 31DEC14} & {\tt 31DEC13} & 1045 & 333 &  848 & 431 & 1023
 & 1843 \\
2015 & {\tt 31DEC15} & {\tt 31DEC14} & 1104 & 309 & 1001 & 350 & 1070
 & 1817 \\
2016 & {\tt 31DEC16} & {\tt 31DEC15} &  878 & 222 &  788 & 372 &  761
 & 1330 \\
2017 & {\tt 31DEC17} & {\tt 31DEC16} &  874 & 408 &  768 & 386 &  644
 & 1383 \\
2018 & {\tt 31DEC18} & {\tt 31DEC17} &  684 & 368 &  603 & 343 &  461
 & 1099 \\
2019 & {\tt 31DEC19} & {\tt 31DEC18} &  754 & 406 &  686 & 388 &  435
 & 1155 \\
\hline
\end{tabular}
\end{center}

\centerline{\resizebox{!}{3.5in}{\includegraphics{FIG/Plot1819.eps}}}

\vfill\eject

\section{Recent \AIPS\ Memoranda}

All \AIPS\ Memoranda are available from the \AIPS\ home page.  \AIPS\
Memo 117 was revised to describe {\tt PP}, {\tt XG}, {\tt RM}, and {\tt
  ZE} tables, Memo 120 was revised to show {\tt CBPLOT}, and Memo 124
was revised to show {\tt CBPLOT} and plotting of the current spectrum
(in the absence of a reference image).

\begin{tabular}{lp{5.8in}}
{\bf 117} & {\bf \AIPS\ FITS File Format}\\
   &  Eric W. Greisen, NRAO\\
   &  October 14, 2019 revision\\
   &  \AIPS\ has been writing images and $uv$ data in FITS-format files
  for a very long time.  While these files have been used widely in
  the community, there is a perception that a detailed document in
  still required.  This memo is an attempt to meet that perception.
  \AIPS\ FITS files for $uv$ are conventions layered upon the standard
  FITS format to assist in the interchange of data recorded by
  interferometric telescopes, particularly by radio telescopes such as
  the EVLA and VLBA\@.
\end{tabular}

\begin{tabular}{lp{5.8in}}
{\bf 120} & {\bf Exploring Image Cubes in \AIPS}\\
   &  Eric W. Greisen, NRAO\\
   &  October 18, 2019 revision\\
   &  \AIPS\ has recently acquired powerful tasks to fit models to the
  spectral axis of image cubes.  These tasks are easier to run if the
  user is already familiar with the general structure of the data
  cube.  A new task {\tt TVSPC} has been written to assist in
  acquiring this familiarity.  This task provides an exploration tool
  within the \AIPS\ environment, rather than requiring users to export
  their cubes to one or more of the many excellent visualization tools
  now available.  In the {\tt 31DEC17} version an additional data cube
  may be displayed one plane at a time.
\end{tabular}

\begin{tabular}{lp{5.8in}}
{\bf 124} & {\bf Further Exploration of Image Cubes in \AIPS}\\
   &  Eric W. Greisen, NRAO\\
   &  October 18, 2019 revision\\
   &  \AIPS\ has powerful tasks to fit models to the spectral axis of
  image cubes.  Tasks like {\tt XGAUS} and {\tt RMFIT} are easier to
  run if the user is already familiar with the general structure of
  the data cube.  Task {\tt TVSPC} was written to explore data cubes
  with emphasis on plots of spectra.  Now a new task {\tt TVIEW} has
  been written to explore data cubes with displays of
  position-velocity transpositions of the data cube.  This task
  provides an additional exploration tool within the \AIPS\
  environment, rather than requiring users to export their cubes to
  one or more of the many excellent visualization tools now available.
  {\tt TVIEW} offers the option of rotating the image in the celestial
  axes so that the position-velocity curves may be viewed along axes
  pertinent to the source, \eg\ the major axis.
\end{tabular}

\vfill\eject

\section{Patch Distribution for \OLDNAME}

Because of the extensive use of binary installations, we now patch the
master copy of the most recently frozen version.  Older versions are
not corrected even for egregious errors.  Thus, \OLDNAME\ was patched
during \THISYEAR\ and \RELEASENAME\ will be patched as needed during
\NEWYEAR.  Your copy of them may be corrected simply by running a
Midnight Job.  Information about patches and the code may be found using
links from the main \AIPS\ web page or by  {\it anonymous} \ftp\ to the
NRAO server {\tt ftp.aoc.nrao.edu}.  Documentation about patches to a
release is placed on this site at {\tt pub/software/aips/}{\it
  release-name} and the code is placed in suitable sub-directories
below this.  Patches to older releases are kept here as well, but they
will require local compilation.

The \OLDNAME\ release is no longer available for installation and will
no longer receive patches even for egregious errors.  It had a number
of important patches during \THISYEAR.  They are
\begin{enumerate}
 \item\ {\tt VBCAL} did not write the output data set. {\it 2019-01-18}
 \item\ {\tt TYCOP} and other tasks had the old number of columns for
   the SY table. {\it 2019-02-13}
 \item\ Model computation had problems when computing multiple {\tt CC}
   models. {\it 2019-03-05}
 \item\ Conversion of linear polarization to Stokes had a wrong
   sign. {\it 2019-03-05}
 \item\ {\tt TYSMO} applied clipping and flags inconsistently. {\it
   2019-03-05}
 \item\ {\tt FILIT} had an infinite loop displaying the image facets and
   did not handle the roam function properly. {\it 2019-03-28}
 \item\ {\tt KNTR} and other tasks truncated one of the ``brightness''
   strings. {\it 2019-04-03}
 \item\ {\tt OOSUB} did not do channel dependent division
   correctly. {\it 2019-04-10}
 \item\ {\tt SPIXR} did not handle sub-images with an {\tt FQ} axis
   correctly. {\it 2019-05-03}
 \item\ {\tt RFLAG} did not handle missing data correctly, making too
   many flags. {\it 2019-06-14}
 \item\ {\tt KNTR} computed the number of planes to plot poorly. {\it
   2019-06-14}
 \item\ {\tt BPWAY, RLCOR} did not change $uvw$ for {\tt BIF} greater
   than one. {\it 2019-06-14}
 \item\ {\tt TAPLT} tested for no data backwards and so did not do good
   plots. {\it 2019-06-21}
 \item\ {\tt BPASS} messed up some of the standard source spectral
   indices. {\it 2019-07-12}
 \item\ {\tt CLIP} messed up reporting its results for linear and other
   non-standard polarization data. {\it 2019-07-26}
 \item\ {\tt UVFLG} did not use the correct antenna data when looping
   over subarrays for shadowing. {\it 2019-08-22}
 \item\ {\tt BPWAY} did not close the table IO when looping over scans.
   {\it 2019-09-30}
 \item\ {\tt TYSMO} could ignore some flags when applying an {\tt FG}
   table to the {\tt TY}/{\tt SY} data. {\it 2019-11-18}
\end{enumerate}
\vfill\eject

% Order form and mailer page
%\cleardoublepage
\pagestyle{empty}
%\vfill
%\centerline{\resizebox{!}{23.3cm}{\includegraphics{FIG/AIPSORDER.PS}}}
\vfill\eject
\vbox to 4.4in{
\vspace{12pt}
%\centerline{\rotatebox{-90}{\resizebox{!}{3.5in}{%
%\includegraphics{FIG/Mandrill.color.plt}}}}
\centerline{\resizebox{!}{3.5in}{\includegraphics{FIG/Mandrill.eps}}}
\vspace{12pt}
\centerline{{\huge \tt \AIPRELEASE}}
\vspace{12pt}
\vfill}
\phantom{...}
\centerline{\resizebox{!}{!}{\includegraphics{FIG/AIPSLETS.PS}}}

\end{document}

