The Fortran sources of the model are provided with a simple `makefile`.
Matlab and the gfortran GNU compiler are required for installation.
The `makefile` uses the definitions of Matlab directories and libraries on the machine
were the model was originally compiled;
before invoking `make` on the command line the user should review the correspondent
definitions and adapt them to his local machine.
After a sucessful compilation the user can place the resulting binary
(`traceo.exe`) and the shell script `runtraceo`
in a directory,
where the system can find them.
The input file has the `in` extension and can be written from Matlab using the M-file
`wtraceoinfil.m`.
After creating the input file (for instance, `munk.in`)
the user can run the model with the command `runtraceo munk`;
according to the desired output the model will create one of the following Matlab mat files:
`rco.mat`: ray coordinates;
`ari.mat`: ray or eigenray information (ray coordinates, plus travel times and amplitudes);
`aad.mat`: arrivals and delays information;
`cpr.mat`: coherent acoustic pressure;
`ctl.mat`: coherent transmission loss;
`pvl.mat`: particle velocity;
`pav.mat`: coherent acoustic pressure and particle velocity.

Although many of the output parameters are expected to be complex linkage issues with the Matlab engine
forced a workaround of packing complex vectors as real two-dimensional matrices
(first row represents the real part, second row the complex part),
and separating complex matrices into a real and a complex part.
Users are welcome to fix this issue.
Besides the Matlab mat files TRACEO writes a short `munk.log` ASCII file,
describing the type of array and the calculation time.
The structure of the input file will be described in the following section.

Orlando Camargo Rodríguez
2012-06-21