Installation

Most of what follows is likely to be of interest to site system managers only and may be skipped by the rest of us.

The FLUXES/FLUXNOW code and associated files are supplied as a compressed tar file: fluxes.tar.Z. To install FLUXES/FLUXNOW the file must be uncompressed and the contents extracted to a suitable directory. On Starlink systems, this would normally be directory /star/fluxes. The operation is:

% cd /star/fluxes           (or some directory you specify)
% zcat /tmp/fluxes.tar.Z | tar xvf -

You must then set an environment variable to identify the type of operating system you are using. The example given below shows the value of SYSTEM needed to create a Solaris version of the software. The values required for other Starlink supported systems may be found in the files mk and makefile.

% setenv SYSTEM sun4_Solaris

The UNIX `make' facility may then be employed to generate FLUXES in the current directory, clean up after itself and move the run time system to the directory from which it will normally be run. Note that you must set the environmental variable INSTALL to reflect the directory above that in which you want FLUXES and FLUXNOW to be installed. On most Starlink system this will be directory /star:

% setenv INSTALL /star
% ./mk build
% ./mk clean strip
% ./mk install

Once this is done you can make FLUXES and FLUXNOW available to you by inserting:

if ( -e /star/bin/fluxes/fluxes) then
   alias fluxes /star/bin/fluxes/fluxes.csh
   alias fluxnow /star/bin/fluxes/fluxnow.csh
else
   alias fluxes cat /star/etc/not_installed
   alias fluxnow cat /star/etc/not_installed
endif

into your /star/etc/cshrc file. The example given assumes that you have chosen to have the FLUXES executable installed in directory /star/bin/fluxes. Obviously you will need to change this if you have placed it elsewhere. On Starlink systems, the /star/etc/cshrc file is already set up to run FLUXES.

In addition, the environmental variable FLUXES_DIR in fluxes.csh and fluxnow.csh must be set to name of the directory where the FLUXES executable resides. The Starlink installations of FLUXES have this set automatically during installation.

This behaviour is not the same as that employed for most other Starlink programs and reflects a compromise between the requirements of the JCMT observatory and normal Starlink practice.