NRAO
 

Astronomical Image Processing System
Special MacIntosh OS X instructions

[AIPS]

The 31DEC15 version of AIPS is available as our active development version. It is likely to change on a daily, weekly, and monthly basis. The older 31DEC14 version is "frozen" although some patches for it may be made. They both contain ports to the MacIntosh OS X (Darwin) operating system for PPC and Intel cpus. These ports are no longer new and the code and instructions below have become stable.. Binay installations, where possible, are recommended and have become fairly routine. Users doing a text installation will need to follow instructions to install the full set of GNU compilers and readline from GNU-provided source code. However, a binary installation is now available, including the update process known as the "Midnight Job." The binary installation provides load modules and run-time libraries build by the (somewhat expensive) IBM xlf or Intel ifort compilers. These executables appear to run up to 50% faster than those produced by the GNU compilers. Most Mac users run the binary version of AIPS and the instructions below may well not be current. Ignore them and simply follow A Guide to the Install Wizard unless you have to compile the code yourself.

Many thanks to Kristy Dyer and Michael Rupen of NRAO who loaned an iBook computer for this development and who provided much need help and encouragement in the process. Boyd Waters (NRAO) and Miguel F. Morales (MIT) also provided considerable advice. Juan Cabanela (St. Cloud State University) was at the forefront in dealing with problems that arose therafter. A number of other Mac owners have also contributed time and effort. Wes Young, formerly of the NRAO AIPS Group, was instrumental in developing the binary installation process and debugging recent OS/X issues.

Table of Contents


Basic downloads required

Binary installations of AIPS will need the basic tools "cvs" and "XWindows" in non-developer form. If you are doing a text installation, i.e. are compiling the code yourself, then you will need Fortran and C compilers and a variety of software developers tools including those for XWindows.
  1. Mac OS X Developer Tools: You will need the basic software developers' kit from Apple. It contains the C compiler and lots of other goodies, and is available for free. The developers' kit may be available in "/Applicatons/Installers/Developer Tools". Use the finder to see if it's there, click on Applications, then Installers, then Developer Tools. If it exists then double click on the package icon and install the compiler. If the Developers' Tools are not available on your hard drive, they may be available from CD if you bought Jaguar or Panther. If you have the CD's locate the Developers' Tools CD (Xcode disk for Panther) and install the "Developers' Tools" package from disk. One final place to get the "Developers' Tools" is from the Apple Developer Connection (ADC). Details on the ADC are available at the ADC membership page, while details of the Developer Tools are available at the tools page. Once you're a member, you can go to http://connect.apple.com site log in and snag the software.
  2. You will need XWindows for either a binary or a text installation. With the Panther (X 10.3) version, X11 is installed from disc 3 of the Panther distribution. The developer tools may be installed from the Xcode CD. Alternatively, the sites mentioned below may be used to obtain X11.
  3. Apple supplies X11R6. Go to the X11 download page and click on "Download X11". Do the usual installation by clicking on the icon of the downloaded object. Note that the version of X11 now available only works on Panther. Jaguar users see below.
  4. For a text installation, you also need the XWindows software developers kit which contains the C include files needed to compile XAS. Apple gives this away too. Go to the main X11 page. At the bottom to the very right hand side is, in small letters, a button to click which will download the SDK. Do the usual installation by clicking on the icon of the downloaded object.
  5. Jaguar users may obtain X11 via sourceforge. The easiest way to do this is to grab XonX. Go to XonX homepage and get Download of X11 4.3.0. That is a simple Mac Installer based package for installing X11 including all the libraries.
    Next, you need a simple Xserver window server. The most "mac-like" one other than Apple's is OroborusX available at: Oroborus homepage. It provides a nice installer and users can then just double click the OroborusX application to launch their X11 server.

Installing the GNU compilers and readline: text installations only

  1. Download the GNU tar balls from GNU or, more simply, from NRAO. They are gcc-3.3.2.tar.gz (31548232 bytes) and readline-4.3.tar.gz (961662 bytes).
  2. Disable the line
             source /sw/bin/init.csh; rehash
    from your account's .tcshrc, .cshrc, or .bashrc file if present. Note that this may have dire consequences for other Fink-supplied utilities and is probably not needed any more. The default Fink gcc has also been of an acceptabloe flavor of late.
  3. Install the compilers using
             ./configure --prefix=/usr/local/gnu
             gnumake bootstrap
             sudo gnumake install
  4. Install readline using
    	 export CC=/usr/local/gnu/bin/gcc 
    	     or
    	 setenv CC /usr/local/gnu/bin/gcc
             ./configure --prefix=/usr/local/gnu --with-curses --disable-shared
             gnumake
             sudo gnumake install

