<?xml version='1.0' encoding='utf-8' ?>
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml">
	<head>
		<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
		<link type="text/css" rel="stylesheet" href="doxygen.css"/>
		<link type="text/css" rel="stylesheet" href="tabs.css"/>
	</head>
	<body>
	<div>
<!-- Generated by Doxygen 1.8.5 -->
</div><!-- top -->
<div class="header">
  <div class="headertitle">
<div class="title">How to Run the Program </div>  </div>
</div><!--header-->
<div class="contents">
<div class="toc"><h3>Table of Contents</h3>
<ul><li class="level1"><a href="#um_how_how">How to give input - general rules</a><ul><li class="level2"><a href="#um_how_how_organization">Organization of input data</a></li>
<li class="level2"><a href="#um_how_how_formats">Formats</a><ul><li class="level3"><a href="#um_how_how_formats_comments">Comments</a></li>
<li class="level3"><a href="#um_how_how_formats_alphanumeric">Alphanumeric Data Items</a></li>
<li class="level3"><a href="#um_how_how_formats_integer">Integer Data Items (denoted integer)</a></li>
<li class="level3"><a href="#um_how_how_formats_real">Real Number Data Items (denoted real)</a></li>
<li class="level3"><a href="#um_how_how_formats_default">Default data items</a></li>
<li class="level3"><a href="#um_how_how_formats_continuation">Continuation of input statements</a></li>
<li class="level3"><a href="#um_how_how_formats_input">The input description list</a></li>
<li class="level3"><a href="#um_how_how_formats_data">Data group identifier</a></li>
</ul>
</li>
</ul>
</li>
<li class="level1"><a href="#um_how_running">Running VIVANA</a><ul><li class="level2"><a href="#um_how_running_vivana">VIVANA4WIN</a></li>
<li class="level2"><a href="#um_how_running_how">How to use standard run command procedures</a></li>
</ul>
</li>
</ul>
</div>
<div class="textblock"><h1><a class="anchor" id="um_how_how"></a>
How to give input - general rules</h1>
<h2><a class="anchor" id="um_how_how_organization"></a>
Organization of input data</h2>
<p>The input data are organized in groups, each group starting with a data group identifier, and terminating on the next data group identifier.</p>
<p>A data group identifier may consist of one, two or three words, which gives a unique description of the data group. Each word may consist of several characters, but only the first four characters of each word are checked. The user may, however, write the complete word if so desired.</p>
<p>In this manual each input line is presented within a standard list, and each list represents either one single input line or a sequence of similar input lines.</p>
<h2><a class="anchor" id="um_how_how_formats"></a>
Formats</h2>
<p>All input data are read by <a class="el" href="a00014.html#um_references_adam">FREAD</a> which is a FORTRAN free-format reader and decoder. This means that the data items may be written anywhere on the input line, as long as the specified order is satisfied. The data items must be separated with at least one blank (exceeding blanks are ignored). Note that since blank is exclusively interpreted as a delimiter, blank can not be used to specify a zero value. All digits, letters and/or special symbols in a data item must be given consecutively without blanks.</p>
<p>Tabulators should not be used in the input files.</p>
<h3><a class="anchor" id="um_how_how_formats_comments"></a>
Comments</h3>
<p>Input lines with an apostrophe (') in the first column are interpreted as comments, and simply ignored. Comments may be inserted in the input data stream in order to improve the readability of the input file.</p>
<p>Only the first 80 characters on each line are decoded.</p>
<h3><a class="anchor" id="um_how_how_formats_alphanumeric"></a>
Alphanumeric Data Items</h3>
<p>In this manual, three types of alphanumeric data items are interpreted, denoted character(4), character(6) and character(8).</p>
<p>An alphanumeric data item may consist of one or more characters. The first character is always a letter (A-Z), while the remaining ones may be letters, digits or special symbols (except /, $, &amp; and blank).</p>
<p>There is no upper limit to the number of characters in an alphanumeric data item. However, a maximum of 4 (<code>'character(4)'</code>), 6 (<code>'character(6)'</code>) or 8 (<code>'character(8)'</code>) characters will be decoded, and all characters in excess of this are simply ignored.</p>
<h4>Example:</h4>
<div class="fragment"><div class="line"><span class="stringliteral">&#39;WITH CHARACTER(4)</span></div>
<div class="line"><span class="stringliteral">ENVIRONMENTAL DATA</span></div>
<div class="line"><span class="stringliteral">&#39;</span>WILL BE INTERPRETED AS</div>
<div class="line">ENVI DATA</div>
<div class="line"><span class="stringliteral">&#39;WITH CHARACTER(6)</span></div>
<div class="line"><span class="stringliteral">ENVIRONMENTAL DATA</span></div>
<div class="line"><span class="stringliteral">&#39;</span>WILL BE INTERPRETED AS</div>
<div class="line">ENVIRO DATA</div>
</div><!-- fragment --><h3><a class="anchor" id="um_how_how_formats_integer"></a>
Integer Data Items (denoted integer)</h3>
<p>All characters must be digits. The first digit may be preceded by a + or a - character.</p>
<h4>Example:</h4>
<div class="fragment"><div class="line">0 1 -27 +66</div>
</div><!-- fragment --><h3><a class="anchor" id="um_how_how_formats_real"></a>
Real Number Data Items (denoted real)</h3>
<p>A real number data entry may consist of up to 3 components, i.e. an integer part i, a decimal part d, and exponent part e. The following 4 basic forms are accepted:</p>
<p><code>(+)i (+)i. (+)i.d (+).d</code></p>
<p>These may all be combined with exponent parts yielding the forms:</p>
<p><code>(+)iE(+)e (+)i.E(+)e (+)i.dE(+)e (+).dE(+)e</code></p>
<h4>Example:</h4>
<div class="fragment"><div class="line">0 -1. -0.2E14 +17.E-3 1.78E+3</div>
</div><!-- fragment --><h3><a class="anchor" id="um_how_how_formats_default"></a>
Default data items</h3>
<p>Some of the input data have default values. These values are inserted when no other values are given. There are two ways to signal that the program shall insert default values. One, that may always be used, is to type a slash (/) for the actual data item. Second, if the actual data item ( or data items) is (are) the last one(s) on the input line, no slash(es) is (are) necessary. FREAD will insert the number of slashes needed. Note that a slash is also a data item, and must be separated from adjacent data items by one or more blanks.</p>
<h4>Example:</h4>
<div class="fragment"><div class="line"><span class="stringliteral">&#39;THE DEFAULT VALUE OF THE SECOND DATA ITEM IS 2. THEN 3 / 5</span></div>
<div class="line"><span class="stringliteral">&#39;</span>WILL BE INTERPRETED AS</div>
<div class="line">3 2 5</div>
<div class="line"><span class="stringliteral">&#39;6 DATA ITEMS ARE REQUIRED AND THE LAST 3 DATA ITEMS HAVE DEFAULT VALUES</span></div>
<div class="line"><span class="stringliteral">&#39;</span>6, 7 AND 8, THEN</div>
<div class="line">1 2 3</div>
<div class="line"><span class="stringliteral">&#39;WILL BE INTERPRETED AS</span></div>
<div class="line"><span class="stringliteral">1 2 3 6 7 8</span></div>
</div><!-- fragment --><h3><a class="anchor" id="um_how_how_formats_continuation"></a>
Continuation of input statements</h3>
<p>An input statement may consist of one or several input lines. If an input statement consists of more than one input line, all its card images except the last one must be terminated by the character &amp;, which must be preceded by at least one blank. This implies that on such cards data cannot be specified beyond column 78.</p>
<h4>Example:</h4>
<div class="fragment"><div class="line">1 2 &amp;</div>
<div class="line">3</div>
<div class="line"><span class="stringliteral">&#39;IS THE SAME AS GIVING</span></div>
<div class="line"><span class="stringliteral">1 2 3</span></div>
</div><!-- fragment --><h3><a class="anchor" id="um_how_how_formats_input"></a>
The input description list</h3>
<div class="fragment"><div class="line">&lt;parameter names, in the order decoded&gt;</div>
</div><!-- fragment --><ul>
<li><code>Parameter: type, default: Default value</code>: Description <img class="formulaInl" alt="$ \mathrm{[unit]} $" src="form_9.png"/><ul>
<li>Optional additional information for the given parameter.</li>
</ul>
</li>
</ul>
<p>Comments, notes etc.</p>
<p>If there is no default value, that part of the line is skipped. The parameter types are integer, real and character.</p>
<p>If unit is not applicable, e.g. for integer options, that part of the line is skipped.</p>
<h4>Example:</h4>
<div class="fragment"><div class="line">IKS DAMP</div>
</div><!-- fragment --><ul>
<li><code>IKS: integer</code>: Stiffness code 1<ul>
<li>1 : Constant spring compression stiffness</li>
<li>N : Table with N pairs of pressure force - displacements to be specified<ul>
<li>N &gt; 2</li>
</ul>
</li>
</ul>
</li>
<li><code>DAMP: real, default: 0</code>: Dash pot damping coefficient <img class="formulaInl" alt="$ \mathrm{[FT/L]}$" src="form_10.png"/></li>
</ul>
<h3><a class="anchor" id="um_how_how_formats_data"></a>
Data group identifier</h3>
<p>As previously mentioned, the input data are organized in groups.</p>
<p>A data-group identifier is given on the first input line of each group.</p>
<div class="fragment"><div class="line">IDW1 IDW2 IDW3</div>
</div><!-- fragment --><ul>
<li><code>IDW1: character(4)</code>: First word of the identifier</li>
<li><code>IDW2: character(4)</code>: Second word of the identifier</li>
<li><code>IDW3: character(4)</code>: Third word of the identifier</li>
</ul>
<p>Data-group identifiers may consist of one, two or three words</p>
<p>In the input description, data-group identifiers are not presented within the standard list, but the words of the identifiers are written completely in the code box above. With format character(4), only the first four characters are checked, and these parts of the words are marked.</p>
<h4>Example:</h4>
<div class="fragment"><div class="line">EVALUATION CONTROL PARAMETERS</div>
</div><!-- fragment --><p>May be given as</p>
<div class="fragment"><div class="line">EVAL CONT PARA</div>
</div><!-- fragment --><h1><a class="anchor" id="um_how_running"></a>
Running VIVANA</h1>
<p><code>VIVANA</code> can be run using the graphical interface <code>VIVANA4WIN</code> or using standard run command procedures.</p>
<h2><a class="anchor" id="um_how_running_vivana"></a>
VIVANA4WIN</h2>
<p><code>VIVANA4WIN</code> is a utility program for running <code>VIVANA</code> analysis modules and viewing key results.</p>
<h2><a class="anchor" id="um_how_running_how"></a>
How to use standard run command procedures</h2>
<p>This section will give a description of how to use the standard <code>VIVANA</code> run command procedure delivered as a part of a <code>VIVANA</code> installation.</p>
<p>The file name convention used consists of a prefix in addition to the basic file names described in <a class="el" href="a00004.html#um_introduction_explanation">Explanation of files used</a>. The prefix and the basic file names are separated by an underscore.</p>
<p>The same type of file name convention is also used for <code>RIFLEX</code>. Prior to running <code>VIVANA</code>, the <code>RIFLEX</code> modules <code>INPMOD</code> and <code>STAMOD</code> must be run according to the <a class="el" href="a00014.html#um_references_riflex_user">RIFLEX User Manual</a>. Necessary commands to do this are given in the following:</p>
<div class="fragment"><div class="line">riflex inpmod prefix</div>
<div class="line">riflex stamod prefix</div>
</div><!-- fragment --><p>The necessary commands to run <code>VIVANA</code> is given by:</p>
<div class="fragment"><div class="line">riflex vivana prefix prefix</div>
</div><!-- fragment --><p>The file names used by the different modules are summarized in the following. For description of the files used for internal communication, see <a class="el" href="a00004.html#um_introduction_explanation">Explanation of files used</a>.</p>
<p>The run command procedure can easily be modified to allow other use of prefixes for file identification, e.g. separate prefixes for <code>STAMOD</code> and <code>INPMOD</code> runs.</p>
<h3>INPMOD files:</h3>
<ul>
<li><code>prefix_inpmod.inp</code> - symbolic input file</li>
<li><code>prefix_inpmod.res</code> - symbolic result file</li>
</ul>
<ul>
<li><code>prefix_ifninp.sam</code> - internal communication file</li>
</ul>
<h3>STAMOD files:</h3>
<ul>
<li><code>prefix_stamod.inp</code> - symbolic input file</li>
<li><code>prefix_stamod.res</code> - symbolic result file</li>
<li><code>prefix_stamod.mpf</code> - MatrixPlot file (ascii format)</li>
</ul>
<ul>
<li><code>prefix_ifnsys.sam</code> - internal communication file</li>
<li><code>prefix_ifnsta.ffi</code> - internal communication file</li>
<li><code>prefix_ifndmp.sam</code> - internal communication file</li>
</ul>
<h3>VIVANA files:</h3>
<ul>
<li><code>prefix_vivana.inp</code> - symbolic input file</li>
<li><code>prefix_vivana.res</code> - symbolic result file</li>
<li><code>prefix_vivana.mpf</code> - MatrixPlot file (ascii format)</li>
<li><code>prefix_ifnviv.ffi</code> - internal communication file</li>
</ul>
<p>The user input is given on files with extension '<code>.inp</code>' while key results can be found on files with extension '<code>.res</code>'. </p>
</div></div><!-- contents -->
	</body>
</html>