NRAO
 

Astronomical Image Processing System

[AIPS]

New helpdesk

NRAO has instituted a "helpdesk" system similar to those at other astronomical institutions. AIPS will participate in this effort which is intended to avoid having problems fall between the cracks. The helpdesk is accessed via https://help.nrao.edu. Note that the help site will forward you to my.nrao to create a login if you do not already have one and the my.nrao site will then offer a tab to reach the helpdesk. The system for the AIPS "department" will make use of the daip@nrao.edu list manager system that we have used for years. Thus, unlike the rest of the NRAO helpdesk, messages to the AIPS portion will be made public in the daip archive. This archive is accessible via the web and is well known to Google among other things. Please switch to the new helpdesk to allow more systematic handling of your AIPS queries and bug reports.

Scheduled Releases

The development version 31DEC14 is available, the previous development version 31DEC13 is slushy, and the old frozen version 31DEC12 will soon be unavailable for installation. (A MNJ on 31DEC12, if it has not been run since October 24, 2013, might still be useful.) The new cvs form of the Midnight Job has been very easy to use and effective in keeping numerous sites up to date. In 2014, the MNJ will work sometimes on 31DEC13 if there has been a released patch. The 31DEC14 and 31DEC13 releases are also available as binary installations (and MNJs).

TeK and message server problems

Users have encountered problems getting the TeK and message servers to work in binary installations. These servers are programs which run in an xterm and that xterm must come up with some knowledge of AIPS libraries. This requires users to modify their login scripts (e.g. .cshrc file for c shell, .bashrc file for bash). See for details.

Linux compiler troubles

There appear to be problems with many of the versions of the gcc/g77 compiler suite. GNU compiler versions known not to work with AIPS include 2.96, 3.0.3, 3.0.4, and 3.3.x. Versions 3.2.2 and 3.4.3 and 3.4.4 are known to work. The new 4.0.x and 4.1.x are thought not to work with AIPS, but 4.2.1 (gfortran) appears to be okay. See the compiler installation notes for general instructions on installing GNU compilers.


WHAT IS AIPS?

Also, see the Users' FAQ: answers to Frequently Asked Questions, the AIPS Managers' FAQ: answers to AIPS Managers (and installers) Frequent Questions; and our page on who is in the AIPS group. The AIPS Manager FAQ page is especially helpful if you are having trouble getting the AIPS TV to run properly or are encountering other general difficulties or wish to configure new machines and disks in your AIPS environment.

THE CURRENT RELEASE

  • 31DEC14 is the new primary development version of AIPS. It is ready for installation. The 6-month progress report on 31DEC14 is available as 31DEC14 AIPSLetter dated 30 June 2014 (PS, 765430 bytes). It is also available gzipped, (329413 bytes) and PDF, (167320 bytes).
  • 31DEC13 is no longer primary development version of AIPS and will be frozen in 2014 except for bug patches. It is available for installation. The final report on 31DEC13 is available as 31DEC13 AIPSLetter dated 31 December 2013 (PS, 913097 bytes). It is also available gzipped, (396159 bytes) and PDF, (196866 bytes). The 6-month progress report on 31DEC13 is available as 31DEC13 AIPSLetter dated 30 June 2013 (PS, 3301312 bytes). It is also available gzipped, (453027 bytes) and PDF, (255543 bytes).
  • 31DEC12 is no longer available for installation. It will not be patched even for egregious errors. The final report on 31DEC12 is available as 31DEC12 AIPSLetter dated 30 December 2012 (PS, 919456 bytes). It is also available gzipped, (399961 bytes) and PDF, (210575 bytes). The 6-month progress report on 31DEC12 is available as 31DEC12 AIPSLetter dated 30 June 2012 (PS, 892100 bytes). It is also available gzipped, (389974 bytes) and PDF, (200356 bytes).
  • 31DEC06 and later releases contain a port to the MacIntosh OS/X system running on Intel cpus. This includes a full binary installation produced with Intel's compiler. An AIPSMark of 150 was obtained on our iMac which will be used to support this "new" architecture.
  • Since the end of January 2009, Linux systems running on 64-bit hardware with 64-bit operating systems have the choice of using LNX64 rather than LINUX as their AIPS architecture. The binary version for LNX64 is compiled with a recent 64-bit Intel compiler and runs somewhat faster than the LINUX version run on the same machines.
  • Since September 1, 2005 the binary versions for Linux are compiled with the Intel compiler version 9.0. They are compiled and linked with options that make the load modules rather large but allow them to run as well as possible on the latest threaded Pentium IVs, older Pentium IVs, and on general machines such as AMDs. Since November 30, 2004, binary installations for MacIntosh OS/X (IBM xlf compiler), Solaris Ultra (SUN compiler), and Linux (Intel 9.0) have been available. They are on the 31DEC05 and later versions. At present, all versions provide considerable advantages over systems done with free compilers.
  • If you own a MacIntosh OS X computer, you may now run AIPS. Get either of the above versions; all contain the new MACPPC and MACINT ports. Note that the somewhat expensive IBM and Intel compilers produce code which runs about 50% faster than the code produced by the GNU compiler. Binaries compiled with the IBM and Intel compilers may be installed and updated from our ftp site. That site is maintained by our Mac computers in Socorro. Read also the special Mac installation instructions which are supplements to the A Guide to the Install Wizard instructions.
  • When you get 31DEC14 or 31DEC13, use the new install wizard; we have a good on-line guide that will help you through it. Read it!
  • The 15OCT99, 31DEC00, 31DEC01, 31DEC02, 31DEC03 31DEC04 31DEC05 31DEC06 31DEC07 31DEC08 31DEC09 31DEC10 and 31DEC11 releases of AIPS are no longer available; the number of bug fixes and differences between them and the 31DEC14 version have become too great. The continued significant demand for a frozen, even if obsolete, version was the main reason we decided to resume regular releases.