Alternate compilers

  1. Intel sells a compiler designed for Intel chips running under Mac OS/X. The latest versions have been problematical. They apply rules of the latest Fortran standards rather strictly without options to ignore some or all of them. AIPS fails to compile with such rules even though it works just fine. Users who tried Intel compilers finally reverted to GNU compilers.
  2. IBM sells a Mac OS/X version of their xlf compiler but it does not work for the new Intel chips used in Macs. This has produced improved performance in our tests and is now understood in $SYSLOCAL files CCOPTS.SH, FDEFAULT.SH, and LDOPTS.SH.
  3. Go to IBM and fill out their marketing survey to get a temporary free trial version of the compiler.
  4. Install it following IBM's instructions.
  5. We have made binary versions of the Mac load modules build with the xlf compiler available to our users, including the necessary run-time libraries. This is now offered for the 31DEC05 and later releases.

File systems

  1. The file systems that you use for AIPS should be fully modern ones. Please use "MACos extended, with lower-case support" file systems. The "FAT32" file system does not allow, among other things, the rename system operation which AIPS requires.

Now install AIPS

  1. Following the instructions for installing the 31DEC15 version of AIPS. After install.pl has been downloaded, it will need to be made executable. Run it with the command perl install.pl or edit it to set /usr/bin/perl rather than /usr/local/bin/perl in its first line. (The command perl install.pl -n is used for the binary installation.)
  2. Make sure on screen 10 that readline points to the /usr/local/gnu/libreadline.a version.
  3. When the installation has finished, copy /etc/services to some area you own and edit it, adding the lines
    sssin           5000/tcp        SSSIN      # AIPS TV server
    ssslock         5002/tcp        SSSLOCK    # AIPS TV Lock
    msgserv         5008/tcp        MSGSERV    # AIPS Message Server
    tekserv         5009/tcp        TEKSERV    # AIPS TekServer
    aipsmt0         5010/tcp        AIPSMT0    # AIPS remote FITS disk access
    aipsmt1         5011/tcp        AIPSMT1    # AIPS remote tape 1
    aipsmt2         5012/tcp        AIPSMT2    # AIPS remote tape 2
    

    You will have to comment out some conflicting services, all of which we believe are obsolete. Then
    sudo cp services /etc
    and enter your password when required.

Now run AIPS

  1. Start up /Applications/X11.ap/Contents/MacOS/X11.
  2. In the xterm that this creates, type the aips command line and begin your aips session.

But there are problems

  1. If things do not work properly, e.g. the TV does not start, see the AIPS Manager FAQ for suggestions. On leopard systems, you will need to reset the DISPLAY environment variable
                export DISPLAY=localhost:0
    or
                setenv DISPLAY localhost:0
    in the xterm that you run aips from to get the local tv. Ob later systems, do NOT set the DISPLAY variable since that will make everything fail.

  2. The default Mac system limits shared memory pages to 4 Mbytes. When XAS starts it tells you that it is making a screen x pixels by y pixels. The memory you will need is at least 4 x y bytes. For the new large screens this is more than 8 Mbytes. On Panther stsems (X 10.3), you can change this limit by changing (as root or admin) the rc file in /etc, adjusting the kern.sysv.shm* line to
             #Setting the shared memory to something a bit more reasonable.
                sysctl -w kern.sysv.shmmax=10485760
                sysctl -w kern.sysv.shmmin=1
                sysctl -w kern.sysv.shmmni=32
                sysctl -w kern.sysv.shmseg=8
                sysctl -w kern.sysv.shmall=4096
  3. On the latest "leopard" systems, /etc/rc is gone and creating it will have no effect. You need to create an /etc/sysctl.conf file and put the values in it,
                kern.sysv.shmmax=10485760
                kern.sysv.shmmin=1
                kern.sysv.shmmni=32
                kern.sysv.shmseg=8
                kern.sysv.shmall=4096
    You should use the values you had when you were running tiger. Those could be in /Previous\ System/etc/rc, assuming you have "Previous System". So three different OS upgrades and three different ways to adjust the default shared memory.

  4. On older Jaguar systems (X 10.2), you can change this limit by changing the SystemTuning file in
     
             /System/Library/StartupItems/SystemTuning
    Look for the lines
             sysctl -w kern.sysv.shmmax=4194304
             sysctl -w kern.sysv.shmall=1024
    Change the 4194304 to 10485760 (for 10 Mbytes) and change the 1024 to 4096 (allows 16 Megabytes).

  5. Note that you must re-boot the computer after making the above changes to the shared memory.

You WILL want a Midnight Job!

If your site has a need for the current version of AIPS with updates via the Internet and the so-called midnight job, Read this information. It has additional information and instructions. Or contact Eric Greisen for further information.

Since releases of AIPS are planned to be only on an annual basis, the midnight job (now with easier setup and NO ssh) will be the only way for AIPS users outside of NRAO to avail themselves in a timely fashion of whatever enhancements, changes, or new functionality we add to Classic AIPS.


Modified on $Date: 2014/12/03 01:16:25 $
[Eric W. Greisen]