       % -*- latex -*-
%-----------------------------------------------------------------------
%;  Copyright (C) 2024
%;  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 2024
\documentclass[twoside]{article}
\usepackage{graphics}

\newcommand{\AIPRELEASE}{December 31, 2024}
\newcommand{\AIPVOLUME}{Volume XLIV}
\newcommand{\AIPNUMBER}{Number 2}
\newcommand{\RELEASENAME}{{\tt 31DEC24}}
\newcommand{\OLDNAME}{{\tt 31DEC23}}
\newcommand{\NEWNAME}{{\tt 31DEC25}}
\newcommand{\Tsys}{${\rm T}_{\rm sys}$}
\newcommand{\THISYEAR}{2024}
\newcommand{\NEWYEAR}{2025}
\newcommand{\OLDYEAR}{2023}


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

\newcommand{\MYSpace}{-11pt}
\normalstyle

\section{General developments in \AIPS}

\subsection{\Aipsletter\ publication}

We have discontinued paper copies of the \Aipsletter\ entirely, at least
for this issue.  The \Aipsletter\ will be available in PostScript and
pdf formats as always from the web site listed above.  New issues will
be announced on the {\tt bananas} and {\tt mnj} list servers and
sometimes in the NRAO eNews.

\subsection{Current and future releases}

\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}\@.

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 {\it and} ARM chips), and Linux
(64-bit) systems, but all architectures can do a full installation
from the source files.  There are no longer binary versions available
for 32-bit Linux, Solaris, and Mac PPC chip architectures.  If you
develop \AIPS\ code locally {\it or have system managers that forbid the
  use of\/} {\tt rsync}, 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 rsync} 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 186-Mbyte {\tt \NEWNAME.tar.gz}
compressed tar file.

\vfill\eject

If compiling locally, new releases must be installed from the tar ball
for that release.  {\tt 31DEC22} 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).  A new installation will not change your current \AIPS\
data files.

{\tt 31DEC15} contains a change in the headers of $uv$ data sets which
will not be understood by previous versions.  {\tt 31DEC20} contains a
change to the {\tt XAS} TV server which will cause problems with older
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, five new tasks appeared.  The tasks are
{\tt UNSPX} to correct an image cube for spectral index, {\tt TVSPX} to
compute spectral index interactively from an image cube, {\tt QBEAM} to
compute and plot beam images from holography data, {\tt ALBUS} to fit
ionospheric Faraday rotation and dispersive delay, and {\tt RIFRM} to
convert {\tt ALBUS} text output to values in a {\tt CL} table.  New
verbs {\tt SGUGET}, {\tt TGUINDEX}, and {\tt SGUINDEX} also appeared to
assist in moving task parameters and \POPS\ environments between users.
In the first six months, there was one new task, one new verb and one
new {\tt RUN} procedure in \RELEASENAME\@.  These are, respectively,
{\tt VH2RL} to convert a data set between linear and circular
polarization basis, {\tt STARTTV} to restart the TV, message, and
Tektronix servers, and {\tt CALMODEL} to compute a model data set to be
used with a new option in {\tt CALIB}\@.

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, not describing temporary bugs in {\tt TST} 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 science user 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{System matters}

Due to the ``end of life'' for RedHat 7, we chose to freeze {\tt
  31DEC23} completely in June 2024.  In this way, the binary version
for {\tt LNX64} could remain as produced by RedHat 7.  {\tt 31DEC24} for
64-bit Linux was then re-compiled with RedHat 8, producing a binary
version incompatible with the older operating system.  At the same time,
we discontinued any development of the 32-bit Linux binary version.
That version is available in binary form but only up to June 20, 2024.
{\tt 31DEC25} will not contain a binary version for 32-bit Linux.  Old
Linux systems left behind by  these actions should note that it is
relatively easy to compile all of \AIPS\ on whatever machine you may
have.  Versions of {\tt gfortran} at least 4.8, but better 6 or more,
are required.  The latest {\tt gfortran} versions should also work.

