Miriad binary releases
For a few popular architectures we make binary releases available. They sometimes don't quite work for you if your compiler is not exactly the same as the one Miriad was compiled with. If so, you probably need to look at an installation from source. Be sure to remind yourself of the Requirements before you use a binary release. For example, you may not need development packages, but you may still need the shared libraries (e.g. for the compiler).
See . Local disk versions can also be found at OVRO and UMD. Pick the correct one matching your OS and compiler. Although we only distribute gnu (g77, gfortran) based releases, the intel compiler can easily give you a significant performance boost (10-100% depending on the application).
- miriad_linux_*: Linux: versions for some linux distros (Fedora, Ubuntu, Centos)
- miriad_linux64_*: linux 64 bit (use the command uname -a to see if you have a 32bit or 64bit processor)
- miriad_max10.4_*: MacOSX/10.4 (tiger) - for g77- soon to be deprecated
- miriad_mac10.5_*: MacOSX/10.5 (leopard) - for gfortran
- miriad_mac10.6_*: MacOSX/10.6 (snow leapard) - for gfortran
Then untar the file and patch the miriad_start scripts to reflect the location on your system e.g.
% wget ftp://ftp.astro.umd.edu/progs/carma/miriad_linux_u10_gfortran.tar.gz % tar zxf miriad_linux_u10_gfortran.tar.gz % cd miriad % install/make_miriad_starts <-- this patches the miriad_start scripts, you need csh
If you don't have wget (e.g. MacOSX), you should have curl, and the first two lines can also be combined as follows:
% curl ftp://ftp.astro.umd.edu/progs/carma/miriad_mac10.5_gfortran.tar.gz | tar zxf - % cd miriad % install/make_miriad_starts <-- this patches the miriad_start scripts, you need csh
Now source the appropriate startup file, depending on your shell, and miriad should now be usable in your shell. You can also make this permanent by adding this to your ~/.cshrc or ~/.bashrc file, e.g. for csh
% source miriad_start.csh
and for bash
$ source miriad_start.sh
It is quite possible that shared libraries on your system are not compatible with the ones in our binary releases. If so, you should try an installation from source. Or be brave and re-install an existing Miriad version.
Activating the new Build System
If you see a directory build_new in the miriad root directory ($MIR), a new build system has probably been installed and if for some reason you would like to try and activate it, do the following:
% cd $MIR % ln -s build_new build % source miriad_start.csh
the same miriad_start knows the difference between old and new script and will act accordingly.
Equally simple, just remove the symbolic link if you want to de-activate it:
% rm build
The WIP package is normally distributed as part of Miriad. It is possible to install it seperately from MIRIAD, but the procedure is currently not well maintained outside of Miriad. With a few commands a binary version of WIP can be extracted from a binary version of Miriad. First follow the steps to install a binary version of Miriad (see above), then issue the command:
% cd $MIR/install % wip.export
After which the wip directory can be copied anywhere. Make sure the wiprc is edited for the final location.
Each binary release is CVS enabled, albeit via the CVS anonymous account. This means you can cvs update your source tree and obtain new code, but not randomly edit and expect the merge to be successfull. If this all means nothing to you, we will cover this at the Party. However, here are some examples of fairly common modifications:
0) Update your miriad source, first checking what is new on the server
% cd $MIR % cvs -nq update <-- check that only two maxdim header files are tagged 'M' as locally modified anything like U is good, anything else M or C is bad. % cvs update -d Update the code % mir.install Build the new code
1) modifying a subroutine
% mirboss % edit $MIRSUBS/fitsio.for % mir.subs fitsio
Caveat: on linux shared libraries are used, on Mac not yet, so all binaries would need to be rebuilt on Mac:
% mir.install prog
2) modify a program
% mirboss % edit $MIRPROG/convert/fits.for % mir.prog fits