9 | | The [wiki:doc/install/automatic automatic installer] normally cares for steps 1-5 that are described below. Failure of the automatic installation process is usually caused by inconsistencies in your software environment (e.g. mismatches between your compiler, NetCDF- and MPI- libraries) which will also cause failure of the manual installation. Anyhow, at least parts of the installation steps may be required to be carried out manually. For example, if your system has a very strict firewall and does not allow downloads from our repository, you may carry out the download (second step below) on a different system and copy the {{trunk}}} folder to your target system, before carrying on with the [wiki:doc/install/automatic automatic installer]. |
10 | | |
11 | | Installation and configuration for batch jobs cannot be done by the [wiki:doc/install/automatic automatic installer] and requires manual work in any case, as described further below. |
| 9 | The install script that comes with the PALM Model System normally cares for steps 1-5 that are described below. Failure of the installation process is usually caused by inconsistencies in your software environment (e.g. mismatches between your compiler, NetCDF- and MPI- libraries) which will also cause failure of the manual installation. Anyhow, at least parts of the installation steps may be required to be carried out manually. |
| 10 | |
| 11 | Installation and configuration for batch jobs cannot be done by the install script and requires manual work in any case, as described further below. |
24 | | In the '''second step''' a working copy of the recent PALM revision, including the source code, scripts, helper routines, etc. must be copied to the working directory by entering the following commands. Replace {{{<your username>}}} by the name that you have chosen in the [https://palm.muk.uni-hannover.de/trac/register register form]. |
25 | | {{{ |
26 | | cd ~/palm/current_version |
27 | | svn checkout --username <your username> https://palm.muk.uni-hannover.de/svn/palm/trunk trunk |
28 | | }}} |
29 | | You will then be prompted for your password that you have set in the register form too. After completion, a subdirectory {{{trunk}}} should appear in your working directory. It contains a number of further subfolders, which contain e.g. the PALM source code ({{{SOURCE}}}) and the scripts for running PALM ({{{SCRIPTS}}}). '''Please never touch any file in your working copy of PALM, unless you know what you are doing.''' In case of any problems with the {{{svn checkout}}} command, the most probable reason are firewall settings on your system. Please check or ask your system administrator, if https-ports are open. \\\\ |
30 | | |
31 | | The above {{{svn checkout}}} command provides you the most recent revision (developer version) of PALM. In case that you like to use a fixed release, please enter |
32 | | {{{ |
33 | | svn checkout --username <your username> https://palm.muk.uni-hannover.de/svn/palm/tags/release-<#> trunk |
34 | | }}} |
35 | | where {{{<#>}}} can be any of the available PALM releases, e.g. "''5.0''". See the [wiki:doc/tec/releasenotes release notes] for a list of available releases. New releases will be announced via the PALM mailing list. |
| 24 | In the '''second step''' a copy of a recent PALM version, including the source code, scripts, helper routines, etc. must be copied to the working directory. First you need to choose [https://gitlab.palm-model.org/releases/palm_model_system/-/releases PALM Releases] and download it. Please unpack the content of the downloaded archive, so that the {{{packages}}} directory, the {{{README.md}}} file and the {{{install}}} script are located inside the directory {{{~/palm/current_version/palm_model_system/}}}. '''Please never touch any file in your working copy of PALM, unless you know what you are doing.''' \\\\ |