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.

Comments at the begiming <strong>of</strong> an input file describing the nature <strong>of</strong> the file, the particular<br />

circumstances being modeled, etc., are usefid <strong>for</strong> later referral. One can also use the TITLE option.<br />

However, titles cannot be put at the very beginning <strong>of</strong> an input fde, while comment lines can be. On<br />

the other hand, because titles are printed at the beginning <strong>of</strong> each long edit and become part <strong>of</strong> the<br />

plot file, they are convenient <strong>for</strong> labeling the output.<br />

13.3.4.6 Hints <strong>for</strong> Collapsing Multi-Cell I.rmutFiles. When modeling a plant, the highest level <strong>of</strong><br />

detail will <strong>of</strong>ten be determined by the <strong>for</strong>mat <strong>of</strong> the available data. Usually, one begins by generating<br />

<strong>CONTAIN</strong> input based on the most detailed nodalization that one believes the analysis requires and<br />

that the data will support. Later, a simpler input file with fewer cells maybe required. There area<br />

number <strong>of</strong> guidelines that will help a user when collapsing large multi-cell input files. First, in<br />

anticipation <strong>of</strong> the possible need to simplify, a detailed input file should be set up using the structure<br />

naming and ordering scheme suggested in Section 13.3.3.5. The following suggestions may also<br />

help to avoid confusion and needless debugging:<br />

Determine the collapsed nodalization and generate a map <strong>of</strong> cells by developing a table that<br />

shows how the “old” cells are combined into the “new” cells.<br />

Develop a flooding pr<strong>of</strong>ile mapping <strong>for</strong> combining the multiple pools in the “old” input file<br />

to the “new” input file. Remember that <strong>CONTAIN</strong> is limited to only one pool per cell. Pool<br />

flow paths may require restructuring, as may the manner in which structures submerge in the<br />

pools.<br />

Generate a concrete structure mapping table <strong>for</strong> the “old” input file showing all <strong>of</strong> the<br />

structure connections. Use the nodalization mapping table to help develop additional<br />

columns in the mapping table that show the new cell and structure numbers.<br />

If the number <strong>of</strong> miscellaneous steel structures needs to be collapsed, also generate a steel<br />

structure mapping table, separating out flooded and unflooded structures. Consider<br />

combining unflooded structures into three to five thickness classes. Comment the combined<br />

structures to indicate the grouping according to the “old” structure names.<br />

If the “old” input file makes use <strong>of</strong> the film tracking model, generate a film flow mapping<br />

table similar to the mapping tables <strong>for</strong> connected structures.<br />

Generate a flow path and elevation mapping table.<br />

Using the mapping tables <strong>for</strong> nodalization, structure, film flow, and flow paths, begin to<br />

mark up a hardcopy <strong>of</strong> the “old” input listing. Do not modi~ an electronic copy <strong>of</strong> the “old”<br />

input be<strong>for</strong>e marking up the changes on the hardcopy. File comparison utilities are awkward<br />

to use in keeping track <strong>of</strong> changes. A hardcopy markup is generally abetter approach. Try<br />

not to rename structures; instead use the comment capability to make notes on naming and<br />

ordering.<br />

Rev O 13 67 6/30/97

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

Saved successfully!

Ooh no, something went wrong!