PROBLEMS AND WARNINGS

There are sometimes considerations which users of older versions of AIPS must take into account due to changes in the latest version. In addition, there are sometimes bugs introduced into the latest version which then get repaired in that version. Such matters may affect those users who keep their AIPS up to date. These bugs often do not get reported in the AIPSLetter since they were temporary but might be of concern for diligent users. They are reported in CHANGE.DOC but those reports are sometimes fragmentary and confusing. We have begun a new web page for problems of this sort. It is hoped that we will keep it up to date.

PATCHES

You really should be getting 31DEC13 or 31DEC14 instead of patching an older version!

With previous releases, we did not change the frozen release tar ball; user sites were required to download the text files and do any compilations themselves. But, beginning with 31DEC04, we provide binary releases for which user sites are not required to have compilers. Therefore, we have reversed our policy. These patches have been applied to the official code of 31DEC11 and may be downloaded using a 31DEC11 "Midnight Job". Any tarball taken after the change date listed below will already have the patches applied. Of course, you may still download and compile the files as before.

There are twenty-four patches for 31DEC13.
  1. Spectral index was not corrected when SOLINT=-1 in BPASS even when there was only one calibration source. 2014-01-14
  2. LISTR failed to read source information when printing "gains". 2014-01-14
  3. DOOSRO run file had a typo in its first line 2014-01-27
  4. UVFND used the real part of channel-averaged data for both real and imaginary parts 2014-02-07
  5. DOBAND 2 and 4 modes had an initialization issue 2014-02-09
  6. DOOSRO pipeline procedure contained a POPS error 2014-02-10
  7. KNTR and PCNTR had minor issues which blocked display of true-color images. 2014-02-11
  8. PCCOR did not handle blanked values from the PC table cable-cal measurements 2014-02-11
  9. FITLD had trouble finding the correct records for MC and IM tables. 2014-03-11
  10. DSKEW did bad things when the input image had a non-zero value of rotation. 2014-03-17
  11. CLCAL failed to re-reference the SN tables when requested. 2014-03-19
  12. SNP2D needed clarification of BCHAN and BIF and to write reference channel phases as well as delays. 2014-03-27
  13. TIORD had a bad format. 2014-03-31
  14. XGAUS and RMFIT called the function routine incorrectly numerous times, mostly with remarkably benign results. 2014-04-02
  15. PRTAB could abort when string data was very long. 2014-04-02
  16. LISTR did not show the correct scaling for angles in the GAIN listing. 2014-04-11
  17. TVFLG and SPFLG interpreted flagged rows in the flag command table as a serious error in a couple of places. 2014-05-29
  18. DTSUM omitted the highest numbered antenna from its matrix list if it did not have autocorrelation records. 2014-06-13
  19. CALIB in phase-only solutions could return amplitude gains other than 1.0 when only 2 baselines occurred in an interval. 2014-06-27
  20. PCAL did not take data flagging into account when averaging data over time. 2014-08-08
  21. TYSMO did not apply flagging correctly except if all flags applied to all Stokes. 2014-08-21
  22. BPASS did not allocate quite enough dynamic memory causing bad messages when it closed. 2014-09-12
  23. SPFLG, TVFLG, FTFLG made a mess of the header in memory when trying to load a fully flagged plane making many operations other than a good TV load fail. 2014-09-12
  24. FITLD had trouble finding widely spaced records for MC tables. 2014-09-30
