Changes between Version 1 and Version 2 of doc/app/userint/comp


Ignore:
Timestamp:
Sep 15, 2010 12:19:19 PM (14 years ago)
Author:
suehring
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • doc/app/userint/comp

    v1 v2  
    11== Compiling and linking user-defined code ==
    22
    3 Users can add their own (modified) user-interface to a PALM-run by carrying out the following steps:
    4 
     3Users can add their own (modified) user-interface to a PALM-run by carrying out the following steps:\\\\
    54   1. Copy the appropriate default (empty) user-interface files {{{user_***.f90}}} to a directory of your choice, e.g.:
    65{{{
     
    98cp trunk/SOURCE/user_***.f90  USER_CODE/example
    109}}}
    11       Attention: do not change the filenames!
     10      '''Attention: do not change the filenames!'''
    1211
    1312   2. Set an additional path in the configuration file .mrun.config to allow mrun to find and include these files:
     
    1514%add_source_path   $base_directory/USER_CODE/$fname
    1615}}}
    17       The default configuration file ({{{trunk/SCRIPTS/.mrun.config.default}}}) already includes this setting.
    18    3. Modify the interface routines according to your needs.
     16      The default configuration file ({{{trunk/SCRIPTS/.mrun.config.default}}}) already includes this setting.\\
     17   3. Modify the interface routines according to your needs.\\
    1918   4. Start a PALM run by executing
    2019{{{
    2120mrun -d example ...
    2221}}}
    23       The files {{{user_***.f90}}} will be automatically compiled within the job and will replace the respective {{{PALM}}}‘s default user-interface routines.
     22      The files {{{user_***.f90}}} will be automatically compiled within the job and will replace the respective {{{PALM}}}‘s default user-interface routines.\\\\
    2423
    25 The above method with including {{{$fname}}} in the additional source path allows to use different user-interfaces for different runs at the same time. Just store the respective interface-files in subdirectories {{{USER_CODE/abcd}}}, {{{USER_CODE/cdef}}}, etc. and start '''mrun''' with option "{{{-d abcd}}}", "{{{-d cdef}}}", etc.
    26 
     24The above method with including {{{$fname}}} in the additional source path allows to use different user-interfaces for different runs at the same time. Just store the respective interface-files in subdirectories {{{USER_CODE/abcd}}}, {{{USER_CODE/cdef}}}, etc. and start '''mrun''' with option "{{{-d abcd}}}", "{{{-d cdef}}}", etc. \\\\
    2725If the user wants to add additional routines, he/she can a) put them into the default user-interface file {{{user_additional_routines.f90}}} or b) can create new files in the additional source directory. These files must have names different from the default {{{PALM}}} source code files. In case of b), the user must also copy the default makefile into the additional source directory:
    2826{{{