<?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">Introduction </div>  </div>
</div><!--header-->
<div class="contents">
<div class="toc"><h3>Table of Contents</h3>
<ul><li class="level1"><a href="#introduction_purpose">Purpose of Program</a></li>
<li class="level1"><a href="#introduction_program">Program Documentation</a></li>
<li class="level1"><a href="#introduction_structure">Structure of Computer Program</a><ul><li class="level2"><a href="#introduction_structure_inpmod">INPMOD module</a></li>
<li class="level2"><a href="#introduction_structure_stamod">STAMOD module</a></li>
<li class="level2"><a href="#introduction_structure_dynmod">DYNMOD module</a></li>
<li class="level2"><a href="#introduction_structure_outmod">OUTMOD module</a></li>
</ul>
</li>
<li class="level1"><a href="#introduction_explanation">Explanation of Files Used</a><ul><li class="level2"><a href="#introduction_explanation_symbolic">Symbolic input/output files</a></li>
<li class="level2"><a href="#introduction_explanation_files_internal">Files for internal communication between modules</a></li>
<li class="level2"><a href="#introduction_explanation_files_external">Files for communication with external programs</a></li>
</ul>
</li>
<li class="level1"><a href="#introduction_applied">Applied Units and Physical Constants</a></li>
</ul>
</div>
<div class="textblock"><h1><a class="anchor" id="introduction_purpose"></a>
Purpose of Program</h1>
<p><code>RIFLEX</code> was developed as a tool for analysis of flexible marine riser systems, but is as well suited for any type of slender structure, such as mooring lines, umbilicals, and also for steel pipelines and conventional risers.</p>
<p>These slender structures may be characterized by:</p>
<ul>
<li>Small bending stiffness</li>
<li>Large deflection</li>
<li>Large upper end motion excitation</li>
<li>Nonlinear cross section properties</li>
<li>Complex cross section structure</li>
</ul>
<p>Due to the complex cross sections typical found for flexible pipes, a global cross section model is applied in <code>RIFLEX</code>. This means that cross section properties such as axial-, bending-, and torsional stiffness must be specified as input. Furthermore, structural response is always computed as global deformations and stress resultants (axial force, moments). Hence, local strains and stresses in different cross section layers and materials are not considered.</p>
<p>Nonlinear cross section behaviour is modelled by introducing nonlinear relations between global deformation parameters and stress resultant, i.e. curvature and moment; relative elongation and tension.</p>
<p>The program computes static and dynamic characteristics of the structure.</p>
<p>Static analysis comprises:</p>
<ul>
<li>Equilibrium configuration</li>
<li>Parameter variations of tension or position parameters, current velocity and direction</li>
</ul>
<p>Dynamic analysis comprises:</p>
<ul>
<li>Eigenvalue analysis, natural frequencies and mode shapes</li>
<li>Response to harmonic motion and wave excitation</li>
<li>Response to irregular wave- and motion excitation</li>
</ul>
<p>The program is based on a nonlinear finite element formulation. The following key features are included:</p>
<ul>
<li>Flexible modelling of simple as well as complex systems</li>
<li>Nonlinear time domain simulation of riser motions and forces</li>
<li>Nonlinear cross section properties</li>
<li>Generalized Morison type of load model Simplified analysis options:<ul>
<li>Static analyses, catenary approximations Linearized time domain simulation</li>
<li>Frequency domain analysis</li>
</ul>
</li>
</ul>
<h1><a class="anchor" id="introduction_program"></a>
Program Documentation</h1>
<p>The program documentation comprises:</p>
<ul>
<li>Theory Manual containing a description of mathematical models used in the program</li>
<li>User's Manual containing description of input and output</li>
<li>Release Notes for each release of the program</li>
</ul>
<h1><a class="anchor" id="introduction_structure"></a>
Structure of Computer Program</h1>
<p>The program system consists of four programs or modules communicating via the file system as shown in the figure below.</p>
<div class="image">
<img src="RIFLEX_UserManual_41_rev1_draft-1.png" alt="RIFLEX_UserManual_41_rev1_draft-1.png"/>
<div class="caption">
Structure of program system </div></div>
<p>A complete dynamic analysis must include a run of all modules. However, an efficient data base system simplifies the work during a complete study by storing input data and intermediate results. (I.e. problem description, static configurations, wave induced vessel motions and water particle velocities and accelerations).</p>
<p>Each module will be further detailed in the following.</p>
<h2><a class="anchor" id="introduction_structure_inpmod"></a>
INPMOD module</h2>
<p>The <code>INPMOD</code> module reads most input data and organizes a data base for use during subsequent analyses. Once the <code>INPMOD</code> module has been run, several analyses can be performed by the other modules without rerun of <code>INPMOD</code>.</p>
<h2><a class="anchor" id="introduction_structure_stamod"></a>
STAMOD module</h2>
<p>The <code>STAMOD</code> module performs several types of static analyses. The results may be used directly in parameter studies etc., and are also used to define the initial configuration for a succeeding dynamic analysis. Element mesh, stressfree configuration and key data for finite element analysis are also generated by <code>STAMOD</code> based on system data given as input to <code>INPMOD</code>.</p>
<h2><a class="anchor" id="introduction_structure_dynmod"></a>
DYNMOD module</h2>
<p>The <code>DYNMOD</code> module carries out time domain dynamic analyses based on the final static configuration, environment data and data to define motions applied as forced displacements in the analysis. It is possible to perform several dynamic analyses without rerun of <code>INPMOD</code> and <code>STAMOD</code>. Response time series are stored on file for further postprocessing by <code>OUTMOD</code>. In addition to dynamic response, natural frequencies and modeshapes can be calculated.</p>
<h2><a class="anchor" id="introduction_structure_outmod"></a>
OUTMOD module</h2>
<p><code>OUTMOD</code> performs postprocessing of selected results generated by <code>STAMOD</code> and <code>DYNMOD</code>. It is also possible to export time series via a standardized file format for further postprocessing by general purpose statistical analysis program (<code>STARTIMES</code>).</p>
<h1><a class="anchor" id="introduction_explanation"></a>
Explanation of Files Used</h1>
<p>In running the 5 different <code>RIFLEX</code> modules different kinds of files are needed. The files can be divided into the following categories:</p>
<ol type="1">
<li>Symbolic input/output files (i.e. readable ASCII files)</li>
<li>Binary files for internal communication between <code>RIFLEX</code> modules</li>
<li>Files for export of results for postprocessing</li>
</ol>
<p>An overview of files used is given in the figure <a class="el" href="a00002.html#File_system_for_communication_between_modules">File system for communication between modules</a>. A <code>RIFLEX</code> user will only need to specify input files for the <code>INPMOD</code>, <code>STAMOD</code>, <code>DYNMOD</code> and <code>OUTMOD</code> modules.</p>
<p>The internal file communication is organized via run command procedures and therefore hidden for the user. The file names and extensions may be adapted to the computers operating system and the actual run command procedures used. Description of the file name conventions used in the standard run command procedure supplied with a <code>RIFLEX</code> installation is given in <a class="el" href="a00008.html#how_to_run_standard">How to use Standard Run Command Procedures</a>.</p>
<p>Below is a brief description of the files used.</p>
<h2><a class="anchor" id="introduction_explanation_symbolic"></a>
Symbolic input/output files</h2>
<p>Each analysis module needs a symbolic data file to read input data from (extension <code>.inp</code>) and one symbolic file to print out major results (extension <code>.res</code>). These files are denoted:</p>
<ul>
<li><code>xxxxxx.inp</code>: symbolic input file to module <code>xxxxxx</code></li>
<li><code>xxxxxx.res</code>: symbolic result file from module <code>xxxxxx</code></li>
</ul>
<p><code>xxxxxx</code> here means either <code>INPMOD</code>, <code>STAMOD</code>, <code>DYNMOD</code> or <code>OUTMOD</code>, see the figure <a class="el" href="a00002.html#File_system_for_communication_between_modules">File system for communication between modules</a>. Description of data needed in the input files are described in Chapters 5-9 of the User Manual.</p>
<h2><a class="anchor" id="introduction_explanation_files_internal"></a>
Files for internal communication between modules</h2>
<p>Files for internal communication are binary, direct access data files in either <code>SAM-DMS</code> format (extension <code>.sam</code>) or in <code>FFILE</code> format (extension <code>.ffi</code>). See <code>RIFLEX</code> maintenance manual for further file format description.</p>
<p>A short description of the files used:</p>
<ul>
<li><code>ifninp.sam</code>: storage of all data given as input to the <code>INPMOD</code> module. System data read by <code>STAMOD</code> for generation of finite element model, wave and transfer function data read by <code>DYNMOD</code></li>
<li><code>ifnsys.sam</code>: contains system finite element model generated by <code>STAMOD</code></li>
<li><code>ifndmp.sam</code>: temporary storage of all system data. To be used in possible restart analysis in <code>STAMOD</code></li>
<li><code>ifnsta.ffi</code>: storage of results from static analysis</li>
<li><code>ifndyn.ffi</code>: storage of results from dynamic analysis</li>
<li><code>ifnirr.ffi</code>: storage of wave kinematics data for irregular dynamic analysis</li>
<li><code>ifnplo.ffi</code>: storage of plot data generated by <code>OUTMOD</code></li>
</ul>
<h2><a class="anchor" id="introduction_explanation_files_external"></a>
Files for communication with external programs</h2>
<p>The following files can optionally be applied to export results from <code>RIFLEX</code> for postprocessing by other programs:</p>
<ul>
<li><code>startimes.ts</code>: Export of response time series from <code>OUTMOD</code> for postprocessing by the general purpose statistical analysis program <code>STARTIMES</code>. File format is standard <code>STARTIMES</code> format (binary, direct access file)</li>
<li><code>ifrdyn.raf</code>: File for communication with general purpose program for advanced graphical presentation</li>
</ul>
<p><a class="anchor" id="File_system_for_communication_between_modules"></a> </p>
<div class="image">
<img src="RIFLEX_UserManual_41_rev1_draft-2.png" alt="RIFLEX_UserManual_41_rev1_draft-2.png"/>
<div class="caption">
File system for communication between modules</div></div>
<h1><a class="anchor" id="introduction_applied"></a>
Applied Units and Physical Constants</h1>
<p>Throughout the theory description a <em>consistent</em> set of units is used.</p>
<p>In the program input the user is allowed to select mass as well as force units. This implies that the user also has to specify the gravitational constant as the ratio of force to mass units <img class="formulaInl" alt="$\mathrm{[F/M]}$" src="form_0.png"/>. In order to allow inconsistent units, e.g. <img class="formulaInl" alt="$\mathrm{kN}$" src="form_1.png"/>, <img class="formulaInl" alt="$\mathrm{kg}$" src="form_2.png"/>, <img class="formulaInl" alt="$\mathrm{m}$" src="form_3.png"/>, <img class="formulaInl" alt="$\mathrm{s}$" src="form_4.png"/>, the acceleration in terms of <img class="formulaInl" alt="$\mathrm{F / M}$" src="form_5.png"/> ratio will be different from acceleration in terms of the ratio length to squared time <img class="formulaInl" alt="$\mathrm{[L / T^2]}$" src="form_6.png"/>. A constant <code>GCONS</code> is therefore introduced as a specification of the difference <code>GCONS</code> <img class="formulaInl" alt="$\mathrm{= \frac{F / M}{L / T^2}}$" src="form_7.png"/>. In the example case, <code>GCONS = 0.001</code>.</p>
 <table class="doxtable">
