Changes between Version 15 and Version 16 of doc/app/userint/output

Timestamp:

Sep 15, 2010 2:41:49 PM (14 years ago)

Author:

suehring

Comment:

--

doc/app/userint/output

@@ -56 +56 @@
    2. These quantities are calculated and output in subroutine [../int#user_statistics user_statistics] for every statistic region {{{sr}}} defined by the user, but at least for the region "total domain":
        
-          ts_value(dots_num_palm+1,sr) = ABS( u_max )
-          ts_value(dots_num_palm+2,sr) = ABS( v_max )
-
- 
+   {{{ts_value(dots_num_palm+1,sr) = ABS( u_max )}}} \\
+   {{{ts_value(dots_num_palm+2,sr) = ABS( v_max )}}} \\
+
 [=#part_3 '''3. Output of user-defined 2d cross sections or 3d volume data'''] \\\\
 
@@ -65 +64 @@
 
    1. The quantity has to be given a unique string identifier, e.g.'' 'u2'.'' This identifier must be different from the identifiers used for the {{{PALM}}} standard output (see list in description of parameter [../../d3par#data_output data_output]). To switch on output of this quantity, the user has to assign the string identifier to the parameter [../../userpar#data_output_user data_output_user], eg.:
-{{{
-data_output_user = 'u2',  'u2_xy_av'
-}}}
+   {{{data_output_user = 'u2',  'u2_xy_av' }}} \\
+
       The pure string'' 'u2' ''switches on the output of instantaneous 3d volume data. Output of cross section data and time averaged data is switched on by additionally appending the strings'' '_xy', '_xz', '_yz', ''and/or'' '_av' ''(for a detailed explanation see parameter [../../d3par#data_output data_output]).\\\\
    2. In order to store the quantities' grid point data within PALM, a 3d data array has to be declared in module [../int#user_module user]:
-{{{
-REAL, DIMENSION(:,:,:), ALLOCATABLE ::  u2, u2_av
-}}} 
+   {{{REAL, DIMENSION(:,:,:), ALLOCATABLE ::  u2, u2_av }}} \\
+
       The second array {{{u2_av}}} is needed in case that output of time averaged data is requested. It is used to store the sum of the data of the respective time levels over which the average has to be carried out. \\\\
    3. The data array has to be allocated in subroutine [../int#user_init user_init]:
+   {{{ALLOCATE( u2(nzb:nzt+1,nys-1:nyn+1,nxl-1:nxr+1) ) }}} \\
+
+      In case that output of time averaged data is requested, the array containing the sum has possibly to be read from the restart file (local filename [../../iofiles#BININ BININ) by executing the following code in [../int#user_init user_init]:
 {{{
-ALLOCATE( u2(nzb:nzt+1,nys-1:nyn+1,nxl-1:nxr+1) )
-}}}
-      In case that output of time averaged data is requested, the array containing the sum has possibly to be read from the restart file (local filename BININ) by executing the following code in [../int#user_init user_init]:
-
           IF ( initializing_actions == 'read_restart_data' )  THEN
              READ ( 13 )  field_char
@@ -99 +95 @@
              ENDDO
           ENDIF
-
+}}}
 
    4. The quantity has to be given a unit (subroutine user_check_data_output):