There are three large and nineteen more normal 31DEC12 patches.
  1. Bandpass calibration was not applied to enough channels to support post-BP frequency smoothing 2013-01-16
  2. Tick increments were computed with an erroneous round-off parameters leading some tick marks to be plotted at offset values. 2013-01-29
  3. POSSM had a number of minor irritating bugs. 2013-02-05
  4. FITLD turned off DIGICOR corrections if the array name is not VLBA. 2013-02-05
  5. FITLD after above correction failed if it could not make a CQ table. 2013-02-18
  6. CL2HF aborted because of an internal name conflict 2013-02-19
  7. PRTAB aborted when writing large values with F format 2013-03-01
  8. COMB did not do POLC correctly when using constant noise values 2013-04-04
  9. AFARS had an addressing bug causing it to try to write too much 2013-04-05
  10. FITLD could get the EQUINOX wrong in the SU table with FITS-IDI input 2013-04-11
  11. COMB messed up scaling when combining two images with one of them not JY/BEAM 2013-05-03
  12. FITLD had a warning message with more arguments than format items 2013-05-21
  13. BPASS rounded times outward for each scan by too much 2013-06-17
  14. IMAGR computed the actual average frequency wrongly 2013-07-03
  15. IMFIT and JMFIT could return negative error bars when the object was negative 2013-07-07
  16. TRANS messed up reversing the order of axes greater than one while swapping the same axis 2013-07-17
  17. PRTAB had formatting issues with large tables, magic blanks 2013-07-25
  18. SU table access was incorrect in some routines including widely used ones 2013-07-29
  19. SPFLG had a gridding counter which could overflow with modern data sets 2013-08-16
  20. PRTAB had formatting issues with required E formats in F-format modes 2013-08-23
  21. SETJY and CVEL were affected by a bad variable in setting the Doppler velocity and the former omitted the system velocity when setting source velocities. 2013-10-21
  22. ISPEC on an image with an FQID axis could fail 2013-10-24
There are ten 31DEC11 patches.
  1. Imaging code had problems with very large gridded modeling. 2012-01-16
  2. UVFIT had many areas of code dimensioned too small to handle the new allowed number of components. 2012-01-16
  3. FARS did not convert residuals to amplitude and phase properly when being output and did not shift back to the input lambda**2 properly. History file had error. 2012-01-16
  4. AFARS did not handle BLC/TRC correctly, producing wrong rotation measure images. Code was added to prevent quadratic fits too close to edges. 2012-01-16
  5. SQASH had a format error in the history writing that caused aborts. 2012-01-16
  6. FITAB did not write the TNULL keyword that is really required with compressed visibility data. 2012-01-16
  7. CLCOR did not correct for the GMRT's opposite phase sign convention. 2012-01-16
  8. VLANT did not correct EVLA data properly. 2012-03-01
  9. SCMAP and SCIMG did not apply the flag table to the data entering the self-cal 2012-03-07
  10. Mac OS/X version Mountain Lion changed ps to issue an error message when there is a library path; procedures needed defenses against this. 2012-11-19
