Changes between Version 11 and Version 12 of doc/install/advanced
- Timestamp:
- Nov 1, 2018 3:43:23 PM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
doc/install/advanced
v11 v12 69 69 {{{ 70 70 cd ~/palm/current_version 71 palmbuild - hdefault72 }}} 73 Option {{{- hdefault}}} can be omitted, because {{{default}}} is the default.71 palmbuild -c default 72 }}} 73 Option {{{-c default}}} can be omitted, because {{{default}}} is the default. 74 74 75 75 {{{palmbuild}}} will prompt some queries, which must all be answered "y". Depending on which compiler optimization options have been set in the configuration file, compilations may take up to 10 minutes. {{{palmbuild}}} is using the ''make'' mechanism. Dependencies are described in a [source:palm/trunk/SOURCE/Makefile Makefile]. {{{palmbuild}}} creates a folder {{{MAKE_DEPOSITORY_<configuration identifier>}}} in your working directory (in the default case it is {{{MAKE_DEPOSITORY_default}}}.\\\\ … … 88 88 The test run can now be started by entering 89 89 {{{ 90 palmrun - d example_cbl -hdefault -X4 -a "d3#"90 palmrun -r example_cbl -c default -X4 -a "d3#" 91 91 }}} 92 92 See the [wiki:doc/app/palmrun palmrun description] for detailed explanations of available options. This specific run will be carried out on 4 cores (if available on your system, others you may need to adjust the {{{-X}}} option). Most important settings of this run are displayed at the terminal window and you are prompted for o.k. ("{{{y}}}") to continue. Informations about the progress of the simulation will be output to the terminal. After {{{palmrun}}} has finished, you should find some result files in folder {{{JOBS/example_cbl/MONITORING}}}. Please compare the contents of file … … 109 109 Running PALM in batch mode on your local computer (requires that the computer where you are logged in has a batch system running) requires to add appropriate batch directives to the configuration file as well as settings for variables like {{{local_jobcatalog}}}, {{{defaultqueue}}}, {{{memory}}}, and {{{submit_command}}}. Settings for {{{module_commands}}} and {{{login_init_cmd}}} may be needed too. See the [wiki:doc/app/palm_config configuration file description] for further details. In order to run PALM in batch mode, the installation process is the same as described above, but {{{palmrun}}} requires additional options and may look like this 110 110 {{{ 111 palmrun - d example_cbl -hdefault -X4 -T4 -t200 -m1000 -a "d3#" -q testqueue -b111 palmrun -r example_cbl -c default -X4 -T4 -t200 -m1000 -a "d3#" -q testqueue -b 112 112 }}} 113 113 The {{{-b}}} option is essential to tell {{{palmrun}}} to generate and submit a batch job. Otherwise, it will try to execute PALM interactively in your terminal session. Again, result files for verifying the installation can be found in folder {{{JOBS/example_cbl/MONITORING}}}, after the batch job has been executed. The protocol file of the batch job, which is typically created by every batch system, can be found in the folder that has been set by {{{local_jobcatalog}}} under the name {{{<configuration identifier>_<run identifier>}}}, which is {{{default_example_cbl}}} in the given example. Further informations about running PALM in batch mode on local machines can be found in the [wiki:doc/app/palmrun_quickstart palmrun quickstart guide]. … … 118 118 Follow the installation steps described above. In addition to the settings for a local batch job, installation of PALM for running batch jobs on remote machines requires further additional entries in the configuration file, at least variables {{{remote_ip}}}, {{{remote_username}}}, and {{{remote_jobcatalog}}} need to be set. For further informations see the [wiki:doc/app/palmrun_quickstart palmrun quickstart guide] and the [wiki:doc/app/palmrun palmrun documentation]. Assuming a configuration file {{{.palm.config.remote_system}}}, compiling the PALM sources via 119 119 {{{ 120 palmbuild - hremote_system120 palmbuild -c remote_system 121 121 }}} 122 122 will copy the PALM sources by {{{scp}}} from your local computer to the remote system and invokes the remote compiler using {{{ssh}}}. The binaries will be put in folder {{{$HOME/palm/current_version/MAKE_DEPOSITORY_remote_system}}} on the remote system. … … 124 124 For using {{{palmrun}}}, additional batch directives have to be added to the configuration file in order to transfer back the job protocol file (see the [wiki:doc/app/palmrun_quickstart palmrun quickstart guide] for further details). The {{{palmrun}}} command for generating the test run then reads 125 125 {{{ 126 palmrun - d example_cbl -hremote_system -X4 -T4 -t200 -m1000 -a "d3#" -q testqueue126 palmrun -r example_cbl -c remote_system -X4 -T4 -t200 -m1000 -a "d3#" -q testqueue 127 127 }}} 128 128 {{{palmrun}}} transfers back the result file via {{{scp}}} and you should find it on your local system in folder {{{JOBS/example_cbl/MONITORING}}} under the name {{{remote_system_example_cbl_rc}}} after the job on the remote system has finished. The job protocol file will also be copied to the folder that has been set by {{{local_jobcatalog}}}. … … 173 173 The compiled PALM code and helper routines must then be updated via 174 174 {{{ 175 palmbuild - hdefault175 palmbuild -c default 176 176 }}} 177 177 or for any other configuration files that you are using.\\\\ … … 204 204 %fast_io_catalog <replace with your fast file system folder> 205 205 }}} 206 Every user will then use the pre-compiled version of PALM that has been created for the central installation under the configuration identifier {{{default}}}. {{{palmrun}}} can only be called with this configuration identifier ({{{palmrun - hdefault ....}}}). If other configurations are required, they have to be created ''by the administrator'' under the central installation206 Every user will then use the pre-compiled version of PALM that has been created for the central installation under the configuration identifier {{{default}}}. {{{palmrun}}} can only be called with this configuration identifier ({{{palmrun -c default ....}}}). If other configurations are required, they have to be created ''by the administrator'' under the central installation 207 207 {{{ 208 208 cp /path_to_the_central_installation/trunk/SCRIPTS/.palm.config.default /path_to_the_central_installation/.palm.config.config_new 209 209 # edit .palm.config.config_new 210 210 cd /path_to_the_central_installation 211 palmbuild - hconfig_new212 }}} 213 After that, users need to copy and modify this configuration file as described above, and can use this configuration via {{{palmrun - hconfig_new ....}}}.211 palmbuild -c config_new 212 }}} 213 After that, users need to copy and modify this configuration file as described above, and can use this configuration via {{{palmrun -c config_new ....}}}.