The {\tt MACARM} binary version of {\tt 31DEC24} is computed on a
machine that was upgraded to ``Sonoma'' (OS version 14.6.1) with a
gfortran upgraded to version 12.2.  The load modules should work on
any system at 13.0 or greater.  The {\tt 31DEC23} version was frozen
at the previous operating system level.  The {\tt MACINT} binary version
continues to be developed, but if the computer used to produce it dies,
our support for that binary version will halt.  Again, you should note
that compiling \AIPS\ locally should go right on working.

{\tt LNX64} now requires two ``containers'' to support the new task {\tt
  ALBUS} (see below).  They should be copied by rsync either by {\tt
  install.pl} or in the MNJ even for text (locally-compiled)
installations.

\subsection{Ionospheric calibration}

Studies of linear polarization of the Moon at low frequency on the VLA
have shown that \AIPS\ task {\tt TECOR} removes the time-dependent
Faraday rotation quite well but, in general, over corrects those data
by an amount that is nearly constant with time and source on any given
day, but which changes some with date.  The previous default TEC file
named {\tt jplg} was found always to produce the greatest
over-correction.  Therefore, the default {\tt TECRTYPE} was changed to
{\tt emrg} which produces a smaller over-correction normally.

An alternative regional model is provided by the program {\tt ALBUS}
(Advanced Long Baseline User Software), developed by James Anderson
initially at New Mexico Tech and then at Lofar in Europe.  Originally
intended to enable phase corrections for VLBI observations, the program
has been modified to enable IFRM estimates.  {\tt ALBUS} derives a local
estimate of the IFRM using the GNSS timing data from ground stations
within a few hundred kilometers of a specified location, and a realistic
distribution of electron density with height.  This software is now
supported and made publicly available by Tony Willis of the Dominion
Radio Astrophysical Observatory.  With his help, Evangelia Tremou of the
NRAO converted the code into a ``container'' which may be used by
\AIPS\@.  A new task, also called {\tt ALBUS}, was written to invoke the
container with parameters suitable to the date, sources, and antennas
found in an \AIPS\ data set.  The task waits for the container to finish
and then converts the text-file report(s) into entries in a {\tt CL}
table for Faraday rotation and dispersive delay.  After much study, it
was found that {\tt ALBUS} produced almost perfect answers for most of
the Moon data sets and better answers than {\tt TECOR} always.  See EVLA
Memo 235 for details.

Sadly, the implementation of {\tt ALBUS} breaks some rules used in
designing \AIPS\@.  It requires that the user install an outside program
called {\tt apptainer} which is readily available for Linux.  However,
it does not work in any reasonable way on Macs.  The \AIPS\ task writes
two text files, a python script and a shell script to execute the python
using the container.  There are two containers shipped with \AIPS, a
recent version and an older version of the {\tt ALBUS} control scripts.
The latter uses different web sites and tends to find rather fewer data
sources.  Surprisingly, the version with fewer data sources often is
slightly superior to the more recent one.  Whether this applies
generally or only to our particular VLA data sets is not known.

A column giving the dispersive delay was added to the {\tt TE} table
format.  This delay is negligible for compact arrays such as the VLA and
MeerKAT, but is quite significant in VLBI data.  An {\tt OPTYPE =
  'DIFF'} was added to {\tt TEPLT} so that ionospheric solutions from
different sources may be compared.

\subsection{Verbs and documentation}

The relatively new verb {\tt TUGET} allows a user to do a {\tt TGET}
from a different user number.  It was enhanced to use {\tt INDISK} to
refer to that user's disk number one (where the {\tt TG} files are
stored).  Three new verbs were created to extend this capability.
{\tt SGUGET} allows a user to {\tt GET} a \POPS\ environment from a
different user number.  {\tt TGUINDEX} and {\tt SGUINDEX} allow the
user to see what tasks and files are available to {\tt TUGET} and
{\tt SGUGET}\@.  Current \AIPS\ usage normally involves a single human
being on a computer, but with multiple projects run under different
user numbers.  These new verbs allow work done under one user number to
benefit the projects being done under different user numbers.

