Simon Jeffery's Software Store

Installation instructions for model atmosphere and other programs

1. Setting up your folders
2. Obtaining the software
3. Building subroutine libraries
4. Building spectrum
5. Building sterne
6. Subroutine library index 7. Programmers Notes

1. Setting up your folders

a. Decide on the root directory where your software is going to go.... /home/friday, for example.

b. In your .cshrc file, define
setenv OSROOT /home/friday
My makefiles need OSROOT in order to find everything....

c. At some stage you will need the following folders (you may already have them)

[/home/friday/]lib	Holder for object libraries
[/home/friday/]bin	Holder for runtime binaries and scripts
[/home/friday/]include	Holder for shared source code (f77 include files)
[/home/friday/]mod	Holder for shared source code (f90 modules)
[/home/friday/]spectrum	Root folder for SPECTRUM
[/home/friday/]sterne	Root folder for STERNE
[/home/friday/]tfit	Root folder for SFIT, TFIT, ...

Some of these should be created automatically when you download and unpack the tar files.

2. Obtaining the software

Collect the appropriate tar files from http://www.arm.ac.uk/~csj/software_store/
You will need 'etc' 'include' and 'pack_tools' at the very least. These are gzipped. You can put them wherever you like. Then:

• gunzip pack_tools.tar.
• cd /home/friday
• tar xvf [wherever_your_file_is]/pack_tools.tar , etc....

Note. Some tar files have not yet been carefully manicured to contain only the stuff you need. Others may have been trimmed too much, so that items are omitted. Please let me know about problems.

3. Building subroutine libraries

Each subroutine library is contained in a subfolder of ../pack/, e.g. ../pack/qub. It will consist of

• source code contained in a text library ../pack/qub/qub.a
• a makefile containing a list of the subprograms to be included in the object library
• (after make) an object code library ../pack/qub/libqub.a
• (after make install) a soft link in the library folder ../lib/libqub.a

Each library makefile only defines things unique to that library. Then a common section of code, found in ../pack/make_library supplies all the necessary targets:

• build
• install
• clean
• update
• remove

The conservative way to build this library is to cd /home/friday/pack/qub; make; make install; make clean

Any system-specific things (eg compilers - FC, compiler options - FFLAGS) are currently set in ../pack/make_library. I know these should be set in .cshrc or .login, but I haven't got round to that yet, and there are complications as we make the transition from .f to .f90 source code. One day the makefiles might be system-independent.

The most likely problems are likely to arise in connection with the include files ( /home/friday/include ). This is the weak link in the whole edifice, so I will probably need to advise when things go wrong.

If you are feeling really brave, you can attempt the global build:
cd /home/friday/pack; make
but this will probably crash with millions of errors.

** WARNING ** When you start hacking the real code, it is very important to do a 'make update' frequently when editing programs. My makefiles currently have a tendency to think that the text libraries are more recent than the piece of code just edited, so a program gets re-extracted and clobbers you're recent edits. ** END OF WARNIG **

Detailed reports describing bugs in the download/installation procedure or in the software itself will be welcome and should be addressed to Simon Jeffery at the address below.

This page is maintained by: Simon Jeffery (csj@star.arm.ac.uk) Last modified: 13/06/01

Simon's home page