Index: palm/trunk/DOC/app/chapter_3.5.4.html
===================================================================
--- palm/trunk/DOC/app/chapter_3.5.4.html (revision 404)
+++ palm/trunk/DOC/app/chapter_3.5.4.html (revision 405)
@@ -1,10 +1,10 @@
+
PALM chapter 3.5.4
-3.5.4
+3.5.4
User-defined output quantities
A very typical request of users is the
@@ -172,8 +172,8 @@
IF ( initializing_actions == 'read_restart_data' )
THEN
- READ ( 13 ) field_chr
- DO WHILE ( TRIM( field_chr ) /= '*** end
+ READ ( 13 ) field_char
+ DO WHILE ( TRIM( field_char ) /= '*** end
user ***' )
- SELECT CASE ( TRIM( field_chr ) )
+ SELECT CASE ( TRIM( field_char ) )
CASE ( 'u2_av' )
ALLOCATE(
@@ -186,6 +186,5 @@
-TRIM(
-field_chr ), '" found in'
+TRIM( field_char ), '" found in'
PRINT*,
'
@@ -276,5 +275,8 @@
grid = 'zu'
The ELSE case is
only needed in case that output of time-averaged data is requested.
-As a special case, xy cross section output can also be defined at one single level at height k=nzb+1 on the u-grid. This features is useful for output of surface data (e.g. heat fluxes). In this case, the corresponding 2d data has to be resorted to the array local_pf(i,j,nzb+1). In addition to this, the grid in user_define_netcdf_grid as well as in user_data_output_2d must be set to grid = 'zu1'.
+As a special case, xy cross section output can also be defined at one single level at height k=nzb+1
+on the u-grid. This features is useful for output of surface data (e.g.
+heat fluxes). In this case, the corresponding 2d data has to be
+resorted to the array local_pf(i,j,nzb+1). In addition to this, the grid in user_define_netcdf_grid as well as in user_data_output_2d must be set to grid = 'zu1'.
CASE
( 'u2_xy' )