Changeset 108 for palm/trunk/DOC/app/chapter_3.4.html
- Timestamp:
- Aug 24, 2007 3:10:38 PM (17 years ago)
- File:
-
- 1 edited
-
palm/trunk/DOC/app/chapter_3.4.html (modified) (58 diffs)
Legend:
- Unmodified
- Added
- Removed
-
palm/trunk/DOC/app/chapter_3.4.html
r97 r108 1 1 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> 2 <html><head> 3 <meta content="text/html; charset=ISO-8859-1" http-equiv="content-type"><title>chapter_3.4</title></head> 4 <body><h3 style="line-height: 100%;"><font color="#000000">3.4 Input and 2 <html> 3 <head> 4 5 6 7 <meta content="text/html; charset=ISO-8859-1" http-equiv="content-type"> 8 9 10 <title>PALM chapter 3.4</title> 11 </head> 12 13 14 <body> 15 16 17 <h3 style="line-height: 100%;"><font color="#000000">3.4 18 Input and 5 19 output files</font></h3> 6 <p style="line-height: 100%;"></p><p style="line-height: 100%;"><font color="#000000">The 20 21 22 <p style="line-height: 100%;"></p> 23 24 25 <p style="line-height: 100%;"><font color="#000000">The 7 26 model works 8 27 with a set of files, which are all located in the temporary working … … 22 41 NetCDF call (NF90_CREATE or NF90_OPEN). These files are only created on 23 42 machines where a NetCDF library is available.<br> 24 </font></p><p style="line-height: 100%;"><font color="#000000">The file 43 44 45 </font></p> 46 47 48 <p style="line-height: 100%;"><font color="#000000">The 49 file 25 50 names described in the list correspond to the names indicated in the 26 51 respective OPEN instruction, i.e. the files are expected and saved … … 34 59 4.5.1</a> which gives more details about the PALM-NetCDF-output).</font> 35 60 </p> 36 <p style="line-height: 100%;"> </p><p style="line-height: 100%;"><font color="#000000">On 61 62 63 <p style="line-height: 100%;"> </p> 64 65 66 <p style="line-height: 100%;"><font color="#000000">On 37 67 parallel 38 68 computers many of the files are read and/or written by the central … … 67 97 expected and/or to which output files are written. The file names in 68 98 these directories are always named _0000, _0001, _0002 etc. </font> 69 </font></p><font color="#000000"><font color="#000000">For internal use, 99 </font></p> 100 101 102 <p><font color="#000000"><font color="#000000">For 103 internal use, 70 104 the model may open a set of further files, which are not 71 105 defined by the user but contain no usable information and 72 therefore are not included in this list. <br> 73 <br></font> 74 <table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2"> <tbody> <tr valign="top"> <td width="8%"> <p><font size="4"><b>Unit</b></font></p> </td> 75 <td width="12%"> <p><font size="4"><b>Name</b></font></p> 76 </td> <td width="4%"> <p><font size="4"><b>I/O</b></font></p> 77 </td> <td width="9%"> <p><font size="4"><b>Format</b></font></p> 78 </td> <td colspan="1" width="67%"> <p><font size="4"><b>Description/contents</b></font></p> 79 </td> </tr> <tr valign="top"> <td style="text-align: center;" width="8%"> 11<br> </td> 80 <td width="12%"> <p><a name="PARIN"></a>PARIN</p> 81 </td> <td width="4%"> <p align="center">I</p> 82 </td> <td style="width: 9%;"> <p>ASCII/ 83 <br>NAMELIST</p> </td> <td colspan="1" width="67%"> <p><font color="#000000">Parameter 106 therefore are not included in this list.</font></font></p> 107 <p><font color="#000000"><font color="#000000"> 108 109 <a name="coupled"></a>In case of <a href="chapter_3.8.html">coupled</a> atmosphere-ocean 110 runs (see <a href="chapter_3.8.html">chapter 3.8</a>), 111 both the atmosphere and the </font></font><font color="#000000"><font color="#000000"><a href="chapter_4.1.html#ocean">ocean</a> executable use 112 the same temporary working directory. However, each executable requires its own, unique set of files for I/O. In order to 113 distinguish between atmosphere and ocean files, coupled </font></font><font color="#000000"><font color="#000000">atmosphere-ocean 114 </font></font><font color="#000000"><font color="#000000">runs use the </font></font><font color="#000000"><font color="#000000">following 115 filename convention</font></font><font color="#000000"><font color="#000000">. </font></font><font color="#000000"><font color="#000000">The 116 atmosphere executable uses the set of normal filenames given in the 117 table below. The ocean executable uses a set of modified filenames that 118 have the string '_O' added to their normal name. The coupled 119 ocean filenames are given in brackets in the table below where 120 applicable. The string '_O' is simply appended </font></font><font color="#000000"><font color="#000000">to most 121 filenames</font></font><font color="#000000"><font color="#000000">; exceptions are highlighted in bold face. (<span style="font-weight: bold;">Note:</span> uncoupled 122 ocean runs use the normal set of filenames without '_O'.)</font></font></p> 123 <p></p> 124 <font color="#000000"><font color="#000000"> 125 126 <br> 127 128 129 </font> 130 <table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2"> 131 132 133 <tbody> 134 135 136 <tr valign="top"> 137 138 139 <td width="8%"> 140 141 <p><font size="4"><b>Unit</b></font></p> 142 143 144 </td> 145 146 147 <td width="12%"> 148 149 <p><font size="4"><b>Name</b></font></p> 150 151 152 </td> 153 154 155 <td width="4%"> 156 157 <p><font size="4"><b>I/O</b></font></p> 158 159 160 </td> 161 162 163 <td width="9%"> 164 165 <p><font size="4"><b>Format</b></font></p> 166 167 168 </td> 169 170 171 <td colspan="1" width="67%"> 172 173 <p><font size="4"><b>Description/contents</b></font></p> 174 175 176 </td> 177 178 179 </tr> 180 181 182 <tr valign="top"> 183 184 185 <td style="text-align: center;" width="8%"> 11<br> 186 187 188 </td> 189 190 191 <td width="12%"> 192 193 <p><a name="PARIN"></a>PARIN<br> 194 195 196 (PARIN_O)</p> 197 198 199 </td> 200 201 202 <td width="4%"> 203 204 <p align="center">I</p> 205 206 207 </td> 208 209 210 <td style="width: 9%;"> 211 212 <p>ASCII/ <br> 213 214 215 NAMELIST</p> 216 217 218 </td> 219 220 221 <td colspan="1" width="67%"> 222 223 <p><font color="#000000">Parameter 84 224 for model steering. This file 85 225 is needed by the model in each case. Its content and structure is … … 87 227 4.0</a>. <a href="chapter_4.4.1.html">Chapter 88 228 4.4.1</a> <font color="#000000">shows a simple 89 example. </font> </p> </td> </tr> <tr valign="top"> <td style="text-align: center;" width="8%"> <p align="center">13</p> </td> 90 <td width="12%"> <p><a name="BININ"></a>BININ/</p> 91 </td> <td width="4%"> <p align="center">I</p> 92 </td> <td width="9%"> <p>Binary</p> </td> 93 <td colspan="1" width="67%"> <p>Binary data, 229 example. </font> </p> 230 231 232 </td> 233 234 235 </tr> 236 237 238 <tr valign="top"> 239 240 241 <td style="text-align: center;" width="8%"> 242 243 <p align="center">13</p> 244 245 246 </td> 247 248 249 <td width="12%"> 250 251 <p><a name="BININ"></a>BININ/<br> 252 253 254 (BININ<span style="font-weight: bold;">_O</span>/)</p> 255 256 257 </td> 258 259 260 <td width="4%"> 261 262 <p align="center">I</p> 263 264 265 </td> 266 267 268 <td width="9%"> 269 270 <p>Binary</p> 271 272 273 </td> 274 275 276 <td colspan="1" width="67%"> 277 278 <p>Binary data, 94 279 which are read in by the model at the beginning 95 280 of a restart run (see <a href="chapter_3.3.html">chapter … … 106 291 reads its own file and the file content is processor-dependent. The 107 292 number of processors which can be used must not be changed during a job 108 chain and/or if a job chain is continued. </p> <p>Knowledge 293 chain and/or if a job chain is continued. </p> 294 295 296 297 <p>Knowledge 109 298 of the file structure is usually not necessary, 110 299 because the file is produced and also read again by the model, but it 111 300 can be useful for error determination in case of read errors . 112 301 Therefore the file structure is described in the following. </p> 113 <p>The first record of this file contains a version number (ten 302 303 304 305 <p>The first record of this file contains a version number 306 (ten 114 307 character string) of the subroutine, which, which output the data that 115 308 follows (write_var_list.f90). This number has to … … 117 310 (read_var_list.f90) in case of a restart run. Otherwise the model run 118 311 is aborted. Version numbers are changed whenever new code revisions 119 require a change of the file format. </p> <p>Starting 312 require a change of the file format. </p> 313 314 315 316 <p>Starting 120 317 from the second record, all initial parameters follow 121 318 (exception: <a href="chapter_4.1.html#initializing_actions">initializing_actions</a>), … … 128 325 and <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>. 129 326 If a variable with unknown name is found the model run is 130 aborted. </p> <p>At the end of the initial 327 aborted. </p> 328 329 330 331 <p>At the end of the initial 131 332 parameters a record with the string "<i>*** 132 333 end ***</i>"follows (filled up with trailing blanks up to a 133 334 length of 134 30 characters). </p> <p>Afterwards the fields 335 30 characters). </p> 336 337 338 339 <p>Afterwards the fields 135 340 of the prognostic and diagnostic 136 341 variables follow. This part of the file also begins with a record … … 138 343 version number of the subroutine that wrote the arrays that follow 139 344 (write_3d_binary.f90). It must agree with the number of the reading 140 subroutine (read_3d_binary.f90). </p> <p>The 345 subroutine (read_3d_binary.f90). </p> 346 347 348 349 <p>The 141 350 following record contains the number of processors which 142 351 were used in the model run producing this file, the processor ID of the … … 147 356 particular on parallel computers, because the jobs of a job chain 148 357 always have to use the same number of processors and the same virtual 149 processor grid. </p> <p>After these tests the 358 processor grid. </p> 359 360 361 362 <p>After these tests the 150 363 individual arrays as well as parameters 151 364 and variables for plots of horizontally averaged vertical profiles … … 158 371 parameter <a href="chapter_4.2.html#use_prior_plot1d_parameters">use_prior_plot1d_parameters</a> 159 372 = <i>.TRUE</i> is selected, otherwise they will be 160 skipped. </p> <p>At the end of the file there 373 skipped. </p> 374 375 376 377 <p>At the end of the file there 161 378 has to be a record with the 162 379 character string "<span style="font-style: italic;"></span><i>*** 163 380 end 164 381 ***</i>"(filled up with trailing blanks up to a length of 20 165 characters).</p> </td> </tr> <tr valign="top"> 166 <td style="text-align: center;" width="8%"> <p align="center">14</p> </td> <td width="12%"> 167 <p><a name="BINOUT"></a>BINOUT/</p> </td> 168 <td width="4%"> <p align="center">O</p> 169 </td> <td width="9%"> <p>Binary</p> </td> 170 <td colspan="1" width="67%"> <p>Binary data, 382 characters).</p> 383 384 385 </td> 386 387 388 </tr> 389 390 391 <tr valign="top"> 392 393 394 <td style="text-align: center;" width="8%"> 395 396 <p align="center">14</p> 397 398 399 </td> 400 401 402 <td width="12%"> 403 404 <p><a name="BINOUT"></a>BINOUT/<br> 405 406 407 (BINOUT<span style="font-weight: bold;">_O</span>/)</p> 408 409 410 </td> 411 412 413 <td width="4%"> 414 415 <p align="center">O</p> 416 417 418 </td> 419 420 421 <td width="9%"> 422 423 <p>Binary</p> 424 425 426 </td> 427 428 429 <td colspan="1" width="67%"> 430 431 <p>Binary data, 171 432 which are written by the model at the end of the 172 433 run and possibly needed by restart runs (see <a href="chapter_3.3.html">chapter … … 185 446 the 186 447 description of the file <a href="#BININ">BININ</a>. 187 </p> <p>The file BINOUT is written by the model only if, 448 </p> 449 450 451 452 <p>The file BINOUT is written by the model only if, 188 453 with the help 189 454 of the <b>mrun</b>-configuration file, the <font face="Thorndale, serif">value</font> <span style="font-family: monospace;">true</span> is … … 192 457 variable <span style="font-size: 10pt; font-family: monospace;">write_binary</span> 193 458 (see <a href="chapter_3.3.html">chapter 194 3.3</a>). </p> <p>With large grid point 459 3.3</a>). </p> 460 461 462 463 <p>With large grid point 195 464 numbers the file BINOUT (or the 196 465 files residing in directory BINOUT/) will be very large and should 197 466 be stored (if available) on the archive system of the remote computer.</p> 198 </td> </tr> <tr> <td style="vertical-align: top; text-align: center;">15<br> 199 </td> <td style="vertical-align: top;"><a name="RUN_CONTROL"></a>RUN_CONTROL</td> <td style="vertical-align: top;">O</td> <td style="vertical-align: top;">Ascii</td> <td colspan="1" width="67%"> <p>This file contains 467 468 469 </td> 470 471 472 </tr> 473 474 475 <tr> 476 477 478 <td style="vertical-align: top; text-align: center;">15<br> 479 480 481 </td> 482 483 484 <td style="vertical-align: top;"><a name="RUN_CONTROL"></a>RUN_CONTROL<br> 485 486 487 (RUN_CONTROL_O)</td> 488 489 490 <td style="vertical-align: top;">O</td> 491 492 493 <td style="vertical-align: top;">Ascii</td> 494 495 496 <td colspan="1" width="67%"> 497 498 <p>This file contains 200 499 the so-called time step control output of 201 500 the model. At certain temporal intervals, which are described by the … … 206 505 file. Additionally, such a control line is always written, whenever the 207 506 time step of the model changes. All data and quantities always refer to 208 the entire model domain. </p> <p>If the 507 the entire model domain. </p> 508 509 510 511 <p>If the 209 512 1D-model is switched on for the initialization of the 210 513 3D-models, then control lines are likewise written into this file at 211 514 certain temporal intervals (see <a href="chapter_4.1.html#dt_run_control_1d">dt_run_control_1d</a>). 212 </p> <p>By default, the file RUN_CONTROL only lists 515 </p> 516 517 518 519 <p>By default, the file RUN_CONTROL only lists 213 520 information 214 521 about the selected model parameters at the beginning of the … … 220 527 it can be achieved that this information is also written at the 221 528 beginning of the file RUN_CONTROL at restart runs. </p> 222 <p>The individual columns of the 1D - time step control output 529 530 531 532 <p>The individual columns of the 1D - time step control 533 output 223 534 have the following meaning (listed by the respective heading of the 224 535 appropriate 225 column in the file): <br> </p> <table style="text-align: left; width: 100%;" cellpadding="2"> 226 <tbody> <tr> <td style="vertical-align: top;">ITER.</td> 227 <td style="vertical-align: top;">Number of time steps 228 accomplished so far</td> </tr> <tr> <td style="vertical-align: top;">HH:MM:SS</td> <td style="vertical-align: top;">Time (in hours: minutes: 229 seconds)</td> </tr> <tr> <td style="vertical-align: top;">DT</td> <td style="vertical-align: top;">Time step (in s)</td> </tr> 230 <tr> <td style="vertical-align: top;">UMAX</td> 231 <td style="vertical-align: top;">Maximum absolute wind 536 column in the file): <br> 537 538 539 </p> 540 541 542 543 <table style="text-align: left; width: 100%;" cellpadding="2"> 544 545 546 <tbody> 547 548 549 <tr> 550 551 552 <td style="vertical-align: top;">ITER.</td> 553 554 555 <td style="vertical-align: top;">Number of 556 time steps 557 accomplished so far</td> 558 559 560 </tr> 561 562 563 <tr> 564 565 566 <td style="vertical-align: top;">HH:MM:SS</td> 567 568 569 <td style="vertical-align: top;">Time (in 570 hours: minutes: 571 seconds)</td> 572 573 574 </tr> 575 576 577 <tr> 578 579 580 <td style="vertical-align: top;">DT</td> 581 582 583 <td style="vertical-align: top;">Time step (in 584 s)</td> 585 586 587 </tr> 588 589 590 <tr> 591 592 593 <td style="vertical-align: top;">UMAX</td> 594 595 596 <td style="vertical-align: top;">Maximum 597 absolute wind 232 598 velocity 233 (u-component) (in m/s)</td> </tr> <tr> <td style="vertical-align: top;">VMAX</td> <td style="vertical-align: top;">Maximum absolute wind 599 (u-component) (in m/s)</td> 600 601 602 </tr> 603 604 605 <tr> 606 607 608 <td style="vertical-align: top;">VMAX</td> 609 610 611 <td style="vertical-align: top;">Maximum 612 absolute wind 234 613 velocity 235 (v-component) (in m/s)</td> </tr> <tr> <td style="vertical-align: top;">U *</td> <td style="vertical-align: top;">Friction velocity (<font color="#000000">in </font>m/s)</td> </tr> 236 <tr> <td style="vertical-align: top;">ALPHA</td> 237 <td style="vertical-align: top;">Angle of the wind vector 614 (v-component) (in m/s)</td> 615 616 617 </tr> 618 619 620 <tr> 621 622 623 <td style="vertical-align: top;">U *</td> 624 625 626 <td style="vertical-align: top;">Friction 627 velocity (<font color="#000000">in </font>m/s)</td> 628 629 630 </tr> 631 632 633 <tr> 634 635 636 <td style="vertical-align: top;">ALPHA</td> 637 638 639 <td style="vertical-align: top;">Angle of the 640 wind vector 238 641 (to the x-axis) at the top of the 239 642 Prandtl layer (k=1) (<font color="#000000">in </font>degrees)</td> 240 </tr> <tr> <td style="vertical-align: middle;">ENERG.</td> 241 <td style="vertical-align: top;">Kinetic energy of the 643 644 645 </tr> 646 647 648 <tr> 649 650 651 <td style="vertical-align: middle;">ENERG.</td> 652 653 654 <td style="vertical-align: top;">Kinetic 655 energy of the 242 656 1D-model (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>), 243 averaged over all grid points</td> </tr> </tbody> </table> 244 <p> 657 averaged over all grid points</td> 658 659 660 </tr> 661 662 663 664 </tbody> 665 666 </table> 667 668 669 670 <p> 245 671 The individual columns of the 3D - time step control output 246 672 have the following meaning (listed by the respective heading of the 247 673 appropriate 248 column in the file):<br> </p> <table style="text-align: left; width: 100%;" cellpadding="2"> 249 <tbody> <tr> <td style="vertical-align: top;">RUN</td> 250 <td style="vertical-align: top;">Serial-number of the job 674 column in the file):<br> 675 676 677 </p> 678 679 680 681 <table style="text-align: left; width: 100%;" cellpadding="2"> 682 683 684 <tbody> 685 686 687 <tr> 688 689 690 <td style="vertical-align: top;">RUN</td> 691 692 693 <td style="vertical-align: top;">Serial-number 694 of the job 251 695 in the job chain. The initial 252 696 run has the number 0, restart runs accordingly have larger numbers.</td> 253 </tr> <tr> <td style="vertical-align: top;">ITER.</td> 254 <td style="vertical-align: top;">Number of time steps 697 698 699 </tr> 700 701 702 <tr> 703 704 705 <td style="vertical-align: top;">ITER.</td> 706 707 708 <td style="vertical-align: top;">Number of 709 time steps 255 710 accomplished since starting time t=0 of 256 the initial run.</td> </tr> <tr> <td style="vertical-align: top;">HH:MM:SS</td> <td style="vertical-align: top;">Time (<font color="#000000">in 257 </font>hours: minutes: 711 the initial run.</td> 712 713 714 </tr> 715 716 717 <tr> 718 719 720 <td style="vertical-align: top;">HH:MM:SS</td> 721 722 723 <td style="vertical-align: top;">Time (<font color="#000000">in </font>hours: minutes: 258 724 seconds) since starting time t=0 of the 259 initial run.</td> </tr> <tr> <td style="vertical-align: top;">DT (E)</td> <td style="vertical-align: top;">Time step (<font color="#000000">in </font>s). The 725 initial run.</td> 726 727 728 </tr> 729 730 731 <tr> 732 733 734 <td style="vertical-align: top;">DT (E)</td> 735 736 737 <td style="vertical-align: top;">Time step (<font color="#000000">in </font>s). The 260 738 following character indicates whether the 261 739 time … … 268 746 Euler). This 269 747 does 270 not apply for the default Runge-Kutta timestep scheme.</td> </tr> 271 <tr> <td style="vertical-align: top;">UMAX</td> 272 <td style="vertical-align: top;">Maximum absolute wind 748 not apply for the default Runge-Kutta timestep scheme.</td> 749 750 751 </tr> 752 753 754 <tr> 755 756 757 <td style="vertical-align: top;">UMAX</td> 758 759 760 <td style="vertical-align: top;">Maximum 761 absolute wind 273 762 velocity (u-component) (<font color="#000000">in </font>m/s). 274 763 If at … … 277 766 horizontal velocity field (see <a href="chapter_4.2.html#create_disturbances">create_disturbances</a>), 278 767 the character D will appear directly after the velocity value.</td> 279 </tr> <tr> <td style="vertical-align: top;">VMAX</td> 280 <td style="vertical-align: top;">Maximum absolute wind 768 769 770 </tr> 771 772 773 <tr> 774 775 776 <td style="vertical-align: top;">VMAX</td> 777 778 779 <td style="vertical-align: top;">Maximum 780 absolute wind 281 781 velocity (v-component) (<font color="#000000">in </font>m/s). 282 782 If at … … 285 785 horizontal velocity field (see <a href="chapter_4.2.html#create_disturbances">create_disturbances</a>), 286 786 the character D will appear directly after the velocity value.</td> 287 </tr> <tr> <td style="vertical-align: top;">WMAX</td> 288 <td style="vertical-align: top;">Maximum absolute wind 787 788 789 </tr> 790 791 792 <tr> 793 794 795 <td style="vertical-align: top;">WMAX</td> 796 797 798 <td style="vertical-align: top;">Maximum 799 absolute wind 289 800 velocity (w-component) (<font color="#000000">in </font>m/s).</td> 290 </tr> <tr> <td style="vertical-align: top;">U 291 *</td> <td style="vertical-align: top;">Horizontal 801 802 803 </tr> 804 805 806 <tr> 807 808 809 <td style="vertical-align: top;">U 810 *</td> 811 812 813 <td style="vertical-align: top;">Horizontal 292 814 average of the 293 815 friction velocity (<font color="#000000">in </font>m/s).</td> 294 </tr> <tr> <td style="vertical-align: top;">W 295 *</td> <td style="vertical-align: top;">Convective 816 817 818 </tr> 819 820 821 <tr> 822 823 824 <td style="vertical-align: top;">W 825 *</td> 826 827 828 <td style="vertical-align: top;">Convective 296 829 velocity scale 297 830 (<font color="#000000">in </font>m/s). The assumed 298 831 boundary layer 299 height is determined via the heat flux minimum criterion.</td> </tr> 300 <tr> <td style="vertical-align: top;">THETA *</td> 301 <td style="vertical-align: top;">Characteristic 832 height is determined via the heat flux minimum criterion.</td> 833 834 835 </tr> 836 837 838 <tr> 839 840 841 <td style="vertical-align: top;">THETA *</td> 842 843 844 <td style="vertical-align: top;">Characteristic 302 845 temperature 303 846 of the Prandtl - layer (<font color="#000000">in </font>K).</td> 304 </tr> <tr> <td style="vertical-align: top;">Z_I</td> 305 <td style="vertical-align: top;">Height of the convective 847 848 849 </tr> 850 851 852 <tr> 853 854 855 <td style="vertical-align: top;">Z_I</td> 856 857 858 <td style="vertical-align: top;">Height of the 859 convective 306 860 boundary layer (<font color="#000000">in </font>m), 307 861 determined via 308 the criterion of the heat flux minimum.</td> </tr> <tr> 309 <td style="vertical-align: middle;">ENERG.</td> <td style="vertical-align: top;">Average resolved total 862 the criterion of the heat flux minimum.</td> 863 864 865 </tr> 866 867 868 <tr> 869 870 871 <td style="vertical-align: middle;">ENERG.</td> 872 873 874 <td style="vertical-align: top;">Average 875 resolved total 310 876 energy of the flow field (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>), 311 normalized with the total number of grid points.</td> </tr> 312 <tr> <td style="vertical-align: middle;">DISTENERG</td> 313 <td style="vertical-align: top;">Average resolved 877 normalized with the total number of grid points.</td> 878 879 880 </tr> 881 882 883 <tr> 884 885 886 <td style="vertical-align: middle;">DISTENERG</td> 887 888 889 <td style="vertical-align: top;">Average 890 resolved 314 891 disturbance energy of flow field (<font color="#000000">in 315 </font>m<sup>2</sup>/s<sup>2</sup>), 316 normalized with the total number of grid points.</td> </tr> 317 <tr> <td style="vertical-align: top;">DIVOLD</td> 318 <td style="vertical-align: top;"><font color="#000000">Divergence 892 </font>m<sup>2</sup>/s<sup>2</sup>), 893 normalized with the total number of grid points.</td> 894 895 896 </tr> 897 898 899 <tr> 900 901 902 <td style="vertical-align: top;">DIVOLD</td> 903 904 905 <td style="vertical-align: top;"><font color="#000000">Divergence 319 906 of the velocity field (sum of 320 907 the absolute values) (</font><font color="#000000">in 321 </font><font color="#000000">1/s) before call of the 908 </font><font color="#000000">1/s) before 909 call of the 322 910 pressure solver, 323 911 normalized with the total number of grid points.</font></td> 324 </tr> <tr> <td style="vertical-align: top;">DIVNEW</td> 325 <td style="vertical-align: top;"><font color="#000000">Divergence 912 913 914 </tr> 915 916 917 <tr> 918 919 920 <td style="vertical-align: top;">DIVNEW</td> 921 922 923 <td style="vertical-align: top;"><font color="#000000">Divergence 326 924 of the velocity field (sum of 327 925 the absolute values) (</font><font color="#000000">in 328 </font><font color="#000000">1/s) after call of the 926 </font><font color="#000000">1/s) after 927 call of the 329 928 pressure solver, normalized</font> 330 with the total number of grid points.</td> </tr> <tr> 331 <td style="vertical-align: top;">UMAX (KJI)</td> <td style="vertical-align: top;">Indices of the grid point 929 with the total number of grid points.</td> 930 931 932 </tr> 933 934 935 <tr> 936 937 938 <td style="vertical-align: top;">UMAX (KJI)</td> 939 940 941 <td style="vertical-align: top;">Indices of 942 the grid point 332 943 with the maximum absolute 333 u-component of the wind velocity (sequence: k, j, i).</td> </tr> 334 <tr> <td style="vertical-align: top;">VMAX (KJI)</td> 335 <td style="vertical-align: top;">Indices of the grid point 944 u-component of the wind velocity (sequence: k, j, i).</td> 945 946 947 </tr> 948 949 950 <tr> 951 952 953 <td style="vertical-align: top;">VMAX (KJI)</td> 954 955 956 <td style="vertical-align: top;">Indices of 957 the grid point 336 958 with the maximum absolute 337 v-component of the wind velocity (sequence: k, j, i).</td> </tr> 338 <tr> <td style="vertical-align: top;">WMAX (KJI)</td> 339 <td style="vertical-align: top;">Indices of the grid point 959 v-component of the wind velocity (sequence: k, j, i).</td> 960 961 962 </tr> 963 964 965 <tr> 966 967 968 <td style="vertical-align: top;">WMAX (KJI)</td> 969 970 971 <td style="vertical-align: top;">Indices of 972 the grid point 340 973 with the maximum absolute 341 w-component of the wind velocity (sequence: k, j, i).</td> </tr> 342 <tr> <td style="vertical-align: top;">ADVECX</td> 343 <td style="vertical-align: top;">Distance (<font color="#000000">in </font>km) the 974 w-component of the wind velocity (sequence: k, j, i).</td> 975 976 977 </tr> 978 979 980 <tr> 981 982 983 <td style="vertical-align: top;">ADVECX</td> 984 985 986 <td style="vertical-align: top;">Distance (<font color="#000000">in </font>km) the 344 987 coordinate system has been moved in 345 988 x-direction with Galilei-Transformation switched on (see <a href="chapter_4.1.html#galilei_transformation">galilei_transformation</a>).</td> 346 </tr> <tr> <td style="vertical-align: top;">ADVECY</td> 347 <td style="vertical-align: top;">Distance (<font color="#000000">in </font>km) the 989 990 991 </tr> 992 993 994 <tr> 995 996 997 <td style="vertical-align: top;">ADVECY</td> 998 999 1000 <td style="vertical-align: top;">Distance (<font color="#000000">in </font>km) the 348 1001 coordinate system has been moved in 349 1002 y-direction with Galilei-Transformation switched on (see <a href="chapter_4.1.html#galilei_transformation">galilei_transformation</a>).</td> 350 </tr> </tbody> </table> </td> </tr> <tr> 351 <td style="vertical-align: top; text-align: center;">16<br> 352 </td> <td style="vertical-align: top;"><a name="LIST_PROFIL"></a>LIST_PROFIL </td> <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii<br> </td> <td style="vertical-align: top;">This file contains horizontally 1003 1004 1005 </tr> 1006 1007 1008 1009 </tbody> 1010 1011 </table> 1012 1013 1014 </td> 1015 1016 1017 </tr> 1018 1019 1020 <tr> 1021 1022 1023 <td style="vertical-align: top; text-align: center;">16<br> 1024 1025 1026 </td> 1027 1028 1029 <td style="vertical-align: top;"><a name="LIST_PROFIL"></a>LIST_PROFIL<br> 1030 1031 1032 (LIST_PROFIL_O) </td> 1033 1034 1035 <td style="vertical-align: top;">O<br> 1036 1037 1038 </td> 1039 1040 1041 <td style="vertical-align: top;">Ascii<br> 1042 1043 1044 </td> 1045 1046 1047 <td style="vertical-align: top;">This file contains 1048 horizontally 353 1049 (and possibly temporally) 354 1050 averaged vertical profiles of some model variables. The quantities … … 363 1059 the respective subdomain (see <a href="chapter_4.3.html#region">region</a>) 364 1060 appears in the header of the respective table. <br> 1061 1062 365 1063 In each case the tables consist of a header, followed by the 366 1064 profiles arranged next to each other in columns. The header contains … … 370 1068 computer, date, time of the beginning of the run, name of the 371 1069 subdomain, output time, kind of averaging). On the u-v-level the 372 following columns are written: <br> <table style="text-align: left; width: 100%;" cellpadding="2"> 373 <tbody> <tr> <td style="text-align: left; vertical-align: middle;">k<br> 374 </td> <td style="text-align: left; vertical-align: middle;">Vertical 375 grid point index.</td> </tr> <tr> <td style="text-align: left; vertical-align: middle;">zu<br> 376 </td> <td style="text-align: left; vertical-align: middle;">Height 1070 following columns are written: <br> 1071 1072 1073 1074 <table style="text-align: left; width: 100%;" cellpadding="2"> 1075 1076 1077 <tbody> 1078 1079 1080 <tr> 1081 1082 1083 <td style="text-align: left; vertical-align: middle;">k<br> 1084 1085 1086 </td> 1087 1088 1089 <td style="text-align: left; vertical-align: middle;">Vertical 1090 grid point index.</td> 1091 1092 1093 </tr> 1094 1095 1096 <tr> 1097 1098 1099 <td style="text-align: left; vertical-align: middle;">zu<br> 1100 1101 1102 </td> 1103 1104 1105 <td style="text-align: left; vertical-align: middle;">Height 377 1106 of the grid point 378 1107 level (<font color="#000000">in </font>m).</td> 379 </tr> <tr> <td style="text-align: left; vertical-align: middle;">u<br> 380 </td> <td style="text-align: left; vertical-align: middle;">u-component 1108 1109 1110 </tr> 1111 1112 1113 <tr> 1114 1115 1116 <td style="text-align: left; vertical-align: middle;">u<br> 1117 1118 1119 </td> 1120 1121 1122 <td style="text-align: left; vertical-align: middle;">u-component 381 1123 of the wind 382 1124 velocity (<font color="#000000">in </font>m/s).</td> 383 </tr> <tr> <td style="text-align: left; vertical-align: middle;">du<br> 384 </td> <td style="text-align: left; vertical-align: middle;">Deviation 1125 1126 1127 </tr> 1128 1129 1130 <tr> 1131 1132 1133 <td style="text-align: left; vertical-align: middle;">du<br> 1134 1135 1136 </td> 1137 1138 1139 <td style="text-align: left; vertical-align: middle;">Deviation 385 1140 of the 386 1141 u-component from the initial profile at the 387 1142 time t=0 (initialization profile) (<font color="#000000">in 388 </font>m/s).</td> </tr> <tr> <td style="text-align: left; vertical-align: middle;">v<br> 389 </td> <td style="text-align: left; vertical-align: middle;">v-component 1143 </font>m/s).</td> 1144 1145 1146 </tr> 1147 1148 1149 <tr> 1150 1151 1152 <td style="text-align: left; vertical-align: middle;">v<br> 1153 1154 1155 </td> 1156 1157 1158 <td style="text-align: left; vertical-align: middle;">v-component 390 1159 of the wind 391 1160 velocity (<font color="#000000">in </font>m/s).</td> 392 </tr> <tr> <td style="text-align: left; vertical-align: middle;">dv<br> 393 </td> <td style="text-align: left; vertical-align: middle;">Deviation 1161 1162 1163 </tr> 1164 1165 1166 <tr> 1167 1168 1169 <td style="text-align: left; vertical-align: middle;">dv<br> 1170 1171 1172 </td> 1173 1174 1175 <td style="text-align: left; vertical-align: middle;">Deviation 394 1176 of the 395 1177 v-component from the initial profile at the 396 1178 time t=0 (initialization profile) (<font color="#000000">in 397 </font>m/s).</td> </tr> <tr> <td style="text-align: left; vertical-align: middle;">pt 398 <br> </td> <td style="text-align: left; vertical-align: middle;">Potential 1179 </font>m/s).</td> 1180 1181 1182 </tr> 1183 1184 1185 <tr> 1186 1187 1188 <td style="text-align: left; vertical-align: middle;">pt 1189 <br> 1190 1191 1192 </td> 1193 1194 1195 <td style="text-align: left; vertical-align: middle;">Potential 399 1196 temperature (<font color="#000000">in </font>K).</td> 400 </tr> <tr> <td style="text-align: left; vertical-align: middle;">dpt<br> 401 </td> <td style="text-align: left; vertical-align: middle;">Deviation 1197 1198 1199 </tr> 1200 1201 1202 <tr> 1203 1204 1205 <td style="text-align: left; vertical-align: middle;">dpt<br> 1206 1207 1208 </td> 1209 1210 1211 <td style="text-align: left; vertical-align: middle;">Deviation 402 1212 of potential 403 1213 temperature from the initial profile at 404 1214 the time t=0 (initialization profile) (<font color="#000000">in 405 </font>K).</td> </tr> <tr> <td style="text-align: left; vertical-align: middle;">e<br> 406 </td> <td style="text-align: left; vertical-align: middle;">Turbulent 1215 </font>K).</td> 1216 1217 1218 </tr> 1219 1220 1221 <tr> 1222 1223 1224 <td style="text-align: left; vertical-align: middle;">e<br> 1225 1226 1227 </td> 1228 1229 1230 <td style="text-align: left; vertical-align: middle;">Turbulent 407 1231 kinetic energy 408 1232 (subgrid-scale) (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td> 409 </tr> <tr> <td style="text-align: left; vertical-align: middle;">Km<br> 410 </td> <td style="text-align: left; vertical-align: middle;">Turbulent 1233 1234 1235 </tr> 1236 1237 1238 <tr> 1239 1240 1241 <td style="text-align: left; vertical-align: middle;">Km<br> 1242 1243 1244 </td> 1245 1246 1247 <td style="text-align: left; vertical-align: middle;">Turbulent 411 1248 diffusion 412 1249 coefficient for momentum (<font color="#000000">in </font>m<sup>2</sup>/s).</td> 413 </tr> <tr> <td style="text-align: left; vertical-align: middle;">Kh<br> 414 </td> <td style="text-align: left; vertical-align: middle;">Turbulent 1250 1251 1252 </tr> 1253 1254 1255 <tr> 1256 1257 1258 <td style="text-align: left; vertical-align: middle;">Kh<br> 1259 1260 1261 </td> 1262 1263 1264 <td style="text-align: left; vertical-align: middle;">Turbulent 415 1265 diffusion 416 1266 coefficient for heat (<font color="#000000">in </font>m<sup>2</sup>/s).</td> 417 </tr> <tr> <td style="text-align: left; vertical-align: middle;">l<br> 418 </td> <td style="text-align: left; vertical-align: middle;">Mixing 1267 1268 1269 </tr> 1270 1271 1272 <tr> 1273 1274 1275 <td style="text-align: left; vertical-align: middle;">l<br> 1276 1277 1278 </td> 1279 1280 1281 <td style="text-align: left; vertical-align: middle;">Mixing 419 1282 length (<font color="#000000">in </font>m).</td> 420 </tr> <tr> <td style="vertical-align: top;"><br> 421 </td> <td style="vertical-align: top;"><br> </td> 422 </tr> </tbody> </table> 423 On the w-level the following columns are written:<br> <br> 424 <table style="text-align: left; width: 100%;" cellpadding="2"> 425 <tbody> <tr> <td style="vertical-align: middle;">k<br> 426 </td> <td style="vertical-align: middle;">Vertical 1283 1284 1285 </tr> 1286 1287 1288 <tr> 1289 1290 1291 <td style="vertical-align: top;"><br> 1292 1293 1294 </td> 1295 1296 1297 <td style="vertical-align: top;"><br> 1298 1299 1300 </td> 1301 1302 1303 </tr> 1304 1305 1306 1307 </tbody> 1308 1309 </table> 1310 1311 1312 On the w-level the following columns are written:<br> 1313 1314 1315 <br> 1316 1317 1318 1319 <table style="text-align: left; width: 100%;" cellpadding="2"> 1320 1321 1322 <tbody> 1323 1324 1325 <tr> 1326 1327 1328 <td style="vertical-align: middle;">k<br> 1329 1330 1331 </td> 1332 1333 1334 <td style="vertical-align: middle;">Vertical 427 1335 grid point 428 index.</td> </tr> <tr> <td style="vertical-align: middle;">zw<br> </td> <td style="vertical-align: middle;">Height of the grid 1336 index.</td> 1337 1338 1339 </tr> 1340 1341 1342 <tr> 1343 1344 1345 <td style="vertical-align: middle;">zw<br> 1346 1347 1348 </td> 1349 1350 1351 <td style="vertical-align: middle;">Height of 1352 the grid 429 1353 point 430 1354 level (<font color="#000000">in </font>m).</td> 431 </tr> <tr> <td style="vertical-align: middle;">w'pt'</td> 432 <td style="vertical-align: middle;">Vertical subgrid-scale 1355 1356 1357 </tr> 1358 1359 1360 <tr> 1361 1362 1363 <td style="vertical-align: middle;">w'pt'</td> 1364 1365 1366 <td style="vertical-align: middle;">Vertical 1367 subgrid-scale 433 1368 kinematic heat flux (<font color="#000000">in </font>K 434 m/s).</td> </tr> <tr> <td style="vertical-align: middle;">wpt</td> <td style="vertical-align: middle;">Vertical total ( 1369 m/s).</td> 1370 1371 1372 </tr> 1373 1374 1375 <tr> 1376 1377 1378 <td style="vertical-align: middle;">wpt</td> 1379 1380 1381 <td style="vertical-align: middle;">Vertical 1382 total ( 435 1383 subgrid-scale + resolved) 436 1384 kinematic heat flux (<font color="#000000">in </font>K 437 m/s).</td> </tr> <tr> <td style="vertical-align: middle;">w'u'</td> <td style="vertical-align: middle;">u-component of the 1385 m/s).</td> 1386 1387 1388 </tr> 1389 1390 1391 <tr> 1392 1393 1394 <td style="vertical-align: middle;">w'u'</td> 1395 1396 1397 <td style="vertical-align: middle;">u-component 1398 of the 438 1399 vertical subgrid-scale momentum flux (<font color="#000000">in 439 </font>m<sup>2</sup>/s<sup>2</sup>).</td> 440 </tr> <tr> <td style="vertical-align: middle;">wu</td> 441 <td style="vertical-align: middle;">u-component of the 1400 </font>m<sup>2</sup>/s<sup>2</sup>).</td> 1401 1402 1403 </tr> 1404 1405 1406 <tr> 1407 1408 1409 <td style="vertical-align: middle;">wu</td> 1410 1411 1412 <td style="vertical-align: middle;">u-component 1413 of the 442 1414 total 443 1415 vertical momentum flux ( 444 1416 subgrid-scale + resolved) (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td> 445 </tr> <tr> <td style="vertical-align: middle;">w'v'</td> 446 <td style="vertical-align: middle;">v-component of the 1417 1418 1419 </tr> 1420 1421 1422 <tr> 1423 1424 1425 <td style="vertical-align: middle;">w'v'</td> 1426 1427 1428 <td style="vertical-align: middle;">v-component 1429 of the 447 1430 vertical subgrid-scale momentum flux (<font color="#000000">in 448 </font>m<sup>2</sup>/s<sup>2</sup>).</td> 449 </tr> <tr> <td style="vertical-align: middle;">wv</td> 450 <td style="vertical-align: middle;">v-component of the 1431 </font>m<sup>2</sup>/s<sup>2</sup>).</td> 1432 1433 1434 </tr> 1435 1436 1437 <tr> 1438 1439 1440 <td style="vertical-align: middle;">wv</td> 1441 1442 1443 <td style="vertical-align: middle;">v-component 1444 of the 451 1445 total 452 1446 vertical momentum flux ( 453 1447 subgrid-scale + resolved) (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td> 454 </tr> </tbody> </table> <br> </td> </tr> 455 <tr> <td style="vertical-align: top; text-align: center;">17 456 </td> <td style="vertical-align: top;"><a name="LIST_PROFIL_1D"></a>LIST_PROFIL_1D </td> <td style="vertical-align: top;">O </td> <td style="vertical-align: top;">Ascii </td> <td style="vertical-align: top;">This file contains the vertical 1448 1449 1450 </tr> 1451 1452 1453 1454 </tbody> 1455 1456 </table> 1457 1458 1459 <br> 1460 1461 1462 </td> 1463 1464 1465 </tr> 1466 1467 1468 <tr> 1469 1470 1471 <td style="vertical-align: top; text-align: center;">17 1472 </td> 1473 1474 1475 <td style="vertical-align: top;"><a name="LIST_PROFIL_1D"></a>LIST_PROFIL_1D<br> 1476 1477 1478 (LIST_PROFIL_1D_O)</td> 1479 1480 1481 <td style="vertical-align: top;">O </td> 1482 1483 1484 <td style="vertical-align: top;">Ascii </td> 1485 1486 1487 <td style="vertical-align: top;">This file contains 1488 the vertical 457 1489 profiles calculated by the 458 1490 1D-model within initial runs. The quantities saved are set … … 466 1498 only switched on at initial runs), executing computer, date, 467 1499 time of the beginning of the run, output time). Afterwards the 468 following columns appear:<br> <table style="text-align: left; width: 100%;" cellpadding="2"> 469 <tbody> <tr> <td style="text-align: left; vertical-align: middle;">k<br> 470 </td> <td style="text-align: left; vertical-align: middle;">Vertical 471 grid point index.</td> </tr> <tr> <td style="text-align: left; vertical-align: middle;">zu<br> 472 </td> <td style="text-align: left; vertical-align: middle;">Height 1500 following columns appear:<br> 1501 1502 1503 1504 <table style="text-align: left; width: 100%;" cellpadding="2"> 1505 1506 1507 <tbody> 1508 1509 1510 <tr> 1511 1512 1513 <td style="text-align: left; vertical-align: middle;">k<br> 1514 1515 1516 </td> 1517 1518 1519 <td style="text-align: left; vertical-align: middle;">Vertical 1520 grid point index.</td> 1521 1522 1523 </tr> 1524 1525 1526 <tr> 1527 1528 1529 <td style="text-align: left; vertical-align: middle;">zu<br> 1530 1531 1532 </td> 1533 1534 1535 <td style="text-align: left; vertical-align: middle;">Height 473 1536 of the grid point 474 1537 level (<font color="#000000">in </font>m).</td> 475 </tr> <tr> <td style="text-align: left; vertical-align: middle;">u<br> 476 </td> <td style="text-align: left; vertical-align: middle;">u-component 1538 1539 1540 </tr> 1541 1542 1543 <tr> 1544 1545 1546 <td style="text-align: left; vertical-align: middle;">u<br> 1547 1548 1549 </td> 1550 1551 1552 <td style="text-align: left; vertical-align: middle;">u-component 477 1553 of the wind 478 1554 velocity (<font color="#000000">in </font>m/s).</td> 479 </tr> <tr> <td style="text-align: left; vertical-align: middle;">v<br> 480 </td> <td style="text-align: left; vertical-align: middle;">v-component 1555 1556 1557 </tr> 1558 1559 1560 <tr> 1561 1562 1563 <td style="text-align: left; vertical-align: middle;">v<br> 1564 1565 1566 </td> 1567 1568 1569 <td style="text-align: left; vertical-align: middle;">v-component 481 1570 of the wind 482 1571 velocity (<font color="#000000">in </font>m/s).</td> 483 </tr> <tr> <td style="text-align: left; vertical-align: middle;">pt<br> 484 </td> <td style="text-align: left; vertical-align: middle;">Potential 1572 1573 1574 </tr> 1575 1576 1577 <tr> 1578 1579 1580 <td style="text-align: left; vertical-align: middle;">pt<br> 1581 1582 1583 </td> 1584 1585 1586 <td style="text-align: left; vertical-align: middle;">Potential 485 1587 temperature (<font color="#000000">in </font>K).</td> 486 </tr> <tr> <td style="text-align: left; vertical-align: middle;">e<br> 487 </td> <td style="text-align: left; vertical-align: middle;">Turbulent 1588 1589 1590 </tr> 1591 1592 1593 <tr> 1594 1595 1596 <td style="text-align: left; vertical-align: middle;">e<br> 1597 1598 1599 </td> 1600 1601 1602 <td style="text-align: left; vertical-align: middle;">Turbulent 488 1603 kinetic energy (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td> 489 </tr> <tr> <td style="text-align: left; vertical-align: middle;">rif<br> 490 </td> <td style="text-align: left; vertical-align: middle;">Flux 491 Richardson number</td> </tr> <tr> <td style="text-align: left; vertical-align: middle;">Km<br> 492 </td> <td style="text-align: left; vertical-align: middle;">Turbulent 1604 1605 1606 </tr> 1607 1608 1609 <tr> 1610 1611 1612 <td style="text-align: left; vertical-align: middle;">rif<br> 1613 1614 1615 </td> 1616 1617 1618 <td style="text-align: left; vertical-align: middle;">Flux 1619 Richardson number</td> 1620 1621 1622 </tr> 1623 1624 1625 <tr> 1626 1627 1628 <td style="text-align: left; vertical-align: middle;">Km<br> 1629 1630 1631 </td> 1632 1633 1634 <td style="text-align: left; vertical-align: middle;">Turbulent 493 1635 diffusion 494 1636 coefficient for momentum (<font color="#000000">in </font>m<sup>2</sup>/s).</td> 495 </tr> <tr> <td style="text-align: left; vertical-align: middle;">Kh<br> 496 </td> <td style="text-align: left; vertical-align: middle;">Turbulent 1637 1638 1639 </tr> 1640 1641 1642 <tr> 1643 1644 1645 <td style="text-align: left; vertical-align: middle;">Kh<br> 1646 1647 1648 </td> 1649 1650 1651 <td style="text-align: left; vertical-align: middle;">Turbulent 497 1652 diffusion 498 1653 coefficient for heat (<font color="#000000">in </font>m<sup>2</sup>/s).</td> 499 </tr> <tr> <td style="text-align: left; vertical-align: middle;">l<br> 500 </td> <td style="text-align: left; vertical-align: middle;"><font color="#000000">Mixing 501 length (</font><font color="#000000">in </font><font color="#000000">m).</font></td> </tr> </tbody> 502 </table> <br> </td> </tr> <tr> <td style="vertical-align: top; text-align: center;">18 </td> 503 <td style="vertical-align: top;"><a name="CPU_MEASURES"></a>CPU_MEASURES 504 </td> <td style="vertical-align: top;">O </td> 505 <td style="vertical-align: top;">Ascii </td> <td style="vertical-align: top;">Time measurements are 1654 1655 1656 </tr> 1657 1658 1659 <tr> 1660 1661 1662 <td style="text-align: left; vertical-align: middle;">l<br> 1663 1664 1665 </td> 1666 1667 1668 <td style="text-align: left; vertical-align: middle;"><font color="#000000">Mixing 1669 length (</font><font color="#000000">in </font><font color="#000000">m).</font></td> 1670 1671 1672 </tr> 1673 1674 1675 1676 </tbody> 1677 1678 </table> 1679 1680 1681 <br> 1682 1683 1684 </td> 1685 1686 1687 </tr> 1688 1689 1690 <tr> 1691 1692 1693 <td style="vertical-align: top; text-align: center;">18 1694 </td> 1695 1696 1697 <td style="vertical-align: top;"><a name="CPU_MEASURES"></a>CPU_MEASURES<br> 1698 1699 1700 (CPU_MEASURES_O)</td> 1701 1702 1703 <td style="vertical-align: top;">O </td> 1704 1705 1706 <td style="vertical-align: top;">Ascii </td> 1707 1708 1709 <td style="vertical-align: top;">Time measurements 1710 are 506 1711 accomplished through the subroutine <span style="font-family: monospace;">cpu_log.f90.</span><span style="font-size: 10pt;"></span> The file 507 1712 CPU_MEASURES contains a header with some basic information of the … … 517 1722 measures) overlaps (in particular with the parts described in the first 518 1723 table) are possible. <br> 1724 1725 519 1726 For each model part it is indicated in the following columns how much 520 1727 CPU time was needed (absolutely and relative), and how often it was … … 527 1734 parallelization the CPU times on the individual processors should 528 1735 differ only little from each other and the standard deviation should be 529 small. </td> </tr> <tr> <td style="vertical-align: top; text-align: center;">19 </td> 530 <td style="vertical-align: top;"><a name="HEADER"></a>HEADER 531 </td> <td style="vertical-align: top;">O </td> 532 <td style="vertical-align: top;">Ascii </td> <td style="vertical-align: top;"> <p>Information about 1736 small. </td> 1737 1738 1739 </tr> 1740 1741 1742 <tr> 1743 1744 1745 <td style="vertical-align: top; text-align: center;">19 1746 </td> 1747 1748 1749 <td style="vertical-align: top;"><a name="HEADER"></a>HEADER<br> 1750 1751 1752 (HEADER_O) </td> 1753 1754 1755 <td style="vertical-align: top;">O </td> 1756 1757 1758 <td style="vertical-align: top;">Ascii </td> 1759 1760 1761 <td style="vertical-align: top;"> 1762 1763 <p>Information about 533 1764 the selected model parameters (physical and 534 1765 numerical values) as well as general information about the 535 run. </p> <p>This file contains the values of 1766 run. </p> 1767 1768 1769 1770 <p>This file contains the values of 536 1771 all important steering 537 1772 parameters … … 554 1789 time reached is missing etc.) and then briefly before the normal end of 555 1790 the simulation. The second, now complete output overwrites the first 556 output.). </p> <p>At the end of the file, 1791 output.). </p> 1792 1793 1794 1795 <p>At the end of the file, 557 1796 information about the values of user 558 1797 parameters (see <a href="chapter_3.7.html">chapter … … 571 1810 profiles and time series are output. All further information to appear 572 1811 here, must be provided by the user (by appropriate 573 WRITE statements in <tt><font style="font-size: 10pt;" size="2">user_header</font></tt>).</p> </td> 574 </tr> <tr> <td style="vertical-align: top; text-align: center;">21 </td> 575 <td style="vertical-align: top;"><a name="PLOT2D_XY"></a>PLOT2D_XY 576 </td> <td style="vertical-align: top;">O<br> </td> 577 <td style="vertical-align: top;">Binary<br> </td> 578 <td style="vertical-align: top;"> <p>This file 1812 WRITE statements in <tt><font style="font-size: 10pt;" size="2">user_header</font></tt>).</p> 1813 1814 1815 </td> 1816 1817 1818 </tr> 1819 1820 1821 <tr> 1822 1823 1824 <td style="vertical-align: top; text-align: center;">21 1825 </td> 1826 1827 1828 <td style="vertical-align: top;"><a name="PLOT2D_XY"></a>PLOT2D_XY<br> 1829 1830 1831 (PLOT2D_XY_O)</td> 1832 1833 1834 <td style="vertical-align: top;">O<br> 1835 1836 1837 </td> 1838 1839 1840 <td style="vertical-align: top;">Binary<br> 1841 1842 1843 </td> 1844 1845 1846 <td style="vertical-align: top;"> 1847 1848 <p>This file 579 1849 contains data of the two-dimensional horizontal 580 1850 cross sections written by the model (see <a href="chapter_4.2.html#data_output">data_output</a>) … … 588 1858 local files <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a> 589 1859 and <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>. 590 </p> <p>With parallel runs and choice of <a href="chapter_4.2.html#data_output_2d_on_each_pe">data_output_2d_on_each_pe</a> 1860 </p> 1861 1862 1863 1864 <p>With parallel runs and choice of <a href="chapter_4.2.html#data_output_2d_on_each_pe">data_output_2d_on_each_pe</a> 591 1865 = <i>.T.</i> each processing element writes the data of 592 1866 its subdomain … … 608 1882 possibly existing files of the other cross sections (xz and/or yz) 609 1883 and three-dimensional arrays (see <a href="#PLOT3D_DATA">PLOT3D_DATA</a>) 610 are also combined. </p> <p>Further information 1884 are also combined. </p> 1885 1886 1887 1888 <p>Further information 611 1889 about the output of plots of 612 1890 two-dimensional cross sections is found in the description of the run 613 1891 parameter <a href="chapter_4.2.html#data_output">data_output</a>.</p> 614 </td> </tr> <tr> <td style="vertical-align: top; text-align: center;">22<br> 615 </td> <td style="vertical-align: top;"><a name="PLOT2D_XZ"></a>PLOT2D_XZ </td> <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Binary<br> </td> <td style="vertical-align: top;"> <p>This file contains 1892 1893 1894 </td> 1895 1896 1897 </tr> 1898 1899 1900 <tr> 1901 1902 1903 <td style="vertical-align: top; text-align: center;">22<br> 1904 1905 1906 </td> 1907 1908 1909 <td style="vertical-align: top;"><a name="PLOT2D_XZ"></a>PLOT2D_XZ<br> 1910 1911 1912 (PLOT2D_XZ_O) </td> 1913 1914 1915 <td style="vertical-align: top;">O<br> 1916 1917 1918 </td> 1919 1920 1921 <td style="vertical-align: top;">Binary<br> 1922 1923 1924 </td> 1925 1926 1927 <td style="vertical-align: top;"> 1928 1929 <p>This file contains 616 1930 the data of the xz 617 1931 cross sections written by the model. </p> 1932 1933 618 1934 The description of the local file <a href="#PLOT2D_XY">PLOT2D_XY</a> 619 applies to this file, respectively </td> </tr> <tr> 620 <td style="vertical-align: top; text-align: center;">23<br> 621 </td> <td style="vertical-align: top;"><a name="PLOT2D_YZ"></a>PLOT2D_YZ </td> <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Binary<br> </td> <td style="vertical-align: top;"> <p>This file contains 1935 applies to this file, respectively </td> 1936 1937 1938 </tr> 1939 1940 1941 <tr> 1942 1943 1944 <td style="vertical-align: top; text-align: center;">23<br> 1945 1946 1947 </td> 1948 1949 1950 <td style="vertical-align: top;"><a name="PLOT2D_YZ"></a>PLOT2D_YZ<br> 1951 1952 1953 <font color="#000000">(PLOT2D_YZ_O)</font></td> 1954 1955 1956 <td style="vertical-align: top;">O<br> 1957 1958 1959 </td> 1960 1961 1962 <td style="vertical-align: top;">Binary<br> 1963 1964 1965 </td> 1966 1967 1968 <td style="vertical-align: top;"> 1969 1970 <p>This file contains 622 1971 the data of the xz 623 1972 cross sections written by the model. </p> 1973 1974 624 1975 The description of the local file <a href="#PLOT2D_XY">PLOT2D_XY</a> 625 applies to this file, respectively </td> </tr> <tr> 626 <td style="vertical-align: top; text-align: center;">27<br> 627 </td> <td style="vertical-align: top;"><a name="PLOT2D_XY_LOCAL"></a>PLOT2D_XY_LOCAL </td> 628 <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii/ NAMELIST<br> </td> 629 <td style="vertical-align: top;"> <p>NAMELIST - 1976 applies to this file, respectively </td> 1977 1978 1979 </tr> 1980 1981 1982 <tr> 1983 1984 1985 <td style="vertical-align: top; text-align: center;">27<br> 1986 1987 1988 </td> 1989 1990 1991 <td style="vertical-align: top;"><a name="PLOT2D_XY_LOCAL"></a>PLOT2D_XY_LOCAL<br> 1992 1993 1994 (PLOT2D_XY_LOCAL_O)</td> 1995 1996 1997 <td style="vertical-align: top;">O<br> 1998 1999 2000 </td> 2001 2002 2003 <td style="vertical-align: top;">Ascii/ NAMELIST<br> 2004 2005 2006 </td> 2007 2008 2009 <td style="vertical-align: top;"> 2010 2011 <p>NAMELIST - 630 2012 parameter sets, with which the plot layout of the 631 2013 data in the local file <a href="#PLOT2D_XY">PLOT2D_XY</a> … … 635 2017 field 636 2018 present at the file PLOT2D_XY). After the model run these parameter 637 sets can be edited by the user, if neccessary. </p> <p>Additionally 2019 sets can be edited by the user, if neccessary. </p> 2020 2021 2022 2023 <p>Additionally 638 2024 ISO2D still needs another so-called global 639 2025 parameter set. This is saved by the model to the local file <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>. … … 650 2036 (only then e.g. when the final value of the global ISO2D - parameter <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html#PLANZ">planz</a> 651 2037 is known), while the local parameter sets are written continuously 652 to the file PLOT2D_XY_LOCAL during the run.</p> </td> </tr> 653 <tr> <td style="vertical-align: top; text-align: center;">28<br> 654 </td> <td style="vertical-align: top;"><a name="PLOT2D_XZ_LOCAL"></a>PLOT2D_XZ_LOCAL </td> 655 <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii/ NAMELIST<br> </td> 656 <td style="vertical-align: top;"> <p>NAMELIST - 2038 to the file PLOT2D_XY_LOCAL during the run.</p> 2039 2040 2041 </td> 2042 2043 2044 </tr> 2045 2046 2047 <tr> 2048 2049 2050 <td style="vertical-align: top; text-align: center;">28<br> 2051 2052 2053 </td> 2054 2055 2056 <td style="vertical-align: top;"><a name="PLOT2D_XZ_LOCAL"></a>PLOT2D_XZ_LOCAL<br> 2057 2058 2059 <font color="#000000">(PLOT2D_XZ_LOCAL_O)</font> 2060 </td> 2061 2062 2063 <td style="vertical-align: top;">O<br> 2064 2065 2066 </td> 2067 2068 2069 <td style="vertical-align: top;">Ascii/ NAMELIST<br> 2070 2071 2072 </td> 2073 2074 2075 <td style="vertical-align: top;"> 2076 2077 <p>NAMELIST - 657 2078 parameter sets, with which the plot layout of the 658 2079 data in the local file <a href="#PLOT2D_XZ">PLOT2D_XZ</a> 659 2080 can be steered, if they are visualized with the plot program <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html">ISO2D</a>. 660 </p> <p>The description of the local file <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a> 661 applies to this file, respectively. </p> </td> </tr> 662 <tr> <td style="vertical-align: top; text-align: center;">29<br> 663 </td> <td style="vertical-align: top;"><a name="PLOT2D_YZ_LOCAL"></a>PLOT2D_YZ_LOCAL </td> 664 <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii/ NAMELIST<br> </td> 665 <td style="vertical-align: top;"> <p>NAMELIST - 2081 </p> 2082 2083 2084 2085 <p>The description of the local file <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a> 2086 applies to this file, respectively. </p> 2087 2088 2089 </td> 2090 2091 2092 </tr> 2093 2094 2095 <tr> 2096 2097 2098 <td style="vertical-align: top; text-align: center;">29<br> 2099 2100 2101 </td> 2102 2103 2104 <td style="vertical-align: top;"><a name="PLOT2D_YZ_LOCAL"></a>PLOT2D_YZ_LOCAL<br> 2105 2106 2107 <font color="#000000">(PLOT2D_YZ_LOCAL_O)</font></td> 2108 2109 2110 <td style="vertical-align: top;">O<br> 2111 2112 2113 </td> 2114 2115 2116 <td style="vertical-align: top;">Ascii/ NAMELIST<br> 2117 2118 2119 </td> 2120 2121 2122 <td style="vertical-align: top;"> 2123 2124 <p>NAMELIST - 666 2125 parameter sets, with which the plot layout of the 667 2126 data in the local file <a href="#PLOT2D_YZ">PLOT2D_YZ</a> 668 2127 can be steered, if they are visualized with the plot program <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html">ISO2D</a>. 669 </p> <p>The description of the local file <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a> 670 applies to this file, respectively. </p> </td> </tr> 671 <tr> <td style="vertical-align: top; text-align: center;">30<br> 672 </td> <td style="vertical-align: top;"><a name="PLOT3D_DATA"></a>PLOT3D_DATA </td> <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Binary<br> </td> <td style="vertical-align: top;"> <p>This file contains 2128 </p> 2129 2130 2131 2132 <p>The description of the local file <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a> 2133 applies to this file, respectively. </p> 2134 2135 2136 </td> 2137 2138 2139 </tr> 2140 2141 2142 <tr> 2143 2144 2145 <td style="vertical-align: top; text-align: center;">30<br> 2146 2147 2148 </td> 2149 2150 2151 <td style="vertical-align: top;"><a name="PLOT3D_DATA"></a>PLOT3D_DATA<br> 2152 2153 2154 (PLOT3D_DATA_O) </td> 2155 2156 2157 <td style="vertical-align: top;">O<br> 2158 2159 2160 </td> 2161 2162 2163 <td style="vertical-align: top;">Binary<br> 2164 2165 2166 </td> 2167 2168 2169 <td style="vertical-align: top;"> 2170 2171 <p>This file contains 673 2172 the data of the three-dimensional arrays 674 2173 (see <a href="chapter_4.2.html#data_output">data_output</a>) … … 685 2184 the file PLOT3D_FLD by the user after the end of the model run (e.g. 686 2185 with an appropriate OUTPUT - command in the MRUN - configuration file: "<span style="font-family: monospace;">cat PLOT3D_FLD_COOR 687 >> PLOT3D_FLD</span>"). </p> <p>With 2186 >> PLOT3D_FLD</span>"). </p> 2187 2188 2189 2190 <p>With 688 2191 parallel runs each processing element writes the data of 689 2192 its subdomain to a separate file with the name … … 701 2204 found). By the call of <tt><font style="font-size: 10pt;" size="2">combine_plot_fields.x</font></tt> 702 2205 also possibly existing files with two-dimensional plot data (see e.g. <a href="#PLOT2D_XY">PLOT2D_XY</a>) 703 are combined. </p> <p>With parallel runs the 2206 are combined. </p> 2207 2208 2209 2210 <p>With parallel runs the 704 2211 output of data of large volume is also 705 2212 possible in compressed form. For this purpose the initialization … … 714 2221 and a further entry in the MRUN-configuration file are needed. More 715 2222 details can be found in <a href="chapter_4.5.6.html">chapter 716 4.5.6</a>.</p> </td> </tr> <tr> <td style="vertical-align: top; text-align: center;">31<br> 717 </td> <td style="vertical-align: top;"><a name="PLOT3D_COOR"></a>PLOT3D_COOR </td> <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Binary<br> </td> <td style="vertical-align: top;"> <p>Coordinate 2223 4.5.6</a>.</p> 2224 2225 2226 </td> 2227 2228 2229 </tr> 2230 2231 2232 <tr> 2233 2234 2235 <td style="vertical-align: top; text-align: center;">31<br> 2236 2237 2238 </td> 2239 2240 2241 <td style="vertical-align: top;"><a name="PLOT3D_COOR"></a>PLOT3D_COOR </td> 2242 2243 2244 <td style="vertical-align: top;">O<br> 2245 2246 2247 </td> 2248 2249 2250 <td style="vertical-align: top;">Binary<br> 2251 2252 2253 </td> 2254 2255 2256 <td style="vertical-align: top;"> 2257 2258 <p>Coordinate 718 2259 information concerning 719 2260 the three-dimensional arrays (see <a href="#PLOT3D_DATA">PLOT3D_DATA</a>) 720 needed by the visualization software AVS. </p> <p>The 2261 needed by the visualization software AVS. </p> 2262 2263 2264 2265 <p>The 721 2266 file PLOT3D_COOR should be saved by the user into the same 722 permanent directory as the file PLOT3D_DATA. </p> <p>For 723 parallel runs PLOT3D_COOR is written by PE0 only.</p> </td> 724 </tr> <tr> <td style="vertical-align: top; text-align: center;">32<br> 725 </td> <td style="vertical-align: top;"><a name="PLOT3D_FLD"></a>PLOT3D_FLD </td> <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii/ <br> 726 AVS-Fld </td> <td style="vertical-align: top;"> <p>AVS-fld-file 2267 permanent directory as the file PLOT3D_DATA. </p> 2268 2269 2270 2271 <p>For 2272 parallel runs PLOT3D_COOR is written by PE0 only.</p> 2273 2274 2275 </td> 2276 2277 2278 </tr> 2279 2280 2281 <tr> 2282 2283 2284 <td style="vertical-align: top; text-align: center;">32<br> 2285 2286 2287 </td> 2288 2289 2290 <td style="vertical-align: top;"><a name="PLOT3D_FLD"></a>PLOT3D_FLD </td> 2291 2292 2293 <td style="vertical-align: top;">O<br> 2294 2295 2296 </td> 2297 2298 2299 <td style="vertical-align: top;">Ascii/ <br> 2300 2301 2302 AVS-Fld </td> 2303 2304 2305 <td style="vertical-align: top;"> 2306 2307 <p>AVS-fld-file 727 2308 describing the three-dimensional 728 2309 array data, saved by the model into the local file <a href="#PLOT3D_DATA">PLOT3D_DATA</a>, 729 needed by the visualization software AVS. </p> <p>This 2310 needed by the visualization software AVS. </p> 2311 2312 2313 2314 <p>This 730 2315 file describes the structure of the file PLOT3D_DATA 731 2316 (e.g. number of arrays, array dimensions, data type etc.). It uses the … … 745 2330 that AVS can find the file PLOT3D_DATA without any problems. If the two 746 2331 files lie in different directories, then the path name of the file 747 PLOT3D_DATA must be added. </p> <p>AVS-fld-files 2332 PLOT3D_DATA must be added. </p> 2333 2334 2335 2336 <p>AVS-fld-files 748 2337 are expected by AVS to have the 749 2338 suffix "<span style="font-family: monospace;">.fld</span>"<font face="Cumberland, monospace">.</font> … … 754 2343 if "<span style="font-family: monospace;">fld</span>" 755 2344 is indicated in the <a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#Spalte6">column 756 6 </a>of the file connection statement. </p> <p>Likewise, 2345 6 </a>of the file connection statement. </p> 2346 2347 2348 2349 <p>Likewise, 757 2350 AVS expects information about the coordinate 758 2351 system underlying the arrays on this file. This information is output … … 763 2356 MRUN-configuration file: “cat PLOT3D_FLD_COOR 764 2357 >> 765 PLOT3D_FLD”). </p> <p>For parallel 766 runs, PLOT3D_FLD is produced by PE0 only.</p> </td> </tr> 767 <tr> <td style="vertical-align: top; text-align: center;">33 768 </td> <td style="vertical-align: top;"><a name="PLOT3D_FLD_COOR"></a>PLOT3D_FLD_COOR </td> 769 <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii/ <br> 770 AVS-Fld </td> <td style="vertical-align: top;"> <p>File 2358 PLOT3D_FLD”). </p> 2359 2360 2361 2362 <p>For parallel 2363 runs, PLOT3D_FLD is produced by PE0 only.</p> 2364 2365 2366 </td> 2367 2368 2369 </tr> 2370 2371 2372 <tr> 2373 2374 2375 <td style="vertical-align: top; text-align: center;">33 2376 </td> 2377 2378 2379 <td style="vertical-align: top;"><a name="PLOT3D_FLD_COOR"></a>PLOT3D_FLD_COOR </td> 2380 2381 2382 <td style="vertical-align: top;">O<br> 2383 2384 2385 </td> 2386 2387 2388 <td style="vertical-align: top;">Ascii/ <br> 2389 2390 2391 AVS-Fld </td> 2392 2393 2394 <td style="vertical-align: top;"> 2395 2396 <p>File 771 2397 for the description of the coordinate information output 772 2398 by the model into the local file <a href="#PLOT3D_COOR">PLOT3D_COOR</a>, 773 2399 which is needed for the visualization of three-dimensional array data 774 by visualization-software AVS. </p> <p>This 2400 by visualization-software AVS. </p> 2401 2402 2403 2404 <p>This 775 2405 file describes the structure of the file PLOT3D_COOR 776 2406 (e.g. grid spacing, data type etc.) using the so-called AVS-Fld-format. … … 785 2415 registered as "unknown" in the file 786 2416 PLOT3D_FLD_COOR and the actual name 787 must be inserted later by hand. </p> <p>AVS 2417 must be inserted later by hand. </p> 2418 2419 2420 2421 <p>AVS 788 2422 expects the information contained in the file 789 2423 PLOT3D_FLD_COOR, as well as the remaining information about the … … 794 2428 MRUN-configuration file: “cat PLOT3D_FLD_COOR 795 2429 >> 796 PLOT3D_FLD”). </p> <p>For parallel 797 runs, PLOT3D_FLD_COOR is written by PE0 only.</p> </td> </tr> 798 <tr> <td style="vertical-align: top; text-align: center;"> 799 <p align="center">40 </p> <p align="center">and/or <br> 800 possibly </p> <p align="center">40-49</p> 801 </td> <td style="vertical-align: top;"> <p><a name="PLOT1D_DATA"></a>PLOT1D_DATA </p> 802 <p>and/or <br> 2430 PLOT3D_FLD”). </p> 2431 2432 2433 2434 <p>For parallel 2435 runs, PLOT3D_FLD_COOR is written by PE0 only.</p> 2436 2437 2438 </td> 2439 2440 2441 </tr> 2442 2443 2444 <tr> 2445 2446 2447 <td style="vertical-align: top; text-align: center;"> 2448 2449 <p align="center">40 </p> 2450 2451 2452 2453 <p align="center">and/or <br> 2454 2455 803 2456 possibly </p> 2457 2458 2459 2460 <p align="center">40-49</p> 2461 2462 2463 </td> 2464 2465 2466 <td style="vertical-align: top;"> 2467 2468 <p><a name="PLOT1D_DATA"></a>PLOT1D_DATA<br> 2469 2470 2471 (PLOT1D_DATA_O) </p> 2472 2473 2474 2475 <p>and/or <br> 2476 2477 2478 possibly </p> 2479 2480 804 2481 PLOT1D_DATA_0 <br> 805 PLOT1D_DATA_1 </td> <td style="vertical-align: top;">O </td> <td style="vertical-align: top;">Ascii </td> <td style="vertical-align: top;"> <p>This file contains 2482 2483 2484 PLOT1D_DATA_1<br> 2485 2486 2487 ...<br> 2488 2489 2490 <br> 2491 2492 2493 (PLOT1D_DATA<span style="font-weight: bold;">_O</span>_0 <br> 2494 2495 2496 <font color="#000000">PLOT1D_DATA<span style="font-weight: bold;">_O</span>_1 <br> 2497 2498 2499 </font><font color="#000000">...)<span style="font-weight: bold;"></span> </font></td> 2500 2501 2502 <td style="vertical-align: top;">O </td> 2503 2504 2505 <td style="vertical-align: top;">Ascii </td> 2506 2507 2508 <td style="vertical-align: top;"> 2509 2510 <p>This file contains 806 2511 data (possibly horizontally and/or 807 2512 temporally averaged) of the vertical profiles (see <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>) … … 818 2523 (<b>data_output_pr</b> = <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'v'</span>,… 819 2524 means that the file starts with the data of the u-component profile, 820 followed by the v-component profile, etc.). </p> <p><br> 2525 followed by the v-component profile, etc.). </p> 2526 2527 2528 2529 <p><br> 2530 2531 821 2532 The data can only be visualized with <span style="font-weight: bold;">profil</span> 822 2533 using NAMELIST-parameter sets, which are saved by the 823 2534 model into the local file <a href="#PLOT1D_PAR">PLOT1D_PAR</a>. 824 </p> <p>The profile data written to the file are described 2535 </p> 2536 2537 2538 2539 <p>The profile data written to the file are described 825 2540 with the 826 2541 run parameter <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>. … … 847 2562 to the file name (e.g. PLOT1D_DATA_1). The name of the file with the 848 2563 data of the total 849 domain in this case reads PLOT1D_DATA_0. </p> <p>For 2564 domain in this case reads PLOT1D_DATA_0. </p> 2565 2566 2567 2568 <p>For 850 2569 presentation in the same plot, profile data of the restart 851 2570 runs can be attached to existing data of preceding runs of a job chain. … … 857 2576 wrong plots (i.e. <span style="font-family: monospace;">use_prior_plot1d_parameters 858 2577 = .T.</span> and "<span style="font-family: monospace;">tra</span>" 859 must be specified together)! </p> <p>Further 2578 must be specified together)! </p> 2579 2580 2581 2582 <p>Further 860 2583 information about output of 861 2584 vertical profile data is given in the description of the run parameter <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>.</p> 862 </td> </tr> <tr> <td style="vertical-align: top; text-align: center;">80 </td> 863 <td style="vertical-align: top;"><a name="PARTICLE_INFOS"></a>PARTICLE_INFOS/ </td> 864 <td style="vertical-align: top;">O </td> <td style="vertical-align: top;">Ascii </td> <td style="vertical-align: top;">This 2585 2586 2587 </td> 2588 2589 2590 </tr> 2591 2592 2593 <tr> 2594 2595 2596 <td style="vertical-align: top; text-align: center;">80 2597 </td> 2598 2599 2600 <td style="vertical-align: top;"><a name="PARTICLE_INFOS"></a>PARTICLE_INFOS/<br> 2601 2602 2603 (PARTICLE_INFOS<span style="font-weight: bold;">_O</span>/) 2604 </td> 2605 2606 2607 <td style="vertical-align: top;">O </td> 2608 2609 2610 <td style="vertical-align: top;">Ascii </td> 2611 2612 2613 <td style="vertical-align: top;">This 865 2614 file is created in case of particle transport (see the <a href="chapter_4.2.html#particles_package">particles 866 2615 package</a>). It contains statistical informations about the … … 869 2618 single PE. These informations are output after every timestep if 870 2619 switched on by parameter <a href="chapter_4.2.html#write_particle_statistics">write_particle_statistics</a>. 871 </td> </tr> <tr> <td style="vertical-align: top; text-align: center;">81 </td> 872 <td style="vertical-align: top;"><a name="PLOTSP_X_PAR"></a>PLOTSP_X_PAR 873 </td> <td style="vertical-align: top;">O </td> 874 <td style="vertical-align: top;">Ascii/<br> 875 NAMELIST </td> <td style="vertical-align: top;">This 2620 </td> 2621 2622 2623 </tr> 2624 2625 2626 <tr> 2627 2628 2629 <td style="vertical-align: top; text-align: center;">81 2630 </td> 2631 2632 2633 <td style="vertical-align: top;"><a name="PLOTSP_X_PAR"></a>PLOTSP_X_PAR<br> 2634 2635 2636 (PLOTSP_X_PAR_O)</td> 2637 2638 2639 <td style="vertical-align: top;">O </td> 2640 2641 2642 <td style="vertical-align: top;">Ascii/<br> 2643 2644 2645 NAMELIST </td> 2646 2647 2648 <td style="vertical-align: top;">This 876 2649 file is created if spectra along x are calculated and output (see the <a href="chapter_4.2.html#particles_package">spectra 877 2650 package</a>). It contains the NAMELIST parameter set, with which … … 880 2653 of the data in the local file <a href="#PLOTSP_X_DATA">PLOTSP_X_DATA</a> 881 2654 can be steered, if these data are plotted with the plot software <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>.<br> 882 <p>It contains the so-called RAHMEN (frame)- and 2655 2656 2657 2658 <p>It contains the so-called RAHMEN (frame)- and 883 2659 CROSS-parameter sets (NAMELIST- group names <span style="font-style: normal;">&RAHMEN and/or 884 2660 &CROSS</span>) 885 2661 needed by <span style="font-weight: bold;">profil</span>. 886 2662 The user can edit these parameter sets (and thus all details of the 887 plot layout) after the run.<br> </p> <p>By default, 2663 plot layout) after the run.<br> 2664 2665 2666 </p> 2667 2668 2669 2670 <p>By default, 888 2671 for one quantity, all spectra at different heights 889 2672 are plotted into a single panel. Different colors and line styles are … … 892 2675 additional page(s). If there is more than one output time (see <a href="chapter_4.2.html#dt_dosp">dt_dosp</a>), 893 2676 additional pages will be plotted for each single output time. </p> 894 </td> </tr> <tr> <td style="vertical-align: top; text-align: center;">82<br> 895 </td> <td style="vertical-align: top;"><a name="PLOTSP_X_DATA"></a>PLOTSP_X_DATA </td> <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii<br> </td> <td style="vertical-align: top;">This 2677 2678 2679 </td> 2680 2681 2682 </tr> 2683 2684 2685 <tr> 2686 2687 2688 <td style="vertical-align: top; text-align: center;">82<br> 2689 2690 2691 </td> 2692 2693 2694 <td style="vertical-align: top;"><a name="PLOTSP_X_DATA"></a>PLOTSP_X_DATA<br> 2695 2696 2697 (PLOTSP_X_DATA_O) </td> 2698 2699 2700 <td style="vertical-align: top;">O<br> 2701 2702 2703 </td> 2704 2705 2706 <td style="vertical-align: top;">Ascii<br> 2707 2708 2709 </td> 2710 2711 2712 <td style="vertical-align: top;">This 896 2713 file is created if spectra along x are calculated and output (see the <a href="chapter_4.2.html#particles_package">spectra 897 2714 package</a>). It contains the spectral data along x (see <a href="chapter_4.2.html#data_output_sp">data_output_sp</a>) … … 900 2717 using NAMELIST parameter sets, which are written by 901 2718 the model to the local file <a href="#PLOTSP_X_PAR">PLOTSP_X_PAR</a>.<br> 902 <br> 2719 2720 2721 <br> 2722 2723 903 2724 Regardless of the (sub)set of spectra specified by <a href="chapter_4.2.html#plot_spectra_level">plot_spectra_level</a> 904 2725 for actual plotting, this file contains all data of spectra specified 905 2726 by <a href="chapter_4.2.html#comp_spectra_level">comp_spectra_level</a>.<br> 906 <br> <font>Each data point of a spectrum is output in a 2727 2728 2729 <br> 2730 2731 2732 <font>Each data point of a spectrum is output in a 907 2733 single line 908 2734 (1st column: … … 912 2738 subsequent columns. </font>The order 913 2739 of the data in the file follows the order used in the assignment for <span style="font-style: italic;"></span><span style="font-style: italic;"></span><a href="chapter_4.2.html#data_output_sp">data_output_sp</a>.<br> 914 <br> 2740 2741 2742 <br> 2743 2744 915 2745 For orientation, a header of comment lines (one for each height level) 916 2746 is placed in front of the spectral data of each quantity. They indicate 917 2747 the respective quantity and the output time. The text of these comment 918 lines is used as a legend in the plot. </td> </tr> <tr> 919 <td style="vertical-align: top; text-align: center;">83<br> 920 </td> <td style="vertical-align: top;"><a name="PLOTSP_Y_PAR"></a>PLOTSP_Y_PAR </td> <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii<br> </td> <td style="vertical-align: top;">This 2748 lines is used as a legend in the plot. </td> 2749 2750 2751 </tr> 2752 2753 2754 <tr> 2755 2756 2757 <td style="vertical-align: top; text-align: center;">83<br> 2758 2759 2760 </td> 2761 2762 2763 <td style="vertical-align: top;"><a name="PLOTSP_Y_PAR"></a>PLOTSP_Y_PAR<br> 2764 2765 2766 (PLOTSP_Y_PAR_O)</td> 2767 2768 2769 <td style="vertical-align: top;">O<br> 2770 2771 2772 </td> 2773 2774 2775 <td style="vertical-align: top;">Ascii<br> 2776 2777 2778 </td> 2779 2780 2781 <td style="vertical-align: top;">This 921 2782 file is created if spectra along y are calculated and output (see the <a href="chapter_4.2.html#particles_package">spectra 922 2783 package</a>). It contains the NAMELIST parameter set, with which … … 925 2786 of the data in the local file <a href="#PLOTSP_Y_DATA">PLOTSP_Y_DATA</a> 926 2787 can be steered, if these data are plotted with the plot software <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>.<br> 927 <br> 2788 2789 2790 <br> 2791 2792 928 2793 For more details see <a href="#PLOTSP_X_PAR">PLOTSP_X_PAR</a>.<br> 929 </td> </tr> <tr> <td style="vertical-align: top; text-align: center;">84<br> 930 </td> <td style="vertical-align: top;"><a name="PLOTSP_Y_DATA"></a>PLOTSP_Y_DATA</td> <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii<br> </td> <td style="vertical-align: top;">This 2794 2795 2796 </td> 2797 2798 2799 </tr> 2800 2801 2802 <tr> 2803 2804 2805 <td style="vertical-align: top; text-align: center;">84<br> 2806 2807 2808 </td> 2809 2810 2811 <td style="vertical-align: top;"><a name="PLOTSP_Y_DATA"></a>PLOTSP_Y_DATA<br> 2812 2813 2814 (PLOTSP_Y_DATA_O)</td> 2815 2816 2817 <td style="vertical-align: top;">O<br> 2818 2819 2820 </td> 2821 2822 2823 <td style="vertical-align: top;">Ascii<br> 2824 2825 2826 </td> 2827 2828 2829 <td style="vertical-align: top;">This 931 2830 file is created if spectra along x are calculated and output (see the <a href="chapter_4.2.html#particles_package">spectra 932 2831 package</a>). It contains the spectral data along y (see <a href="chapter_4.2.html#data_output_sp">data_output_sp</a>) … … 935 2834 using NAMELIST parameter sets, which are written by 936 2835 the model to the local file <a href="#PLOTSP_Y_PAR">PLOTSP_Y_PAR</a>.<br> 937 <br> 2836 2837 2838 <br> 2839 2840 938 2841 For more details see <a href="#PLOTSP_X_DATA">PLOTSP_X_DATA</a>.</td> 939 </tr> <tr> <td style="vertical-align: top; text-align: center;">85<br> 940 </td> <td style="vertical-align: top;"><a name="PARTICLE_DATA"></a>PARTICLE_DATA/</td> <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Binary<br> </td> <td style="vertical-align: top;">This 2842 2843 2844 </tr> 2845 2846 2847 <tr> 2848 2849 2850 <td style="vertical-align: top; text-align: center;">85<br> 2851 2852 2853 </td> 2854 2855 2856 <td style="vertical-align: top;"><a name="PARTICLE_DATA"></a>PARTICLE_DATA/<br> 2857 2858 2859 (PARTICLE_DATA<span style="font-weight: bold;">_O</span>/)</td> 2860 2861 2862 <td style="vertical-align: top;">O<br> 2863 2864 2865 </td> 2866 2867 2868 <td style="vertical-align: top;">Binary<br> 2869 2870 2871 </td> 2872 2873 2874 <td style="vertical-align: top;">This 941 2875 file is created if particle transport is switched on (see the <a href="chapter_4.2.html#particles_package">particles 942 2876 package</a>) and contains all particle data for one or several 943 2877 output 944 2878 times (see <a href="chapter_4.2.html#dt_write_particle_data">dt_write_particle_data</a>).<br> 945 <br> 2879 2880 2881 <br> 2882 2883 946 2884 The first record of this file contains an identification string (PALM 947 2885 version number, run identifier, etc., 80 characters long). The second … … 953 2891 the actual particle data. A FORTRAN TYPE structure is used for storing 954 2892 the particle attributes. See file <span style="font-family: monospace;">advec_particles.f90</span> 955 for the detailed format.</td> </tr> <tr> <td style="vertical-align: top; text-align: center;">90</td> 956 <td style="vertical-align: top;"><a name="PARTICLE_RESTART_DATA_IN"></a>PARTICLE_RESTART_<br> 957 DATA_IN/</td> <td style="vertical-align: top;">I<br> 958 </td> <td style="vertical-align: top;">Binary<br> 959 </td> <td style="vertical-align: top;">Binary 2893 for the detailed format.</td> 2894 2895 2896 </tr> 2897 2898 2899 <tr> 2900 2901 2902 <td style="vertical-align: top; text-align: center;">90</td> 2903 2904 2905 <td style="vertical-align: top;"><a name="PARTICLE_RESTART_DATA_IN"></a>PARTICLE_RESTART_<br> 2906 2907 2908 DATA_IN/</td> 2909 2910 2911 <td style="vertical-align: top;">I<br> 2912 2913 2914 </td> 2915 2916 2917 <td style="vertical-align: top;">Binary<br> 2918 2919 2920 </td> 2921 2922 2923 <td style="vertical-align: top;">Binary 960 2924 data, which are read in by the model at the beginning 961 2925 of a restart run (see <a href="chapter_3.3.html">chapter … … 971 2935 The 972 2936 number of processors which can be used must not be changed during a job 973 chain and/or if a job chain is continued. <br> <br> 2937 chain and/or if a job chain is continued. <br> 2938 2939 2940 <br> 2941 2942 974 2943 The first record of this file contains a version number (four character 975 2944 string) of the subroutine, which output the data that follows (<span style="font-family: monospace;">write_particles</span>, … … 992 2961 attributes. For detailed informations about the file format see the 993 2962 corresponding READ statements in file <span style="font-family: monospace;">init_particles.f90</span> 994 .<br> </td> </tr> <tr> <td style="vertical-align: top; text-align: center;">90<br> 995 </td> <td style="vertical-align: top;"><a name="PARTICLE_RESTART_DATA_IN"></a>PARTICLE_RESTART_<br> 996 DATA_OUT/</td> <td style="vertical-align: top;">O<br> 997 </td> <td style="vertical-align: top;">Binary<br> 998 </td> <td style="vertical-align: top;">Binary 2963 .<br> 2964 2965 2966 </td> 2967 2968 2969 </tr> 2970 2971 2972 <tr> 2973 2974 2975 <td style="vertical-align: top; text-align: center;">90<br> 2976 2977 2978 </td> 2979 2980 2981 <td style="vertical-align: top;"><a name="PARTICLE_RESTART_DATA_IN"></a>PARTICLE_RESTART_<br> 2982 2983 2984 DATA_OUT/</td> 2985 2986 2987 <td style="vertical-align: top;">O<br> 2988 2989 2990 </td> 2991 2992 2993 <td style="vertical-align: top;">Binary<br> 2994 2995 2996 </td> 2997 2998 2999 <td style="vertical-align: top;">Binary 999 3000 data, which are output at the end of the 1000 3001 run and possibly needed by restart runs (see <a href="chapter_3.3.html">chapter … … 1004 3005 package</a>). For a more detailed description of the file 1005 3006 structure see <a href="#PARTICLE_RESTART_DATA_IN">PARTICLE_RESTART_DATA_IN</a>.</td> 1006 </tr> <tr> <td style="vertical-align: top; text-align: center;">90<br> 1007 </td> <td style="vertical-align: top;"> <p><a name="PLOT1D_PAR"></a>PLOT1D_PAR </p> 1008 <p>and/or <br> 1009 possibly </p> <p>PLOT1D_PAR_0 <br> 3007 3008 3009 </tr> 3010 3011 3012 <tr> 3013 3014 3015 <td style="vertical-align: top; text-align: center;">90<br> 3016 3017 3018 </td> 3019 3020 3021 <td style="vertical-align: top;"> 3022 3023 <p><a name="PLOT1D_PAR"></a>PLOT1D_PAR<br> 3024 3025 3026 (PLOT1D_PAR_O) </p> 3027 3028 3029 3030 <p>and/or <br> 3031 3032 3033 possibly </p> 3034 3035 3036 3037 <p>PLOT1D_PAR_0 <br> 3038 3039 1010 3040 PLOT1D_PAR_1 <br> 3041 3042 1011 3043 1012 3044 . <br> 3045 3046 1013 3047 1014 3048 . <br> 3049 3050 1015 3051 1016 3052 . <br> 1017 PLOT1D_PAR_9</p> </td> <td style="vertical-align: top;">O<br> 1018 </td> <td style="vertical-align: top;">Ascii/ 1019 NAMELIST<br> </td> <td style="vertical-align: top;"> 1020 <p>NAMELIST parameter set, with which the layout of a plot 3053 3054 3055 PLOT1D_PAR_9</p> 3056 3057 3058 3059 <p></p> 3060 3061 3062 3063 <p>(PLOT1D_PAR<span style="font-weight: bold;">_O</span>_0 3064 <br> 3065 3066 3067 PLOT1D_PAR<font color="#000000"><span style="font-weight: bold;">_O</span></font>_1 3068 <br> 3069 3070 3071 3072 . <br> 3073 3074 3075 3076 . <br> 3077 3078 3079 3080 . <br> 3081 3082 3083 PLOT1D_PAR<font color="#000000"><span style="font-weight: bold;">_O</span></font>_9)</p> 3084 3085 3086 </td> 3087 3088 3089 <td style="vertical-align: top;">O<br> 3090 3091 3092 </td> 3093 3094 3095 <td style="vertical-align: top;">Ascii/ 3096 NAMELIST<br> 3097 3098 3099 </td> 3100 3101 3102 <td style="vertical-align: top;"> 3103 3104 <p>NAMELIST parameter set, with which the layout of a plot 1021 3105 of the data in the local file <a href="#PLOT1D_DATA">PLOT1D_DATA</a> 1022 3106 can be steered, if these data are visualized with the plot program <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>. 1023 </p> <p>This file contains the so-called RAHMEN (frame)- 3107 </p> 3108 3109 3110 3111 <p>This file contains the so-called RAHMEN (frame)- 1024 3112 and 1025 3113 CROSS-parameter sets (NAMELIST- group names <span style="font-style: normal;">&RAHMEN and/or … … 1032 3120 into which plane and how these planes are arranged on the 1033 3121 plot, is determined with the parameters <a href="chapter_4.2.html#cross_profiles">cross_profiles</a>, 1034 <a href="chapter_4.2.html#profile_columns">profile_columns</a>3122 <a href="chapter_4.2.html#profile_columns">profile_columns</a> 1035 3123 and <a href="chapter_4.2.html#profile_rows">profile_rows</a>. 1036 </p> <p>The file PLOT1D_PAR is created by the model 3124 </p> 3125 3126 3127 3128 <p>The file PLOT1D_PAR is created by the model 1037 3129 briefly before 1038 3130 the end of a run. If a model run crashes uncontrolled (run time 1039 3131 errors or CPU - time exceeded), this file is usually missing, although 1040 profile data were saved to the file PLOT1D_DATA. </p> <p>If 3132 profile data were saved to the file PLOT1D_DATA. </p> 3133 3134 3135 3136 <p>If 1041 3137 the model has to create profiles for different subdomains 1042 3138 (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>), … … 1044 3140 the respective subdomain (e.g. PLOT1D_PAR_1). In this case the name of 1045 3141 the file with NAMELIST parameters of the total domain is 1046 PLOT1D_PAR_0. </p> <p>For presentation in the 3142 PLOT1D_PAR_0. </p> 3143 3144 3145 3146 <p>For presentation in the 1047 3147 same plot, profile data of the restart 1048 3148 runs can be appended to existing data of preceding runs of a job chain. … … 1055 3155 wrong plots (i.e. <span style="font-family: monospace;">use_prior_plot1d_parameters 1056 3156 = .T.</span> and "<span style="font-family: monospace;">tra</span>" 1057 must be specified together)!</p> </td> </tr> <tr> 1058 <td style="vertical-align: top; text-align: center;">90<br> 1059 </td> <td style="vertical-align: top;"><a name="PLOT2D_XY_GLOBAL"></a>PLOT2D_XY_GLOBAL</td> 1060 <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii/ <br> 1061 NAMELIST</td> <td style="vertical-align: top;"> <p>NAMELIST 3157 must be specified together)!</p> 3158 3159 3160 </td> 3161 3162 3163 </tr> 3164 3165 3166 <tr> 3167 3168 3169 <td style="vertical-align: top; text-align: center;">90<br> 3170 3171 3172 </td> 3173 3174 3175 <td style="vertical-align: top;"><a name="PLOT2D_XY_GLOBAL"></a>PLOT2D_XY_GLOBAL<br> 3176 3177 3178 (PLOT2D_XY_GLOBAL_O)</td> 3179 3180 3181 <td style="vertical-align: top;">O<br> 3182 3183 3184 </td> 3185 3186 3187 <td style="vertical-align: top;">Ascii/ <br> 3188 3189 3190 NAMELIST</td> 3191 3192 3193 <td style="vertical-align: top;"> 3194 3195 <p>NAMELIST 1062 3196 parameter set, with which the plot layout 1063 3197 of the data in local file <a href="#PLOT2D_XY">PLOT2D_XY</a> … … 1070 3204 will be drawn onto a separate page (thus no color shading 1071 3205 presentation, no vector arrows, streamlines etc.). </p> 1072 <p>Additionally <span style="font-weight: bold;">iso2d</span> 3206 3207 3208 3209 <p>Additionally <span style="font-weight: bold;">iso2d</span> 1073 3210 needs the so-called local parameter 1074 3211 sets. These are saved by the model to the local file <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>. … … 1089 3226 to the file PLOT2D_XY_LOCAL during the run. Since the file 1090 3227 PLOT2D_XY_GLOBAL needs to be addressed only briefly once, output-unit 1091 90 is used, which is also used for other files.</p> </td> </tr> 1092 <tr> <td style="vertical-align: top; text-align: center;">90<br> 1093 </td> <td style="vertical-align: top;"><a name="PLOT2D_XZ_GLOBAL"></a>PLOT2D_XZ_GLOBAL</td> 1094 <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii/ <br> 1095 NAMELIST</td> <td style="vertical-align: top;"> <p>NAMELIST 3228 90 is used, which is also used for other files.</p> 3229 3230 3231 </td> 3232 3233 3234 </tr> 3235 3236 3237 <tr> 3238 3239 3240 <td style="vertical-align: top; text-align: center;">90<br> 3241 3242 3243 </td> 3244 3245 3246 <td style="vertical-align: top;"><a name="PLOT2D_XZ_GLOBAL"></a>PLOT2D_XZ_GLOBAL<br> 3247 3248 3249 (PLOT2D_XZ_GLOBAL_O)</td> 3250 3251 3252 <td style="vertical-align: top;">O<br> 3253 3254 3255 </td> 3256 3257 3258 <td style="vertical-align: top;">Ascii/ <br> 3259 3260 3261 NAMELIST</td> 3262 3263 3264 <td style="vertical-align: top;"> 3265 3266 <p>NAMELIST 1096 3267 parameter set, with which the plot layout of the data 1097 3268 in the local file <a href="#PLOT2D_XZ">PLOT2D_XZ</a> 1098 3269 can be steered, if they are visualized with the plot program <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html">iso2d</a>. 1099 </p> <p>The description of the local file <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a> 1100 applies to this file, respectively.</p> </td> </tr> 1101 <tr> <td style="vertical-align: top; text-align: center;">90<br> 1102 </td> <td style="vertical-align: top;"><a name="PLOT2D_YZ_GLOBAL"></a>PLOT2D_YZ_GLOBAL</td> 1103 <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii/ <br> 1104 NAMELIST</td> <td style="vertical-align: top;"> <p>NAMELIST 3270 </p> 3271 3272 3273 3274 <p>The description of the local file <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a> 3275 applies to this file, respectively.</p> 3276 3277 3278 </td> 3279 3280 3281 </tr> 3282 3283 3284 <tr> 3285 3286 3287 <td style="vertical-align: top; text-align: center;">90<br> 3288 3289 3290 </td> 3291 3292 3293 <td style="vertical-align: top;"><a name="PLOT2D_YZ_GLOBAL"></a>PLOT2D_YZ_GLOBAL<br> 3294 3295 3296 (PLOT2D_YZ_GLOBAL_O)</td> 3297 3298 3299 <td style="vertical-align: top;">O<br> 3300 3301 3302 </td> 3303 3304 3305 <td style="vertical-align: top;">Ascii/ <br> 3306 3307 3308 NAMELIST</td> 3309 3310 3311 <td style="vertical-align: top;"> 3312 3313 <p>NAMELIST 1105 3314 parameter set, with which the plot layout of the data 1106 3315 in the local file <a href="#PLOT2D_YZ">PLOT2D_YZ</a> 1107 3316 can be steered, if they are visualized with the plot program <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html">iso2d</a>. 1108 </p> <p>The description of the local file <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a> 1109 applies to this file, respectively.</p> </td> </tr> 1110 <tr> <td style="vertical-align: top; text-align: center;">90</td> 1111 <td style="vertical-align: top;"><a name="TOPOGRAPHY_DATA"></a>TOPOGRAPHY_DATA</td> <td style="vertical-align: top;">I</td> <td style="vertical-align: top;">Ascii</td> <td>Two-dimensional <font color="#000000">topography height information</font> 3317 </p> 3318 3319 3320 3321 <p>The description of the local file <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a> 3322 applies to this file, respectively.</p> 3323 3324 3325 </td> 3326 3327 3328 </tr> 3329 3330 3331 <tr> 3332 3333 3334 <td style="vertical-align: top; text-align: center;">90</td> 3335 3336 3337 <td style="vertical-align: top;"><a name="TOPOGRAPHY_DATA"></a>TOPOGRAPHY_DATA</td> 3338 3339 3340 <td style="vertical-align: top;">I</td> 3341 3342 3343 <td style="vertical-align: top;">Ascii</td> 3344 3345 3346 <td>Two-dimensional <font color="#000000">topography 3347 height information</font> 1112 3348 in m.<br> 3349 3350 1113 3351 In case of <a href="chapter_4.1.html#topography">topography</a> 1114 3352 = <span style="font-style: italic;">'read_from_file'</span> … … 1117 3355 a free floating point format. The data on file are laid out naturally, 1118 3356 i.e. in W-E orientation horizontally and in S-N orientation vertically, 1119 they must thus be organized as follows:<br> <ul> <li>each 3357 they must thus be organized as follows:<br> 3358 3359 3360 3361 <ul> 3362 3363 3364 <li>each 1120 3365 line contains height information in m from <span style="font-style: italic;">i = 0, ..., nx</span>,</li> 1121 <li>the top line contains height information in m for <span style="font-style: italic;">j = ny</span> (North), the 3366 3367 3368 <li>the top line contains height information in m for <span style="font-style: italic;">j = ny</span> (North), the 1122 3369 bottom line for <span style="font-style: italic;">j = 0</span> 1123 (South),</li> <li>individual data must be separated by at 1124 least one blank.</li> </ul> 1125 Layout sketch:<br> <span style="font-family: Cumberland AMT;"> 3370 (South),</li> 3371 3372 3373 <li>individual data must be separated by at 3374 least one blank.</li> 3375 3376 3377 3378 </ul> 3379 3380 3381 Layout sketch:<br> 3382 3383 3384 <span style="font-family: Cumberland AMT;"> 1126 3385 1127 3386 N<br> 3387 3388 1128 3389 (0,ny) </span><font color="#000000"><span style="font-family: Cumberland AMT;">(1,ny) 1129 3390 </span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(2,ny) 1130 3391 ... </span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(nx,ny) 1131 3392 <span style="font-family: Times New Roman,Times,serif;"></span></span></font><font color="#000000"> top of file</font><font color="#000000"><span style="font-family: Cumberland AMT;"><span style="font-family: Times New Roman,Times,serif;"></span></span></font><br> 1132 <font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;"> 3393 3394 3395 <font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;"> 1133 3396 (0,ny-1) </span><font color="#000000"><span style="font-family: Cumberland AMT;">(1,ny-1) </span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(2,ny-1) 1134 3397 ... </span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(nx,ny-1) <br> 1135 </span></font></font><font color="#000000"><span style="font-family: Cumberland AMT;"></span></font></font><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">W 3398 3399 3400 </span></font></font><font color="#000000"><span style="font-family: Cumberland AMT;"></span></font></font><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">W 1136 3401 (0,ny-2) </span><font color="#000000"><span style="font-family: Cumberland AMT;">(1,ny-2) </span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(2,ny-2) 1137 3402 ... </span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(nx,ny-2) E<br> 1138 </span></font></font></font><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;"> 3403 3404 3405 </span></font></font></font><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;"> 1139 3406 1140 3407 :<br> 3408 3409 1141 3410 1142 3411 1143 :<br> </span></font></font><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;"> 3412 :<br> 3413 3414 3415 </span></font></font><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;"> 3416 1144 3417 (0,0) </span><font color="#000000"><span style="font-family: Cumberland AMT;">(1,0) 1145 3418 </span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(2,0) 1146 3419 ... </span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(nx,0) 1147 3420 </span></font></font></font><font color="#000000"> bottom of file</font><br> 1148 <font color="#000000"><span style="font-family: Cumberland AMT;"> 3421 3422 3423 <font color="#000000"><span style="font-family: Cumberland AMT;"> 1149 3424 1150 3425 S</span></font><br> 1151 <span style="font-family: Arial;"></span><br> 3426 3427 3428 <span style="font-family: Arial;"></span><br> 3429 3430 1152 3431 These data must exactly match the horizontal grid.<br> 3432 3433 1153 3434 Alternatively, the user may add code to the user interface subroutine <a href="chapter_3.5.1.html#user_init_grid">user_init_grid</a> 1154 to allow different data formats.</td> <td><br> </td> 1155 </tr> <tr> <td style="vertical-align: top; text-align: center;"><font color="#000000">101</font></td> <td style="vertical-align: top;"><font color="#000000"><a name="DATA_2D_XY_NETCDF"></a>DATA_2D_XY_NETCDF</font></td> 1156 <td style="vertical-align: top;"><font color="#000000">I/O</font></td> 1157 <td style="vertical-align: top;"><font color="#000000">Binary/<br> 3435 to allow different data formats.</td> 3436 3437 3438 <td><br> 3439 3440 3441 </td> 3442 3443 3444 </tr> 3445 3446 3447 <tr> 3448 3449 3450 <td style="vertical-align: top; text-align: center;"><font color="#000000">101</font></td> 3451 3452 3453 <td style="vertical-align: top;"><font color="#000000"><a name="DATA_2D_XY_NETCDF"></a>DATA_2D_XY_NETCDF<br> 3454 3455 3456 (DATA_2D_XY_NETCDF_O)</font></td> 3457 3458 3459 <td style="vertical-align: top;"><font color="#000000">I/O</font></td> 3460 3461 3462 <td style="vertical-align: top;"><font color="#000000">Binary/<br> 3463 3464 1158 3465 NetCDF-<br> 1159 format</font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000">This file 3466 3467 3468 format</font></td> 3469 3470 3471 <td style="vertical-align: top;"><font color="#000000"><font color="#000000">This file 1160 3472 contains data of the two-dimensional horizontal 1161 3473 cross sections (see <a href="../app/chapter_4.2.html#data_output">data_output</a>) 1162 3474 in NetCDF format. The data in this file can be visualized by any 1163 graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> <br> 3475 graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> 3476 3477 3478 <br> 3479 3480 1164 3481 More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter 4.5.1</a>.</font></font></td> 1165 <td style="vertical-align: top;"><br> </td> </tr> 1166 <tr> <td style="vertical-align: top; text-align: center;"><font color="#000000">102</font></td> <td style="vertical-align: top;"><font color="#000000"><a name="DATA_2D_XZ_NETCDF"></a>DATA_2D_XZ_NETCDF</font></td> 1167 <td style="vertical-align: top;"><font color="#000000">I/O</font></td> 1168 <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br> 3482 3483 3484 <td style="vertical-align: top;"><br> 3485 3486 3487 </td> 3488 3489 3490 </tr> 3491 3492 3493 <tr> 3494 3495 3496 <td style="vertical-align: top; text-align: center;"><font color="#000000">102</font></td> 3497 3498 3499 <td style="vertical-align: top;"><font color="#000000"><a name="DATA_2D_XZ_NETCDF"></a>DATA_2D_XZ_NETCDF<br> 3500 3501 3502 (DATA_2D_XZ_NETCDF_O)</font></td> 3503 3504 3505 <td style="vertical-align: top;"><font color="#000000">I/O</font></td> 3506 3507 3508 <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br> 3509 3510 1169 3511 NetCDF-<br> 1170 format</font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file 3512 3513 3514 format</font></font></td> 3515 3516 3517 <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file 1171 3518 contains data of the two-dimensional vertical (xz) 1172 3519 cross sections (see <a href="../app/chapter_4.2.html#data_output">data_output</a>) 1173 3520 in NetCDF format. The data in this file can be visualized by any 1174 graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> <br> 3521 graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> 3522 3523 3524 <br> 3525 3526 1175 3527 More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter 4.5.1</a>.</font></font></font></td> 1176 <td style="vertical-align: top;"><br> </td> </tr> 1177 <tr> <td style="vertical-align: top; text-align: center;"><font color="#000000">103</font></td> <td style="vertical-align: top;"><font color="#000000"><a name="DATA_2D_YZ_NETCDF"></a>DATA_2D_YZ_NETCDF</font></td> 1178 <td style="vertical-align: top;"><font color="#000000">I/O</font></td> 1179 <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br> 3528 3529 3530 <td style="vertical-align: top;"><br> 3531 3532 3533 </td> 3534 3535 3536 </tr> 3537 3538 3539 <tr> 3540 3541 3542 <td style="vertical-align: top; text-align: center;"><font color="#000000">103</font></td> 3543 3544 3545 <td style="vertical-align: top;"><font color="#000000"><a name="DATA_2D_YZ_NETCDF"></a>DATA_2D_YZ_NETCDF<br> 3546 3547 3548 (DATA_2D_YZ_NETCDF_O)</font></td> 3549 3550 3551 <td style="vertical-align: top;"><font color="#000000">I/O</font></td> 3552 3553 3554 <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br> 3555 3556 1180 3557 NetCDF-<br> 1181 format</font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file 3558 3559 3560 format</font></font></td> 3561 3562 3563 <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file 1182 3564 contains data of the two-dimensional vertical 1183 3565 (yz) cross sections (see <a href="../app/chapter_4.2.html#data_output">data_output</a>) 1184 3566 in NetCDF format. The data in this file can be visualized by any 1185 graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> <br> 3567 graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> 3568 3569 3570 <br> 3571 3572 1186 3573 More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter 4.5.1</a>.</font></font></font></td> 1187 <td style="vertical-align: top;"><br> </td> </tr> 1188 <tr> <td style="vertical-align: top; text-align: center;"><font color="#000000">104</font></td> <td style="vertical-align: top;"><font color="#000000"><a name="DATA_1D_PR_NETCDF"></a>DATA_1D_PR_NETCDF</font></td> 1189 <td style="vertical-align: top;"><font color="#000000">I/O</font></td> 1190 <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br> 3574 3575 3576 <td style="vertical-align: top;"><br> 3577 3578 3579 </td> 3580 3581 3582 </tr> 3583 3584 3585 <tr> 3586 3587 3588 <td style="vertical-align: top; text-align: center;"><font color="#000000">104</font></td> 3589 3590 3591 <td style="vertical-align: top;"><font color="#000000"><a name="DATA_1D_PR_NETCDF"></a>DATA_1D_PR_NETCDF<br> 3592 3593 3594 (DATA_1D_PR_NETCFD_O)</font></td> 3595 3596 3597 <td style="vertical-align: top;"><font color="#000000">I/O</font></td> 3598 3599 3600 <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br> 3601 3602 1191 3603 NetCDF-<br> 1192 format</font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file 3604 3605 3606 format</font></font></td> 3607 3608 3609 <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file 1193 3610 contains data of the horizontally averaged vertical profiles (see <a href="../app/chapter_4.2.html#data_output_pr">data_output_pr</a>) 1194 3611 in NetCDF format. The data in this file can be visualized by any 1195 graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> <br> 3612 graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> 3613 3614 3615 <br> 3616 3617 1196 3618 More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter 4.5.1</a>.</font></font></font></td> 1197 <td style="vertical-align: top;"><br> </td> </tr> 1198 <tr> <td style="vertical-align: top; text-align: center;"><font color="#000000">105</font></td> <td style="vertical-align: top;"><font color="#000000"><a name="DATA_1D_TS_NETCDF"></a>DATA_1D_TS_NETCDF</font></td> 1199 <td style="vertical-align: top;"><font color="#000000">I/O</font></td> 1200 <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br> 3619 3620 3621 <td style="vertical-align: top;"><br> 3622 3623 3624 </td> 3625 3626 3627 </tr> 3628 3629 3630 <tr> 3631 3632 3633 <td style="vertical-align: top; text-align: center;"><font color="#000000">105</font></td> 3634 3635 3636 <td style="vertical-align: top;"><font color="#000000"><a name="DATA_1D_TS_NETCDF"></a>DATA_1D_TS_NETCDF<br> 3637 3638 3639 (DATA_1D_TS_NETCDF_O)</font></td> 3640 3641 3642 <td style="vertical-align: top;"><font color="#000000">I/O</font></td> 3643 3644 3645 <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br> 3646 3647 1201 3648 NetCDF-<br> 1202 format</font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file 3649 3650 3651 format</font></font></td> 3652 3653 3654 <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file 1203 3655 contains data of the timeseries (see <a href="chapter_4.2.html#dt_dots">dt_dots</a>) 1204 3656 in NetCDF format. The data in this file can be visualized by any 1205 graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> <br> 3657 graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> 3658 3659 3660 <br> 3661 3662 1206 3663 More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter 4.5.1</a>.</font></font></font></td> 1207 <td style="vertical-align: top;"><br> </td> </tr> 1208 <tr> <td style="vertical-align: top; text-align: center;"><font color="#000000">106</font></td> <td style="vertical-align: top;"><font color="#000000"><a name="DATA_3D_NETCDF"></a>DATA_3D_NETCDF</font></td> 1209 <td style="vertical-align: top;"><font color="#000000">I/O</font></td> 1210 <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br> 3664 3665 3666 <td style="vertical-align: top;"><br> 3667 3668 3669 </td> 3670 3671 3672 </tr> 3673 3674 3675 <tr> 3676 3677 3678 <td style="vertical-align: top; text-align: center;"><font color="#000000">106</font></td> 3679 3680 3681 <td style="vertical-align: top;"><font color="#000000"><a name="DATA_3D_NETCDF"></a>DATA_3D_NETCDF<br> 3682 3683 3684 (DATA_3D_NETCDF_O)</font></td> 3685 3686 3687 <td style="vertical-align: top;"><font color="#000000">I/O</font></td> 3688 3689 3690 <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br> 3691 3692 1211 3693 NetCDF-<br> 1212 format</font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file 3694 3695 3696 format</font></font></td> 3697 3698 3699 <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file 1213 3700 contains data of the 3d-volume data (see <a href="../app/chapter_4.2.html#data_output">data_output</a>) 1214 3701 in NetCDF format. The data in this file can be visualized by any 1215 graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> <br> 3702 graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> 3703 3704 3705 <br> 3706 3707 1216 3708 More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter 4.5.1</a>.</font></font></font></td> 1217 <td style="vertical-align: top;"><br> </td> </tr> 1218 <tr> <td style="vertical-align: top; text-align: center;"><font color="#000000">107</font></td> <td style="vertical-align: top;"><font color="#000000"><a name="DATA_1D_SP_NETCDF"></a>DATA_1D_SP_NETCDF</font></td> 1219 <td style="vertical-align: top;"><font color="#000000">I/O</font></td> 1220 <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br> 3709 3710 3711 <td style="vertical-align: top;"><br> 3712 3713 3714 </td> 3715 3716 3717 </tr> 3718 3719 3720 <tr> 3721 3722 3723 <td style="vertical-align: top; text-align: center;"><font color="#000000">107</font></td> 3724 3725 3726 <td style="vertical-align: top;"><font color="#000000"><a name="DATA_1D_SP_NETCDF"></a>DATA_1D_SP_NETCDF<br> 3727 3728 3729 (DATA_1D_SP_NETCDF_O)</font></td> 3730 3731 3732 <td style="vertical-align: top;"><font color="#000000">I/O</font></td> 3733 3734 3735 <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br> 3736 3737 1221 3738 NetCDF-<br> 1222 format</font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file 3739 3740 3741 format</font></font></td> 3742 3743 3744 <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file 1223 3745 contains data of the horizontal spectra (see <a href="../app/chapter_4.2.html#data_output_sp">data_output_sp</a>) 1224 3746 in NetCDF format. The data in this file can be visualized by any 1225 graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> <br> 3747 graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> 3748 3749 3750 <br> 3751 3752 1226 3753 More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter 4.5.1</a>.</font></font></font></td> 1227 <td style="vertical-align: top;"><br> </td> </tr> 1228 <tr> <td style="vertical-align: top; text-align: center;"><font color="#000000">108</font></td> <td style="vertical-align: top;"><font color="#000000"><a name="DATA_PRT_NETCDF"></a>DATA_PRT_NETCDF/</font></td> 1229 <td style="vertical-align: top;"><font color="#000000">I/O</font></td> 1230 <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br> 3754 3755 3756 <td style="vertical-align: top;"><br> 3757 3758 3759 </td> 3760 3761 3762 </tr> 3763 3764 3765 <tr> 3766 3767 3768 <td style="vertical-align: top; text-align: center;"><font color="#000000">108</font></td> 3769 3770 3771 <td style="vertical-align: top;"><font color="#000000"><a name="DATA_PRT_NETCDF"></a>DATA_PRT_NETCDF/<br> 3772 3773 3774 (DATA_PRT_NETCDF<span style="font-weight: bold;">_O</span>/)</font></td> 3775 3776 3777 <td style="vertical-align: top;"><font color="#000000">I/O</font></td> 3778 3779 3780 <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br> 3781 3782 1231 3783 NetCDF-<br> 1232 format</font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file 3784 3785 3786 format</font></font></td> 3787 3788 3789 <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file 1233 3790 contains particle data (see <a href="../app/chapter_4.2.html#dt_prel">dt_prel</a>) 1234 3791 in NetCDF format. The data in this file can be visualized by any 1235 graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> <br> 3792 graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> 3793 3794 3795 <br> 3796 3797 1236 3798 More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter 4.5.1</a>.</font></font></font></td> 1237 <td style="vertical-align: top;"><br> </td> </tr> 1238 <tr> <td style="vertical-align: top; text-align: center;">109</td> 1239 <td align="left" valign="top"><a name="DATA_1D_PTS_NETCDF"></a>DATA_1D_PTS_NETCDF</td> 1240 <td align="left" valign="top">I/O</td> <td align="left" valign="top">Binary/<br> 3799 3800 3801 <td style="vertical-align: top;"><br> 3802 3803 3804 </td> 3805 3806 3807 </tr> 3808 3809 3810 <tr> 3811 3812 3813 <td style="vertical-align: top; text-align: center;">109</td> 3814 3815 3816 <td align="left" valign="top"><a name="DATA_1D_PTS_NETCDF"></a>DATA_1D_PTS_NETCDF<br> 3817 3818 3819 (DATA_1D_PTS_NETCDF_O)</td> 3820 3821 3822 <td align="left" valign="top">I/O</td> 3823 3824 3825 <td align="left" valign="top">Binary/<br> 3826 3827 1241 3828 NetCDF-<br> 1242 format</td> <td align="left" valign="top">This 3829 3830 3831 format</td> 3832 3833 3834 <td align="left" valign="top">This 1243 3835 file contains data of the timeseries of particle quantities (<font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">see <a href="chapter_4.2.html#dt_prel">dt_prel</a>) 1244 3836 in NetCDF format. </font></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">The data 1245 3837 in this file can be visualized by any graphic software which provides a 1246 3838 NetCDF interface (e.g. <span style="font-weight: bold;">NCL 1247 </span>or<span style="font-weight: bold;"> ferret</span>). 3839 </span>or<span style="font-weight: bold;"> 3840 ferret</span>). 1248 3841 For a list of available output quantities see </font></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"> <a href="chapter_4.2.html#dt_dopts">dt_dopts</a>.</font></font></font></font></font><br> 1249 <font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><br> 1250 </font></font></font></font><span lang="en-GB"><font face="Thorndale">In case of 3842 3843 3844 <font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><br> 3845 3846 3847 </font></font></font></font><span lang="en-GB"><font face="Thorndale">In case of 1251 3848 using more than one particle group (see <a href="chapter_4.2.html#number_of_particle_groups">number_of_particle_groups</a>), 1252 3849 seperate time series are output for each of the groups. The long names … … 1254 3851 timeseries all end with the string</font><span style="font-style: italic; font-family: monospace;">' PG ##'</span><font face="Thorndale">, where ## is the number of the particle 1255 3852 group (<span style="font-style: italic;">01</span>, <span style="font-style: italic;">02</span>, etc.). <br> 1256 <br> </font></span><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">More detailed informations about the 3853 3854 3855 <br> 3856 3857 3858 </font></span><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">More detailed informations about the 1257 3859 PALM-NetCDF-output are given in <a href="chapter_4.5.1.html">chapter 1258 3860 4.5.1</a>.</font></font></font></font></td> 1259 <td align="left" valign="top"></td> </tr> 1260 <tr> <td style="text-align: center; vertical-align: top;">111</td> 1261 <td style="vertical-align: top;"><a name="DATA_2D_XY_AV_NETCDF"></a>DATA_2D_XY_AV_NETCDF</td> 1262 <td style="vertical-align: top;">I/O</td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br> 3861 3862 3863 <td align="left" valign="top"></td> 3864 3865 3866 </tr> 3867 3868 3869 <tr> 3870 3871 3872 <td style="text-align: center; vertical-align: top;">111</td> 3873 3874 3875 <td style="vertical-align: top;"><a name="DATA_2D_XY_AV_NETCDF"></a>DATA_2D_XY_AV_NETCDF<br> 3876 3877 3878 (DATA_2D_XY_AV_NETCDF_O)</td> 3879 3880 3881 <td style="vertical-align: top;">I/O</td> 3882 3883 3884 <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br> 3885 3886 1263 3887 NetCDF-<br> 1264 format</font></font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file 3888 3889 3890 format</font></font></font></td> 3891 3892 3893 <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file 1265 3894 contains data of the temporally averaged two-dimensional horizontal 1266 3895 cross sections (see <a href="chapter_4.2.html#data_output">data_output</a>) 1267 3896 in NetCDF format. The data in this file can be visualized by any 1268 graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> <br> 3897 graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> 3898 3899 3900 <br> 3901 3902 1269 3903 More detailed informations about the PALM-NetCDF-output are given in <a href="chapter_4.5.1.html">chapter 4.5.1</a>.</font></font></font></td> 1270 <td></td> </tr> <tr> <td style="text-align: center; vertical-align: top;">112</td> 1271 <td style="vertical-align: top;"><a name="DATA_2D_XZ_AV_NETCDF"></a>DATA_2D_XZ_AV_NETCDF</td> 1272 <td style="vertical-align: top;">I/O</td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br> 3904 3905 3906 <td></td> 3907 3908 3909 </tr> 3910 3911 3912 <tr> 3913 3914 3915 <td style="text-align: center; vertical-align: top;">112</td> 3916 3917 3918 <td style="vertical-align: top;"><a name="DATA_2D_XZ_AV_NETCDF"></a>DATA_2D_XZ_AV_NETCDF<br> 3919 3920 3921 (DATA_2D_XZ_AV_NETCDF_O)</td> 3922 3923 3924 <td style="vertical-align: top;">I/O</td> 3925 3926 3927 <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br> 3928 3929 1273 3930 NetCDF-<br> 1274 format</font></font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">This file contains data of the temporally 3931 3932 3933 format</font></font></font></td> 3934 3935 3936 <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">This file 3937 contains data of the temporally 1275 3938 averaged two-dimensional vertical (xz) 1276 3939 cross sections (see <a href="chapter_4.2.html#data_output">data_output</a>) 1277 3940 in NetCDF format. The data in this file can be visualized by any 1278 graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> <br> 3941 graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> 3942 3943 3944 <br> 3945 3946 1279 3947 More detailed informations about the PALM-NetCDF-output are given in <a href="chapter_4.5.1.html">chapter 4.5.1</a>.</font></font></font></font></td> 1280 <td></td> </tr> <tr> <td style="text-align: center; vertical-align: top;">113</td> 1281 <td style="vertical-align: top;"><font color="#000000"><a name="DATA_2D_YZ_AV_NETCDF"></a>DATA_2D_YZ_AV_NETCDF</font></td> 1282 <td style="vertical-align: top;">I/O</td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br> 3948 3949 3950 <td></td> 3951 3952 3953 </tr> 3954 3955 3956 <tr> 3957 3958 3959 <td style="text-align: center; vertical-align: top;">113</td> 3960 3961 3962 <td style="vertical-align: top;"><font color="#000000"><a name="DATA_2D_YZ_AV_NETCDF"></a>DATA_2D_YZ_AV_NETCDF<br> 3963 3964 3965 (DATA_2D_YZ_AV_NETCDF_O)</font></td> 3966 3967 3968 <td style="vertical-align: top;">I/O</td> 3969 3970 3971 <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br> 3972 3973 1283 3974 NetCDF-<br> 1284 format</font></font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">This file contains data of the temporally 3975 3976 3977 format</font></font></font></td> 3978 3979 3980 <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">This file 3981 contains data of the temporally 1285 3982 averaged two-dimensional vertical 1286 3983 (yz) cross sections (see <a href="chapter_4.2.html#data_output">data_output</a>) 1287 3984 in NetCDF format. The data in this file can be visualized by any 1288 graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> <br> 3985 graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> 3986 3987 3988 <br> 3989 3990 1289 3991 More detailed informations about the PALM-NetCDF-output are given in <a href="chapter_4.5.1.html">chapter 4.5.1</a>.</font></font></font></font></td> 1290 <td></td> </tr> <tr> <td style="text-align: center; vertical-align: top;">116</td> 1291 <td style="vertical-align: top;"><font color="#000000"><a name="DATA_3D_AV_NETCDF"></a>DATA_3D_AV_NETCDF</font></td> 1292 <td style="vertical-align: top;">I/O</td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br> 3992 3993 3994 <td></td> 3995 3996 3997 </tr> 3998 3999 4000 <tr> 4001 4002 4003 <td style="text-align: center; vertical-align: top;">116</td> 4004 4005 4006 <td style="vertical-align: top;"><font color="#000000"><a name="DATA_3D_AV_NETCDF"></a>DATA_3D_AV_NETCDF<br> 4007 4008 4009 (DATA_3D_AV_NETCDF_O)</font></td> 4010 4011 4012 <td style="vertical-align: top;">I/O</td> 4013 4014 4015 <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br> 4016 4017 1293 4018 NetCDF-<br> 1294 format</font></font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">This file contains data of the temporally 4019 4020 4021 format</font></font></font></td> 4022 4023 4024 <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">This file 4025 contains data of the temporally 1295 4026 averaged 3d-volume data (see <a href="chapter_4.2.html#data_output">data_output</a>) 1296 4027 in NetCDF format. The data in this file can be visualized by any 1297 graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> <br> 4028 graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> 4029 4030 4031 <br> 4032 4033 1298 4034 More detailed informations about the PALM-NetCDF-output are given in <a href="chapter_4.5.1.html">chapter 4.5.1</a>.</font></font></font></font></td> 1299 <td></td> </tr> </tbody> 1300 </table><font color="#000000"><br> 4035 4036 4037 <td></td> 4038 4039 4040 </tr> 4041 4042 4043 4044 </tbody> 4045 </table> 4046 4047 4048 <font color="#000000"><br> 4049 4050 1301 4051 </font><br> 1302 <font color="#000080"><font color="#000080"><a href="chapter_3.3.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.html"><font color="#000080"><img src="right.gif" name="Grafik3" align="bottom" border="2" height="32" width="32"></font></a></font></font><br> 4052 4053 4054 <font color="#000080"><font color="#000080"><a href="chapter_3.3.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.html"><font color="#000080"><img src="right.gif" name="Grafik3" align="bottom" border="2" height="32" width="32"></font></a></font></font><br> 4055 4056 4057 1303 4058 <br> 4059 4060 1304 4061 1305 4062 <span style="font-style: italic;">Last change:</span> 1306 4063 $Id$<br> 1307 </font><br></body></html> 4064 4065 4066 </font><br> 4067 4068 4069 </body> 4070 </html>
Note: See TracChangeset
for help on using the changeset viewer.
