Changes between Version 21 and Version 22 of doc/app/userint/output

Timestamp:

Sep 15, 2010 3:44:12 PM (14 years ago)

Author:

suehring

Comment:

--

doc/app/userint/output

@@ -113 +113 @@
    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':
-
-          CASE ( 'after_integration' )
-      !
-      !--    Enter actions to be done after every time integration (before
-      !--    data output)
-      !--    Sample for user-defined output:
-             DO  i = nxl-1, nxr+1
-                DO  j = nys-1, nyn+1
-                   DO  k = nzb, nzt+1
-                      u2(k,j,i) = u(k,j,i)**2
-                   ENDDO
-                ENDDO
-             ENDDO
-
+   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': \\
+
+   {{{ CASE ( 'after_integration' ) }}} \\
+   {{{!}}} \\
+   {{{!--    Enter actions to be done after every time integration (before}}} \\
+   {{{!--    data output) }}} \\
+   {{{!--    Sample for user-defined output: }}} \\
+   {{{       DO  i = nxld, nxrd }}} \\
+      {{{       DO  j = nysd, nynd }}} \\
+         {{{       DO  k = nzb, nzt+1 }}} \\
+            {{{       u2(k,j,i) = u(k,j,i)**2 }}} \\
+         {{{       ENDDO }}} \\
+      {{{       ENDDO }}} \\
+   {{{       ENDDO }}} \\
        
    7. In case that output of time-averaged data is requested, the sum- and average-operations as well as the allocation of the sum-array have to be carried out in subroutine user_3d_data_averaging: