| | 1 | = '''This page is under construction! ''' = |
| | 2 | \\\\\\ |
| | 3 | |
| | 4 | = The PALM configuration file |
| | 5 | |
| | 6 | Running PALM with the {{{palmrun}}} script or compiling PALM with {{{palmbuild}}} requires a configuration file in the working directory from where the scripts are called. The configuration file contains information about |
| | 7 | |
| | 8 | * the compiler and compiler options to be used |
| | 9 | * paths to required libraries (e.g. MPI, netCDF, or fftw) |
| | 10 | * preprocessor directives to switch on/off special features of PALM |
| | 11 | * paths to be used for storing PALM's input and output files |
| | 12 | * paths where user-interface routines and job protocol files can be found |
| | 13 | * the execute command to be used for starting the PALM executable |
| | 14 | * settings of other UNIX environment variable |
| | 15 | * batch job directives |
| | 16 | * unix commands to be executed before / after the PALM code is started, or that should be carried out in case of errors that appeared during the run |
| | 17 | |
| | 18 | If PALM has been successfully installed by the automatic installer, the installer creates a configuration named {{{.palm.config.default}}} in the working directory of the user (which by default is assumed to be {{{$HOME/palm/current_version}}}). This file should contain all relevant information to run PALM on the respective computer. |
| | 19 | |
| | 20 | The installer may fail for various reasons, e.g. because of mismatches in the user's system configuration. Problems may appear if the user has installed more than one FORTRAN compiler, and/or if the netCDF libraries have been generated with a different compiler than is used for compiling PALM. Furthermore, the automatic installer cannot be used on many larger computer systems where software (compilers, libraries) are managed via the {{{module}}} environment. In all these cases, the user has to setup the configuration file manually. |
