Changes between Version 71 and Version 72 of doc/app/userint/output


Ignore:
Timestamp:
Jan 21, 2015 7:37:09 AM (10 years ago)
Author:
raasch
Comment:

--

Legend:

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

    v71 v72  
    1212[=#part_1 '''1. Output of user-defined vertical profiles'''] \\\\
    1313This 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.\\
    14    1. 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 parameter [../../d3par#data_output_pr data_output_pr]). The identifier must not contain more than '''ten''' characters. To switch on output of this quantity, the user has to assign the string identifier to the parameter [../../userpar#data_output_pr_user data_output_pr_user], eg.:\\
     14   1. 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 parameter [../../d3par#data_output_pr data_output_pr]). The identifier must not contain more than '''ten''' characters. In case that 2d cross section output is defined on one single level only (see chapter 3, paragraph 9, further below), the identifier string must contain an asterisk ({{{"*"}}}). To switch on output of the quantity, the user has to assign the string identifier to the parameter [../../userpar#data_output_pr_user data_output_pr_user], eg.:\\
    1515
    1616   {{{ data_output_pr_user = 'u*v*' }}}, \\
     
    169169      The {{{ELSE}}} case is only needed in case that output of time-averaged data is requested. \\
    170170
    171       As a special case, ''xy'' cross section output can also be defined at one single level at height {{{k=nzb+1}}} on the u-grid. This features is useful for output of surface data (e.g. heat fluxes). In this case, the corresponding 2d data has to be resorted to the array {{{local_pf(i,j,nzb+1)}}}. In addition to this, the grid in [../int#user_define_netcdf_grid user_define_netcdf_grid] as well as in [../#user_data_output_2d user_data_output_2d] must be set to {{{grid = 'zu1'}}}.
    172 
    173       {{{ CASE ( 'u2_xy' ) }}} \\
     171      As a special case, ''xy'' cross section output can also be defined at one single level at height {{{k=nzb+1}}} on the u-grid. This features is useful for output of surface data (e.g. heat fluxes). In this case, the corresponding 2d data has to be resorted to the array {{{local_pf(i,j,nzb+1)}}}. In addition to this, the grid in [../int#user_define_netcdf_grid user_define_netcdf_grid] as well as in [../#user_data_output_2d user_data_output_2d] must be set to {{{grid = 'zu1'}}}. Furthermore, the identifier string must contain an asterisk ({{{'*'}}}).
     172
     173      {{{ CASE ( 'u2*_xy' ) }}} \\
    174174         {{{ IF ( av == 0 )  THEN }}} \\
    175175            {{{    DO  i = nxlg, nxrg }}} \\