587 | | ??\\ |
588 | | With parallel runs each processing element writes the data of its subdomain to a separate file with the name PLOT3D_DATA_<Processor-Id>, where <Processor-Id> is a four digit number (e.g. PLOT3D_DATA_0000). These files are not suitable for AVS, but after the end of the model run they can be combined to one file readable for AVS with the help of the program {{{combine_plot_fields.x}}}. This tool expects the files of the individual processing elements under the names described above and outputs the combined file into a new file PLOT3D_DATA. Usually it is called by an appropriate OUTPUT - command in the '''mrun'''-configuration file. The tool writes informative messages about the accomplished actions into the job protocol (e.g., even if no files were found). By the call of {{{combine_plot_fields.x}}} also possibly existing files with two-dimensional plot data (see e.g. PLOT2D_XY) are combined. \\\\ |
| 586 | With parallel runs each processing element writes the data of its subdomain to a separate file with the name PLOT3D_DATA_<Processor-Id>, where <Processor-Id> is a four digit number (e.g. PLOT3D_DATA_0000). These files are not suitable for AVS, but after the end of the model run they can be combined to one file readable for AVS with the help of the program {{{combine_plot_fields.x}}} (automatically activated by mrun). This tool expects the files of the individual processing elements under the names described above and outputs the combined file into a new file PLOT3D_DATA. |
| 587 | The tool writes informative messages about the accomplished actions into the job protocol (e.g., even if no files were found). By the call of {{{combine_plot_fields.x}}} also possibly existing files with two-dimensional plot data (see e.g. PLOT2D_XY) are combined. \\\\ |