There are eighteen 31DEC10 patches already:
  1. UVCOP ignored the last 4 characters of SOURCE making sources with long names inaccesible when selecting by name. 2011-01-18
  2. DBCON was vulnerable to errors in table headers causing it to attempt semi-infinite file expansions. 2011-01-18
  3. FRING had an error when attempting exhaustive searches causing it to find wrong answers for all except the first IF 2011-01-21
  4. Object oriented uv tasks had a chance to find the wrong output file when a file of the same name and higher sequence number was on the same disk.2011-01-21
  5. CALIB failed to build the output header correctly for non-standard single-source data sets 2011-01-24
  6. RLDIF did not handle the one-source continuum corrections properly 2011-01-24
  7. SWAPR ignored autocorrelation data. 2011-01-24
  8. SNPLT did not check phase range in plotting PC table phases. 2011-03-23
  9. IMAGR did not average multi-channel data correctly when doing on-the-fly baseline-length timae averaging 2011-04-15
  10. NX tables were written incorrectly when there were multiple subarrays. 2011-04-15
  11. IMEAN did not write the text file output correctly. 2011-06-08
  12. NOIFS did not scale the UVW's correctly, normally being half an IF off 2011-06-14
  13. CVEL did not die when it should on fatal errors 2011-06-23
  14. FITLD and friends did not read table header character-valued keywords correctly
  15. UVCOP did not apply flags when SOURCES was specified. 2011-07-01
  16. IMAGR did not keep the correct Clean beams for facets other than one when making an image cube with ONEBEAM true. 2011-07-25
  17. VPLOT did not plot models correctly for more than 64 facets. 2011-07-29
  18. CLCOR used the wrong sign of the antenna Y position for the EOPS and SUND operations. than 64 facets. 2011-08-04

CONTRIBUTED CODE

With the advent of the binary versions of AIPS, it has become more difficult to compile special local tasks. If one wants to do this and also take advantage of the improved performance of the NRAO-purchased compilers (Intel for LINUX, LNX64, and MACINT; IBM for MACPPC; SUN for Solaris), the user must purchase the compiler(s) for himself. This can be rather expensive. There are two ways out of this bind. If the local task is of sufficient interest, you could try to pursuade the AIPS group to include it in the general AIPS distribution. This requires the code to be written up to a least some minimal standard. A recent example is ATLOD which translates older Autralia Telescope data into AIPS. The alternative is to send the code and help file to the AIPS group and ask them to compile to routines, leaving the results on the AIPS ftp site. This has now been done for 4 tasks: HAP and ORFIT in a CfA directory and SETVY and CALIV in a WSRT directory. Both of these site directories are located in a CONTRIB directory at the main AIPS public ftp site.

The load modules are stored under the name task.EXE.arch to identify the operating system (arch) to which the load module corresponds. To install them in your system, copy the help file (task.HLP) to $TST/HELP/ and copy the appropriate load module to $TST/$ARCH/LOAD/task.EXE. Note that one has to rename the load module dropping the architecture string. For LNX64 machines two load modules are provided, one compiled with the gnu compiler and one with the intel compiler. In general, for a binary installation, you will want the intel version.

THE MIDNIGHT JOB

... will be of interest to you if you want the latest 31DEC06 and 31DEC07 versions updated nightly, weekly, or occasionally. It can do either text or binary updates depending on which sort you did with install.pl.

NVSS and WENSS/WISH Survey files for AIPS

The WENSS/WISH files have been corrected (2 July 2004) to omit the sources which are the sum of other "components" also appearing in the lists. Note that the survey files shipped with AIPS releases include the shorter lists of the stronger sources. The full lists are only available from this ftp site.

DOCUMENTATION

AIPS Memos, Reports, old AIPSLetters, the Cookbook, Going AIPS, access to the newest versions of the HELP files, search CHANGE.DOC and more. The most recent AIPS Memos are:

  • number 118, discussing the usage of XGAUS, ZEMAN, and RMFIT spectral modeling tasks
  • number 117, discussing the detailed FITS format used by AIPS, revision dated August 28 2012,
  • number 116, discussing new RFI mitigation options in AIPS, dated June 2010,
  • number 115, discussing new auto-boxing for Clean capabilites in AIPS, dated June 29, 2009,
  • number 114, re-stating the FITS-IDI convention with corrections and added tables, revised December 15, 2009,
  • number 113, discussing a "new" geometric way to handle the W problem, dated May 22, 2009,
  • number 112, discussing the AIPS pipeline for VLA data reduction, dated March 19, 2007,
  • number 111, discussing phase referencing with more than one calibrator using ATMCA, dated January 6, 2005,
  • number 110, discussing strategy for removing troposppheric and clock errors using DELZN, revised October 21, 2009, dated August 31, 2004,
  • number 109, discussing AIPS on DVDs and read-only data systems, dated January 20, 2004,
  • number 108, discussing weights for VLA data, dated January 21, 2003,
  • number 107, discussing the differences between FRING and KRING, dated April 8, 2002,
  • number 106, discussing the Brandeis scheme for making movies in AIPS dated June 6, 2001,
  • number 105, discussing the new RUN file to simplify VLBA data reduction dated February 28, 2001 and April 26, 2001,
  • number 104, discussing the new Y2K performance test dated September 8, 2000, and
  • number 103, discussing data weighting in AIPS dated 2000-03-21.