The new verb {\tt STARTTV} was given a synonym {\tt TVRESTOR} to
restart the TV, Tek, and message servers without exiting the {\tt AIPS}
program.  The {\tt GETITIME} verb, which attempts to determine the
integration time in a $uv$ data set, was enhanced to examine a user
selected portion of the data set to insure that the {\tt INTTIME} random
parameter is constant.  If that parameter is not present in the data
set, the verb looks at the increments in time of the data samples and
returns its best guess but other possibilities are displayed in
messages.

The verbs {\tt INP}, {\tt INPUTS}, and {\tt QINP} did not display
adverbs which are solely used as outputs from verbs and tasks.  The user
was expected to use the verb {\tt OUTPUTS} to examine such adverbs.  But
that assumed that the user knew that there were output adverbs and knew
about using {\tt OUTPUTS}\@.  The inputs verbs were changed to display
output adverbs as well and the inputs sections of all affected verbs and
tasks were changed to mark the output adverbs clearly.

The verb {\tt PRTHI} has the ability to limit its display to those lines
starting with a user-specified character string, usually the verb or
task name.  The adverb {\tt KEYSTRNG} was added to limit the display to
any line containing that string.  Either or both may be applied.  The
verb was also changed to request the display to occur in backwards
order, thus displaying the most recent history first.  If {\tt PRTASK}
is not specified, the display is done strictly in inverse order.  If it
is specified, each group of history records from that task is displayed
in order starting with the most recent group and working backwards.

When minimum match fails, \eg\ {\tt HELP T }, the {\tt AIPS} program
prints a list of the possible completions.  That display, which was
limited to 64 values, is now limited to 256 which should never be
reached.

The \Cookbook\ was systematically updated in March, June, October, and
late November.  The shopping lists in Chapter 13 were corrected in March
and April so that they would display properly in the web-capable pdf and
jpg versions of the \Cookbook\@.  The TAB completion, {\tt APROPO}, and
{\tt ABOUT} text files were updated at the same time.  The help files
for adverbs contain lists of the verbs, procedures, and tasks which use
them.  These were also updated regularly.

\subsection{UV data}

\begin{description}
\myitem{BPASS} and {\tt CPASS} were changed to drop {\tt DOBAND} and
       {\tt BPVER}\@.  Bandpass tables are not cumulative, making this
       option erroneous.
\myitem{ANTAB} was changed to allow much larger input data files.
\myitem{FITLD} was changed to honor the {\tt SOURCES} adverb when
       writing {\tt PC} and {\tt TY} tables.  Having ``unknown'' sources
       in these tables confused later tasks.
\myitem{CVEL} was changed to have the correct number of columns in the
       {\tt SU} table.
\myitem{UVHOL} was changed to plot scans on diagonal tracks as well as
       vertical and horizontal tracks.  The plotting was made
       forgiving when some samples in a track are flagged.
\myitem{PBEAM} was given an additional display of the beam major and
       minor axes.
\myitem{QBEAM} is a new task to compute images from holography data and
       plot and/or save them like {\tt PBEAM} but without the model
       fitting.  This would be most useful with data in Stokes Q, U, and
       V\@.
\myitem{Pulse-cal} routines for the many pulse data sets were changed
       to display the antenna number where appropriate.
\end{description}

\subsection{Imaging and Display}

There are two new tasks for processing spectral-index cubes.  {\tt
  TVSPX} is similar to {\tt SPIXR} in that it fits a spectral index to