<tr>
<th align="left">Physical quantity </th><th align="left">Symbol </th><th align="left">Units, SI </th><th align="left">Modified SI <img class="formulaInl" alt="$\mathrm{(kN)}$" src="form_8.png"/>  </th></tr>
<tr>
<td align="left"><b>Basic</b> </td><td align="left"></td><td align="left"></td><td align="left"></td></tr>
<tr>
<td align="left">Time </td><td align="left"><img class="formulaInl" alt="$\mathrm{T}$" src="form_9.png"/> </td><td align="left"><img class="formulaInl" alt="$\mathrm{s}$" src="form_4.png"/> </td><td align="left"><img class="formulaInl" alt="$\mathrm{s}$" src="form_4.png"/> </td></tr>
<tr>
<td align="left">Length </td><td align="left"><img class="formulaInl" alt="$\mathrm{L}$" src="form_10.png"/> </td><td align="left"><img class="formulaInl" alt="$\mathrm{m}$" src="form_3.png"/> </td><td align="left"><img class="formulaInl" alt="$\mathrm{m}$" src="form_3.png"/> </td></tr>
<tr>
<td align="left">Mass </td><td align="left"><img class="formulaInl" alt="$\mathrm{M}$" src="form_11.png"/> </td><td align="left"><img class="formulaInl" alt="$\mathrm{kg}$" src="form_2.png"/> </td><td align="left"><img class="formulaInl" alt="$\mathrm{kg}$" src="form_2.png"/> </td></tr>
<tr>
<td align="left">Force </td><td align="left"><img class="formulaInl" alt="$\mathrm{F=ML / T^2}$" src="form_12.png"/> </td><td align="left"><img class="formulaInl" alt="$\mathrm{N}$" src="form_13.png"/> </td><td align="left"><img class="formulaInl" alt="$\mathrm{kN}$" src="form_1.png"/> </td></tr>
<tr>
<td align="left"><b>Derived</b> </td><td align="left"></td><td align="left"></td><td align="left"></td></tr>
<tr>
<td align="left">Pressure, stress </td><td align="left"><img class="formulaInl" alt="$\mathrm{P = F / L^2}$" src="form_14.png"/> </td><td align="left"><img class="formulaInl" alt="$\mathrm{N/m^2}$" src="form_15.png"/> </td><td align="left"><img class="formulaInl" alt="$\mathrm{kN/m^2}$" src="form_16.png"/> </td></tr>
<tr>
<td align="left">Velocity </td><td align="left"><img class="formulaInl" alt="$\mathrm{V = L / T}$" src="form_17.png"/> </td><td align="left"><img class="formulaInl" alt="$\mathrm{m/s}$" src="form_18.png"/> </td><td align="left"><img class="formulaInl" alt="$\mathrm{m/s}$" src="form_18.png"/> </td></tr>
<tr>
<td align="left"><b>Physical constants</b> </td><td align="left"></td><td align="left"></td><td align="left"></td></tr>
<tr>
<td align="left">Acceleration of gravity </td><td align="left"><code>G</code> <img class="formulaInl" alt="$\mathrm{\left[F / M\right]}$" src="form_19.png"/> </td><td align="left"><img class="formulaInl" alt="$9.81 \, \mathrm{N / kg}$" src="form_20.png"/> </td><td align="left"><img class="formulaInl" alt="$0.00981 \, \mathrm{kN / kg}$" src="form_21.png"/> </td></tr>
<tr>
<td align="left">Acceleration of gravity </td><td align="left"><code>G</code> <img class="formulaInl" alt="$\mathrm{\left[L / T^2\right]}$" src="form_22.png"/> </td><td align="left"><img class="formulaInl" alt="$9.81 \, \mathrm{m / s^2}$" src="form_23.png"/> </td><td align="left"><img class="formulaInl" alt="$9.81 \, \mathrm{m / s^2}$" src="form_23.png"/> </td></tr>
<tr>
<td align="left">Consistency of units </td><td align="left"><code>GCONS</code> </td><td align="left"><code>1</code> </td><td align="left"><code>0.001</code> </td></tr>
<tr>
<td align="left">Density of sea water </td><td align="left"><code>WATDEN</code> <img class="formulaInl" alt="$\mathrm{\left[M/L^3\right]}$" src="form_24.png"/> </td><td align="left"><img class="formulaInl" alt="$\mathrm{1025 \, kg/m^3}$" src="form_25.png"/> </td><td align="left"><img class="formulaInl" alt="$\mathrm{1025 \, kg/m^3}$" src="form_25.png"/> </td></tr>
</table>
</div></div><!-- contents -->
	</body>
</html>