Changes between Version 1 and Version 2 of doc/app/palm_config

Timestamp:

May 24, 2018 1:10:53 PM (7 years ago)

Author:

raasch

Comment:

--

doc/app/palm_config

@@ -16 +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
 
-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.
+If PALM has been successfully installed by the automatic installer, the installer creates a configuration file 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.
 
-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.
+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) is managed via the {{{module}}} environment. In all these cases, the user has to setup the configuration file manually.
+
+
+== How to generate a configuration file manually
+
+As a first step, copy the default template of the configuration file (which is part of the PALM download) to your working directory:
+{{{
+  cd $HOME/palm/current_version
+  cp trunk/SCRIPTS/.palm.config.default .
+}}}