each pixel in an image cube.  It then displays images of the spectral
parameters and offers options to revisit pixels that appear incorrect.
The user may flag data channels at the selected pixels to see if a
better fit can be obtained with the remaining points.  The second new
task, {\tt UNSPX} takes the output of {\tt TVSPX} or {\tt SPIXR} and
applies it to an image cube to remove the spectral index.  The initial
use of this task was to remove the Stokes I spectral index from the
Stokes Q and U cubes in order to study the changes in polarization with
frequency.

Plot files in \AIPS\ are a non-standard data structure that cannot be
represented as a standard table.  There are in fact 19 record types of
a variety of lengths including data-dependent lengths.  As a result,
FITS files written by \AIPS\ have omitted plot files, causing them to be
lost when data are backed up.  {\tt FITTP} and {\tt FITAB} have been
changed to offer the option of saving plot files within the output FITS
files.  The format that is used for simplicity is a literal copy of each
1 kilo-byte file record as if it contained 256 integers.  {\tt FITLD},
{\tt UVLOD}, and {\tt IMLOD} were then changed to read this ``table''
back in reproducing the plot file.

\begin{description}
\myitem{SETFC} was given the {\tt REFREQ} adverb to specify the
         reference frequency used to recommend {\tt CELLSIZE} and {\tt
           IMSIZE}\@.  The new default is the highest frequency,
         replacing the header frequency used previously.
\myitem{DFTPL} was given an {\tt OUTTEXT} option and multi-Stokes
         capabilities {\tt 'HALF'}, {\tt 'IQU'}, and {\tt 'FPA'} where
         the last is {\tt 'IQU'} converted to fractional polarization,
         total polarization, and polarization angle.
\myitem{MARSP} was enhanced with the {\tt PIXRANGE} adverb, control over
         the number of boxes, and removal of the 90 degree offset
         options.
\myitem{LEVS} displays on contour images were improved and problems with
         negative {\tt ZINC} in {\tt KNTR} were corrected.
\myitem{POSSM} was changed to not plot {\tt PP} table error bars by
         default and the handling of the stop time was corrected.
\myitem{TVCPS} was given an {\tt RGBCOLOR} adverb to set the color to be
         used instead of pure 0 (black) in the background.
\end{description}

\section{Recent Memoranda}

All \AIPS\ Memoranda are available from the \AIPS\ home page.  Memo 123
was revised to add further descriptions of the multiple pulse-cal data.
Memo 117 was revised to describe the new plot ``tables'' and to update
the descriptions of {\tt SY}. {\tt BD}, {\tt PP}, and {\tt TE} tables.
EVLA Memo 235 is of special interest also.

\begin{tabular}{lp{5.8in}}
{\bf 117} & {\bf \AIPS\ FITS File Format}\\
   &  Eric W. Greisen, NRAO\\
   &  November 1, 2024 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 is
  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 VLA and VLBA\@.
\end{tabular}

\begin{tabular}{lp{5.8in}}
{\bf 123} & {\bf New Pulse-cal Capabilities for VLBI in \AIPS}\\
   &  Eric W. Greisen, NRAO\\
   &  December 11, 2024 revision\\
   &  The DiFX correlator has acquired the capability of measuring and
recording large numbers of pulse-cal tones, typically at intervals of
1 MHz through each spectral window.  These pulse-cal tones have very
high signal-to-noise, but show a roll-off at the edges of each
spectral window and usually have one or more single channels which
have amplitude and residual phase differing significantly from the
average for the spectral window.  \AIPS\ has acquired the ability to
deal with these data including new tasks to display and edit them and
to derive calibration from them.  This memo was revised in December
2024 to add additional descriptions of typical many-tone {\tt PC}
tables.
\end{tabular}

