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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

VECTOR<br />

ovname<br />

keyword that initiates input <strong>of</strong> the name <strong>for</strong> the specific vector type<br />

comprising a given curve. Curves are only written to the vector file if a name<br />

is specified through use <strong>of</strong> this keyword. The VECTOR keyword applies<br />

only to individual curves and not the entire TDB. If no vectors are defined,<br />

the vector file will not be created or will be created with a zero file size.<br />

the name <strong>of</strong> the curve that will be written to the vector file. This name can<br />

be any string up to eight characters in length and not containing an input<br />

delimiter.<br />

IK.EY1 and item keywords as defined in Table 16-1. It is important that item keywords<br />

IKEY2 are understood since they compose the major portion <strong>of</strong> TDB curve<br />

definitions. These keywords are discussed separately because a different set<br />

<strong>of</strong> keywords applies to each individual plot flag. Item keywords are used to<br />

identi~ which element <strong>of</strong> a data record <strong>of</strong> a particular flag is to be extracted<br />

<strong>for</strong> the TDB curve being defined. Normally, an item keyword must be<br />

followed by either one or two values. These values maybe numerical values<br />

or character strings. Two item keywords are listed here, IKEY1 and IKEY2,<br />

because in some instances an item keyword maybe followed by another item<br />

keyword, which in turn must be followed by one or two values. Further<br />

clarification <strong>of</strong> item keywords and a few examples are given below.<br />

valuel; value2 identi~ing values <strong>for</strong> an item keyword. The validity <strong>of</strong> the value given is<br />

determined by POSTCON based on various entries <strong>for</strong> control in<strong>for</strong>mation<br />

written to the plot fde by <strong>CONTAIN</strong>. Most values are either character strings<br />

(eight character maximum) or integers. As mentioned above, some item<br />

keywords are followed by an additional item keyword, which in turn must be<br />

followed by an appropriate value field. The “va.lue2” field is required in a<br />

few cases where the item keyword requires two entries as opposed to one. A<br />

short discussion <strong>of</strong> the contents <strong>of</strong> a typical <strong>CONTAIN</strong> plot file record is<br />

given below <strong>for</strong> further clarification <strong>of</strong> item keywords and values.<br />

When <strong>CONTAIN</strong> writes in<strong>for</strong>mation onto a plot file, it labels each record<br />

with a flag (and usually a cell number). However, each individual numerical<br />

value written to the plot fde obviously cannot have its own unique flag.<br />

Instead, results are grouped into categories and then written with the same<br />

flag. For example, structure temperatures <strong>for</strong> all structures and all structure<br />

nodes are written with a 610 flag. In this case, item keywords followed by<br />

the appropriate values would be used to identify which structure and which<br />

node temperature to extract. Perhaps some actual examples <strong>of</strong> IKEY1 and<br />

IKEY2 input blocks will clarify the above discussion. In the examples<br />

below, the item keywords are boldfaced in order to distinguish them from<br />

constant values, since both are capitalized according to standard <strong>CONTAIN</strong><br />

notational conventions.<br />

Rev O 16 29 6/30/97

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

Saved successfully!

Ooh no, something went wrong!