<?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">Input to STAMOD </div>  </div>
</div><!--header-->
<div class="contents">
<div class="toc"><h3>Table of Contents</h3>
<ul><li class="level1"><a href="#stamod_general_information">General Information</a></li>
<li class="level1"><a href="#stamod_gen_comment">Note: Static Analysis with Fixed Parameters and Parameter Variation</a></li>
<li class="level1"><a href="#stamod_a">Data Group A: Control Information</a><ul><li class="level2"><a href="#stamod_a_principal">Principal run parameters</a><ul><li class="level3"><a href="#stamod_a_principal_data">Data group identifier, one input line</a></li>
<li class="level3"><a href="#stamod_a_principal_heading">Heading, three input lines</a></li>
<li class="level3"><a href="#stamod_a_principal_options">Options and print switches, one input line</a></li>
<li class="level3"><a href="#stamod_a_principal_specification">Specification of restart run</a></li>
</ul>
</li>
<li class="level2"><a href="#stamod_a_data">Data set identifier for present analysis</a><ul><li class="level3"><a href="#stamod_a_data_group">Data group identifier, one input line</a></li>
<li class="level3"><a href="#stamod_a_data_set">Data set identifier for results, one input line</a></li>
</ul>
</li>
<li class="level2"><a href="#stamod_a_identifier">Identifier of environment data</a><ul><li class="level3"><a href="#stamod_a_identifier_data">Data group identifier, one input line</a></li>
<li class="level3"><a href="#stamod_a_identifier_identifier">Identifier of environment data, one input line</a></li>
</ul>
</li>
<li class="level2"><a href="#stamod_a_export">Export of element responses, one input line</a><ul><li class="level3"><a href="#stamod_a_export_detailed">Detailed specification of exported element responses</a></li>
</ul>
</li>
</ul>
</li>
<li class="level1"><a href="#stamod_b">Data Group B: Static Analysis with Fixed Parameters</a><ul><li class="level2"><a href="#stamod_b_definition">Definition of subsequent input</a><ul><li class="level3"><a href="#stamod_b_definition_data">Data group identifier</a></li>
<li class="level3"><a href="#stamod_b_definition_external1">External, static loads</a></li>
<li class="level3"><a href="#stamod_b_definition_additional">Additional, static load components</a></li>
<li class="level3"><a href="#stamod_b_definition_load">Load formulation and matrix format</a></li>
</ul>
</li>
<li class="level2"><a href="#stamod_b_computational">Computational procedure selection</a><ul><li class="level3"><a href="#stamod_b_computational_data">Data group identifier, one input line</a></li>
<li class="level3"><a href="#stamod_b_computational_method">Method for static equilibrium computation</a></li>
</ul>
</li>
<li class="level2"><a href="#stamod_b_cat">Catenary analysis procedure, CAT</a><ul><li class="level3"><a href="#stamod_b_cat_data">Data group identifier</a></li>
<li class="level3"><a href="#stamod_b_cat_parameters">Parameters for catenary analysis</a></li>
</ul>
</li>
<li class="level2"><a href="#stamod_b_catfem">Catenary and subsequent finite element analysis, CATFEM</a><ul><li class="level3"><a href="#stamod_b_catfem_data">Data group identifier</a></li>
<li class="level3"><a href="#stamod_b_catfem_parameters">Parameters for catenary equilibrium calculation</a></li>
</ul>
</li>
<li class="level2"><a href="#stamod_b_stafem">Finite element analysis from start configuration, STAFEM</a><ul><li class="level3"><a href="#stamod_b_stafem_data">Data group identifier</a></li>
<li class="level3"><a href="#stamod_b_stafem_name">Name of file containing the start solution</a></li>
</ul>
</li>
<li class="level2"><a href="#stamod_b_fem">Finite element analysis, FEM</a><ul><li class="level3"><a href="#stamod_b_fem_data">Data group identifier</a></li>
</ul>
</li>
<li class="level2"><a href="#stamod_b_incremental">Incremental loading procedure</a><ul><li class="level3"><a href="#stamod_b_incremental_load">Load group specification</a><ul><li class="level4"><a href="#stamod_b_incremental_load_data">Data group identifier, one input line</a></li>
<li class="level4"><a href="#stamod_b_incremental_load_group_incrementation">Load group incrementation and iteration parameters, one input line</a></li>
<li class="level4"><a href="#stamod_b_incremental_load_types">Load types to be activated, one line for each load type to be activated within the load group</a></li>
<li class="level4"><a href="#stamod_b_incremental_load_pipe">Pipe-in-pipe contact; One input line given if LOTYPE=PIPE and ISPEC = 1</a></li>
<li class="level4"><a href="#stamod_b_incremental_load_temperature">Temperature variation, NLSPEC input lines only given if LOTYPE = TEMP</a></li>
<li class="level4"><a href="#stamod_b_incremental_load_pressure">Pressure variation, NLSPEC input lines if LOTYPE = PRES</a></li>
<li class="level4"><a href="#stamod_b_incremental_load_boundary">Boundary changes, 2 x NBOUND input lines if LOTYPE = BOUN</a></li>
<li class="level4"><a href="#stamod_b_incremental_load_winch">Winch run, NLSPEC input lines only given if LOTYPE = WINC</a></li>
<li class="level4"><a href="#stamod_b_incremental_load_growth">Growth profile, ISPEC=1 input lines only given if LOTYPE = GROW</a></li>
<li class="level4"><a href="#stamod_b_incremental_load_wind">Wind force, ISPEC=1 input lines only given if LOTYPE = WIND</a></li>
</ul>
</li>
</ul>
</li>
<li class="level2"><a href="#stamod_b_define">Define stressfree configuration</a><ul><li class="level3"><a href="#stamod_b_define_data">Data group identifier</a></li>
<li class="level3"><a href="#stamod_b_define_file_name">File name</a></li>
<li class="level3"><a href="#stamod_b_define_file_format">File format</a></li>
</ul>
</li>
<li class="level2"><a href="#stamod_b_bottom">Bottom geometry file</a><ul><li class="level3"><a href="#stamod_b_bottom_data">Data group identifier</a></li>
<li class="level3"><a href="#stamod_b_bottom_file">File name</a></li>
<li class="level3"><a href="#stamod_b_bottom_coordinates">Coordinates of the seabed file reference system</a></li>
</ul>
</li>
</ul>
</li>
<li class="level1"><a href="#stamod_c">Data Group C: Static Analysis with Parameter Variation</a><ul><li class="level2"><a href="#stamod_c_parameter">Parameter variation definition</a><ul><li class="level3"><a href="#stamod_c_parameter_data_one">Data group identifier, one input line</a></li>
<li class="level3"><a href="#stamod_c_parameter_number">Number of variations and variation codes</a></li>
<li class="level3"><a href="#stamod_c_parameter_load">Load types to be activated. One line for each load type. Optional input, maximum 4 specifications.</a><ul><li class="level4"><a href="#stamod_c_parameter_load_specification">Specification of boundary change, 2 x NBOUND lines</a></li>
</ul>
</li>
<li class="level3"><a href="#stamod_c_parameter_variation">Variation of static positions</a><ul><li class="level4"><a href="#stamod_c_parameter_data_2">Data group identifier</a></li>
<li class="level4"><a href="#stamod_c_parameter_static">Static position increments</a></li>
</ul>
</li>
</ul>
</li>
<li class="level2"><a href="#stamod_c_variation_of_current">Variation of current velocity and direction</a><ul><li class="level3"><a href="#stamod_c_variation_of_current_data">Data group identifier, one input line</a></li>
<li class="level3"><a href="#stamod_c_variation_of_current_velocity">Current velocity and direction increments</a></li>
</ul>
</li>
<li class="level2"><a href="#stamod_c_variation_of_specified">Variation of specified forces</a><ul><li class="level3"><a href="#stamod_c_variation_of_specified_data">Data group identifier, one input line</a></li>
<li class="level3"><a href="#stamod_c_variation_of_specified_force">Force increments, NLCOMP input lines to be given</a></li>
</ul>
</li>
<li class="level2"><a href="#stamod_c_control">Control parameters for printing of results</a><ul><li class="level3"><a href="#stamod_c_control_data">Data group identifier, one input line</a></li>
<li class="level3"><a href="#stamod_c_control_parameters">Control parameters for print of results from static parameter variation analysis</a></li>
</ul>
</li>
</ul>
</li>
<li class="level1"><a href="#stamod_sawu">Static Analysis with Updated Drag Forces</a><ul><li class="level2"><a href="#stamod_sawu_data">Data group identifier, one input line</a></li>
<li class="level2"><a href="#stamod_sawu_load">Specification of file for input of drag amplification, one input line</a></li>
</ul>
</li>
<li class="level1"><a href="#stamod_description">Description of Additional Input Files</a><ul><li class="level2"><a href="#stamod_description_define_stressfree">Define Stressfree Configuration</a><ul><li class="level3"><a href="#stamod_description_define_stressfree_number">Number of nodes, one input line</a></li>
<li class="level3"><a href="#stamod_description_define_stressfree_coordinates">Coordinates for stressfree configuration, NFSNOD input lines</a></li>
</ul>
</li>
<li class="level2"><a href="#stamod_description_define_start">Define Start Configuration</a><ul><li class="level3"><a href="#stamod_description_define_start_number">Number of nodes, one input line</a></li>
<li class="level3"><a href="#stamod_description_define_start_coordinates">Coordinates for start configuration, NFSNOD input lines</a></li>
</ul>
</li>
<li class="level2"><a href="#stamod_description_define_uneven">Define uneven seabed geometry</a><ul><li class="level3"><a href="#stamod_description_define_uneven_description">Description text of geometry</a></li>
<li class="level3"><a href="#stamod_description_define_uneven_grid_dimension">Grid dimension and extension, one input file</a></li>
<li class="level3"><a href="#stamod_description_define_uneven_grid_orientation">Grid orientation, one input line</a></li>
<li class="level3"><a href="#stamod_description_define_uneven_depths">Depths at gridpoint, NGY input lines</a></li>
</ul>
</li>
</ul>
</li>
</ul>
</div>
<div class="textblock"><h1><a class="anchor" id="stamod_general_information"></a>
General Information</h1>
<p>The input to the <code>STAMOD MODULE</code> is divided into 3 main sections, referred to ass</p>
<ul>
<li><a class="el" href="a00012.html#stamod_a">Data Group A: Control Information</a></li>
<li><a class="el" href="a00012.html#stamod_b">Data Group B: Static Analysis with Fixed Parameters</a></li>
<li><a class="el" href="a00012.html#stamod_c">Data Group C: Static Analysis with Parameter Variation</a></li>
</ul>
<p>Theoretical description of the static analysis procedures is given in the chapters 'Static Catenary Analysis ' and 'Static Finite Element Analysis ' in the <code>RIFLEX</code> Theory Manual. Guidance to static analysis is given in the 'Guidance to Static Analysis' section of the 'Static Finite Element Analysis' part of the <code>RIFLEX</code> Theory Manual.</p>
<h1><a class="anchor" id="stamod_gen_comment"></a>
Note: Static Analysis with Fixed Parameters and Parameter Variation</h1>
<p>In static analysis with fixed parameters, loads types can be activated by the user specified input. For specification of the load types, see data group identfier <a class="el" href="a00012.html#stamod_b_incremental_load_data">LOAD GROUP DATA</a>.</p>
<p>In static analysis with parameter variation, loads types are activated using the data group identfier <a class="el" href="a00012.html#stamod_c_parameter_number">PARAmeter VARIation DEFInition</a>. The loads that can be activated by user specification are</p>
<ul>
<li>Static offset variation</li>
<li>Current variation</li>
<li>Specified force variation</li>
<li>Bottom friction forces</li>
<li>Global springs</li>
<li>Material memory function</li>
<li>Boundary change</li>
</ul>
<p>In addition, a set of load types are automatically activated using the data group identfier <a class="el" href="a00012.html#stamod_c_parameter_number">PARAmeter VARIation DeFInition</a>. These loads types are</p>
<ul>
<li>Volume forces</li>
<li>Tensioner forces</li>
<li>Roller contact forces</li>
<li>Initail stressed elements</li>
<li>Floater forces</li>
</ul>
<p>Note that if current, wind and specfied force are specified in <code>STAMOD</code> but not activated using the data group identfier <a class="el" href="a00012.html#stamod_b_incremental_load_data">LOAD GROUP DATA</a>, current load, wind load and specified force will be applied in <code>DYNMOD</code>. Volume forces will be activated i <code>DYNMOD</code> if not activated by using the data group identfier <code>LOAD GROUP DATA</code>.</p>
<h1><a class="anchor" id="stamod_a"></a>
Data Group A: Control Information</h1>
<p>This data group is mandatory for all types of analysis with <code>STAMOD</code>.</p>
<h2><a class="anchor" id="stamod_a_principal"></a>
Principal run parameters</h2>
<h3><a class="anchor" id="stamod_a_principal_data"></a>
Data group identifier, one input line</h3>
<div class="fragment"><div class="line">STAMod CONTrol INFOrmation CHVERS</div>
</div><!-- fragment --><ul>
<li><code>CHVERS: character(8)</code>: <code>RIFLEX</code> input file version, e.g. 3.6</li>
</ul>
<h3><a class="anchor" id="stamod_a_principal_heading"></a>
Heading, three input lines</h3>
<p>Identification of the run alphanumerical text. This text will be output when running <code>STAMOD</code>.</p>
<div class="fragment"><div class="line">HEAD1 HEAD2 HEAD3</div>
</div><!-- fragment --><ul>
<li><code>HEAD1: character</code>: Line 1 of heading text</li>
<li><code>HEAD2: character</code>: Line 2 of heading text</li>
<li><code>HEAD3: character</code>: Line 3 of heading text</li>
</ul>
<p>Always 3 input lines which may all be blank</p>
<h3><a class="anchor" id="stamod_a_principal_options"></a>
Options and print switches, one input line</h3>
<div class="fragment"><div class="line">IRUNCO IDRIS IANAL IPRDAT IPRCAT IPRFEM IPFORM IPRNOR IFILFM IFILCO</div>
</div><!-- fragment --><ul>
<li><code>IRUNCO: integer, default: 0</code>: Run code for data check or executable run<ul>
<li><code>IRUNCO = 0</code>: Data check run</li>
<li><code>IRUNCO = 1</code>: Analysis run</li>
<li><code>IRUNCO = 2</code>: Restart analysis. The data group 'Specification of restart run' must be given subsequent to this input line</li>
</ul>
</li>
<li><code>IDRIS: character(6)</code>: Data set identifier corresponding to data for one riser system established by <code>INPMOD</code></li>
<li><code>IANAL: integer</code>: Type of analysis to be performed<ul>
<li><code>IANAL = 1</code>: Static analysis. Data group B must be provided for this analysis</li>
<li><code>IANAL = 2</code>: Static analysis with parameter variation. Data groups B and C must be provided</li>
</ul>
</li>
<li><code>IPRDAT: integer, default: 2</code>: Print switch for the amount of output from the data generation<ul>
<li><code>IPRDAT=1</code>: Only identifiers and a few key data are printed</li>
<li><code>IPRDAT&gt;2</code>: Tabulated print of system and environmental data (recommended)</li>
<li><code>IPRDAT=-5</code>: Print of system presented by segment and print of environment data</li>
</ul>
</li>
<li><code>IPRCAT: integer, default: 1</code>: Print switch for the amount of output from the catenary analysis<ul>
<li><code>IPRCAT=1</code>: Gives print of final catenary solution</li>
<li><code>IPRCAT=5</code>: Gives in addition print of stress free configuration</li>
<li><code>IPRCAT=10</code>: Gives in addition print of the catenary iteration (for debug purposes)</li>
</ul>
</li>
<li><code>IPRFEM: integer, default: 1</code>: Print switch for the amount of output from <code>FEM</code> analysis<ul>
<li><code>IPRFEM=1</code>: Results are printed for the equilibrium configuration at the end of the final static load step. If the analysis includes parameter variation, results are also printed after the final parameter variation load step.</li>
<li><code>IPRFEM=5</code>: Results are printed for equilibrium configurations at the end of each load group</li>
<li><code>IPRFEM=10</code>: Results are printed for the equilibrium configurations at every load step</li>
</ul>
</li>
<li><code>IPFORM: integer, default: 1</code>: Format for print of <code>FEM</code> results<ul>
<li><code>IPFORM=-1</code>: Debug format</li>
<li><code>IPFORM=1</code>: Results are presented line by line. Moments and curvatures are given at both element ends</li>
<li><code>IPFORM=2</code>: Results are presented line by line. Moments and curvatures are averaged at internal line nodes. Results at element ends are used at line ends (similar to <code>OUTMO</code> processing)</li>
<li><code>IPFORM=3</code>: Results are presented segment by segment. Moments and curvatures are averaged at internal segment nodes. Results at element ends are used at segment ends.</li>
</ul>
</li>
<li><code>IPRNOR: integer, default: 1</code>: Print switch for convergence norms in static <code>FEM</code> analysis<ul>
<li><code>IPRNOR=0</code>: No output of convergence norms</li>
<li><code>IPRNOR=1</code>: Print of convergence norms</li>
</ul>
</li>
<li><code>IFILFM: integer, default: 2</code>: Option for Matrix Plot file<ul>
<li><code>IFILFM=0</code>: No print</li>
<li><code>IFILFM</code> <img class="formulaInl" alt="$ \neq $" src="form_96.png"/> <code>0</code>: Matrix Plot file named <code>&lt;prefix&gt;_stamod.mpf</code> (<code>IPRFEM</code> controls how often static key results are written to the Matrix Plot file)</li>
</ul>
</li>
<li><code>IFILCO: integer, default: 0</code>: Print switch for storing system configuration to ascii files. Initial configuration used for FE-analysis and configurations after each load-group during the loading sequence are stored. The stored configurations may be used as start configuration for subsequent <code>STAFEM</code>-analysis.<ul>
<li><code>IFILCO=0</code>: No additional files</li>
<li><code>IFILCO=1</code>:<ul>
<li>Configurations stored to ASCii files:<ul>
<li><code>&lt;prefix&gt;_config-lg&lt;i&gt;</code> where the number <code>&lt;i&gt;</code> indicates the load group number.</li>
</ul>
</li>
<li>For configurations after parameter variation the files are named:<ul>
<li><code>&lt;prefix&gt;_config-lg&lt;i&gt;-&lt;n&gt;</code> where <code>&lt;n&gt;</code> is the step number</li>
</ul>
</li>
</ul>
</li>
</ul>
</li>
</ul>
<p>Note that projection angles will only be printed to <code>&lt;prefix&gt;_stamod.res</code> for lines that consist of bar elements.</p>
<h3><a class="anchor" id="stamod_a_principal_specification"></a>
Specification of restart run</h3>
<p>These input lines are only given for a restart run of <code>STAMOD</code> (<code>IRUNCO=2</code> in the previous data group, 'Options and print switches, one input line'), and should be given subsequent to <code>STAMOD CONTROL INFORMATION</code>.</p>
<p>Restart of <code>STAMOD</code> makes it possible to continue computation from the last successful load group.</p>
<p>A restart run of <code>STAMOD</code> requires two data files from the previous run:</p>
<ul>
<li><code>IFNDMP</code> which contains the entire work array</li>
<li><code>IFNSTA</code> which contains the results to be processed by <code>OUTMOD</code></li>
</ul>
<p>During a run of <code>STAMOD</code>, the entire work array (all data in core) will be written to file <code>IFNDMP</code> at the end of each completed load group. The file is overwritten each time, so the content is always related to the last (successful) load group. Therefore a restart will normally start with the next load group. In case of restart from parameter variations, the analysis will continue with the next parameter variation step. This makes the parameter variation more flexible as the user can choose to vary one parameter at a time.</p>
<p>It is also possible to carry out several runs with parameter variations from the same static equilibrium configuration. The procedure to be used in this case is illustrated through the following example:</p>
<p>1) Run <code>STAMOD</code> in a normal way, (<code>IANAL=1</code>). A file prefix of SA_ is inserted for the example.</p>
<p>2) Make a copy of the files SA_IFNDMP.SAM and SA_IFNSTA.FFI to e.g. BACKUP.SAM and BACKUP.FFI, respectively.</p>
<p>3) Run restart with parameter variations, (<code>IANAL=2</code>).</p>
<p>4) Now, a new restart can be made from the original static equilibrium configuration by copying BACKUP.SAM and BACKUP.FFI to SA_IFNDMP.SAM and SA_IFNSTA.FFI prior to execution.</p>
<p>The procedure with backup of files can easily be automated in a run command procedure.</p>
<p>Note that current must be present in the original run if restart with parameter variation of current data is specified. Otherwise, the original current will be loaded in the first parameters variation step.</p>
<div class="fragment"><div class="line">RESTart PARAmeters STAMod </div>
</div><!-- fragment --><div class="fragment"><div class="line">IDSTA</div>
</div><!-- fragment --><ul>
<li><code>IDSTA: character(6)</code>: Identifier for original static analysis results</li>
</ul>
<h2><a class="anchor" id="stamod_a_data"></a>
Data set identifier for present analysis</h2>
<h3><a class="anchor" id="stamod_a_data_group"></a>
Data group identifier, one input line</h3>
<div class="fragment"><div class="line">RUN IDENtification </div>
</div><!-- fragment --><h3><a class="anchor" id="stamod_a_data_set"></a>
Data set identifier for results, one input line</h3>
<div class="fragment"><div class="line">IDRES</div>
</div><!-- fragment --><ul>
<li><code>IDRES: character(6)</code>: Data set identifier for this run</li>
</ul>
<h2><a class="anchor" id="stamod_a_identifier"></a>
Identifier of environment data</h2>
<h3><a class="anchor" id="stamod_a_identifier_data"></a>
Data group identifier, one input line</h3>
<div class="fragment"><div class="line">ENVIronment REFErence IDENtifier</div>
</div><!-- fragment --><h3><a class="anchor" id="stamod_a_identifier_identifier"></a>
Identifier of environment data, one input line</h3>
<div class="fragment"><div class="line">IDENV</div>
</div><!-- fragment --><ul>
<li><code>IDENV: character(6)</code>: Identifier of environment data given as input to the <code>INPMOD</code> module</li>
</ul>
<p>This data group is dummy for coupled analysis.</p>
<h2><a class="anchor" id="stamod_a_export"></a>
Export of element responses, one input line</h2>
<p>This specification is optional. Specifying export of element responses enables visualization of the incremental loading configurations by use of the computer program <code>SIMVIS</code> subsequent to static analysis. In present version it is possible to specify element responses in form of effective tension, resulting curvature and longitudinal stress (if available).</p>
<div class="fragment"><div class="line">STORe VISUalisation RESPonses </div>
</div><!-- fragment --><h3><a class="anchor" id="stamod_a_export_detailed"></a>
Detailed specification of exported element responses</h3>
<p>This data group is optional.</p>
<p>By default effective tension for all lines will be exported. This input line makes it possible to limit or specify response types for selected lines in the system.</p>
<p>Number of input lines: as many as necessary.</p>
<div class="fragment"><div class="line">OPTION CHRESP CHILIN</div>
</div><!-- fragment --><ul>
<li><code>OPTION: character</code>:<ul>
<li><code>= STORE</code></li>
<li><code>= NOSTORE</code></li>
</ul>
</li>
<li><code>CHRESP: character</code>: Response type to be exported<ul>
<li><code>= EFF-AX-FORCE</code>: Effective tension</li>
<li><code>= RES-CURV</code>: Resultant curvature</li>
<li><code>= LONG-STRESS</code>: Longitudinal stress</li>
<li><code>= ALL</code>: All of the above described responses</li>
</ul>
</li>
<li><code>CHILIN: character</code>:<ul>
<li><code>= LINE-ID</code>: Reference to line identifier</li>
<li><code>= ALL</code>: All lines</li>
</ul>
</li>
</ul>
<h1><a class="anchor" id="stamod_b"></a>
Data Group B: Static Analysis with Fixed Parameters</h1>
<p>This section is mandatory, and the analysis must always be carried out before any type of dynamic analysis is started.</p>
<h2><a class="anchor" id="stamod_b_definition"></a>
Definition of subsequent input</h2>
<h3><a class="anchor" id="stamod_b_definition_data"></a>
Data group identifier</h3>
<div class="fragment"><div class="line">STATic CONDition INPUt</div>
</div><!-- fragment --><h3><a class="anchor" id="stamod_b_definition_external1"></a>
External, static loads</h3>
<div class="fragment"><div class="line">NLCOMP ICURIN CURFAC IWINDIN</div>
</div><!-- fragment --><ul>
<li><code>NLCOMP: integer, default: 0</code>: Number of additional load components. Loads to be specified in next data group, 'Additional, static load components', which is omitted if <code>NLCOMP=0</code>.</li>
<li><code>ICURIN: integer, default: 0</code>: Current indicator<ul>
<li><code>ICURIN = 0</code>: No current</li>
<li><code>ICURIN = N</code>: Current profile no. N on referenced environmental description (<code>IDENV</code>) is used. The profile may be scaled by <code>CURFAC</code></li>
</ul>
</li>
<li><code>CURFAC: integer, real: 1</code>: Scaling factor to amplify or reduce the referred current profile <img class="formulaInl" alt="$ \mathrm{[1]}$" src="form_291.png"/></li>
<li><code>IWINDIN: integer, default: 0</code>: Wind indicator<ul>
<li><code>IWINDIN = 0</code>: No wind</li>
<li><code>IWINDIN = N</code>: Wind specification no. N on referenced environmental description (<code>IDENV</code>) is used.</li>
</ul>
</li>
</ul>
<p>If current loads are applied in <code>STAMOD</code>, the current active at the end of the static analysis will be used in <code>DYNMOD</code>. If current loads are not applied in <code>STAMOD</code>, the specified current profile <code>ICURIN</code> will be used in <code>DYNMOD</code> with the scaling factor <code>CURFAC</code> specified here.</p>
<p><code>CURFAC</code> must be 1.0 for a restart analysis.</p>
<h3><a class="anchor" id="stamod_b_definition_additional"></a>
Additional, static load components</h3>
<p>This data specification is omitted if <code>NLCOMP=0</code>. Otherwise <code>NLCOMP</code> input lines are specified.</p>
<div class="fragment"><div class="line">LINE-ID ILSEG ILNODE ILDOF RLMAG CHICOO</div>
</div><!-- fragment --><ul>
<li><code>LINE-ID: character(8)</code>: Reference to line identifier.</li>
<li><code>ILSEG: integer</code>: Segment number within the actual line.</li>
<li><code>ILNODE: integer</code>: Local node (<code>CHICOO=GLOBAL</code>) or element number (<code>CHICOO=LOCAL</code>).</li>
<li><code>ILDOF: integer</code>: Degree of freedom within the specified node/element.<ul>
<li><code>ILDOF = 7....12</code> at end 2 of an element.</li>
</ul>
</li>
<li><code>RLMAG: real, default: 0</code>: Magnitude of load component (F or FL).</li>
<li><code>CHICOO: character(6), default: GLOBAL</code>: Reference system for application of nodal load components.<ul>
<li><code>CHICOO = GLOBAL</code>: Force component refers to global system. The force is applied at the specified node.</li>
<li><code>CHICOO = LOCAL</code>: Force component refers to local system. The force is applied to the specified element.</li>
<li>If skew boundaries or vessel boundary are specified at the node <code>CHICOO=GLOBAL</code> means that the load component acts in the skew (vessel) system.</li>
</ul>
</li>
</ul>
<h3><a class="anchor" id="stamod_b_definition_load"></a>
Load formulation and matrix format</h3>
<div class="fragment"><div class="line">LCONS ISOLVR</div>
</div><!-- fragment --><ul>
<li><code>LCONS: integer, default: 0</code>: Switch for lumped or consistent load and mass formulation.<ul>
<li><code>LCONS = 0</code>: Lumped load and mass formulation.</li>
<li><code>LCONS = 1</code>: Consistent load and mass formulation.</li>
<li>Applies also to DYNMOD</li>
</ul>
</li>
<li><code>ISOLVR: integer, default: 1</code>: Matrix storage format. Applies also to <code>DYNMOD</code>.<ul>
<li><code>ISOLVR = 1</code>: Skyline, recommended for simple, single line riser models.</li>
<li><code>ISOLVR = 2</code>: Sparse, recommended for coupled analysis and complex models with branch points.</li>
<li>The free vibration option in <code>DYNMOD</code> requires <code>ISOLVR = 1</code></li>
</ul>
</li>
</ul>
<p>When applying the lumped load and mass formulation (<code>LCONS=0</code>), the element nodes are assigned part of the distributed external element load and mass directly. When using a consistent formulation (<code>LCONS=1</code>), the external element load and mass is distributed to the nodes using the same interpolation (shape) functions as applied when determining the element stiffness matrix. See the theory manual for more details.</p>
<p>The numerical solution speed for static and subsequent dynamic analysis depends on the matrix storage format. For a typical single riser analysis where the resulting stiffness matrix is rather narrow banded, the skyline matrix storage method is the most efficient, <code>ISOLVR=1</code>.</p>
<p>In case of many branch points, or when doing coupled analysis with many mooring lines and/or risers connected to the same floating vessel, the stiffness matrix may be significantly more broad banded. In such a case, choosing sparse matrix storage may increase the numerical solution speed, <code>ISOLVR=2</code>.</p>
<p>Note: Since the difference in solution speed could be practically negligible for small models, sparse matrix storage (<code>ISOLVR=2</code>) may be a good initial choice. Later, one could check if skyline matrix storage gives better numerical performance.</p>
<h2><a class="anchor" id="stamod_b_computational"></a>
Computational procedure selection</h2>
<h3><a class="anchor" id="stamod_b_computational_data"></a>
Data group identifier, one input line</h3>
<div class="fragment"><div class="line">COMPutational PROCedure </div>
</div><!-- fragment --><h3><a class="anchor" id="stamod_b_computational_method"></a>
Method for static equilibrium computation</h3>
<div class="fragment"><div class="line">AMETH</div>
</div><!-- fragment --><ul>
<li><code>AMETH: character(6)</code>: Code for computation method. The following options are available:<ul>
<li><code>CAT</code>: Catenary analysis, bending stiffness neglected</li>
<li><code>CATFEM</code>: Finite element method based on catenary start configuration</li>
<li><code>STAFEM</code>: Finite element method based on start configuration read from file.</li>
<li><code>FEM</code>: Finite element method based on stress free start configuration</li>
</ul>
</li>
</ul>
<p>Selection of options according to system type and whether a subsequent dynamic analysis is to be carried out or not:</p>
<div class="image">
<img src="um_sta_fig180.svg" alt="um_sta_fig180.svg"/>
<div class="caption">
Available options for static and dynamic analysis</div></div>
<h2><a class="anchor" id="stamod_b_cat"></a>
Catenary analysis procedure, CAT</h2>
<h3><a class="anchor" id="stamod_b_cat_data"></a>
Data group identifier</h3>
<div class="fragment"><div class="line">CATEnary ANALysis PARAmeters </div>
</div><!-- fragment --><h3><a class="anchor" id="stamod_b_cat_parameters"></a>
Parameters for catenary analysis</h3>
<div class="fragment"><div class="line">XL50 FL10 XU1TOL XU3TOL</div>
</div><!-- fragment --><ul>
<li><code>XL50: real, default: see below</code>: Initial estimate of angle from vertical at the point where the catenary calculation starts <img class="formulaInl" alt="$ \mathrm{[deg]}$" src="form_76.png"/></li>
<li><code>FL10: real, default: see below</code>: Initial estimate of axial force at the point where the catenary calculation starts <img class="formulaInl" alt="$ \mathrm{[F]}$" src="form_215.png"/></li>
<li><code>XU1TOL: real, default: see below</code>: Tolerance of X1 coordinate at upper end <img class="formulaInl" alt="$ \mathrm{[L]}$" src="form_75.png"/></li>
<li><code>XU3TOL: real, default: see below</code>: Tolerance of X3 coordinate at upper end <img class="formulaInl" alt="$ \mathrm{[L]}$" src="form_75.png"/></li>
</ul>
<p>Default values will be computed for the standard riser system based on geometry and specified weights and forces, if the parameter is given a "slash"(/). For standard system SA, SB and SD the calculation of the catenary solution starts at the upper end, for SC it starts at the lower end.</p>
<p>For <code>XL50</code> and <code>FL10</code> default values are recommended. The values are printed out on the result file. For the SC system these parameters are dummy.</p>
<p>The default values of <code>XU1TOL</code> and <code>XU3TOL</code> are calculated as <img class="formulaInl" alt="$ 10^{-4}$" src="form_389.png"/> (length of the riser).</p>
<h2><a class="anchor" id="stamod_b_catfem"></a>
Catenary and subsequent finite element analysis, CATFEM</h2>
<h3><a class="anchor" id="stamod_b_catfem_data"></a>
Data group identifier</h3>
<div class="fragment"><div class="line">CATFem ANALysis PARAmeters </div>
</div><!-- fragment --><h3><a class="anchor" id="stamod_b_catfem_parameters"></a>
Parameters for catenary equilibrium calculation</h3>
<div class="fragment"><div class="line">XL50 FL10 XU1TOL XU3TOL</div>
</div><!-- fragment --><ul>
<li><code>XL50: real, default: see below</code>: Initial estimate of angle from vertical at the point where the catenary calculation starts <img class="formulaInl" alt="$ \mathrm{[deg]}$" src="form_76.png"/></li>
<li><code>FL10: real, default: see below</code>: Initial estimate of axial force at the point where the catenary calculation starts <img class="formulaInl" alt="$ \mathrm{[F]}$" src="form_215.png"/></li>
<li><code>XU1TOL: real, default: see below</code>: Tolerance of X1 coordinate at upper end <img class="formulaInl" alt="$ \mathrm{[L]}$" src="form_75.png"/></li>
<li><code>XU3TOL: real, default: see below</code>: Tolerance of X3 coordinate at upper end <img class="formulaInl" alt="$ \mathrm{[L]}$" src="form_75.png"/></li>
</ul>
<p>Default values will be computed for the standard riser system based on geometry and specified weights and forces, if the parameter is given a "slash"(/).</p>
<p>For standard system SA, SB and SD the calculation of the catenary solution starts at the upper end, for SC it starts at the lower end.</p>
<p>For <code>XL50</code> and <code>FL10</code> default values are recommended. The values are printed out on the result file. For the SC system these parameters are dummy.</p>
<p>The default values of <code>XU1TOL</code> and <code>XU3TOL</code> are calculated as <img class="formulaInl" alt="$ 10^{-4}$" src="form_389.png"/> (length of the main riser line).</p>
<p>Next data group is <a class="el" href="a00012.html#stamod_b_incremental">Incremental loading procedure</a>.</p>
<h2><a class="anchor" id="stamod_b_stafem"></a>
Finite element analysis from start configuration, STAFEM</h2>
<p>Preliminary test version.</p>
<p>In present version it is assumed that the start solution represent a catenary solution.</p>
<h3><a class="anchor" id="stamod_b_stafem_data"></a>
Data group identifier</h3>
<div class="fragment"><div class="line">STAFem ANALysis PARAmeters </div>
</div><!-- fragment --><h3><a class="anchor" id="stamod_b_stafem_name"></a>
Name of file containing the start solution</h3>
<div class="fragment"><div class="line">CHFSTA KFORM</div>
</div><!-- fragment --><ul>
<li><code>CHFSTA: character(60)</code>: File name with specification of start configuration . The content of this file is described in <a class="el" href="a00012.html#stamod_description_define_start">Define Start Configuration</a>.</li>
<li><code>KFORM: integer, default: 1</code>: Code for file format<ul>
<li><code>KFORM = 1</code>: Co-ordinates and base vector system given for all FEM-nodes in increasing node number order.</li>
</ul>
</li>
</ul>
<p>Next data group is <a class="el" href="a00012.html#stamod_b_incremental">Incremental loading procedure</a>.</p>
<h2><a class="anchor" id="stamod_b_fem"></a>
Finite element analysis, FEM</h2>
<h3><a class="anchor" id="stamod_b_fem_data"></a>
Data group identifier</h3>
<div class="fragment"><div class="line">FEM ANALysis PARAmeters </div>
</div><!-- fragment --><h2><a class="anchor" id="stamod_b_incremental"></a>
Incremental loading procedure</h2>
<p>This data group describes the incremental loading procedure from catenary solution (<code>CATFEM</code>), from a specified start solution (<code>STAFEM</code>) or from stress free configuration (<code>FEM</code>) to the final static equilibrium configuration.</p>
<p>A brief summary of the incremental loading procedure applied, is given in the following. For a more detailed description including analysis guidance, see 'Static Finite Element Analysis' in the RIFLEX Theory Manual.</p>
<p>Based on load groups, the user is free to specify an arbitrary load sequence. Incrementation and iteration parameters are specified separately for each load group. One or several load types can be applied within each load group. Simultaneous application of several load types and user-defined order of the load application is therefore possible.</p>
<p>The incremental loading is normally carried out in the following sequence:</p>
<ul>
<li>Load group 1: Volume forces (weight and buoyancy)</li>
<li>Load group 2: Specified displacements (i.e. displacements to final position of nodal points with specified boundary conditions)</li>
<li>Load group 3: Specified forces (nodal point loads)</li>
<li>Load group 4: Position dependent forces (current forces)</li>
</ul>
<p>All user-defined load types have to be specified within a load group in order to be applied during the incremental loading of the system. Examples are roller and tensioner contact forces (elastic contact surface), initially stressed segments or floater forces.</p>
<p>The user may specify the load group for application of bottom friction and global linear springs. It is also possible to neglect friction and springs in normal static analysis and activate friction during static parameter variation or at the start of dynamic analysis.</p>
<h4>CATFEM analysis</h4>
<p>Volume forces have to be applied within one incremental step in the first specified load group. This is because volume forces and prescribed translations from stress free to final positions of terminal points are included in the catenary start solution. Deviations between the catenary and the final <code>FEM</code> solution are, however, present due to different mathematical formulations and neglection of bending stiffness in the catenary analysis. The first load group applying volume forces in one incremental step, is therefore a simple equilibrium iteration starting from the catenary solution with weight and buoyancy forces acting. The equilibrium iteration may fail if there are significant differences between the catenary solution and the final solution due to bending stiffness. It is therefore possible to apply the bending stiffness in several incremental steps to reach the final solution.</p>
<p>The iterative approach on boundary conditions used in the catenary analysis will give deviations between specified translating boundary conditions (i.e. x and z co-ordinates) and boundary condition computed by the catenary analysis. Further, specified boundary conditions for rotations at the supports will not be satisfied by the catenary analysis due to neglection of bending stiffness. A load group for prescribed displacements should therefore be included to account for inaccuracies in boundary conditions from the catenary analysis.</p>
<h4>STAFEM analysis</h4>
<p>The load types applied for the start configuration have to be indicated in the first specified load group. These load types will act with full force while the residual forces will be off-loaded the specified number of load steps. The residual forces are the unbalanced forces based on the indicated load types and the internal forces that appear when the start configuration is described in the finite element formulation.</p>
<p>Note that it is assumed that final boundary conditions are included in the start configuration. As a consequence the procedure will be indifferent to specification of prescribed displacements.</p>
<h3><a class="anchor" id="stamod_b_incremental_load"></a>
Load group specification</h3>
<p>The input lines 'Data group identifier...', 'Load group incrementation...' and 'Load types to be activated...' have to be given in one block for each load group.</p>
<h4><a class="anchor" id="stamod_b_incremental_load_data"></a>
Data group identifier, one input line</h4>
<div class="fragment"><div class="line">LOAD GROUP DATA </div>
</div><!-- fragment --><h4><a class="anchor" id="stamod_b_incremental_load_group_incrementation"></a>
Load group incrementation and iteration parameters, one input line</h4>
<div class="fragment"><div class="line">NSTEP MAXIT RACU CHNORM EACU</div>
</div><!-- fragment --><ul>
<li><code>NSTEP: integer</code>: Number of load steps</li>
<li><code>MAXIT: integer, default: 10</code>: Maximum number of iterations during application of load</li>
<li><code>RACU: real, default:</code> <img class="formulaInl" alt="$ 10^{-6} $" src="form_390.png"/>: Required accuracy measured by displacement norm <img class="formulaInl" alt="$ \mathrm{[1]} $" src="form_65.png"/></li>
<li><code>CHNORM: character(4), default: DISP</code>: Convergence norm switch<ul>
<li><code>= DISP</code>: Use the default Euclidean displacement norm only</li>
<li><code>= BOTH</code>: Use both the default Euclidean displacement norm and the energy norm</li>
</ul>
</li>
<li><code>EACU: real, default:</code> <img class="formulaInl" alt="$ 10^{-6} $" src="form_390.png"/>: Required accuracy measured by energy norm<ul>
<li>Dummy if <code>CHNORM=DISP</code></li>
</ul>
</li>
</ul>
<h4><a class="anchor" id="stamod_b_incremental_load_types"></a>
Load types to be activated, one line for each load type to be activated within the load group</h4>
<div class="fragment"><div class="line">LOTYPE ISPEC</div>
</div><!-- fragment --><ul>
<li><code>LOTYPE: character(4)</code>: Load type to be applied<ul>
<li><code>= VOLU</code>: Volume forces</li>
<li><code>= DISP</code>: Specified displacements</li>
<li><code>= SFOR</code>: Specified forces</li>
<li><code>= CURR</code>: Current forces</li>
<li><code>= TENS</code>: Activate tensioner contact forces</li>
<li><code>= ROLL</code>: Activate roller and tubular contact forces</li>
<li><code>= PIPE</code>: Activate pipe-in-pipe contact forces</li>
<li><code>= ISTR</code>: Initially pre-stressed segments</li>
<li><code>= FLOA</code>: Floater forces</li>
<li><code>= FRIC</code>: Activate bottom friction forces</li>
<li><code>= SPRI</code>: Activate global springs</li>
<li><code>= BEND</code>: Bending stiffness</li>
<li><code>= TEMP</code>: Temperature variation</li>
<li><code>= PRES</code>: Pressure variation</li>
<li><code>= MEMO</code>: Activate material memory formulation (Isotropic/kinematic hardening)</li>
<li><code>= BOUN</code>: Activate boundary change</li>
<li><code>= WINC</code>: Run winch(es)</li>
<li><code>= GROW</code>: Apply cross-section changes from growth profile</li>
<li><code>= WIND</code>: Wind forces</li>
</ul>
</li>
<li><code>ISPEC: integer</code>: Parameter used for further description of applied load type:<ul>
<li><code>LOTYPE = PIPE</code>:<ul>
<li><code>ISPEC = 0</code> (default): Possible pipe-in-pipe contact enabled (ENTERED)</li>
<li><code>= 1</code>: Specify start condition for pipe-in-pipe contact</li>
</ul>
</li>
<li><code>LOTYPE = TEMP</code>:<ul>
<li><code>ISPEC = NLSPEC</code>: Number of subsequent input lines for specification of temperature variation.</li>
</ul>
</li>
<li><code>LOTYPE = PRES</code>;<ul>
<li><code>ISPEC = Nxxx</code>: Number of subsequent input lines for specification of pressure variation</li>
</ul>
</li>
<li><code>LOTYPE = BOUN</code>:<ul>
<li><code>ISPEC = NBOUND</code>: Number of nodes with change in boundary conditions.</li>
</ul>
</li>
<li><code>LOTYPE = WINC</code>:<ul>
<li><code>ISPEC = Nxxx</code>: Number of subsequent input lines for specification of winch run</li>
</ul>
</li>
<li><code>LOTYPE = GROW</code>:<ul>
<li><code>ISPEC = 0</code> (default): No scaling of growth profile.</li>
<li><code>ISPEC = 1</code>: Number of subsequent input lines for specification of growth scaling.</li>
</ul>
</li>
<li><code>LOTYPE = WIND</code>:<ul>
<li><code>ISPEC = 0</code> (default): No wind on turbine blades</li>
<li><code>ISPEC = 1</code>: Number of subsequent input lines for specification of wind on turbine blades.</li>
</ul>
</li>
<li><code>ISPEC</code> is dummy for other load types</li>
</ul>
</li>
</ul>
<p>Note that some static loads will be incremented over <code>NSTEP</code> load steps while others will be activated at the beginning of the load group. For example volume forces and current forces are incremented over the specified load steps while element memory and contact forces are activated at the beginning of the load group in which they are specified.</p>
<p>Volume forces have to be applied in the first specified load group in case of <code>CATFEM</code> or <code>STAFEM</code> analysis. For <code>CATFEM</code> analysis the number of load steps in this load group has to be one (<code>NSTEP = 1</code>).</p>
<h4><a class="anchor" id="stamod_b_incremental_load_pipe"></a>
Pipe-in-pipe contact; One input line given if LOTYPE=PIPE and ISPEC = 1</h4>
<div class="fragment"><div class="line">CHPCNT</div>
</div><!-- fragment --><ul>
<li><code>CHPCNT: character</code>:<ul>
<li><code>= ENTERED</code></li>
<li><code>= NOT ENTERED</code></li>
</ul>
</li>
</ul>
<h4><a class="anchor" id="stamod_b_incremental_load_temperature"></a>
Temperature variation, NLSPEC input lines only given if LOTYPE = TEMP</h4>
<div class="fragment"><div class="line">LINE-ID ISEG IEC TEMP</div>
</div><!-- fragment --><ul>
<li><code>LINE-ID: character(8)</code>: Reference to line identifier</li>
<li><code>ISEG: integer/character</code>: Segment number<ul>
<li><code>= 0</code> / "ALL": All segments in specified line</li>
</ul>
</li>
<li><code>IEL: integer/character</code>: Element number<ul>
<li><code>= 0</code> / "ALL": All elements in specified line</li>
</ul>
</li>
<li><code>Temp: real</code>: Temperature at end of temperature variation</li>
</ul>
<p>The temperature is varied linearly during the load group from the starting temperature given in the cross-sectional data in <code>INPMOD</code> and ending with the temperature specified here.</p>
<p>A linear variation of temperature over a sequence of elements may be specified by giving a negative element number at the second end of the linear variation</p>
<h4><a class="anchor" id="stamod_b_incremental_load_pressure"></a>
Pressure variation, NLSPEC input lines if LOTYPE = PRES</h4>
<div class="fragment"><div class="line">MRL-ID PRESSI DPRESS VVELI</div>
</div><!-- fragment --><ul>
<li><code>MRL-ID: character(8)</code>: Reference to Main Riser Line identifier</li>
<li><code>PRESSI: real, default: 0</code>: Final pressure at inlet end <img class="formulaInl" alt="$ \mathrm{ \left[ F/L^2 \right]} $" src="form_177.png"/></li>
<li><code>DPRESS: real, default: 0</code>: Final pressure drop <img class="formulaInl" alt="$ \mathrm{ \left[ F/L^3 \right]} $" src="form_391.png"/></li>
<li><code>VVELI: real, default: 0</code>: Final fluid velocity <img class="formulaInl" alt="$ \mathrm{ \left[ L^3/T \right]} $" src="form_392.png"/><ul>
<li>Dummy in present version</li>
</ul>
</li>
</ul>
<h4><a class="anchor" id="stamod_b_incremental_load_boundary"></a>
Boundary changes, 2 x NBOUND input lines if LOTYPE = BOUN</h4>
<p>Identification of node for boundary change </p>
<div class="fragment"><div class="line">IREF-ID ILSEG ILNODE IOP</div>
</div><!-- fragment --><ul>
<li><code>IREF-ID: character(8)</code>: Reference to line or supernode identifier.</li>
<li><code>ILSEG: integer</code>:<ul>
<li>If <code>IREF-ID</code> refers to a line, <code>ILSEG</code> is the segment number within this line</li>
<li>If <code>IREF-ID</code> refers to a supernode, <code>ILSEG</code> must be zero</li>
</ul>
</li>
<li><code>ILNODE: integer</code>:<ul>
<li>If <code>IREF-ID</code> refers to a line, <code>ILNODE</code> is the node number within segment <code>ILSEG</code></li>
<li>If <code>IREF-ID</code> refers to a supernode, <code>ILNODE</code> must be zero</li>
</ul>
</li>
<li><code>IOP: integer</code>: Parameter for boundary change option<ul>
<li><code>= 0</code>: Boundary conditions: fixed, pre-scribed or free</li>
<li><code>= -1</code>: Boundary conditions: rigid node connection (The node will become a slave node.)</li>
</ul>
</li>
</ul>
<p>Ordinary (line end) supernodes and SIMO body nodes with <code>CHLOCA_OPT='POSI'</code> may have boundary change.</p>
<p>Status for nodal degrees of freedom. To be given if <code>IOP = 0</code> </p>
<div class="fragment"><div class="line">IPOS IX IY IZ IRX IRY IRZ</div>
</div><!-- fragment --><ul>
<li><code>IPOS: integer</code>: Boundary condition type<ul>
<li><code>IPOS = 0</code>: The node is fixed in global system</li>
<li><code>IPOS = N</code>: The node is attached to support vessel no N</li>
</ul>
</li>
<li><code>IX: integer</code>: Boundary condition code for translation in X-direction<ul>
<li><code>IX = 0</code>: Free</li>
<li><code>IX = 1</code>: Fixed of prescribed</li>
</ul>
</li>
<li><code>IY: integer</code>: Boundary condition code for translation in Y-direction<ul>
<li>Same interpretation as for <code>IX</code>.</li>
</ul>
</li>
<li><code>IZ: integer</code>: Boundary condition code for translation in Z-direction<ul>
<li>Same interpretation as for <code>IX</code>.</li>
</ul>
</li>
<li><code>IRX: integer</code>: Boundary condition code for rotation around X-direction<ul>
<li>Same interpretation as for <code>IX</code>.</li>
</ul>
</li>
<li><code>IRY: integer</code>: Boundary condition code for rotation around Y-direction<ul>
<li>Same interpretation as for <code>IX</code>.</li>
</ul>
</li>
<li><code>IRZ: integer</code>: Boundary condition code for rotation around Z-direction<ul>
<li>Same interpretation as for <code>IX</code>.</li>
</ul>
</li>
</ul>
<p>Identification of master node. To be given if <code>IOP = -1</code> </p>
<div class="fragment"><div class="line">LINE-ID ILSEG ILNODE</div>
</div><!-- fragment --><ul>
<li><code>LINE-ID: character(8)</code>: Reference to line identifier</li>
<li><code>ILSEG: integer</code>: Segment number within the actual line</li>
<li><code>ILNODE: integer</code>: Local node number within segment</li>
</ul>
<h4><a class="anchor" id="stamod_b_incremental_load_winch"></a>
Winch run, NLSPEC input lines only given if LOTYPE = WINC</h4>
<div class="fragment"><div class="line">IWINCH WILNG</div>
</div><!-- fragment --><ul>
<li><code>IWINCH: integer</code>: Line number</li>
<li><code>WILNG: real</code>: Total run length <img class="formulaInl" alt="$ \mathrm{[L]}$" src="form_75.png"/></li>
</ul>
<p><code>WILNG &gt; 0</code>: winching out, i.e. the winch run will increase the active length.</p>
<h4><a class="anchor" id="stamod_b_incremental_load_growth"></a>
Growth profile, ISPEC=1 input lines only given if LOTYPE = GROW</h4>
<div class="fragment"><div class="line">GFAC</div>
</div><!-- fragment --><ul>
<li><code>GFAC: real, default: 1.0</code>: Scaling of growth profile</li>
</ul>
<h4><a class="anchor" id="stamod_b_incremental_load_wind"></a>
Wind force, ISPEC=1 input lines only given if LOTYPE = WIND</h4>
<div class="fragment"><div class="line">WindOnTurbineBlades</div>
</div><!-- fragment --><ul>
<li><code>WindOnTurbineBlades: character(8), default: OFF</code>: Code for wid loads on turbine blades<ul>
<li><code>WindOnTurbineBlades = OFF</code>: No wind loads on turbine blades in static analysis.</li>
<li><code>WindOnTurbineBlades = ON</code>: Wind loads on turbine blades in static analysis.</li>
</ul>
</li>
</ul>
<p>Note that wind loads will be applied on turbine blades and the rest of the structure in dynamic analysis.</p>
<h2><a class="anchor" id="stamod_b_define"></a>
Define stressfree configuration</h2>
<p>This data group is optionally available for AR systems. It enables the user to define an arbitrary stressfree configuration without having to establish a complex line/supernode system model. The option is useful for effective modelling of pre-bent sections.</p>
<p>This data group will redefine the stressfree configuration, but will not affect the coordinates for static equilibrium position given as input to <code>INPMOD</code>, data group <a class="el" href="a00010.html#inpmod_b_arbitrary_specification">Specification of boundary conditions, stressfree configuration and static equilibrium configuration</a>.</p>
<h3><a class="anchor" id="stamod_b_define_data"></a>
Data group identifier</h3>
<div class="fragment"><div class="line">DEFIne STREssfree CONFiguration </div>
</div><!-- fragment --><h3><a class="anchor" id="stamod_b_define_file_name"></a>
File name</h3>
<div class="fragment"><div class="line">CHFCON</div>
</div><!-- fragment --><ul>
<li><code>CHFCON: character(80)</code>: File name with definition of stress free configuration</li>
</ul>
<h3><a class="anchor" id="stamod_b_define_file_format"></a>
File format</h3>
<div class="fragment"><div class="line">KFORM</div>
</div><!-- fragment --><ul>
<li><code>KFORM: integer, default: 1</code>: Code for file format<ul>
<li><code>KFORM = 1</code>: Stress free co-ordinates given for all <code>FEM</code>-nodes in increasing node number order</li>
</ul>
</li>
</ul>
<h2><a class="anchor" id="stamod_b_bottom"></a>
Bottom geometry file</h2>
<p>This data group is given if <code>IBOT 3D = 1</code> in the <code>INPMOD</code> input file, and allows the user to define an uneven seabed, using depth data in a regular grid with equidistant spacing.</p>
<h3><a class="anchor" id="stamod_b_bottom_data"></a>
Data group identifier</h3>
<div class="fragment"><div class="line">BOTTom GEOMetry FILE </div>
</div><!-- fragment --><h3><a class="anchor" id="stamod_b_bottom_file"></a>
File name</h3>
<div class="fragment"><div class="line">CHFBOT</div>
</div><!-- fragment --><ul>
<li><code>CHFBOT: character(80)</code>: File name with seabed geometry data</li>
</ul>
<p>The content of this file is described in <a class="el" href="a00012.html#stamod_description_define_uneven">Define uneven seabed geometry</a>.</p>
<h3><a class="anchor" id="stamod_b_bottom_coordinates"></a>
Coordinates of the seabed file reference system</h3>
<div class="fragment"><div class="line">XOS YOS ZOS ANGOS</div>
</div><!-- fragment --><ul>
<li><code>XOS: real, default: 0</code>: x-coordinate of the origin of the seabed file reference system, in the global reference system <img class="formulaInl" alt="$ \mathrm{[L]}$" src="form_75.png"/></li>
<li><code>YOS: real, default: 0</code>: y-coordinate of the origin of the seabed file reference system, in the global reference system <img class="formulaInl" alt="$ \mathrm{[L]}$" src="form_75.png"/></li>
<li><code>ZOS: real, default: 0</code>: z-coordinate of the origin of the seabed file reference system, in the global reference system <img class="formulaInl" alt="$ \mathrm{[L]}$" src="form_75.png"/></li>
<li><code>ANGOS: real, default: 0</code>: Angle between the x-axis of the seabed file reference system and the x-axis of the global reference system <img class="formulaInl" alt="$ \mathrm{[deg]}$" src="form_76.png"/></li>
</ul>
<h1><a class="anchor" id="stamod_c"></a>
Data Group C: Static Analysis with Parameter Variation</h1>
<h2><a class="anchor" id="stamod_c_parameter"></a>
Parameter variation definition</h2>
<h3><a class="anchor" id="stamod_c_parameter_data_one"></a>
Data group identifier, one input line</h3>
<div class="fragment"><div class="line">PARAmeter VARIation DEFInition </div>
</div><!-- fragment --><h3><a class="anchor" id="stamod_c_parameter_number"></a>
Number of variations and variation codes</h3>
<div class="fragment"><div class="line">NSTVAR IOFPOS ICUVAR IFOVAR MAXIPV RACUPV CHNORM EACUPV</div>
</div><!-- fragment --><ul>
<li><code>NSTVAR: integer</code>: Number of steps in parameter variations</li>
<li><code>IOFPOS: integer, default: 0</code>: Code for static offset variation<ul>
<li><code>IOFPOS = 0</code>: The parameter is not varied</li>
<li><code>IOFPOS = 1</code>: The parameter is varied in <code>NSTVAR</code> steps according to subsequent specification</li>
</ul>
</li>
<li><code>ICUVAR: integer, default: 0</code>: Code for current variation<ul>
<li><code>ICUVAR = 0</code>: The parameter is not varied</li>
<li><code>ICUVAR = 1</code>: The parameter is varied in <code>NSTVAR</code> steps according to subsequent specification</li>
</ul>
</li>
<li><code>IFOVAR: integer, default: 0</code>: Code for specified force variation<ul>
<li><code>IFOVAR = 0</code>: The parameter is not varied</li>
<li><code>IFOVAR = 1</code>: The parameter is varied in <code>NSTVAR</code> steps according to subsequent specification</li>
</ul>
</li>
<li><code>MAXIPV: integer, default: 1</code>: Maximum number of iterations for each variation</li>
<li><code>RACUPV: real, default:</code> <img class="formulaInl" alt="$ 10^{-5}$" src="form_393.png"/>: Required accuracy measured by displacement norm</li>
<li><code>CHNORM: character(4), default: DISP</code>: Convergence norm switch<ul>
<li><code>= DISP</code>: Use the default Euclidean displacement norm only</li>
<li><code>= BOTH</code>: Use both the default Euclidean displacement norm and the energy norm</li>
</ul>
</li>
<li><code>EACUPV: real, default:</code> <img class="formulaInl" alt="$ 10^{-5} $" src="form_394.png"/>: Required accuracy measured by energy norm<ul>
<li>Dummy if <code>CHNORM=DISP</code></li>
</ul>
</li>
</ul>
<p>The total number of load steps in parameter variation is <code>NSTVAR</code>.</p>
<p>All parameter for which variations are specified, are varied simultaneously</p>
<p>Information about parameter values are to be specified in the subsequent data groups. The initial configuration as specified according to data section B is automatically taken as the first case.</p>
<p><code>ICURIN</code> must be greater than zero and <code>CURFAC</code> must be 1.0 (See <a class="el" href="a00012.html#stamod_b_definition_external1">External, static loads</a>).</p>
<p>See also <a class="el" href="a00012.html#stamod_gen_comment">Note: Static Analysis with Fixed Parameters and Parameter Variation</a>.</p>
<h3><a class="anchor" id="stamod_c_parameter_load"></a>
Load types to be activated. One line for each load type. Optional input, maximum 4 specifications.</h3>
<div class="fragment"><div class="line">LOTYPE ISPEC</div>
</div><!-- fragment --><ul>
<li><code>LOTYPE: character(4)</code>: Load type to be applied<ul>
<li><code>= FRIC</code>: Activate bottom friction forces</li>
<li><code>= SPRI</code>: Activate global springs</li>
<li><code>= MEMO</code>: Activate material memory formulation (Isotropic/kinematic hardening)</li>
<li><code>= BOUN</code>: Boundary change</li>
</ul>
</li>
<li><code>ISPEC: integer</code>: Parameter used for further description of applied load type:<ul>
<li><code>LOTYPE = BOUN</code>:<ul>
<li><code>ISPEC = NBOUND</code>; Number of nodes with change in boundary conditions.</li>
</ul>
</li>
<li><code>ISPEC</code> is dummy for other load types</li>
</ul>
</li>
</ul>
<p>If specified load type is activated before, the input given here is disregarded.</p>
<p>Activation of sea floor friction is given by <code>FRIC</code>.</p>
<h4><a class="anchor" id="stamod_c_parameter_load_specification"></a>
Specification of boundary change, 2 x NBOUND lines</h4>
<p>Identification of node for boundary change </p>
<div class="fragment"><div class="line">IREF-ID ILSEG ILNODE IOP</div>
</div><!-- fragment --><ul>
<li><code>IREF-ID: character(8)</code>: Reference to line or supernode identifier.</li>
<li><code>ILSEG: integer</code>:<ul>
<li>If <code>IREF-ID</code> refers to a line, <code>ILSEG</code> is the segment number within this line</li>
<li>If <code>IREF-ID</code> refers to a supernode, <code>ILSEG</code> must be zero</li>
</ul>
</li>
<li><code>ILNODE: integer</code>:<ul>
<li>If <code>IREF-ID</code> refers to a line, <code>ILNODE</code> is the node number within segment <code>ILSEG</code></li>
<li>If <code>IREF-ID</code> refers to a supernode, <code>ILNODE</code> must be zero</li>
</ul>
</li>
<li><code>IOP: integer</code>: Parameter for boundary change option<ul>
<li><code>= 0</code>: Boundary conditions: fixed, pre-scribed or free</li>
<li><code>= -1</code>: Boundary conditions: rigid node connection (The node will become a slave node.)</li>
</ul>
</li>
</ul>
<p>Ordinary (line end) supernodes and SIMO body nodes with <code>CHLOCA_OPT='POSI'</code> may have boundary change.</p>
<p>Status for nodal degrees of freedom. To be given if <code>IOP = 0</code> </p>
<div class="fragment"><div class="line">IPOS IX IY IZ IRX IRY IRZ</div>
</div><!-- fragment --><ul>
<li><code>IPOS: integer</code>: Boundary condition type<ul>
<li><code>IPOS = 0</code>: The node is fixed in global system</li>
<li><code>IPOS = N</code>: The node is attached to support vessel no N</li>
</ul>
</li>
<li><code>IX: integer</code>: Boundary condition code for translation in X-direction<ul>
<li><code>IX = 0</code>: Free</li>
<li><code>IX = 1</code>: Fixed of prescribed</li>
</ul>
</li>
<li><code>IY: integer</code>: Boundary condition code for translation in Y-direction<ul>
<li>Same interpretation as for <code>IX</code>.</li>
</ul>
</li>
<li><code>IZ: integer</code>: Boundary condition code for translation in Z-direction<ul>
<li>Same interpretation as for <code>IX</code>.</li>
</ul>
</li>
<li><code>IRX: integer</code>: Boundary condition code for rotation around X-direction<ul>
<li>Same interpretation as for <code>IX</code>.</li>
</ul>
</li>
<li><code>IRY: integer</code>: Boundary condition code for rotation around Y-direction<ul>
<li>Same interpretation as for <code>IX</code>.</li>
</ul>
</li>
<li><code>IRZ: integer</code>: Boundary condition code for rotation around Z-direction<ul>
<li>Same interpretation as for <code>IX</code>.</li>
</ul>
</li>
</ul>
<p>Identification of master node. To be given if <code>IOP = -1</code> </p>
<div class="fragment"><div class="line">LINE-ID ILSEG ILNODE </div>
</div><!-- fragment --><ul>
<li><code>LINE-ID: character(8)</code>: Reference to line ID</li>
<li><code>ILSEG: integer</code>: Segment number within the actual line</li>
<li><code>ILNODE: integer</code>: Local node number within segment</li>
</ul>
<h3><a class="anchor" id="stamod_c_parameter_variation"></a>
Variation of static positions</h3>
<p>This data group is relevant only if <code>IOFPOS=1</code>.</p>
<h4><a class="anchor" id="stamod_c_parameter_data_2"></a>
Data group identifier</h4>
<div class="fragment"><div class="line">STATic OFFSet INCRements </div>
</div><!-- fragment --><h4><a class="anchor" id="stamod_c_parameter_static"></a>
Static position increments</h4>
<div class="fragment"><div class="line">CHIREF DXOFF DYOFF DZOFF IROT DROT</div>
</div><!-- fragment --><ul>
<li><code>CHIREF: character(8)</code>: Reference to moving point<ul>
<li><code>CHIREF = -IVES</code>: Support vessel number <code>IVES</code></li>
<li><code>CHIREF = SNOD_ID</code>: Supernode identifier. <code>SNOD_ID</code> must refer to a supernode with specified position</li>
</ul>
</li>
<li><code>DXOFF: real, default: 0</code>: Displacement increment, X-direction <img class="formulaInl" alt="$ \mathrm{[L]}$" src="form_75.png"/></li>
<li><code>DYOFF: real, default: 0</code>: Displacement increment, Y-direction <img class="formulaInl" alt="$ \mathrm{[L]}$" src="form_75.png"/></li>
<li><code>DZOFF: real, default: 0</code>: Displacement increment, Z-direction <img class="formulaInl" alt="$ \mathrm{[L]}$" src="form_75.png"/></li>
<li><code>IROT: integer, default: 0</code>: Rotation code<ul>
<li><code>IROT = 0</code>: No rotation</li>
<li><code>IROT = 1</code>: The given rotation is taken about X-axis</li>
<li><code>IROT = 2</code>: The given rotation is taken about Y-axis</li>
<li><code>IROT = 3</code>: The given rotation is taken about Z-axis</li>
</ul>
</li>
<li><code>DROT: real, default: 0</code>: Rotation increment <img class="formulaInl" alt="$ \mathrm{[deg]}$" src="form_76.png"/><ul>
<li>Dummy if <code>IROT=0</code></li>
</ul>
</li>
</ul>
<p>If a support vessel is specified (<code>IREF=-IVES</code>) the displacement increments refer to the support vessel coordinate system. Otherwise the increments refer to the global coordinate system.</p>
<p>Only rotation around the Z-axis may be given if <code>IREF = -IVES</code></p>
<p>If the supernode has boundary conditions specified in a skew co-ordinate system or in the vessel system, displacements and the rotation increment <code>DROT</code> take place in the skew / vessel system. It should also be noted that the orientation of such a skew co-ordinate system is kept constant during the static position incrementation (relevant for AR systems only).</p>
<h2><a class="anchor" id="stamod_c_variation_of_current"></a>
Variation of current velocity and direction</h2>
<p>This data group is relevant only if <code>ICUVAR=1</code>.</p>
<h3><a class="anchor" id="stamod_c_variation_of_current_data"></a>
Data group identifier, one input line</h3>
<div class="fragment"><div class="line">CURRent VARIation INCRements </div>
</div><!-- fragment --><h3><a class="anchor" id="stamod_c_variation_of_current_velocity"></a>
Current velocity and direction increments</h3>
<div class="fragment"><div class="line">DCUVEL DCUDIR</div>
</div><!-- fragment --><ul>
<li><code>DCUVEL: real, default: 0</code>: Current velocity increment <img class="formulaInl" alt="$ \mathrm{[L/T]}$" src="form_68.png"/></li>
<li><code>DCUDIR: real, default: 0</code>: Current direction increment <img class="formulaInl" alt="$ \mathrm{[deg]}$" src="form_76.png"/></li>
</ul>
<p>In the case of multilayer current specification, these increments are interpreted as follows.</p>
<ul>
<li>DCUVEL: This applies directly to the uppermost layer. The lower layers are incremented in the same proportion, so that the shape of the current profile is maintained.</li>
<li>DCUDIR: This applies to all current layers, so that the whole current profile is rotated the same amount.</li>
</ul>
<h2><a class="anchor" id="stamod_c_variation_of_specified"></a>
Variation of specified forces</h2>
<p>This data group is relevant only if <code>IFOVAR=1</code> and <code>NLCOMP &gt;= 1</code> (See <a class="el" href="a00012.html#stamod_b_definition">Definition of subsequent input</a>).</p>
<h3><a class="anchor" id="stamod_c_variation_of_specified_data"></a>
Data group identifier, one input line</h3>
<div class="fragment"><div class="line">SPECified FORCe INCRements </div>
</div><!-- fragment --><h3><a class="anchor" id="stamod_c_variation_of_specified_force"></a>
Force increments, NLCOMP input lines to be given</h3>
<div class="fragment"><div class="line">DRLMAG</div>
</div><!-- fragment --><ul>
<li><code>DRLMAG: real, default: 0</code>: Force increment on specified forces <code>RLMAG</code> (F or FL).<ul>
<li>See <a class="el" href="a00012.html#stamod_b_definition_additional">Additional, static load components</a>.</li>
</ul>
</li>
</ul>
<h2><a class="anchor" id="stamod_c_control"></a>
Control parameters for printing of results</h2>
<h3><a class="anchor" id="stamod_c_control_data"></a>
Data group identifier, one input line</h3>
<div class="fragment"><div class="line">STAMod PRINt CONTrol </div>
</div><!-- fragment --><h3><a class="anchor" id="stamod_c_control_parameters"></a>
Control parameters for print of results from static parameter variation analysis</h3>
<div class="fragment"><div class="line">ISTEP ISFOR ISPOS</div>
</div><!-- fragment --><ul>
<li><code>ISTEP: integer, default: 1</code>: Step interval for print of specified parameters.<ul>
<li>Print is given for the following steps: 1, 1+<code>ISTEP</code>, 1+2 <img class="formulaInl" alt="$\times$" src="form_395.png"/> <code>ISTEP</code>, 1+3 <img class="formulaInl" alt="$\times$" src="form_395.png"/> <code>ISTEP, ..., NSTVAR</code></li>
<li><code>ISTEP = 1</code>: Gives print of results for all variation steps</li>
</ul>
</li>
<li><code>ISFOR: integer, default: 1</code>: Parameter for print of forces<ul>
<li><code>ISFOR = 0</code>: No print of external forces</li>
<li><code>ISFOR = 1</code>: Print of external force components in global x, y, z direction at all supernodes with the following status codes: <code>TSNFX, TSNFX2, TSNPOSI1</code></li>
<li>Not yet implemented</li>
</ul>
</li>
<li><code>ISPOS: integer, default: 1</code>: Parameter for print of position<ul>
<li><code>ISPOS = 0</code>: No print of positions</li>
<li><code>ISPOS = 1</code>: Print of x, y and z coordinates for all free supernodes (i.e. status code <code>TSNBRA</code> and <code>TSNFRE</code>)</li>
</ul>
</li>
</ul>
<h1><a class="anchor" id="stamod_sawu"></a>
Static Analysis with Updated Drag Forces</h1>
<p>An important consequence of VIV response is increased in-line current forces. One of the key results from the <code>VIVANA</code> program is therefore drag amplification factors along the structure. The objective of this input is to enable static and dynamic analysis using the updated drag forces.</p>
<p>To use this option the <code>RIFLEX</code> program modules must be run in the following order:</p>
<ul>
<li><code>INPMOD</code></li>
<li><code>STAMOD</code></li>
<li><code>VIVANA</code></li>
<li><code>STAMOD</code> with the drag amplification data group specified</li>
</ul>
<p>Note that drag amplication cannot be used in combination with marine growth profile specification (<a class="el" href="a00010.html#inpmod_c_growth">Growth - Specification of marine growth profile</a> ).</p>
<h2><a class="anchor" id="stamod_sawu_data"></a>
Data group identifier, one input line</h2>
<div class="fragment"><div class="line">DRAG AMPLIFICATION INPUT </div>
</div><!-- fragment --><h2><a class="anchor" id="stamod_sawu_load"></a>
Specification of file for input of drag amplification, one input line</h2>
<div class="fragment"><div class="line">CHFDRG CHIOP</div>
</div><!-- fragment --><ul>
<li><code>CHFDRG: character(60)</code>: File with drag amplification coefficient; e.g case22_vivana.mpf</li>
<li><code>CHIOP: character(60)</code>: Format of file with drag amplification coefficients</li>
</ul>
<p>The <code>CHFDRG</code> file may be generated by running <code>VIVANA</code>.</p>
<p>The only file type currently available is the MatrixPlot file format. Thus; <code>CHIOP = MPF</code>.</p>
<h1><a class="anchor" id="stamod_description"></a>
Description of Additional Input Files</h1>
<h2><a class="anchor" id="stamod_description_define_stressfree"></a>
Define Stressfree Configuration</h2>
<p>The file "CHFCON" specified in <a class="el" href="a00012.html#stamod_b">Data Group B: Static Analysis with Fixed Parameters</a>, contains definition of stressfree configuration. The file is a free format sequential ASCII-file.</p>
<p>The file description depends on the parameter "KFORM" specified in <a class="el" href="a00012.html#stamod_b_stafem">Finite element analysis from start configuration, STAFEM</a>.</p>
<p>File description: <code>KFORM = 1</code>.</p>
<h3><a class="anchor" id="stamod_description_define_stressfree_number"></a>
Number of nodes, one input line</h3>
<div class="fragment"><div class="line">NFSNOD</div>
</div><!-- fragment --><ul>
<li><code>NFSNOD: integer</code>: Number of <code>FEM</code>-nodes for which coordinates for stressfree configuration are specified. In this version <code>NFSNOD</code> must be equal to the total number of <code>FEM</code>-nodes</li>
</ul>
<h3><a class="anchor" id="stamod_description_define_stressfree_coordinates"></a>
Coordinates for stressfree configuration, NFSNOD input lines</h3>
<div class="fragment"><div class="line">INOD X0 Y0 Z0</div>
</div><!-- fragment --><ul>
<li><code>INOD: integer</code>: Node number 1 &gt;= <code>INOD</code> &gt;= <code>NFSNOD</code></li>
<li><code>X0: real</code>: x-coordinate describing stressfree configuration</li>
<li><code>Y0: real</code>: y-coordinate describing stressfree configuration</li>
<li><code>Z0: real</code>: z-coordinate describing stressfree configuration</li>
</ul>
<p>The coordinate must be consistent with the stressfree element length</p>
<h2><a class="anchor" id="stamod_description_define_start"></a>
Define Start Configuration</h2>
<p>The file 'CHFSTA' specified in <a class="el" href="a00012.html#stamod_b_stafem">Finite element analysis from start configuration, STAFEM</a>, contains definition of start configuration. The file is a free format sequential ASCII-file.</p>
<p>The file description depends on the parameter 'KFORM' specified in <a class="el" href="a00012.html#stamod_b_stafem">Finite element analysis from start configuration, STAFEM</a>.</p>
<p>File description: <code>KFORM = 1</code>.</p>
<h3><a class="anchor" id="stamod_description_define_start_number"></a>
Number of nodes, one input line</h3>
<div class="fragment"><div class="line">NFSNOD</div>
</div><!-- fragment --><ul>
<li><code>NFSNOD: integer</code>: Number of <code>FEM</code>-nodes for which coordinates for stressfree configuration are specified. In this version <code>NFSNOD</code> must be equal to the total number of <code>FEM</code>-nodes</li>
</ul>
<h3><a class="anchor" id="stamod_description_define_start_coordinates"></a>
Coordinates for start configuration, NFSNOD input lines</h3>
<div class="fragment"><div class="line">INOD X0 Y0 Z0 T11 T12 T13 T21 T22 T23 T31 T32 T33</div>
</div><!-- fragment --><ul>
<li><code>INOD: integer</code>: Node number 1 &gt;= <code>INOD</code> &gt;= <code>NFSNODI</code></li>
<li><code>X0: real</code>: x-coordinate describing stressfree configuration</li>
<li><code>Y0: real</code>: y-coordinate describing stressfree configuration</li>
<li><code>Z0: real</code>: z-coordinate describing stressfree configuration</li>
</ul>
<p>Nodal base vector system:</p>
<ul>
<li>x-direction of node system referred to the global system<ul>
<li><code>T11: real, default: 1</code>: component in global x-direction</li>
<li><code>T12: real, default: 0</code>: component in global y-direction</li>
<li><code>T13: real, default: 0</code>: component in global z-direction</li>
</ul>
</li>
<li>y-direction of node system referred to the global system<ul>
<li><code>T21: real, default: 0</code>:</li>
<li><code>T22: real, default: 1</code>:</li>
<li><code>T23: real, default: 0</code>:</li>
</ul>
</li>
<li>z-direction of node system referred to the global system<ul>
<li><code>T31: real, default: 0</code>:</li>
<li><code>T32: real, default: 0</code>:</li>
<li><code>T33: real, default: 1</code>:</li>
</ul>
</li>
</ul>
<h2><a class="anchor" id="stamod_description_define_uneven"></a>
Define uneven seabed geometry</h2>
<p>The seabed geometry data is given on a regularly spaced grid. The grid can be rotated and translated relatively to the reference system of the seabed geometry file. (In addition the reference system of the seabed geometry file can be rotated relatively to the global reference system ref. <a class="el" href="a00012.html#stamod_b_bottom_coordinates">Coordinates of the seabed file reference system</a>).</p>
<p>A MATLAB script is available, to generate such a file from data given as a set of x, y, z coordinates</p>
<p>At each step of the static and dynamic analysis, it is checked that every node of the model has x and y coordinates that are within the grid. Excursions from the grid will cause the program to terminate.</p>
<h3><a class="anchor" id="stamod_description_define_uneven_description"></a>
Description text of geometry</h3>
<div class="fragment"><div class="line">CHBOTT</div>
</div><!-- fragment --><ul>
<li><code>CHBOTT: character</code>: Descriptive text of geometry</li>
</ul>
<h3><a class="anchor" id="stamod_description_define_uneven_grid_dimension"></a>
Grid dimension and extension, one input file</h3>
<div class="fragment"><div class="line">NGX NGY XSmin XSmax YSmin YSmax DGX DGY</div>
</div><!-- fragment --><ul>
<li><code>NGX: integer</code>: Number of points in the grid in the x direction</li>
<li><code>NGY: integer</code>: Number of points in the grid in the y direction</li>
<li><code>Xsmin: real</code>: Coordinate of the first point in the grid in the x direction <img class="formulaInl" alt="$ \mathrm{[L]}$" src="form_75.png"/></li>
<li><code>Xsmax: real</code>: Coordinate of the last point in the grid in the x direction <img class="formulaInl" alt="$ \mathrm{[L]}$" src="form_75.png"/>. Used to check consistency of the grid input and whether a node is outside the grid.</li>
<li><code>Ysmin: real</code>: Coordinate of the first point in the grid in the y direction <img class="formulaInl" alt="$ \mathrm{[L]}$" src="form_75.png"/></li>
<li><code>Ysmax: real</code>: Coordinate of the last point in the grid in the y direction <img class="formulaInl" alt="$ \mathrm{[L]}$" src="form_75.png"/>. Used to check consistency of the grid input and whether a node is outside the grid.</li>
<li><code>DGX: real</code>: Distance between grid points in the x direction <img class="formulaInl" alt="$ \mathrm{[L]}$" src="form_75.png"/></li>
<li><code>DGY: real</code>: Distance between grid points in the y direction <img class="formulaInl" alt="$ \mathrm{[L]}$" src="form_75.png"/></li>
</ul>
<p>The x and y coordinates of the grid corners and the distances between grid ponts are converted to integer values with unit <img class="formulaInl" alt="$\mathrm{[L/100]}$" src="form_396.png"/>.</p>
<h3><a class="anchor" id="stamod_description_define_uneven_grid_orientation"></a>
Grid orientation, one input line</h3>
<div class="fragment"><div class="line">XOL YOL ANGOL</div>
</div><!-- fragment --><ul>
<li><code>XOL: real</code>: x-coordinate of the origin of the grid, in the seabed file reference system <img class="formulaInl" alt="$ \mathrm{[L]}$" src="form_75.png"/></li>
<li><code>YOL: real</code>: y-coordinate of the origin of the grid, in the seabed file reference system <img class="formulaInl" alt="$ \mathrm{[L]}$" src="form_75.png"/></li>
<li><code>ANGOL: real</code>: Angle between the x axis of the grid and the x axis of the seabed file reference system <img class="formulaInl" alt="$ \mathrm{[deg]}$" src="form_76.png"/></li>
</ul>
<h3><a class="anchor" id="stamod_description_define_uneven_depths"></a>
Depths at gridpoint, NGY input lines</h3>
<div class="fragment"><div class="line">IZBOT1 ........ IZBOTngx</div>
</div><!-- fragment --><ul>
<li><code>IZBOT1: integer</code>: 100 <img class="formulaInl" alt="$ \times $" src="form_303.png"/> Depth at first x value <img class="formulaInl" alt="$\mathrm{[L/100]}$" src="form_396.png"/></li>
<li>.</li>
<li>.</li>
<li>.</li>
<li><code>IZBOTngx: integer</code>: 100 <img class="formulaInl" alt="$ \times $" src="form_303.png"/> Depth at last x value <img class="formulaInl" alt="$\mathrm{[L/100]}$" src="form_396.png"/></li>
</ul>
<p>The input line may be given over several lines of text by using the continuation character ‘&amp;’. </p>
</div></div><!-- contents -->
	</body>
</html>