\begin{tabular}{lp{5.8in}}
{\bf 235} & {\bf Testing Ionospheric Faraday Rotation Measure Models}\\
   &  Rick Perley, Eric Greisen, Lilia Tremou, Bryan Butler, NRAO\\
   &  Tony Willis, DRAO \\
   &  October 21, 2024 revision {\bf EVLA Memo Series}\\
   &  We test the accuracy of ionospheric Faraday rotation measure
      estimates derived from global models of the vertical total
      electron content using the \AIPS\ task {\tt TECOR}, and from two
      versions using a regional model derived from ground station data
      using the {\tt ALBUS} program. We use six VLA P-band lunar
      observations to make these tests. We find that all models remove
      the day/night change in Ionospheric Faraday Rotation Measure
      (IFRM) with an accuracy better than 0.1 rad/m2. However, all
      global models introduce an offset in the IFRM of 0.5 to 1.0
      rad/m2. This offset varies from day to day, and is nearly
      constant within a given observation. Both of the
      regionally-derived {\tt ALBUS} IFRM estimates are closer to the
      actual IFRM than any of the global models. Based on these
      observations, the {\tt ALBUS} model provides IFRM estimates
      correct to about 0.2 rad/m2.
\end{tabular}

\section{Patch Distribution for \OLDNAME}

Normally, this section lists the patches that have been released for
\OLDNAME\@.  This was based on the assumption that users would want to
download individual files to compile them locally.  However, the
``Midnight Job'' ({\tt \$HOME/do\_daily.}{\it hostname}) will do this
for you on both locally-compiled and binary installations.  Therefore
there is no reason to continue the old procedure.  Major bug corrections
were moved to \OLDNAME\ as they occur and users should use the MNJ on
occasion on both the {\tt NEW} and {\tt TST} versions of \AIPS\@.

The \OLDNAME\ release is still available for installation, but is not
recommended and will no longer receive patches even for egregious
errors.  It had a number of important patches during \THISYEAR, but,
because of the ``end of life'' issues described above, no patches were
made after June 18, 2024.  The patches from before then are
\begin{enumerate}
  \item\ {\tt VBRFI}, {\tt VLBRF}, {\tt PLRFI} needed another digit for
    P-band and  needed corrections in plot scaling. {\it 2024-01-11}
  \item\ Unlike {\tt IMHEAD}, {\tt IM}{\it x}{\tt HEAD} verbs did not
    display keyword values. {\it 2024-01-18}
  \item\ {\tt VLBAUTIL.001} and {\tt VLAPROCS.001} needed a better if
      statement to set the downloaded file name for {\tt TECOR}\@. {\it
        2024-01-26}
  \item\ Amplitude calibration for delay errors applied a correction to
      EVLA data that is only appropriate for VLBA data. {\it 2024-02-22}
  \item\ {\tt POSSM} needed to set {\tt SOLINT} to 0 for {\tt BD} tables.
      {\it 2024-02-27}
  \item\ {\tt POSSM} plotted the X axis incorrectly. {\it 2024-03-11}
  \item\ {\tt XAS.SHR} changed to reorder the close down operations.
      Macs do not finish the routine when X windows are closed.
      {\it 2024-05-15}
  \item\ {\tt install.pl} misidentified the {\tt MACARM} architecture as
      {\tt MACINT}. {\it 2024-05-15}
  \item\ The rsync host will be renamed to {\tt rsync.aoc.nrao.edu};
      changed {\tt UPDCONFIG} and {\tt install.pl}. {\it 2024-05-29}
  \item\ {\tt POSSM} had problems plotting {\tt CP} tables and other minor
      issues. {\it 2024-06-04}
  \item\ {\tt FITLD} had trouble with rPICARD files (which do not
      exactly match the FITS standard but are usable) and forced there
      to be only one {\tt PC} table version. {\it 2024-06-04}
  \item\ {\tt SUBIM} did not set {\tt TRC} properly when the axis
      increment was more than one. {\it 2024-06-10}
  \item\ {\tt install.pl} needed to change {\tt ftp.aoc} to {\tt
      rsync.aoc} in a second place. {\it 2024-06-10}
  \item\ Changed fetching of TEC files to account for the different
      dates at which the file names changed format.
      {\it 2024-06-13}
  \item\ {\tt UVFIT} had errors in the number of adverbs and the usage of
       the Clean Component output file. {\it 2024-06-17}
  \item\ {\tt SPFLG} clip menu items were not addressed properly.
      {\it 2024-06-18}
