PREREQUISITES:
=============

Before attempting to compile and run these programs please ensure that
the NetCDF libraries and header files have been installed on your system;
see user manual and https://www.unidata.ucar.edu/software/netcdf.

It will be necessary to compile and specify where NetCDF has
been installed as described in the file "compile".

The MCD datafiles are in the 'data' directory which contains some
important common global data files and subdirectories (at least 'clim_aveEUV'
must be present) containing datafiles specific for given MCD scenarios.
Additional scenarios (e.g. 'clim_maxEUV', 'warm', 'cold', 'strm', etc.),
which may be added as directories in the main 'data' directory, alongside
the 'clim_aveEUV' directory.

It is advised to create a symbolic link MCD_DATA in the current working
directory which points to the location where the MCD data files are
stored; e.g.:
ln -s /full/path/to/mcd/data MCD_DATA
Creating this symbolic link is not mandatory (in fact this 'symbolic link
strategy' is only valid on Linux/Unix systems, not Windows); it is simply the
default path to data defined in our software. It is possible to specify
another path via the routines' input arguments; see the user's guide and
comments embeded in the codes.

DIRECTORY CONTENTS:
==================

call_mcd.F          This is the main collection of fortran subroutines
                    for access to the MCD which can be called from your
                    own code and is used by programs below. Input and
                    output arguments of 'call_mcd' are documented in
                    the code and in the user's guide.

constants_mcd.inc   include file of containing data and parameters common
                    to call_mcd and subsidiary routines.

test_mcd.F          A simple example program provided to display (and test)
                    the way to call call_mcd from main fortran programs.

compile             Unix script file containing a command to compile test_emcd
                    Read and edit it to fit your settings. 
                    Even if you don't want to compile test_mcd, you should
                    take a look, as it illustrates how to compile and link
                    a main program which uses call_mcd. 

test_mcd.def        A list of input values for test_emcd.
                    Edit it, and (once test_mcd compiled), redirect it:
                    test_emcd < test_emcd.def

julian.F            Subroutine to convert Earth GMT dates to Julian days.

heights.F           Subroutine to convert vertical coordinates. Users do
                    not need to use it directly but call_mcd requires some
                    of the routines contained in this file to function.

README              This file.

testcase     Subdirectory containing test cases you should use to test your
             installation of the database. See the README there.

pres0        Subdirectory containing the 'pres0' tool. See the README there,
             as well as the user's guide for details.

idl          Subdirectory containing examples of IDL intefaces to MCD
             software.

matlab       Subdirectory containing examples of Matlab intefaces to MCD
             software.

scilab       Subdirectory containing examples of Scilab intefaces to MCD
             software.

c_interfaces Subdirectory containing examples of C and C++ programs calling
             the MCD Fortran routines.

python       Subdirectory containing examples of Python scripts calling
             the MCD Fortran routines.