Changeset 493 for palm/trunk/DOC/app/chapter_4.2.html
- Timestamp:
- Mar 1, 2010 8:30:24 AM (15 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
palm/trunk/DOC/app/chapter_4.2.html
r354 r493 1 1 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> 2 <html> 3 <head> 2 <html><head> 3 4 4 5 5 6 … … 11 12 12 13 13 <meta content="text/html; charset=ISO-8859-1" http-equiv="content-type"> 14 15 16 17 18 19 20 21 22 <title>PALM chapter 4.2</title> 23 </head> 24 25 26 <body> 14 <meta content="text/html; charset=ISO-8859-1" http-equiv="content-type"><title>PALM chapter 4.2</title></head><body> 27 15 28 16 … … 1733 1721 1734 1722 <p>Umlauts 1735 are possible (write & ldquo; in front of, similar to TeX), as1723 are possible (write “ in front of, similar to TeX), as 1736 1724 well as super- and subscripts (use ">" or "<" in front of 1737 1725 each … … 2007 1995 2008 1996 2009 <td></td> 1997 <td><br> 1998 </td> 2010 1999 2011 2000 … … 2071 2060 2072 2061 2073 <td style="vertical-align: top;"></td> 2062 <td style="vertical-align: top;"><br> 2063 </td> 2074 2064 2075 2065 … … 2237 2227 2238 2228 2239 <td style="vertical-align: top;"></td> 2229 <td style="vertical-align: top;"><br> 2230 </td> 2240 2231 2241 2232 … … 2391 2382 2392 2383 2393 <td style="vertical-align: top;"></td> 2384 <td style="vertical-align: top;"><br> 2385 </td> 2394 2386 2395 2387 … … 2610 2602 2611 2603 2612 <td style="vertical-align: top;"></td> 2604 <td style="vertical-align: top;"><br> 2605 </td> 2613 2606 2614 2607 … … 2673 2666 2674 2667 2675 <td style="vertical-align: top;"></td> 2668 <td style="vertical-align: top;"><br> 2669 </td> 2676 2670 2677 2671 … … 2735 2729 2736 2730 2737 <td style="vertical-align: top;"></td> 2731 <td style="vertical-align: top;"><br> 2732 </td> 2738 2733 2739 2734 … … 2765 2760 2766 2761 2767 <td></td> 2762 <td><br> 2763 </td> 2768 2764 2769 2765 … … 3109 3105 the file 3110 3106 PLOT3D_FLD (by suitable OUTPUT command in the <span style="font-weight: bold;">mrun</span> 3111 configuration file: & ldquo;<span style="font-family: monospace;">cat3112 PLOT3D_FLD_COOR >> PLOT3D_FLD</span>& rdquo;)3107 configuration file: “<span style="font-family: monospace;">cat 3108 PLOT3D_FLD_COOR >> PLOT3D_FLD</span>”) 3113 3109 after PALM has 3114 3110 finished. To reduce the amount of data, output to this file … … 3147 3143 respective files with suffix _GLOBAL (by 3148 3144 suitable OUTPUT commands in the <span style="font-weight: bold;">mrun</span> 3149 configuration file, e.g.: & ldquo;<span style="font-family: monospace;">cat3150 PLOT2D_XY_LOCAL >> PLOT2D_XY_GLOBAL</span>& rdquo;)3145 configuration file, e.g.: “<span style="font-family: monospace;">cat 3146 PLOT2D_XY_LOCAL >> PLOT2D_XY_GLOBAL</span>”) 3151 3147 after PALM has 3152 3148 finished. Cross sections can be directly plotted with <span style="font-weight: bold;">iso2d</span> using the … … 3228 3224 default, all data (profiles, time 3229 3225 series, spectra, particle data, cross sections, volume data) are output 3230 in NetCDF format (see chapter <a href="chapter_4.5.1.html">4.5.1</a>).3226 in NetCDF 64bit-offset format (see chapter <a href="chapter_4.5.1.html">4.5.1</a>). 3231 3227 Exception: restart data (local files <a href="chapter_3.4.html#BININ">BININ</a>, <a href="chapter_3.4.html#BINOUT">BINOUT</a>, <a href="chapter_3.4.html#PARTICLE_RESTART_DATA_IN">PARTICLE_RESTART_DATA_IN</a>, 3232 3228 <a href="chapter_3.4.html#PARTICLE_RESTART_DATA_OUT">PARTICLE_RESTART_DATA_OUT</a>) … … 3242 3238 3243 3239 The 3244 numerical precision of the NetCDF output is determined with parameter <a href="#chapter_4.1.html#netcdf_precision">netcdf_precision</a>.<br> 3245 3246 3247 3248 3249 <br> 3250 3251 3252 3253 3254 The 3255 maximum file size for NetCDF files is 2 GByte by default. Use the 3256 parameter <a href="#netcdf_64bit">netcdf_64bit</a> 3257 if larger files have to be created.<br> 3240 numerical precision of the NetCDF output is determined with parameter <a href="chapter_4.1.html#netcdf_precision">netcdf_precision</a>.<br> 3241 3242 3243 3244 3245 <br>Other NetCDF formats (classic, NetCDF4/HDF5) can be selected with parameter <a href="#netcdf_data_format">netcdf_data_format</a>.<br> 3258 3246 3259 3247 … … 8428 8416 8429 8417 <tr> 8430 8431 8432 8433 8434 <td style="vertical-align: top;"><a name="netcdf_64bit"></a><span style="font-weight: bold;">netcdf_64bit</span><br> 8435 8436 8437 8438 8439 8418 <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="netcdf_data_format"></a>netcdf_data_format</span><br> 8440 8419 </td> 8441 8442 8443 8444 8445 <td style="vertical-align: top;">L<br> 8446 8447 8448 8449 8450 </td> 8451 8452 8453 8454 8455 8456 <td style="vertical-align: top;"><span style="font-style: italic;">.F.</span><br> 8457 8458 8459 8460 8461 </td> 8462 8463 8464 8465 8466 8467 <td style="vertical-align: top;">All NetCDF files - except those containing 3d 8468 volume data - will have 64 8469 bit offset format if <span style="font-weight: bold;">netcdf_64bit</span> 8470 = .TRUE..<br> 8471 8472 8473 8474 8420 <td style="vertical-align: top;">I<br> 8421 </td> 8422 <td style="vertical-align: top;"><span style="font-style: italic;">2</span><br> 8423 </td> 8424 <td style="vertical-align: top;">Data format for NetCDF files.<br> 8475 8425 <br> 8476 8477 8478 8479 8480 By 8481 default, the maximum file size of the NetCDF files opened by PALM is 2 8482 GByte. Using <span style="font-weight: bold;">netcdf_64bit</span> = .TRUE. allows file sizes larger than 2 8483 GByte.<br> 8484 8485 8486 8487 8426 This variable defines the format of the NetCDF files. Following values are allowed:<br> 8488 8427 <br> 8489 8490 8491 8492 8493 The 64 bit offset format for those NetCDF files containing 3d volume data (<span style="font-family: Courier New,Courier,monospace;">DATA_3D_NETCDF</span>, 8494 <span style="font-family: Courier New,Courier,monospace;">DATA_3D_AV_NETCDF</span>) 8495 is controlled independently by the switch <a href="#netcdf_64bit_3d">netcdf_64bit_3d</a>.<br> 8496 8497 8498 8499 8428 <table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2"> 8429 <tbody> 8430 <tr> 8431 <td style="vertical-align: top;"><span style="font-style: italic;">1</span><br> 8432 </td> 8433 <td style="vertical-align: top;">NetCDF classic format (filesize limited to 2GB)<br> 8434 </td> 8435 </tr> 8436 <tr> 8437 <td style="vertical-align: top;"><span style="font-style: italic;">2</span><br> 8438 </td> 8439 <td style="vertical-align: top;">NetCDF 64-bit-offset format (large file support, but single variable still limited to 2GB)<br> 8440 </td> 8441 </tr> 8442 <tr> 8443 <td style="vertical-align: top;"><span style="font-style: italic;">3</span><br> 8444 </td> 8445 <td style="vertical-align: top;">NetCDF-4 (HDF5) format (files can be as large as file system supports; unlimited variable size; allows parallel I/O)<br> 8446 </td> 8447 </tr> 8448 <tr> 8449 <td style="vertical-align: top;"><span style="font-style: italic;">4</span><br> 8450 </td> 8451 <td style="vertical-align: top;">NetCDF-4 format, but with NF90_CLASSIC_MODEL bit set (some new features of NetCDF4 are not available)<br> 8452 </td> 8453 </tr> 8454 </tbody> 8455 </table> 8500 8456 <br> 8501 8502 8503 8504 8505 <span style="font-weight: bold;">Warning:</span><br> 8506 8507 8508 8509 8510 Some 8511 (PD or commercial) software may not support the 64 bit offset format.<br> 8512 8513 8514 8515 8516 8457 <span style="font-weight: bold;">Important:</span><br> 8458 Setting <span style="font-weight: bold;">netcdf_data_format </span>> <span style="font-style: italic;">2 </span>requires a NetCDF4 library (set <span style="font-family: Courier New,Courier,monospace;">-I</span>, <span style="font-family: Courier New,Courier,monospace;">-L</span>, and<span style="font-family: Courier New,Courier,monospace;"> -l </span>options for compiling and linking appropriately in configuration file). Also, preprocessor switch <span style="font-family: Courier New,Courier,monospace;">__netcdf4 </span>has to be set (see line starting with <span style="font-family: Courier New,Courier,monospace;">%cpp_opts </span>in the configuration file).<br> 8459 <br> 8460 Files with NetCDF4 format cannot be read with NetCDF3 libraries.<br> 8517 8461 </td> 8518 8519 8520 8521 8522 </tr>8523 8524 8525 8526 8527 <tr>8528 8529 8530 8531 8532 <td style="vertical-align: top;"><a name="netcdf_64bit_3d"></a><span style="font-weight: bold;">netcdf_64bit_3d</span></td>8533 8534 8535 8536 8537 <td style="vertical-align: top;">L</td>8538 8539 8540 8541 8542 <td style="vertical-align: top;">.T.</td>8543 8544 8545 8546 8547 <td style="vertical-align: top;">NetCDF files containing 3d8548 volume data will have 64 bit offset format if <span style="font-weight: bold;">netcdf_64bit_3d</span>8549 = .TRUE..<br>8550 8551 <br>8552 8553 8554 8555 8556 By8557 default, the maximum file size of the NetCDF files opened by PALM is 28558 GByte. Using <span style="font-weight: bold;">netcdf_64bit_3d</span> = .TRUE. allows file sizes larger than 28559 GByte.<br>8560 8561 <br>8562 8563 8564 8565 8566 The 64 bit offset format for all other NetCDF files (<span style="font-style: italic;">not</span> containing 3d volume data) is controlled independently by the switch <a href="chapter_4.2.html#netcdf_64bit">netcdf_64bit</a>.<br>8567 8568 <br>8569 8570 8571 8572 8573 <span style="font-weight: bold;">Warning:</span><br>8574 8575 8576 8577 8578 Some8579 (PD or commercial) software may not support the 64 bit offset format.</td>8580 8581 8582 8583 8584 8462 </tr> 8463 8464 8465 8466 8467 8468 8585 8469 8586 8470 … … 8741 8625 <td style="vertical-align: top;">I</td> 8742 8626 8743 <td style="vertical-align: top;"></td> 8627 <td style="vertical-align: top;"><br> 8628 </td> 8744 8629 8745 8630 <td style="vertical-align: top;"> … … 8837 8722 <td style="vertical-align: top;">I</td> 8838 8723 8839 <td style="vertical-align: top;"></td> 8724 <td style="vertical-align: top;"><br> 8725 </td> 8840 8726 8841 8727 <td style="vertical-align: top;"> … … 11938 11824 user-interface (subroutine</span></font> <span style="font-family: monospace;">user_init_particles</span>)<span lang="en-GB"><font face="Thorndale, serif">. 11939 11825 Particles can pull a 11940 & ldquo;tail” behind themselves to improve their11826 “tail” behind themselves to improve their 11941 11827 visualization. 11942 11828 This is steered via the parameter <a href="chapter_4.2.html#use_particle_tails">use_particle_tails</a>.</font></span><a href="chapter_4.2.html#maximum_number_of_tailpoints"><span lang="en-GB"></span></a></p> … … 11996 11882 11997 11883 11998 <td style="vertical-align: top;"><i> ´reflect´</i></td>11884 <td style="vertical-align: top;"><i>ŽreflectŽ</i></td> 11999 11885 12000 11886 … … 12021 11907 default, particles are reflected at the bottom boundary. 12022 11908 Alternatively, a particle absorption can set by <b>bc_par_b</b> 12023 = <i> ´absorb´</i>.</p>11909 = <i>ŽabsorbŽ</i>.</p> 12024 11910 12025 11911 … … 12064 11950 12065 11951 12066 <td style="vertical-align: top;"><i> ´cyclic´</i></td>11952 <td style="vertical-align: top;"><i>ŽcyclicŽ</i></td> 12067 11953 12068 11954 … … 12090 11976 are used along x. 12091 11977 Alternatively, reflection (<b>bc_par_lr</b> 12092 = <i> ´reflect´</i>) or absorption (<b>bc_par_lr</b>12093 = <i> ´absorb´</i>)11978 = <i>ŽreflectŽ</i>) or absorption (<b>bc_par_lr</b> 11979 = <i>ŽabsorbŽ</i>) 12094 11980 can be set. <br> 12095 11981 … … 12152 12038 12153 12039 12154 <td style="vertical-align: top;"><i> ´cyclic´</i></td>12040 <td style="vertical-align: top;"><i>ŽcyclicŽ</i></td> 12155 12041 12156 12042 … … 12178 12064 are used along y. 12179 12065 Alternatively, reflection (<b>bc_par_ns</b> 12180 = <i> ´reflect´</i>) or absorption (<b>bc_par_ns</b>12181 = <i> ´absorb´</i>)12066 = <i>ŽreflectŽ</i>) or absorption (<b>bc_par_ns</b> 12067 = <i>ŽabsorbŽ</i>) 12182 12068 can be set.<br> 12183 12069 … … 12230 12116 12231 12117 12232 <td style="vertical-align: top;"><i> ´absorb´</i></td>12118 <td style="vertical-align: top;"><i>ŽabsorbŽ</i></td> 12233 12119 12234 12120 … … 12255 12141 particles are absorbed at the top boundary. 12256 12142 Alternatively, a reflection condition can be set by <b>bc_par_t</b> 12257 = <i> ´reflect´</i>.</p>12143 = <i>ŽreflectŽ</i>.</p> 12258 12144 12259 12145 … … 14324 14210 14325 14211 <td style="vertical-align: top;">Rear 14326 (& ldquo;north”) edge of a14212 (“north”) edge of a 14327 14213 particle source (in m). </td> 14328 14214 … … 14424 14310 14425 14311 <td style="vertical-align: top;">Front 14426 (& ldquo;south”) edge of a14312 (“south”) edge of a 14427 14313 particle source (in m). </td> 14428 14314 … … 14614 14500 14615 14501 14616 <p><span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy:initial;"><font color="#000000">Initial position of the</font></span>14502 <p><span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;"><font color="#000000">Initial position of the</font></span> 14617 14503 particles is 14618 14504 varied randomly within certain limits. </p> … … 16290 16176 (cross sections), and <span style="font-style: italic;">'particles'</span>. 16291 16177 Within the strings the hash characters ("##") have to be replaced by two 16292 digits 01& le;##≤99. Up to 10 objects16178 digits 01≤##≤99. Up to 10 objects 16293 16179 can be assigned at the same time, e.g.: </p> 16294 16180 … … 17353 17239 subsequent columns. </font>The order 17354 17240 of the data in the file follows the order used in the assignment for <b>data_output_sp</b> 17355 (<b>data_output_sp</b> = <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'v'</span>,& hellip;17241 (<b>data_output_sp</b> = <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'v'</span>,… 17356 17242 means that the file starts with the spectra of the u-component, 17357 17243 followed by the v-component spectra, etc.). Additional to the files … … 17748 17634 17749 17635 17750 </body> 17751 </ html>17636 17637 </body></html>
Note: See TracChangeset
for help on using the changeset viewer.