Jump to: navigation, search

The same as User:PeterWilliams. For some reason that account doesn't seem to work anymore.

The MIRIAD Installation Instructions Mess

There are too many sets of instructions for how to install MIRIAD. Here's my attempt to list them all:

Tentative updated instructions for installing MIRIAD with the autotools:

Miriad can be compiled and installed using a standard system known as the "GNU autotools". We refer to this as the "new" build style in the context of Miriad. These standard tools are maintained by the broader open-source community and so are almost universally available and provide maximum portability and correctness.

Note that it is usually easiest to install miriad via Miriad binary releases. You may, however, wish to compile Miriad from the source yourself if:

  • There aren't any binary releases for your system architecture.
  • You want to modify Miriad tasks yourself.
  • You want to have the most up-to-date version of Miriad possible by tracking and building the CVS source tree.
  • You want an installation built via the GNU autotools, for which there are no binary releases, instead of the classic build system.

Easiest Installation Instructions

  1. Decide on your installation prefix, an absolute directory name which we will call PREFIX. The Miriad files will be installed underneath PREFIX in directories named bin, lib, etc., using the same structure as seen in /usr on Unix systems. Good choices might be /usr/local, /opt/miriad, $HOME/opt, or /sw on Fink-using Mac machines. If PREFIX is in a system-wide location, you will probably need access to superuser privileges (via sudo or su) to run the installation.
  2. Decide which telescope's data you want to customize your Miriad build for. Supported options are ata, atnf, bima, carma, lofar, fasr, gmrt, sma, or wrst. We will call this choice TELESCOPE.
  3. Download and unpack the Miriad source code.
  4. cd to the top Miriad source code directory.
  5. Optionally you can issue cvs update here to update the tree with the latest updates.
  6. Run ./configure --prefix=PREFIX --with-telescope=TELESCOPE, substituting the capitalized words with the choices you made above. This program will perform a bunch of checks to make sure that your system is capable of compiling Miriad.
    • If configure reports an error, you have to resolve it. Unfortunately, the messages returned by configure are not always easy to decipher. Your local system administrator may be able to help you understand the output of configure even if he or she is not familiar with Miriad in particular.
  7. Once configure completes successfully, run make to compile all of Miriad.
    • If configure completes successfully, make should as well. However, if your system has an unusual setup then the configure tests may miss something that results in the make failing. You should contact the Miriad developers (see below) to help them understand and fix the issue.
  8. Once make completes successfully, run make install to install Miriad into the prefix you chose. If you need superuser permissions to run the installation, you may need to run sudo make install or su -c "make install". If make install fails, it's extremely likely that there is a permissions problem, which your local system administrator should be able to help you understand.
  9. The Miriad files are now in place. To set up your shell login to work with Miriad, you need to configure various environment variables. This can be accomplished by sourcing the file MYPREFIX/lib/miriad/automiriad.csh if you use a C shell or MYPREFIX/lib/miriad/ (note the different extension) if you use a Bourne shell. You could put the necessary source shell command in your shell initialization scripts or in an alias to automate this step.
Personal tools