| [5] | 1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> |
|---|
| 2 | <html><head> |
|---|
| [90] | 3 | <meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252"><title>PALM chapter 3.5.1</title> <meta name="GENERATOR" content="StarOffice 7 (Win32)"> <meta name="AUTHOR" content="Siegfried Raasch"> <meta name="CREATED" content="20040802;11451548"> <meta name="CHANGED" content="20041112;14401801"> <meta name="KEYWORDS" content="parallel LES model"> <style> |
|---|
| [5] | 4 | <!-- |
|---|
| 5 | @page { size: 21cm 29.7cm } |
|---|
| 6 | --> |
|---|
| [62] | 7 | </style></head> |
|---|
| 8 | <body style="direction: ltr;" lang="en-US"><h3 style="line-height: 100%;">3.5.1 Interfaces for |
|---|
| [5] | 9 | user-defined code<br> |
|---|
| [62] | 10 | </h3><p style="margin-bottom: 0cm; line-height: 100%;">The |
|---|
| [5] | 11 | following table |
|---|
| 12 | describes the available interfaces for user-defined code in the model, |
|---|
| 13 | the |
|---|
| 14 | names and possible arguments of the subroutines involved as well as |
|---|
| 15 | actions which can be accomplished in these subroutines. <br> |
|---|
| 16 | </p> |
|---|
| [62] | 17 | <table style="width: 100%;" border="1" cellpadding="2" cellspacing="4"> <col width="211"> <col width="117"> <col width="862"> <tbody> <tr><td width="211"> <p><font size="4"><b>Call |
|---|
| 18 | location</b></font></p> </td> <td width="117"> <p><font size="4"><b>Subroutine |
|---|
| 19 | name and |
|---|
| 20 | argument</b></font></p> </td> <td style="width: 862px;"> <p><font size="4"><b>Possible |
|---|
| 21 | actions</b></font></p> </td> </tr> <tr><td>---</td><td><span style="font-family: monospace;"><a name="user"></a>MODULE |
|---|
| 22 | user</span></td><td>All |
|---|
| [5] | 23 | user-defined variables which are used outside the respective local |
|---|
| [62] | 24 | scopes of the user-defined subroutines have to be declared here.</td></tr><tr valign="top"> <td width="211"> <p>End |
|---|
| 25 | of <tt><font style="font-size: 10pt;" size="2">parin.f90</font></tt></p> |
|---|
| 26 | </td> <td width="117"> <p><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><a name="user_parin"></a>user_parin</font></font></tt></p> |
|---|
| 27 | </td> <td width="862"> <p>Declaration of |
|---|
| 28 | user-defined parameters in the NAMELIST |
|---|
| [5] | 29 | group <tt><font style="font-size: 10pt;" size="2">&userpar</font></tt>. |
|---|
| 30 | These |
|---|
| 31 | parameters can be read from the local file <a href="chapter_3.4.html#PARIN">PARIN</a> |
|---|
| 32 | and be used for steering the user-defined code (see <a href="chapter_4.0.html">chapter |
|---|
| 33 | 4.0</a>). The user-defined parameter <a href="chapter_4.3.html#region">region</a> |
|---|
| 34 | is already pre-defined in <tt><font style="font-size: 10pt;" size="2">&userpar</font></tt> |
|---|
| 35 | and must not be changed. Additional NAMELIST groups may be declared if |
|---|
| 36 | desired. <br> |
|---|
| 37 | The CPU time needed for executing <tt><font style="font-size: 10pt;" size="2">user_parin</font></tt> |
|---|
| 38 | is included in the |
|---|
| 39 | local file <a href="chapter_3.4.html#CPU_MEASURES">CPU_MEASURES</a> |
|---|
| [62] | 40 | within the category “initialisation”.</p> </td> |
|---|
| 41 | </tr> <tr valign="top"> <td width="211"><p>End |
|---|
| 42 | of <tt><font style="font-size: 10pt;" size="2">header.f90</font></tt></p> |
|---|
| 43 | </td> |
|---|
| 44 | <td width="117"> <p><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><a name="user_header"></a>user_header( |
|---|
| 45 | io )</font></font></tt></p> </td> <td width="862"> <p>Output of the values of the |
|---|
| 46 | user-defined parameters to |
|---|
| [5] | 47 | the |
|---|
| 48 | local files <a href="chapter_3.4.html#HEADER">HEADER</a> |
|---|
| 49 | and <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>. |
|---|
| 50 | This output should be made anyway in order to subsequently check the |
|---|
| 51 | parameter values used for the respective run. The number of the output |
|---|
| 52 | unit is passed as an argument and must be used in each WRITE statement |
|---|
| 53 | (e.g.: “<tt><font face="Cumberland, monospace"><font style="font-size: 10pt;" size="2">WRITE </font><font style="font-size: 10pt;" size="2">( io,…</font></font></tt><font style="font-size: 10pt;" size="2">”))</font>. |
|---|
| 54 | By default, this |
|---|
| 55 | subroutine only creates output if a user-defined NAMELIST is found in |
|---|
| 56 | file <a href="chapter_3.4.html#PARIN">PARIN</a> |
|---|
| 57 | (in this case <tt><font face="Thorndale, serif">the</font></tt> |
|---|
| 58 | variable <tt><font style="font-size: 10pt;" size="2">user_defined_namelist_found</font></tt> |
|---|
| 59 | is set <i>.TRUE.</i> in <tt><font style="font-size: 10pt;" size="2">user_parin</font></tt>). |
|---|
| 60 | The names of any |
|---|
| 61 | user-defined |
|---|
| 62 | subdomains are displayed by default (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>).</p> |
|---|
| [62] | 63 | </td> </tr> <tr valign="top"> <td width="211"> <p>End of <tt><font style="font-size: 10pt;" size="2">init_3d_model.f90</font></tt></p> |
|---|
| 64 | </td> <td width="117"> <p><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><a name="user_init"></a>user_init</font></font></tt></p> |
|---|
| 65 | </td> <td width="862"> <p>Here, user-defined |
|---|
| 66 | initialization actions which should |
|---|
| [5] | 67 | be |
|---|
| 68 | accomplished before the start of the 3D-model can be implemented (e.g. |
|---|
| 69 | inhomogenous change of the surface temperature, the roughness length, |
|---|
| 70 | or similar). At this point, all default parameter initializations of |
|---|
| 71 | the model (<a href="chapter_4.1.html">chapter |
|---|
| 72 | 4.1</a>) have already been carried out at all. </p> |
|---|
| [62] | 73 | <p>One of the most important actions here is the definition |
|---|
| [5] | 74 | of |
|---|
| 75 | user-defined subdomains for statistic analysis and output (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a> |
|---|
| 76 | and <a href="chapter_3.5.3.html">chapter |
|---|
| [62] | 77 | 3.5.3</a>) and of additional time series quantities (see comment |
|---|
| 78 | line example in the file). <br> |
|---|
| [5] | 79 | CPU time for <tt><font style="font-size: 10pt;" size="2">user_init</font></tt> |
|---|
| 80 | is considered in the local file <a href="chapter_3.4.html#CPU_MEASURES">CPU_MEASURES</a> |
|---|
| [62] | 81 | within the category “initialisation”.</p><p>See |
|---|
| 82 | also <tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><a href="#user_init_3d_model">user_init_3d_model</a>.</font></font></tt></p> |
|---|
| 83 | </td> </tr> <tr> <td style="vertical-align: top;"><tt><font style="font-size: 10pt;" size="2">DEFAULT</font></tt> |
|---|
| [5] | 84 | case of <tt><font style="font-size: 10pt;" size="2">SELECT |
|---|
| 85 | CASE( TRIM(topography) ) </font></tt>command in the |
|---|
| [62] | 86 | middle of <tt><font style="font-size: 10pt;" size="2">init_grid.f90</font></tt></td> <td style="vertical-align: top;"><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><a name="user_init_grid"></a>user_init_grid</font></font></tt></td> |
|---|
| 87 | <td> <p>Execution of user-defined grid initializing |
|---|
| 88 | actions.</p> <p>Here, the user can define the |
|---|
| 89 | two-dimensional index |
|---|
| [5] | 90 | array <tt><font style="font-size: 10pt;" size="2">nzb_local</font></tt> that is used to |
|---|
| 91 | set up a non-flat topography. This requires definition of at least one |
|---|
| 92 | new <a href="chapter_4.1.html#topography">topography</a> mode |
|---|
| 93 | in the <tt><font style="font-size: 10pt;" size="2">SELECT CASE( TRIM(topography) ) </font></tt>command |
|---|
| 94 | in <tt><font style="font-size: 10pt;" size="2">user_init_grid</font></tt>. |
|---|
| 95 | Note that the <a href="chapter_4.1.html#topography">topography</a> modes |
|---|
| [62] | 96 | <span style="font-style: italic;">'flat'</span> |
|---|
| [5] | 97 | and <span style="font-style: italic;">'single_building'</span> |
|---|
| 98 | are not allowed here since these are the standard cases used in the |
|---|
| [62] | 99 | calling routine <tt><font style="font-size: 10pt;" size="2">init_grid</font></tt>. </p> <p>CPU |
|---|
| 100 | time for <tt><font style="font-size: 10pt;" size="2">user_init_grid</font></tt> |
|---|
| [5] | 101 | is considered in the local file <a href="chapter_3.4.html#CPU_MEASURES">CPU_MEASURES</a> |
|---|
| [62] | 102 | within the category “initialisation”.</p> </td> |
|---|
| 103 | </tr> <tr><td style="vertical-align: top;">In |
|---|
| 104 | the middle of <tt><font style="font-size: 10pt;" size="2">init_3d_model.f90</font></tt></td><td style="vertical-align: top;"><span style="font-family: monospace;"></span><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><a name="user_init_3d_model"></a>user_init_3d_<br>model</font></font></tt></td><td style="vertical-align: top;">Initialization of the 3d-model.<br><br>Allows |
|---|
| [46] | 105 | the complete initialization of the 3d model. The user is responsible to |
|---|
| [62] | 106 | set at least all those quantities which are normally set within <tt><font style="font-size: 10pt;" size="2">init_3d_model</font></tt>.</td></tr><tr valign="top"> <td width="211"> <p>In |
|---|
| 107 | the middle of <tt><font style="font-size: 10pt;" size="2">init_particles.f90</font></tt></p> |
|---|
| 108 | </td> <td width="117"> <p><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><a name="user_init_particles"></a>user_init_</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"> <br> </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">particles</font></font></tt></p> |
|---|
| 109 | </td> <td width="862"> <p>With this routine |
|---|
| 110 | e.g. size and color of particles, |
|---|
| [5] | 111 | which have |
|---|
| 112 | been released initially from a source, can be specified. Like the |
|---|
| 113 | calling routine <tt><font style="font-size: 10pt;" size="2">init_particles</font><font style="font-size: 11pt;" size="2">,</font></tt> |
|---|
| 114 | this routine is only |
|---|
| 115 | called if particle advection is switched on (see package parameter <a href="chapter_4.2.html#dt_prel">dt_prel</a>).</p> |
|---|
| [62] | 116 | </td> </tr> <tr valign="top"> <td width="211"> <p>End of <tt><font style="font-size: 10pt;" size="2">advec_particles.f90</font></tt></p> |
|---|
| 117 | </td> <td width="117"> <p><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><a name="user_particle_attributes"></a>user_particle_</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"> <br> </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">attributes</font></font></tt></p> |
|---|
| 118 | </td> <td width="862"> <p>Here the particles |
|---|
| 119 | can be assigned new attributes |
|---|
| [5] | 120 | (diameter, |
|---|
| 121 | color etc.) after each time step. Like the calling routine <tt><font style="font-size: 10pt;" size="2">advec_particles</font><font style="font-size: 11pt;" size="2">,</font> </tt>this |
|---|
| 122 | routine is only |
|---|
| 123 | called if particle advection is switched on (see package parameter <a href="chapter_4.2.html#dt_prel">dt_prel</a>).</p> |
|---|
| [62] | 124 | </td> </tr> <tr valign="top"> <td width="211"> <p>Before the plot of particles and |
|---|
| 125 | cross-sections in <br> <tt><font style="font-size: 10pt;" size="2">dvrp_plot.f90</font></tt></p> |
|---|
| 126 | </td> <td width="117"> <p><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><a name="user_dvrp_coltab"></a>user_dvrp_coltab |
|---|
| [5] | 127 | (</font></font></tt><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"> mode )</font></font></tt></p> |
|---|
| [62] | 128 | </td> <td width="862"> <p>With this routine, |
|---|
| 129 | color tables can be adjusted which |
|---|
| [5] | 130 | should |
|---|
| 131 | be used for output with the dvrp software. Individuell color tables for |
|---|
| 132 | particles and cross-sections are possible. For this purpose the two |
|---|
| 133 | arrays <tt><font style="font-size: 10pt;" size="2">interval_values_dvrp</font></tt> |
|---|
| 134 | and <tt><font style="font-size: 10pt;" size="2">interval_h_dvrp</font></tt> |
|---|
| 135 | (declared in the module <tt><font style="font-size: 10pt;" size="2">dvrp_variables</font></tt>) |
|---|
| 136 | have to be preset with appropriate values. The number of color table |
|---|
| 137 | entries must be assigned to the variable of <tt><font style="font-size: 10pt;" size="2">dvrp_colourtable_entries</font></tt>. |
|---|
| 138 | The value of the subroutine argument <span style="font-family: monospace;">mode</span> defines, |
|---|
| 139 | whether the color |
|---|
| 140 | table is valid for particles or for cross-sections<span style="font-family: monospace;"></span> (i.e. <tt><font size="2">mode</font></tt> |
|---|
| 141 | can have the values “<i>particles”</i> |
|---|
| 142 | or “<i>slicer”</i>). <br> |
|---|
| 143 | This routine only becomes active if dvrp-graphics is switched on (see |
|---|
| 144 | package parameter <a href="chapter_4.2.html#dt_dvrp">dt_dvrp</a>).</p> |
|---|
| [62] | 145 | </td> </tr> <tr valign="top"> <td width="211"> <p>Beginning and end of the time |
|---|
| 146 | integration loop |
|---|
| 147 | of <br> <tt><font style="font-size: 10pt;" size="2">time_integration.f90</font></tt> |
|---|
| 148 | as well as after each prognostic equation in <br> <tt><font style="font-size: 10pt;" size="2">prognostic_equations.f90</font></tt></p> |
|---|
| 149 | </td> <td width="117"> <p><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><a name="user_actions"></a>user_actions( |
|---|
| 150 | location )</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"> </font></font> </p> |
|---|
| 151 | <p>or<br> <font face="Cumberland, monospace"><font style="font-size: 10pt;" size="2"> </font></font> |
|---|
| 152 | </p> <p><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">user_actions( |
|---|
| 153 | i, j,</font></font></tt><span style="font-family: Cumberland,monospace;"> </span><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">location )</font></font></tt></p> |
|---|
| 154 | </td> <td width="862"> <p>In this routine |
|---|
| 155 | user actions can be implemented which |
|---|
| [5] | 156 | are to |
|---|
| 157 | be executed either at each time step or at certain times (defined by |
|---|
| 158 | the user). Since in each case the routine is called at the beginning |
|---|
| 159 | and at the end of a time step as well as after each prognostic equation |
|---|
| 160 | it must be defined at which place (and/or at which places) the |
|---|
| 161 | respective actions are supposed to be executed. For this purpose an |
|---|
| 162 | appropriate CASE structure is already inserted in this routine. The |
|---|
| 163 | location of the calling routine is passed to this routine via the |
|---|
| 164 | argument <tt><font style="font-size: 10pt;" size="2">location</font></tt>. |
|---|
| 165 | For example, if called at the beginning of a time step, <tt><font style="font-size: 10pt;" size="2">location</font></tt> |
|---|
| 166 | = <i>'before_timestep' </i>and if |
|---|
| [62] | 167 | called at the end, <tt><font style="font-size: 10pt;" size="2">location</font></tt><font style="font-size: 10pt;" size="2"> </font>= <i>'after_timestep'</i><span style="font-weight: bold;">.</span></p><p>Calculation |
|---|
| 168 | of user-defined output quantities should be carried out at <span style="font-family: monospace;">location</span> = <span style="font-style: italic;">'after_integration'</span>.<span style="font-weight: bold;"></span></p><p><span style="font-weight: bold;">Important:</span> |
|---|
| [5] | 169 | if the |
|---|
| 170 | cache-optimized version of <span style="font-family: monospace;">prognostic_equation.f90</span> |
|---|
| 171 | is used (this is the default for IBM-Regatta-Systems), the loop |
|---|
| 172 | variables <tt>i</tt> and <tt>j</tt> must be |
|---|
| 173 | passed as arguments for |
|---|
| 174 | all calls within <span style="font-family: monospace;">prognostic_equations</span>. |
|---|
| [62] | 175 | </p> <p>CPU time for <tt><font style="font-size: 10pt;" size="2">user_actions</font></tt> |
|---|
| [5] | 176 | appears within the category “user_actions” in the |
|---|
| 177 | local file <a href="chapter_3.4.html#CPU_MEASURES">CPU_MEASURES</a>. |
|---|
| 178 | If the cache-optimized version of <span style="font-family: monospace;">prognostic_equation.f90</span> |
|---|
| 179 | is used, this time measurement only considers the CPU time which was |
|---|
| 180 | needed outside of the prognostic equations. Time needed for calls |
|---|
| 181 | within prognostic_equations is considered within the category "all |
|---|
| [62] | 182 | prog.equations".<br> </p> <p><b>Important:</b> |
|---|
| 183 | this subroutine is written |
|---|
| [5] | 184 | as a FORTRAN |
|---|
| 185 | module, which uses so-called function overloading. It can be called in |
|---|
| 186 | two ways: with one argument (<tt><font style="font-size: 10pt;" size="2">location</font></tt>) |
|---|
| 187 | and with three arguments <font style="font-size: 10pt;" size="2">(</font><tt><font style="font-size: 10pt;" size="2">i, j, location</font></tt><font style="font-size: 10pt;" size="2">)</font>. The |
|---|
| 188 | three argument version |
|---|
| 189 | is used in the cache-optimized version of <span style="font-family: monospace;">prognostic_equations</span>. |
|---|
| 190 | Depending |
|---|
| 191 | on the number of given arguments the subroutine internally calls <tt><font style="font-size: 10pt;" size="2">user_actions</font></tt> |
|---|
| 192 | or <tt><font style="font-size: 10pt;" size="2">user_actions_ij</font></tt>. |
|---|
| 193 | So the |
|---|
| 194 | user must insert the actions (code extensions) desired for the |
|---|
| 195 | respective prognostic equation either in the CASE structure of <tt><font style="font-size: 10pt;" size="2">user_actions</font><font style="font-size: 11pt;" size="2">,</font> </tt>or/and |
|---|
| 196 | in the CASE |
|---|
| [62] | 197 | structure of <tt><font style="font-size: 10pt;" size="2">user_actions_ij</font></tt>!</p> </td> |
|---|
| 198 | </tr> <tr valign="top"> <td width="211"><p><tt><font style="font-size: 10pt;" size="2">flow_statistics.f90</font></tt> |
|---|
| [5] | 199 | before the summation of array <span style="font-family: monospace;">hom</span> |
|---|
| [62] | 200 | (horizontal averages)<br> </p> </td> <td width="117"> <p><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><a name="user_statistics"></a>user_statistics<br>( |
|---|
| 201 | sr )</font></font></tt></p> </td> <td width="862"> <p>Horizontal |
|---|
| [48] | 202 | averages of vertical profiles of user-defined |
|---|
| 203 | quantities can be computed here. Also, additional time series |
|---|
| 204 | quantities can be calculated. They have to be defined before in routine |
|---|
| [90] | 205 | <a style="font-family: monospace;" href="#user_init">user_init</a>. |
|---|
| 206 | The routine is called once for each defined statistic region (see <a href="chapter_4.1.html#statistic_region">statistic_region</a>).</p><p>The |
|---|
| [62] | 207 | routine contains some simple examples (as comment lines) in order to |
|---|
| [90] | 208 | demonstrate how to use it.<br><br>Profile sums have to |
|---|
| 209 | be stored in |
|---|
| 210 | the array <tt><font style="font-size: 10pt;" size="2">sums_l</font></tt>. The profile identification number (second index of array <span style="font-family: monospace;">sums_l</span>) must be within the range [<span style="font-family: monospace;"> pr_palm+1 , pr_palm+max_pr_user</span> ], where <span style="font-family: monospace;">pr_palm</span> is an internal parameter and <span style="font-family: Courier New,Courier,monospace;">max_pr_user</span> is the number of user-defined profiles as given by parameter <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.3.html#data_output_pr_user">data_output_pr_user</a> in the respective PALM run.</p><p> These additional |
|---|
| [5] | 211 | profiles |
|---|
| [90] | 212 | are further processed (e.g. temporally averaged), like the standard profiles, in <tt><font style="font-size: 10pt;" size="2">flow_statistics</font></tt>.</p> </td> |
|---|
| [62] | 213 | </tr> <tr><td style="vertical-align: top;">End |
|---|
| 214 | of <span style="font-family: monospace;">check_parameters.f90</span> |
|---|
| [90] | 215 | where 2d/3d output quantities are checked</td><td style="vertical-align: top;"><span style="font-family: monospace;"><a name="user_check_data_output"></a>user_check_data_<br>output( |
|---|
| 216 | variable, unit )</span></td><td style="vertical-align: top;">Here the physical <span style="font-family: monospace;">unit</span>(s) of |
|---|
| 217 | user-defined 2d/3d output quantities (see <a href="chapter_4.3.html#data_output_user">data_output_user</a>) |
|---|
| [62] | 218 | have to be set. Input parameter <span style="font-family: monospace;">variable</span> |
|---|
| 219 | contains the string identifier of the respective variable. For those |
|---|
| 220 | variables not recognized by the user, the parameter <span style="font-family: monospace;">unit</span> is set to |
|---|
| 221 | "illegal", which tells the calling routine that the output variable is |
|---|
| 222 | not defined and leads to a program abort.<br><br>See <a href="chapter_3.5.4.html">chapter 3.5.4</a> about |
|---|
| [90] | 223 | creating user-defined output quantities.</td></tr><tr><td style="vertical-align: top;">End |
|---|
| 224 | of <span style="font-family: monospace;">check_parameters.f90</span> |
|---|
| 225 | where vertical profile output quantities are checked</td><td style="vertical-align: top;"><a name="user_check_data_output_pr"></a><br><span style="font-family: monospace;">user_check_data_</span><br style="font-family: monospace;"><span style="font-family: monospace;">output_pr(</span><br style="font-family: monospace;"><span style="font-family: monospace;">variable, var_count, unit )</span></td><td style="vertical-align: top;">Here the physical <span style="font-family: monospace;">unit</span>(s) and vertical grid (u- or w-grid) of |
|---|
| 226 | user-defined vertical profile output quantities (see <a href="chapter_4.3.html#data_output_pr_user">data_output_pr_user</a>) |
|---|
| 227 | have to be set. Input parameter <span style="font-family: monospace;">variable</span> |
|---|
| 228 | contains the string identifier of the respective variable. Parameter<span style="font-family: monospace;"> var_count </span>contains the internal profile number and must not be changed by the user. For those |
|---|
| 229 | variables not recognized by the user, the parameter <span style="font-family: monospace;">unit</span> is set to |
|---|
| 230 | "illegal", which tells the calling routine that the output variable is |
|---|
| 231 | not defined and leads to a program abort.<br><br>See <a href="chapter_3.5.4.html">chapter 3.5.4</a> about |
|---|
| [62] | 232 | creating user-defined output quantities.</td></tr><tr><td style="vertical-align: top;"><span style="font-family: monospace;">netcdf.f90</span> (4 |
|---|
| 233 | times) where the vertical grid coordinates for cross sections and |
|---|
| 234 | volume data are defined</td><td style="vertical-align: top;"><span style="font-family: monospace;"><a name="user_define_netcdf_grid"></a>user_define_<br>netcdf_grid( |
|---|
| 235 | variable, found, grid_x, grid_y, grid_z )</span></td><td style="vertical-align: top;">Set the grid on which |
|---|
| 236 | user-defined output quantities (see <a href="chapter_4.3.html#data_output_user">data_output_user</a>) |
|---|
| 237 | are defined. Input parameter <span style="font-family: monospace;">variable</span> |
|---|
| 238 | contains the string identifier of the respective variable. Allowed |
|---|
| 239 | values are <span style="font-style: italic;">'x'</span> |
|---|
| 240 | and <span style="font-style: italic;">'xu'</span> |
|---|
| 241 | for <span style="font-family: monospace;">grid_x</span>, |
|---|
| 242 | <span style="font-style: italic;">'y'</span> and <span style="font-style: italic;">'yv'</span> for <span style="font-family: monospace;">grid_y</span>, and<span style="font-family: monospace;"></span> <span style="font-style: italic;">'zu'</span> and <span style="font-style: italic;">'zw'</span> for <span style="font-family: monospace;">grid_z</span>. The |
|---|
| 243 | output parameter <span style="font-family: monospace;">found</span> |
|---|
| 244 | has to be set <span style="font-style: italic;">.TRUE.</span> |
|---|
| 245 | by the user, otherwise an error message will appear in the job protocol |
|---|
| 246 | for the respective output quantity.<br><br><span style="font-weight: bold;">Example:</span><br>If |
|---|
| 247 | an output quantity is defined at the center of the grid boxes, the |
|---|
| 248 | following settings have to be used:<br><br><div style="margin-left: 40px;"><span style="font-family: monospace;">grid_x = <span style="font-style: italic;">'x'</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">grid_y = <span style="font-style: italic;">'y'</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">grid_z = <span style="font-style: italic;">'zu'</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">found = <span style="font-style: italic;">.TRUE.</span></span><br></div><br>For |
|---|
| 249 | defining an output quantity at the grid points where the |
|---|
| 250 | u-velocity-component is defined, please use<br><br><div style="margin-left: 40px;"><span style="font-family: monospace;">grid_x = <span style="font-style: italic;">'xu'</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">grid_y = <span style="font-style: italic;">'y'</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">grid_z = <span style="font-style: italic;">'zu'</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">found = <span style="font-style: italic;">.TRUE.</span></span><br></div><br>See |
|---|
| 251 | <a href="chapter_3.5.4.html">chapter 3.5.4</a> about |
|---|
| 252 | creating user-defined output quantities.</td></tr><tr><td style="vertical-align: top;">Middle of <span style="font-family: monospace;">data_output_2d.f90</span></td><td style="vertical-align: top;"><span style="font-family: monospace;"><a name="user_data_output_2d"></a>user_data_<br>output_2d( |
|---|
| 253 | av, variable, found, grid, local_pf )</span></td><td style="vertical-align: top;">Resorts user-defined quantities |
|---|
| 254 | (to be output as cross-section data; see <a href="chapter_4.3.html#data_output_user">data_output_user</a>) |
|---|
| 255 | with indices (k,j,i) to a temporary array <span style="font-family: monospace;">local_pf</span> with |
|---|
| 256 | indices (i,j,k) and sets the <span style="font-family: monospace;">grid</span> |
|---|
| 257 | on which they are defined. Depending on the value of input parameter <span style="font-family: monospace;">av</span> resorting is |
|---|
| 258 | done for instantaneous (<span style="font-family: monospace;">av</span>=<span style="font-style: italic;">0</span>) or time averaged |
|---|
| 259 | data (<span style="font-family: monospace;">av</span>=<span style="font-style: italic;">1</span>). Input parameter |
|---|
| 260 | <span style="font-family: monospace;">variable</span> |
|---|
| 261 | contains the string identifier of the respective variable. Allowed |
|---|
| 262 | values for <span style="font-family: monospace;">grid</span> |
|---|
| 263 | are <span style="font-style: italic;">'zu'</span> |
|---|
| 264 | and <span style="font-style: italic;">'zw'</span>. |
|---|
| 265 | The output parameter <span style="font-family: monospace;">found</span> |
|---|
| 266 | has to be set <span style="font-style: italic;">.TRUE.</span> |
|---|
| 267 | by the user, otherwise an error message will appear in the job protocol |
|---|
| 268 | for the respective output quantity.<br><br>See <a href="chapter_3.5.4.html">chapter 3.5.4</a> about |
|---|
| 269 | creating user-defined output quantities.</td></tr><tr><td style="vertical-align: top;"><span style="font-family: monospace;">data_output_3d.f90</span> |
|---|
| 270 | at the end of the CASE structure</td><td style="vertical-align: top;"><span style="font-family: monospace;"><a name="user_data_output_3d"></a>user_data_<br>output_3d( |
|---|
| 271 | av, variable, found, local_pf, nz_do )</span></td><td style="vertical-align: top;">Resorts user-defined quantities |
|---|
| 272 | (to be output as volume data; see <a href="chapter_4.3.html#data_output_user">data_output_user</a>) |
|---|
| 273 | with indices (k,j,i) to a temporary array <span style="font-family: monospace;">local_pf</span> with |
|---|
| 274 | indices (i,j,k) and sets the <span style="font-family: monospace;">grid</span> |
|---|
| 275 | on which they are defined. Depending on the value of input parameter <span style="font-family: monospace;">av</span> resorting is |
|---|
| 276 | done for instantaneous (<span style="font-family: monospace;">av</span>=<span style="font-style: italic;">0</span>) or time averaged |
|---|
| 277 | data (<span style="font-family: monospace;">av</span>=<span style="font-style: italic;">1</span>). Input parameter |
|---|
| 278 | <span style="font-family: monospace;">variable</span> |
|---|
| 279 | contains the string identifier of the respective variable<span style="font-family: monospace;"></span><span style="font-style: italic;"></span><span style="font-style: italic;"></span>. The input |
|---|
| 280 | parameter <span style="font-family: monospace;">nz_do</span> |
|---|
| 281 | defines the upper limit of vertical grid index k of the output array |
|---|
| 282 | (see <a href="chapter_4.2.html#nz_do3d">nz_do3d</a>). |
|---|
| 283 | The output parameter <span style="font-family: monospace;">found</span> |
|---|
| 284 | has to be set <span style="font-style: italic;">.TRUE.</span> |
|---|
| 285 | by the user, otherwise an error message will appear in the job protocol |
|---|
| 286 | for the respective output quantity.<br><br>See <a href="chapter_3.5.4.html">chapter 3.5.4</a> about |
|---|
| 287 | creating user-defined output quantities.</td></tr><tr><td style="vertical-align: top;">End of <span style="font-family: monospace;">average_3d_data.f90</span>, |
|---|
| 288 | middle and end of <span style="font-family: monospace;">sum_up_3d_data.f90</span></td><td style="vertical-align: top;"><span style="font-family: monospace;"><a name="user_3d_data_averaging"></a>user_3d_data_<br>averaging( |
|---|
| 289 | mode, variable )</span></td><td style="vertical-align: top;">Sum up and time-average of |
|---|
| 290 | user-defined output quantities (see <a href="chapter_4.3.html#data_output_user">data_output_user</a>) |
|---|
| 291 | as well as allocation of the arrays necessary for storing the |
|---|
| 292 | respective averages. Input parameter <span style="font-family: monospace;">variable</span> |
|---|
| 293 | contains the string identifier of the respective variable. Depending on |
|---|
| 294 | the requested action, input parameter <span style="font-family: monospace;">mode</span> has the |
|---|
| 295 | value <span style="font-style: italic;">'allocate'</span>, |
|---|
| 296 | <span style="font-style: italic;">'sum'</span>, or <span style="font-style: italic;">'average'</span>.<br><br>See |
|---|
| 297 | <a href="chapter_3.5.4.html">chapter 3.5.4</a> about |
|---|
| 298 | creating user-defined output quantities. </td></tr><tr valign="top"> <td width="211"> <p>End |
|---|
| 299 | of <tt><font style="font-size: 10pt;" size="2">palm.f90</font></tt></p> |
|---|
| 300 | </td> <td width="117"> <p><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><a name="user_last_action"></a>user_last_</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"> <br> </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">action</font></font></tt></p> |
|---|
| 301 | </td> <td width="862"> <p>User-defined |
|---|
| 302 | actions which are to be executed at the end |
|---|
| [5] | 303 | of a |
|---|
| 304 | model run. When <tt><font style="font-size: 10pt;" size="2">user_last_actions</font></tt> |
|---|
| 305 | is called all model actions are already completed, but the files opened |
|---|
| 306 | by the model are not closed yet and possibly terminating actions for |
|---|
| 307 | these files (see subroutine of <tt><font style="font-size: 10pt;" size="2">close_files</font></tt>) |
|---|
| 308 | are also not carried |
|---|
| 309 | out yet. <br> |
|---|
| 310 | CPU time for <tt><font style="font-size: 10pt;" size="2">user_last_actions</font></tt> |
|---|
| 311 | appears in the local file <a href="chapter_3.4.html#CPU_MEASURES">CPU_MEASURES</a> |
|---|
| 312 | within the category “last actions” (the time |
|---|
| 313 | necessary for <tt><font style="font-size: 10pt;" size="2">close_files</font></tt> is included).</p> |
|---|
| [62] | 314 | </td> </tr> </tbody></table><hr> |
|---|
| 315 | <p style="line-height: 100%;"><br><font color="#000080"><font color="#000080"><a href="chapter_3.5.html"><font color="#000080"><img src="left.gif" name="Grafik1" align="bottom" border="2" height="32" width="32"></font></a><a href="index.html"><font color="#000080"><img src="up.gif" name="Grafik2" align="bottom" border="2" height="32" width="32"></font></a><a href="chapter_3.5.2.html"><font color="#000080"><img src="right.gif" name="Grafik3" align="bottom" border="2" height="32" width="32"></font></a></font></font></p><p style="line-height: 100%;"><i>Last |
|---|
| 316 | change: </i>$Id: chapter_3.5.1.html 90 2007-05-30 09:18:47Z letzel $</p> |
|---|
| [5] | 317 | </body></html> |
|---|
