Changes between Version 34 and Version 35 of doc/install
- Timestamp:
- Sep 15, 2010 12:43:21 PM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
doc/install
v34 v35 1 = Code Installation = 1 = Code installation = 2 [[TracNav(doc/install/toc)]] 2 3 3 4 This chapter describes the installation of PALM on a Linux workstation (local host). There are two methods to install and run PALM. With the [#simple simple method], you can run PALM interactively on the local computer. This method is using the scripts '''palm_simple_install''' and '''palm_simple_run'''. The simple method cannot create batch jobs itself, and cannot be used to create restart runs. Also file handling and most other features of the [#advanced advanced method] are not available. This method is only recommended for those who like to test PALM quickly.\\\\ … … 40 41 You should not be prompted for a password. 41 42 42 === Package Installation ===43 === Package installation === 43 44 44 45 The '''first installation step''' requires creating a set of directories on the local and, for the [#advanced advanced method], on the remote host. These are: … … 68 69 This version may contain new features (they might not be documented well), but it may also contain bugs. 69 70 70 === Package Configuration ===71 === Package configuration === 71 72 72 73 To use the PALM scripts, the {{{PATH}}}-variable has to be extended and the environment variable {{{PALM_BIN}}} has to be set (on local and remote host) in the respective profile of the users default shell (e.g. in {{{.profile}}}, if {{{ksh}}} is used): … … 94 95 The second call also copies the PALM scripts (like '''mrun''' and '''mbuild''') to the remote host. 95 96 96 === Pre- Compilation of PALM Code ===97 === Pre-compilation of PALM code === 97 98 98 99 To avoid the re-compilation of the complete source code for each model run, PALM willl be pre-compiled once on the remote host by again using the script '''mbuild'''. Due to the use of FORTRAN modules in the source code, the subroutines must be compiled in a certain order. Therefore the so-called ''make'' mechanism is used (see the respective man-page of the Unix operating system), requiring a {{{Makefile}}}, in which the dependencies are described. This file is found in subdirectory {{{trunk/SOURCE}}}, where also the PALM code is stored. The compiled sources (object files) are stored on the remote computer in the default directory {{{~/palm/current_version/MAKE_DEPOSITORY_<block_descriptor>}}}, where {{{<block_descriptor>}}} is composed of the third (and fourth, if existing) column of the respective block in the configuration file (e.g. {{{lcsgih_parallel}}} for HLRN). … … 111 112 }}} 112 113 113 === Installation Verification ===114 === Installation verification === 114 115 115 116 As a last step, after the compilation has been finished, the PALM installation has to be verified. For this purpose a simple test run is carried out. This once again requires the '''mrun''' configuration file (described in [../chapter_3_2 chapter 3.2]), as well as the [../parameterfile parameter file] (described in [../chapter_4_4_1 chapter 4.4.1]). The parameter file must be copied from the PALM working copy by … … 198 199 The simple installation method is using the scripts '''palm_simple_install''' and '''palm_simple_run''' for installing and running PALM. 199 200 200 === Package Installation ===201 === Package installation === 201 202 202 203 '''First step:''' Create a directory:
