Changes between Version 31 and Version 32 of doc/app/userint/output


Ignore:
Timestamp:
Sep 16, 2010 7:33:48 AM (14 years ago)
Author:
suehring
Comment:

--

Legend:

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

    v31 v32  
    277277
    278278[=#part_5 '''5. Output of user-defined spectra'''] \\\\
    279 This example shows the output of the quantity "turbulent resolved-scale horizontal momentum flux" (u*v*). If more than one user-defined quantity shall be output, the following steps have to be carried out in the same way for each of the quantities.
    280 
    281    1. The calculation of user-defined spectra is closely linked with the calculation of part 1. (user-defined vertical profiles) and part 3. (user-defined 3d volume data). Therefore, the following prerequisites apply for each user-defined spectra quantity:
    282 
    283          1. From part 1. (user-defined vertical profiles) steps 2 and 3.
    284             See the sample code (as comment lines) for 'u*v*' and ustvst, respectively. (Actual output of vertical profiles - step 1 - is not required.)
    285          2. From part 3. (user-defined 3d volume data) steps 2, 3, 4, 5, and 6.
    286             See the sample code (as comment lines) for 'u*v*' and ustvst, respectively. (Actual output of 3d volume data - step 1 - is not required.)
    287          3. The quantity has to be given a unique string identifier, e.g. 'u*v*'. This identifier must be different from the identifiers used for the PALM standard output (see list in description of package parameter data_output_sp). To switch on output of this quantity, the user has to assign the string identifier to the package parameter data_output_sp, eg.:
    288 
    289                 data_output_sp =  'u*v*'
    290 
    291       A. and B. as prerequisites for C. require a naming convention of identical identifiers, e.g. data_output_pr_user = 'u*v*', data_output_user = 'u*v*' and data_output_sp = 'u*v*'. This naming convention applies only in case of user-defined spectra.
    292 
    293    2. Edit the subroutine user_spectra (only those parts in red) as follows:
     279This example shows the output of the quantity "turbulent resolved-scale horizontal momentum flux" ''(u*v*).'' If more than one user-defined quantity shall be output, the following steps have to be carried out in the same way for each of the quantities.
     280
     281   1. The calculation of user-defined spectra is closely linked with the calculation of [#part_1 part 1. (user-defined vertical profiles)] and [part_3 part 3. (user-defined 3d volume data)]. Therefore, the following prerequisites apply for each user-defined spectra quantity:
     282
     283         1. From [#part_1 part 1. (user-defined vertical profiles)] steps 2 and 3.
     284            See the sample code (as comment lines) for'' 'u*v*' ''and ustvst, respectively. (Actual output of vertical profiles - step 1 - is not required.)
     285         2. From [#part_3 part 3. (user-defined 3d volume data)] steps 2, 3, 4, 5, and 6.
     286            See the sample code (as comment lines) for'' 'u*v*' ''and {{{ustvst}}}, respectively. (Actual output of 3d volume data - step 1 - is not required.)
     287         3. The quantity has to be given a unique string identifier, e.g.'' 'u*v*'.'' This identifier must be different from the identifiers used for the {{{PALM}}} standard output (see list in description of package parameter [../../sppar#data_output_sp data_output_sp]). To switch on output of this quantity, the user has to assign the string identifier to the package parameter [../../sppar#data_output_sp data_output_sp], eg.:
     288
     289         {{{ data_output_sp =  'u*v*' }}} \\
     290
     291   A. and B. as prerequisites for C. require a naming convention of identical identifiers, e.g. [../../userpar#data_output_pr_user data_output_pr_user]='' 'u*v*','' [../../userpar#data_output_user data_output_user] ='' 'u*v*' ''and [../../sppar#data_output_sp data_output_sp]='' 'u*v*'.'' This naming convention applies only in case of user-defined spectra.
     292
     293   2. Edit the subroutine user_spectra (only those parts in [[span(red,style=color: red)]]) as follows:
    294294
    295295          IF ( mode == 'preprocess' )  THEN