Changes between Version 23 and Version 24 of doc/app/palm_config
- Timestamp:
- Nov 20, 2018 4:23:12 PM (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
doc/app/palm_config
v23 v24 128 128 Strings in double curly brackets are interpreted as variables and are replaced by {{{palmrun}}} based on settings via specific {{{palmrun}}} options or settings in the environment variable section of the configurations file. From the given batch directives, {{{palmrun}}} generates a batch script (file), also called batch job, which is then submitted to the batch system using the submit command that has been defined by {{{submit_command}}} (see environment variable section above). If you like to check the generated batch script, then run {{{palmrun}}} with additional option {{{-F}}}, which will write the batch script to file {{{jobfile.#####}}} in your current working directory, where {{{#####}}} is a 5-digit random number (which is part of the so-called job-id). A batch job will not be submitted. 129 129 130 In addition to the batch directives, the configuration file requires further information to be set for using the batch system, which is done by adding / modifying variable assignments. A minimum set of variables to be added / modified: 131 {{{ 132 # to be added 133 %submit_command /opt/moab/default/bin/msub -E 134 %defaultqueue small 135 %memory 1500 136 137 # to be modified 138 %local_jobcatalog /home/username/local_jobcatalog 139 %fast_io_catalog /gfs2/work 140 %execute_command aprun -n {{mpi_tasks}} -N {{tasks_per_node}} ./palm 141 }}} 142 Given values are just examples! The automatic installer may have already included these variable settings as comment lines (starting with {{{#}}}). Then just remove the {{{#}}} and provide a proper value. 143 144 130 145 The following variables are frequently used in batch directives and recognized by {{{palmrun}}} by default: 131 146