Miriad binary releases
See . Local versions can also be found on kern.ovro.caltech.edu:/export/miriad at OVRO. 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 Fedora Core 5 (also works on unbuntu) and Mandrake 10.1
- miriad_linux: linux IA-64
- miriad_darwin_ppc*: MacOSX/10.4 (tiger) - a version for g77 and gfortran
- miriad_darwin_intel*: MacOSX/10.4 (tiger) - a version for g77 and gfortran (a test with 10.5 is also available now)
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/bima/miriad_darwin_intel_g77.tar.gz % tar zxf miriad_darwin_intel_g77.tar.gz % cd miriad % install/make_miriad_starts <-- this patches the miriad_start scripts
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.
% source miriad_start.csh
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.
The WIP package is normally distributed as part of Miriad. It is possible to install it seperately, 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 Update the 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