Changes between Version 47 and Version 48 of doc/app/palmrun


Ignore:
Timestamp:
Nov 23, 2018 8:55:33 AM (6 years ago)
Author:
scharf
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • doc/app/palmrun

    v47 v48  
    195195If the run has finished successfully, results can be found in folders {{{JOBS/neutral/MONITORING}}} and {{{JOBS/neutral/OUTPUT}}}.
    196196
    197 == [#=batch Batch mode] ==
    198 
    199 Large simulation set-ups usually cannot be run interactively, since the large amount of required resources (memory as well as cpu-time) are only provided through batch environments. {{{palmrun}}} supports two different ways to run PALM in batch mode. In both cases it creates a batch job, i.e. a file containing directives for a queuing-system plus commands to run PALM, which is then either submitted to your local computer or to a remote computer. Running PALM in batch mode requires you to manually modify and extend your [wiki:doc/palm_confi configuration file], and that a batch system (e.g. PBS, Slurm, ...) is installed on the respective computer.
    200 
    201 === [#=batch_local Running PALM in batch on a local computer] ===
     197== [=#batch Batch mode] ==
     198
     199Large simulation set-ups usually cannot be run interactively, since the large amount of required resources (memory as well as cpu-time) are only provided through batch environments. {{{palmrun}}} supports two different ways to run PALM in batch mode. In both cases it creates a batch job, i.e. a file containing directives for a queuing-system plus commands to run PALM, which is then either submitted to your local computer or to a remote computer. Running PALM in batch mode requires you to manually modify and extend your [wiki:doc/app/palm_config configuration file], and that a batch system (e.g. PBS, Slurm, ...) is installed on the respective computer.
     200
     201=== [=#batch_local Running PALM in batch on a local computer] ===
    202202
    203203The local computer is the one where the commands that you enter in a terminal sessions are executed. This might be your local PC/workstation, or a login-node of a cluster-system / computer center where you are logged in via ssh. Regardless of the computer, it is assumed that PALM has been successfully installed on that machine, either using the automatic installer or via manual installation.
     
    250250
    251251 
    252 === [#=batch_remote Running PALM in batch on a remote computer] ===
     252=== [=#batch_remote Running PALM in batch on a remote computer] ===
    253253
    254254You can use the {{{palmrun}}} command on your local computer (e.g. your local PC or workstation) and let it submit a batch job to a remote computer at any place in the world. {{{palmrun}}} copies required input files from your local computer to the remote machine and transfers output files back to your local machine, depending on the settings in the {{{.palm.iofiles}}} file. The job protocol file will also be automatically copied back to your local computer.
     
    280280
    281281
    282 == [#=options palmrun options] ==
     282== [=#options palmrun options] ==
    283283There are two groups of options, one are the '''user options''' that you can specify yourself when manually calling {{{palmrun}}} from the terminal, and another group of '''internal options''' that are used for automatically created internal calls of {{{palmrun}}}. Internal calls of {{{palmrun}}} are those that are part of the batch job, and those used for automatically starting restart jobs. Normally, you should never use the internal options. User options from a manual call are automatically added to the internal calls of {{{palmrun}}}.
    284284