10.08.2013 Views

Code Manual for CONTAIN 2.0 - Federation of American Scientists

Code Manual for CONTAIN 2.0 - Federation of American Scientists

Code Manual for CONTAIN 2.0 - Federation of American Scientists

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

16.3.4.1 Simzle Pass. For simple problems, POSTCON processing can be per<strong>for</strong>med in a single<br />

pass. All <strong>of</strong> the necessary in<strong>for</strong>mation <strong>for</strong> processing the binary plot file is placed in the POSTCON<br />

input file and all processing is done at once. This approach works well if no modification <strong>of</strong> the<br />

output <strong>for</strong>mats is expected.<br />

16.3.4.2 Multide Passe$. A more flexible approach is to per<strong>for</strong>m data extraction separately from<br />

the data mixing. If no mixing in<strong>for</strong>mation is found in the PINP file, POSTCON will terminate after<br />

it generates the PVEC and POUT files. POSTCON can then be run with a second PINP file to<br />

per<strong>for</strong>m the algebraic manipulations on the data in the PVEC file.<br />

The advantage <strong>of</strong> doing this is that massaging <strong>of</strong> the output <strong>for</strong>mats can be done more efficiently<br />

since the most time consuming part <strong>of</strong> a POSTCON run, the reading <strong>of</strong> the binary plot file, does not<br />

need to be repeated. Note, however, that POSTCON must always have a binary plot file as input.<br />

If the postprocessing is continued on the same machine used <strong>for</strong> the original <strong>CONTAIN</strong> run, the<br />

original plot file can be used again; only one pass through this file is made, which is not very time<br />

consuming. If the postprocessing is done on a different machine, a dummy plot file must be created<br />

on that machine. Figure 16-2 shows a simple FORTRAN program that can be used to create such<br />

a dummy file.<br />

16.3.4.3 Processin~ Results from Sources Other than <strong>CONTAIN</strong>. Finally, POSTCON can be used<br />

independently <strong>of</strong> <strong>CONTAIN</strong> manipulate data generated by other sources. The data simply needs to<br />

be put into a fde in PVEC <strong>for</strong>mat. Once this is accomplished, POSTCON can process it exactly like<br />

a vector file.<br />

16.4 kwt and Ou tmt Files and the File Definition Block<br />

16.4.1 File Descriptions<br />

A set <strong>of</strong> input and output files is associated with each POSTCON run. Figure 16-1 illustrates how<br />

each <strong>of</strong> these fdes is used. Each rectangle represents a code, each diamond represents a process, and<br />

each elIipse represents a file labeled with its default name. The arrows indicate the direction <strong>of</strong> data<br />

flow. Notice that some files are associated with all <strong>of</strong> the major POSTCON processes while others<br />

are limited to one or two <strong>of</strong> the processes. Details <strong>of</strong> each <strong>of</strong> the files follows.<br />

16.4.1.1 ~). All user instructions to POSTCON are placed in a file called PINP.<br />

This file instructs POSTCON on how memory will be initialized, what files will be used, what<br />

in<strong>for</strong>mation will be processed, how output will be <strong>for</strong>matted, and what mixing operations will be<br />

per<strong>for</strong>med. Much <strong>of</strong> the remaining portion <strong>of</strong> this chapter deals with how to create this file.<br />

16.4.1.2 ~). In order <strong>for</strong> the user to be able to debug POSTCON runs, an error file<br />

is produced to provide in<strong>for</strong>mation on what went wrong. The name <strong>of</strong> this file is PERR. Whenever<br />

a command is read from the PINP file, it is echoed to the PERR file. Furthermore, whenever an error<br />

is detected, an error message is written to the PERR file.<br />

Rev. O 16-19 6/30/97

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!