Changes between Version 35 and Version 36 of doc/app/userint/int


Ignore:
Timestamp:
Sep 14, 2010 3:10:25 PM (14 years ago)
Author:
suehring
Comment:

--

Legend:

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

    v35 v36  
    200200}}}
    201201{{{#!td style="vertical-align:top; text-align:left;style="width: 50px"
    202 [=#user_check_data_output_pr {{{user_check_data_output_pr}}}]\\{{{(variable, var_count, unit )}}}
    203 }}}
    204 {{{#!td
    205 Here the physical {{{unit}}}(s) and vertical grid (u- or w-grid) of user-defined vertical profile output quantities (see [../../userpar#data_output_pr_user data_output_pr_user]) have to be set. Input parameter {{{variable}}} contains the string identifier of the respective variable. Parameter {{{var_count}}} contains the internal profile number and must not be changed by the user. For those variables not recognized by the user, the parameter {{{unit}}} is set to "illegal", which tells the calling routine that the output variable is not defined and leads to a program abort.
     202[=#user_check_data_output_pr {{{user_check_data_output_pr}}}] \\{{{(variable, var_count, unit )}}}
     203}}}
     204{{{#!td
     205Here the physical {{{unit}}}(s) and vertical grid (u- or w-grid) of user-defined vertical profile output quantities (see [../../userpar#data_output_pr_user data_output_pr_user]) have to be set. Input parameter {{{variable}}} contains the string identifier of the respective variable. Parameter {{{var_count}}} contains the internal profile number and must not be changed by the user. For those variables not recognized by the user, the parameter {{{unit}}} is set to "illegal", which tells the calling routine that the output variable is not defined and leads to a program abort.\\
     206See [wiki:chapter_354 chapter 3.5.4] about creating user-defined output quantities.
     207}}}
     208|----------------
     209{{{#!td style="vertical-align:top; text-align:left;width: 150px"
     210{{{netcdf.f90}}} (4 times) where the vertical grid coordinates for cross sections and volume data are defined
     211}}}
     212{{{#!td style="vertical-align:top; text-align:left;style="width: 50px"
     213[=#user_define_netcdf_grid {{{user_define_netcdf_grid}}}] \\{{{( variable, found, grid_x, grid_y, grid_z )}}}
     214}}}
     215{{{#!td
     216Set the grid on which user-defined output quantities (see [../../userpar#data_output_user data_output_user]) are defined. Input parameter {{{variable}}} contains the string identifier of the respective variable. Allowed values are'' 'x' ''and'' 'xu' ''for {{{grid_x}}},'' 'y' ''and'' 'yv' ''for {{{grid_y}}}, and'' 'zu' ''and'' 'zw' ''for {{{grid_z}}}. The output parameter {{{found}}} has to be set ''.TRUE.'' by the user, otherwise an error message will appear in the job protocol for the respective output quantity.\\
    206217
     218Example:
     219If an output quantity is defined at the center of the grid boxes, the following settings have to be used:
     220{{{
     221grid_x = 'x'
     222grid_y = 'y'
     223grid_z = 'zu'
     224found  = .TRUE.
     225}}}
     226For defining an output quantity at the grid points where the u-velocity-component is defined, please use
     227{{{
     228grid_x = 'xu'
     229grid_y = 'y'
     230grid_z = 'zu'
     231found  = .TRUE.
     232}}}
    207233See [wiki:chapter_354 chapter 3.5.4] about creating user-defined output quantities.
    208234}}}