Changes between Version 10 and Version 11 of doc/app/userint/output

Timestamp:

Sep 15, 2010 2:07:19 PM (14 years ago)

Author:

suehring

Comment:

--

doc/app/userint/output

@@ -39 +39 @@
    Once again, only those parts in red have to be adjusted by the user.\\
    The turbulent resolved-scale momentum flux ''u*v*'' is defined as the product of the deviations of the horizontal velocities from their respective horizontally averaged mean values. These mean values are stored in array {{{hom(..,1,1,sr)}}} and {{{hom(..,1,2,sr)}}} for the u- and v-component, respectively. Since due to the staggered grid, u and v are not defined at the same gridpoints, they have to be interpolated appropriately (here to the center of the gridbox). The result of the calculation is stored in array {{{sums_l}}}. The second index of this array is the identification number of the profile which must match the one given in the previous step 2. \\\\
-[#part_2 '''2. Output of user-defined timeseries'''] \\\\
+[=#part_2 '''2. Output of user-defined timeseries'''] \\\\
 This example shows the output of two time series for the absolut extremal values of the horizontal velocities u and 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.\\\\
    1. For each time series quantity you have to give a label and a unit (subroutine [../int#user_init user_init]), which will be used for the netCDF file. They must not contain more than seven characters. The value of {{{dots_num}}} has to be increased by the number of new time series quantities. Its old value has to be stored in {{{dots_num_palm}}}.
@@ -59 +59 @@
 
  
-[part_3 '''3. Output of user-defined 2d cross sections or 3d volume data'''] \\\\
+[=#part_3 '''3. Output of user-defined 2d cross sections or 3d volume data'''] \\\\
 
 This example shows the output of the quantity "square of the u-component" ('''Note:''' this quantity could of course easily be calculated from the u-component by postprocessing the {{{PALM}}} output so that calculation within {{{PALM}}} is not necessarily required). 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.
@@ -272 +272 @@
           ENDIF
 
-[#part_4 '''4. Output of user-defined DVRP objects'''] \\\\
+[=#part_4 '''4. Output of user-defined DVRP objects'''] \\\\
 This example shows the output of the quantity "square of the u-component", u2. 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. First, steps 1 - 6 of part 3. (2d cross section or 3d volume data) are required. Second, the gridpoint data of the quantity has to be resorted to array local_pf in subroutine user_data_output_dvrp as follows:
 
@@ -288 +288 @@
 After performing these steps, the user-defined quantity 'u2' can be selected like standard model quantities by the dvrp_graphics package parameter mode_dvrp.
 
-[part_5 '''5. Output of user-defined spectra'''] \\\\
+[=#part_5 '''5. Output of user-defined spectra'''] \\\\
 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.