Changes between Version 2 and Version 3 of doc/app/examples/coupled

Timestamp:

Dec 2, 2010 2:22:35 PM (15 years ago)

Author:

fricke

Comment:

--

doc/app/examples/coupled

@@ -10 +10 @@
 }}}
 The {{{-X ...}}} option here specifies the total number of processors assigned to the coupled model. Currently, half of them are assigned to each of the two coupled executables. Therefore it is advisable to specify an even number with {{{-X ...}}}. Otherwise, in case of an odd total number of processors, one processor remains idle.\\\\
-Each coupled executable has its own, unique set of I/O filenames; [[chapter 3.4]] gives information on file name conventions of coupled runs. The configuration file {{{.mrun.config}}} has to be extended for coupled runs. It is recommended to duplicate existing file connection identifiers such as {{{"d3#"}}}, {{{"pr#"}}} etc. using the coupled ocean filenames accordingly. For example, the example of the previous chapters could be duplicated as follows:
+Each coupled executable has its own, unique set of I/O filenames. Information on file name conventions of coupled runs are given [../../iofiles here]. The configuration file {{{.mrun.config}}} has to be extended for coupled runs. It is recommended to duplicate existing file connection identifiers such as {{{"d3#"}}}, {{{"pr#"}}} etc. using the coupled ocean filenames accordingly. For example, the example of the previous chapters could be duplicated as follows:
 {{{
 PARIN in:job:npe d3# ~/palm/current_version/JOBS/$fname/INPUT _p3d