Changes between Version 19 and Version 20 of doc/app/userint/output

Timestamp:

Sep 15, 2010 3:37:36 PM (14 years ago)

Author:

suehring

Comment:

--

doc/app/userint/output

@@ -99 +99 @@
    {{{    ENDIF }}} \\
 
-   4. The quantity has to be given a unit (subroutine user_check_data_output):
-
-          CASE ( 'u2' )
-             unit = 'm2/s2'
-       
-      Otherwise, PALM will abort.
-
-
-   5. The vertical grid on which the quantity is defined (given by the levels 'zu' or 'zw', on which the u- or w-component of the velocity are defined) has to be specified for the NetCDF output files in subroutine user_define_netcdf_grid:
-
-          CASE ( 'u2', 'u2_xy', 'u2_xz', 'u2_yz' )
-             grid = 'zu'
-       
-      As the example shows, this grid has to be defined for the 3d volume data as well as for all of the three cross sections.
-
+   4. The quantity has to be given a unit (subroutine [../int#user_check_data_output user_check_data_output]): \\
+
+   {{{ CASE ( 'u2' )}}} \\
+      {{{ unit = 'm2/s2' }}} \\
+       
+   Otherwise, {{{PALM}}} will abort. \\ 
+
+   5. The vertical grid on which the quantity is defined (given by the levels '{{{zu}}}' or '{{{zw}}}', on which the u- or w-component of the velocity are defined) has to be specified for the netCDF output files in subroutine [../int#user_define_netcdf_grid user_define_netcdf_grid]:
+
+   {{{ CASE ( 'u2', 'u2_xy', 'u2_xz', 'u2_yz' ) }}} \\
+     {{{ grid = 'zu' }}} \\
+       
+   As the example shows, this grid has to be defined for the 3d volume data as well as for all of the three cross sections. \\
 
    6. After each timestep, the quantity has to be calculated at all gridpoints and to be stored. This has to be done in subroutine user_actions at location 'after_integration':