MAIL GROUPS

The AIPS group maintains three e-mail exploder lists. The first, called daip, is restricted to immediate members of the AIPS group and a few NRAO scientist advisors. The other two are, however, open to any suitable person. Membership is moderated, of course, because SPAM has become so annoying.

The group intended for discussion of AIPS issues is called bananas and is used, among other things, to announce patches to the "frozen" versions of AIPS. Traffic is light. You can subscribe yourself to this list on-line.

The group intended for discussion of problems related to the "Midnight Job" is called mnj and is used to announce AIPS Manager things related to the current MNJ. Traffic is light, but the announcements can have a serious impact on any site attempting to stay current with the development version of AIPS. You can subscribe yourself to this list on-line.

FITS-IDI

The FITS Interferometry Data Interchange format is a set of FITS binary table definitions and a set of conventions for using them to transport radio interferometry data between different software packages.

The FITS Interferometry Data Interchange Convention (formerly Format) has been accepted as an IAU-acknowledged convention. This convention was documented by Chris Flatters in AIPS Memo 102 which, unfortunately, was not accompanied by an editable text version. Therefore, Eric Greisen had to re-type the document. While doing so, he updated some matters, corrected minor wording issues, and added 5 new sections for 5 new tables, 3 of which are actually in use. Interested parties should review AIPS Memo 114 revised (ps) or AIPS Memo 114 revised (pdf); it has been submitted to the IAU FITS Committee. Greisen has attempted to highlight the changed parts in red in this draft. The current draft is dated August 2011 and includes the MODEL_COMPS table and comments from Lorant Sjowerman, Bill Cotton, and others. Please e-mail egreisen@nrao.edu with comments.

AIPS MANAGER/INSTALLER FAQ

Help for the weary AIPS Installer. Very much experimental and incomplete, and probably needs updating, but better than nothing.

BENCHMARKS (the "DDT" and now the "Y2K")

The AIPS Benchmark was known as the "DDT" (Dirty Dozen Tasks); we have results for a variety of systems. A more modern test called "Y2K" has been developed in 2000 to test faster computers and to use IMAGR rather than MX. For 31DEC04 we have new master images and data sets. In addition, we have a new HUGE test using multi-resolution IMAGR on Cygnus A. Changes to CALIB and VTESS in particular forced this update, while faster computers make Y2K LARGE run in as little as 5 minutes.

DESIGNATED AIP

The former designated-AIP-of-the-week program; rotation has been halted due to the lack of personnel. The e-mail address (daip@nrao.edu) was the best method of reaching all the members of the AIPS Group and will still work. However, we ask you to use the new NRAO-wide helpdesk instead. Go to https://help.nrao.edu and login with your my.nrao.edu username and password. There you may peruse the "knowledge base" (currently empty), enter new tickets in any of several departments including AIPS, and review and update any tickets you have submitted.

AIPS COPYRIGHT

AIPS is copyrighted by Associated Universities, Inc. using the GNU copright form. The full text is available with every AIPS release and may be read here.

RELATED SOFTWARE


FITS

This is the Flexible Image Transport System, and is the standard data interchange format used by most Astronomical Software, including AIPS. Follow the above reference for a very extensive set of documentataion, including a large resource list for Astronomy on the internet.

HELP!

The primary AIPS address is the daip one referenced on our main Contact page, and general queries, requests for distribution tapes, documents, ftp access, and so on should be directed there. Application-oriented questions should be directed to the Designated AIP.


Modified on $Date: 2014/09/30 15:12:06 $
Eric W. Greisen