\end{enumerate}

\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 284 different IP
addresses downloaded the frozen form of \OLDNAME\ and 470 IP
addresses downloaded \RELEASENAME\ in tarball or binary form.  With the
change to the MNJ (rsync only) we are unable even to guess how many
sites have run the MNJ\@.  The total number of unique IP addresses in
these five lists was 678, only 76 \% of last year.  The plot of numbers
versus time and the table shows that 2024 was slightly ahead of 2023
in the {\tt NEW}, but rather behind in the {\tt TST} numbers.

\begin{center}
\begin{tabular}{|rrrrrrrr|}
\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 & unique \\
\hline
2004 & {\tt 31DEC04} & {\tt 31DEC03} &  808 & 196 &      &     & 1276 \\
2005 & {\tt 31DEC05} & {\tt 31DEC04} &  832 & 246 &  299 &  48 & 1460 \\
2006 & {\tt 31DEC06} & {\tt 31DEC05} &  806 & 191 &  402 &  94 & 1398 \\
2007 & {\tt 31DEC07} & {\tt 31DEC06} &  965 & 277 &  669 & 161 & 1811 \\
2008 & {\tt 31DEC08} & {\tt 31DEC07} & 1058 & 246 &  986 & 303 & 2107 \\
2009 & {\tt 31DEC09} & {\tt 31DEC08} & 1228 & 307 & 1082 & 478 & 2399 \\
2010 & {\tt 31DEC10} & {\tt 31DEC09} & 1228 & 307 & 1203 & 477 & 2416 \\
2011 & {\tt 31DEC11} & {\tt 31DEC10} & 1105 & 270 & 1064 & 424 & 2228 \\
2012 & {\tt 31DEC12} & {\tt 31DEC11} &  940 & 284 & 1028 & 396 & 1698 \\
2013 & {\tt 31DEC13} & {\tt 31DEC12} & 1014 & 307 &  990 & 443 & 1937 \\
2014 & {\tt 31DEC14} & {\tt 31DEC13} & 1045 & 333 &  848 & 431 & 1843 \\
2015 & {\tt 31DEC15} & {\tt 31DEC14} & 1104 & 309 & 1001 & 350 & 1817 \\
2016 & {\tt 31DEC16} & {\tt 31DEC15} &  878 & 222 &  788 & 372 & 1330 \\
2017 & {\tt 31DEC17} & {\tt 31DEC16} &  874 & 408 &  768 & 386 & 1383 \\
2018 & {\tt 31DEC18} & {\tt 31DEC17} &  684 & 368 &  603 & 343 & 1099 \\
2019 & {\tt 31DEC19} & {\tt 31DEC18} &  754 & 406 &  686 & 388 & 1155 \\
2020 & {\tt 31DEC20} & {\tt 31DEC19} &  796 & 434 &  750 & 470 & 1230 \\
2021 & {\tt 31DEC21} & {\tt 31DEC20} &  659 & 399 &  604 & 376 & 1215 \\
2022 & {\tt 31DEC22} & {\tt 31DEC21} &  590 & 226 &  572 & 221 &  965 \\
2023 & {\tt 31DEC23} & {\tt 31DEC22} &  597 & 239 &  596 & 243 &  896 \\
2024 & {\tt 31DEC24} & {\tt 31DEC23} &  470 & 284 &  480 & 272 &  678 \\
\hline
\end{tabular}
\end{center}

\vfill
\centerline{\resizebox{!}{3.25in}{\includegraphics{FIG/PLOTIT2324all.eps}}}

\vfill\eject
%\vspace*{4in}
%\centerline{This page deliberately left blank.}
%\vfill\eject

% Order form and mailer page
%\cleardoublepage
\pagestyle{empty}
%\hphantom{...}
%\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}
