<?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">General Line Data Specification </div>  </div>
</div><!--header-->
<div class="contents">
<div class="toc"><h3>Table of Contents</h3>
<ul><li class="level1"><a href="#ug_general_line_line_system">Line system definition</a><ul><li class="level2"><a href="#ug_general_line_line_system_topology">Topology specification</a></li>
<li class="level2"><a href="#ug_general_line_line_system_seafloor">Seafloor support condition (optional)</a></li>
<li class="level2"><a href="#ug_general_line_line_system_advanced">Advanced analysis option (optional)</a></li>
</ul>
</li>
<li class="level1"><a href="#ug_general_line_boundary">Boundary conditions and coordinates for line nodes</a></li>
<li class="level1"><a href="#ug_general_line_line_type">Line type definition</a></li>
<li class="level1"><a href="#ug_general_line_cross">Cross section description</a></li>
<li class="level1"><a href="#ug_general_line_nodal">Nodal component description</a></li>
</ul>
</div>
<div class="textblock"><p>General line data enables the user to model simple as well as complex line systems. Loads due to gravity, buoyancy, current and seafloor contact are accounted for. Several line systems may be modelled. Each line system may consist of one or several lines connected to one or several bodies and/or to earth.</p>
<p>Each line system is described in a finite element formulation. The quasi-static system responses are calculated at each time step during time domain analysis.</p>
<h3>Line system</h3>
<p>A line system is identified by a unique “line-system identifier”. The line system topology is in general described in terms of branching points and terminal points. These points are denoted <b>line nodes</b>. Line nodes are connected by simple <b>lines</b>. This means that the line system topology is uniquely determined by the connectivity between a number of defined <b>line nodes</b> and <b>lines</b>.</p>
<h3>Line node</h3>
<p>Line nodes are classified as <b>free</b>, <b>fixed</b>, or <b>prescribed</b>, depending on their boundary condition specification. Line nodes of type <b>fixed</b> are used for modelling termination at fixed structures, seafloor connection, etc. <b>Prescribed</b> line nodes are used for modelling supports with prescribed motions, i.e. connection to <b>bodies</b>.</p>
<p>A line node is identified by a unique “line-node-identifier”. This means that a line node may be referred several times in a system topology description, and also referred to by several line systems.</p>
<h3>Line and segment</h3>
<p>A line is a structural element between two line nodes. Its composition is described in a <b>line type</b> specification. The line type is specified in terms of a sequence of <b>segments</b> and <b>nodal components</b>. A <b>segment</b> has homogeneous <b>cross section</b> properties. For each segment a <b>cross section</b> type and a number of <b>elements</b> to be used for the finite element discretization, are specified, see the figure below. <b>Nodal components</b> (clump weights and buoys) may be specified at segment intersections.</p>
<p>The line is identified by a unique “line-identifier”. The line type is identified by a unique line-type-identifier. This means that a line type may be referred several times in the topology description of one or several line systems.</p>
<h3>Cross section and nodal component</h3>
<p>The cross section and the nodal component represent the elementary description of the mechanical properties. Cross section properties are given by axial stiffness, weight (in air and submerged) and drag coefficients (transverse and longitudinal). The vertical force and drag coefficient of nodal components may be depth dependent.</p>
<p>A cross section is identified by a unique “cross-section-identifier”, and a nodal component by a “nodal-component-identifier". Thus a cross section type or a nodal component type may be referred several times in the description of line types.</p>
<div class="image">
<img src="app-a_image037.png" alt="app-a_image037.png"/>
<div class="caption">
System definition terms</div></div>
<h4>1 input line</h4>
<div class="fragment"><div class="line">GENEral LINE DATA</div>
</div><!-- fragment --><h4>If the data shall be exported to HLA, 1 identification input line.</h4>
<div class="fragment"><div class="line">HLA EXPOrt</div>
</div><!-- fragment --><h4>If HLA EXPOrt, HLA name of general line system.</h4>
<div class="fragment"><div class="line">CHGHLA</div>
</div><!-- fragment --><ul>
<li><code>CHGHLA: character(120)</code>: Character string</li>
</ul>
<p>In case of more than one line system, the following data groups have to be repeated:</p>
<ul>
<li>Line System Definition</li>
<li>Topology specification</li>
<li>Seafloor support condition (optional)</li>
</ul>
<h1><a class="anchor" id="ug_general_line_line_system"></a>
Line system definition</h1>
<h4>1 input line</h4>
<div class="fragment"><div class="line">LINE SYSTem DEFInition</div>
</div><!-- fragment --><h4>System identification, 1 input line</h4>
<div class="fragment"><div class="line">LINE-SYSTEM-ID</div>
</div><!-- fragment --><ul>
<li><code>LINE-SYSTEM-ID: character(8)</code>: Line system identifier</li>
</ul>
<h2><a class="anchor" id="ug_general_line_line_system_topology"></a>
Topology specification</h2>
<h4>1 input line</h4>
<div class="fragment"><div class="line">LINE TOPOlogy DATA</div>
</div><!-- fragment --><h4>Topology, as many input lines as necessary (1 input line per simple line in the system)</h4>
<div class="fragment"><div class="line">LINE-ID  LINE-TYPE-ID  LINE-NODE-ID-1  LINE-NODE-ID-2</div>
</div><!-- fragment --><ul>
<li><code>LINE-ID: character(8)</code>: Line identifier</li>
<li><code>LINE-TYPE-ID: character(8)</code>: Line type identifier</li>
<li><code>LINE-NODE-ID 1: character(8)</code>: Line node 1 (from end 1) identifier</li>
<li><code>LINE-NODE-ID 2: character(8)</code>: Line node 2 (to end 2) identifier</li>
</ul>
<h2><a class="anchor" id="ug_general_line_line_system_seafloor"></a>
Seafloor support condition (optional)</h2>
<p>The bottom is given as one “non-curved” plane that may be oriented inclined to the water surface. The contact forces between the bottom and a line is given by vertical bilinear springs.</p>
<h4>1 input line</h4>
<div class="fragment"><div class="line">BOTTom CONTact DATA</div>
</div><!-- fragment --><h4>1 input line</h4>
<div class="fragment"><div class="line">XB  YB  ZB  XN  YN  ZN  BOTSTIF  ZBLOAD</div>
</div><!-- fragment --><ul>
<li><code>XB: real</code>: X coordinates of point on seafloor</li>
<li><code>YB: real</code>: Y coordinates of point on seafloor</li>
<li><code>ZB: real</code>: Z coordinates of point on seafloor</li>
<li><code>XN: real</code>: X components of the normal vector at the seafloor point</li>
<li><code>YN: real</code>: Y components of the normal vector at the seafloor point</li>
<li><code>ZN: real</code>: Z components of the normal vector at the seafloor point</li>
<li><code>BOTSTIF: real</code>: Spring stiffness (normal to seafloor) <img class="formulaInl" alt="$[F/L]$" src="form_150.png"/></li>
<li><code>ZBLOAD: real</code>: Minimum distance from seafloor plane for distributed element load formulation, i.e. elements attached to a node with a distance less than <code>ZBLOAD</code> from bottom plane will be given a lumped load formulation, see the figure below.</li>
</ul>
<div class="image">
<img src="load_formulations.svg" alt="load_formulations.svg"/>
<div class="caption">
Load formulations</div></div>
<h2><a class="anchor" id="ug_general_line_line_system_advanced"></a>
Advanced analysis option (optional)</h2>
<h4>1 input line</h4>
<div class="fragment"><div class="line">ADVAnced ANALysis OPTIon</div>
</div><!-- fragment --><h4>1 input line</h4>
<div class="fragment"><div class="line">LRELV  MET_S  MAX_S  MIN_S  MET_D  MAX_D  MIN_D  TOLINC  TOLNOR  MAXIT</div>
</div><!-- fragment --><ul>
<li><code>LRELV: integer, default: 0</code>: Control parameter for relative velocity<ul>
<li>Dummy in present version</li>
<li><code>= 0</code>: Drag force caused by current action only</li>
<li><code>= 1</code>: Drag force caused by relative velocity between current velocity and structural velocity</li>
</ul>
</li>
<li><code>MET_S: integer, default: 1</code>: Static analysis (<code>STAMOD</code>)<ul>
<li>Incrementation control parameter</li>
<li><code>= 1</code>: Constant incrementation</li>
<li><code>= 2</code>: Variable incrementation</li>
</ul>
</li>
<li><code>MAX_S: integer, default: 100</code>:<ul>
<li>if <code>MET_S = 1</code>: Number of incrementation steps</li>
<li>if <code>MET_S = 2</code>: Maximum incrementation steps</li>
</ul>
</li>
<li><code>MIN_S: integer, default: 5</code>:<ul>
<li>if <code>MET_S = 1</code>: Dummy</li>
<li>if <code>MET_S = 2</code>: Minimum incrementation steps</li>
</ul>
</li>
<li><code>MET_D: integer, default: 2</code>: Dynamic analysis (<code>DYNMOD</code>)<ul>
<li>Incrementation control parameter; dynamic analysis</li>
<li><code>= 1</code>: Constant incrementation</li>
<li><code>= 2</code>: Variable incrementation</li>
</ul>
</li>
<li><code>MAX_D: integer, default: 2</code>:<ul>
<li>if <code>MET_D = 1</code>: Number of incrementation steps</li>
<li>if <code>MET_D = 2</code>: Maximum incrementation steps</li>
</ul>
</li>
<li><code>MIN_D: integer, default: 1</code>:<ul>
<li>if <code>MET_D = 1</code>: Dummy</li>
<li>if <code>MET_D = 2</code>: Minimum incrementation steps</li>
</ul>
</li>
<li><code>TOLINC: real, default: 10</code> <img class="formulaInl" alt="$ ^{-3} $" src="form_228.png"/>: Displacement norm for termination of global equilibrium iteration; Used during incrementation</li>
<li><code>TOLNOR: real, default: 10</code> <img class="formulaInl" alt="$ ^{-4} $" src="form_229.png"/>: Displacement norm for termination of global equilibrium iteration; Used for last incrementation step</li>
<li><code>MAXIT: integer, default: 100</code>: Maximum number of iterations</li>
</ul>
<h1><a class="anchor" id="ug_general_line_boundary"></a>
Boundary conditions and coordinates for line nodes</h1>
<h4>Data group identifier, 1 input line</h4>
<div class="fragment"><div class="line">LINE NODE DEFInition</div>
</div><!-- fragment --><h4>Boundary condition and coordinates, 2 input lines per line node.</h4>
<p>Line node identifier and type </p>
<div class="fragment"><div class="line">LINE-NODE-ID  NODE-TYPE</div>
</div><!-- fragment --><ul>
<li><code>LINE-NODE-ID: character(8)</code>: line node identifier</li>
<li><code>NODE-TYPE: character</code>: type of boundary<ul>
<li><code>= FIXEd</code> (Earth-fixed)</li>
<li><code>= FREE</code></li>
<li><code>= BODY</code> (Attached to body component)</li>
</ul>
</li>
</ul>
<h4>IF NODE-TYPE = FIXED or FREE: Node coordinates and reference system</h4>
<div class="fragment"><div class="line">REF-SYSTEM  X  Y  Z  BODY-ID</div>
</div><!-- fragment --><ul>
<li><code>REF-SYSTEM: character</code>: reference system<ul>
<li><code>= LOCAL</code></li>
<li><code>= GLOBAL</code></li>
</ul>
</li>
<li><code>X: real</code>: Initial coordinates for fixed and free line nodes</li>
<li><code>Y: real</code>: Initial coordinates for fixed and free line nodes</li>
<li><code>Z: real</code>: Initial coordinates for fixed and free line nodes</li>
<li><code>BODY-ID: character(8)</code>:<ul>
<li><code>REF-SYSTEM = LOCAL</code>: Reference to body ID for local reference system</li>
<li><code>REF-SYSTEM = GLOBAL</code>: Dummy</li>
</ul>
</li>
</ul>
<h4>IF NODE-TYPE = BODY: Body component reference</h4>
<div class="fragment"><div class="line">BODY-COMP-ID</div>
</div><!-- fragment --><ul>
<li><code>BODY-COMP-ID: character(8)</code>: Reference to body component ID for which the line node is attached.</li>
</ul>
<h1><a class="anchor" id="ug_general_line_line_type"></a>
Line type definition</h1>
<p>A line type is labeled with a unique identifier. The line is described by segments and nodal components in a sequence from line node 1 to line node 2, ref data group <a class="el" href="a00028.html#ug_general_line_line_system_topology">Topology specification</a>. The line must consist of minimum one segment. Nodal components (buoys/clump weights) may be inserted at segment ends.</p>
<h4>Data group identifier, 1 input line</h4>
<div class="fragment"><div class="line">LINE TYPE DEFInition</div>
</div><!-- fragment --><h4>Line type identifier, 1 input line</h4>
<div class="fragment"><div class="line">LINE-TYPE-ID</div>
</div><!-- fragment --><h4>Line part specification. Number of input lines as many as necessary</h4>
<div class="fragment"><div class="line">LINE-PART-TYPE  CROSS-ID / NODAL-COMP-ID  SLENGTH  NELSEG</div>
</div><!-- fragment --><ul>
<li><code>LINE-PART-TYPE: character(8)</code>:<ul>
<li><code>= SEGMENT</code></li>
<li><code>= NODAL</code></li>
</ul>
</li>
</ul>
<p><code>LINE-PART-TYPE = SEGMENT</code></p>
<ul>
<li><code>CROSS-ID: character(8)</code>: Cross section identifier</li>
<li><code>SLENGTH: real</code>: Segment length <img class="formulaInl" alt="$[L]$" src="form_69.png"/></li>
<li><code>NELSEG: integer</code>: Number of elements for FEM analysis</li>
</ul>
<p><code>LINE-PART-TYPE = NODAL</code></p>
<ul>
<li><code>NODAL-COMP-ID: character(8)</code>: Nodal component identifier</li>
</ul>
<h1><a class="anchor" id="ug_general_line_cross"></a>
Cross section description</h1>
<p>The cross section properties data below has the same definition as the corresponding line characteristics data given in section <a class="el" href="a00024.html#ug_body_positioning_catenary">Catenary anchor lines</a>.</p>
<h4>Data group identifier, 1 input line</h4>
<div class="fragment"><div class="line">CROSs SECTion DEFInition</div>
</div><!-- fragment --><h4>Cross section identifier and properties, 1 input line</h4>
<div class="fragment"><div class="line">CROSS-ID  DIAMETER  EMOD  EMFACT  UWIA  WATFAC  CDN  CDT</div>
</div><!-- fragment --><ul>
<li><code>CROSS-ID: character(8)</code>: Cross section identifier</li>
<li><code>DIAMETER: real</code>: Cross section diameter used for axial stiffness and hydrodynamic forces <img class="formulaInl" alt="$[L]$" src="form_69.png"/></li>
<li><code>EMOD: real</code>: Modulus of elasticity <img class="formulaInl" alt="$[F/L^2]$" src="form_230.png"/></li>
<li><code>EMFACT: real</code>: Factor of elasticity</li>
<li><code>UWIA: real</code>: Unit weight in air <img class="formulaInl" alt="$[F/L]$" src="form_150.png"/></li>
<li><code>WATFAC: real</code>: The ratio between weight in water to weight in air</li>
<li><code>CDN: real</code>: Transverse drag coefficient</li>
<li><code>CDL: real</code>: Longitudinal drag coefficient</li>
</ul>
<p>The axial stiffness is calculated by:</p>
<ul>
<li><img class="formulaInl" alt="$ \mathrm{EA = EMOD \times EMFACT \times DIAMETER^2 \times \pi /4}$" src="form_231.png"/></li>
</ul>
<p>Drag force per unit length by:</p>
<ul>
<li><img class="formulaInl" alt="$ \mathrm{F^D_N = 0.5 \times RHOW \times CDN \times DIAMETER \times V^2_N} \quad \quad $" src="form_232.png"/> Normal direction</li>
<li><img class="formulaInl" alt="$ \mathrm{F^D_I = 0.5 \times RHOW \times CDL \times DIAMETER \times V^2_L} \quad \quad $" src="form_233.png"/> Longitudinal direction</li>
</ul>
<h1><a class="anchor" id="ug_general_line_nodal"></a>
Nodal component description</h1>
<h4>Data group identifier, 1 input line</h4>
<div class="fragment"><div class="line">NODAl COMPonent DEFInition</div>
</div><!-- fragment --><h4>Identifier and number of points in force and drag coefficient table, 1 input line</h4>
<div class="fragment"><div class="line">NODAL-COMP-ID  NFZ</div>
</div><!-- fragment --><ul>
<li><code>COMP-ID: character(8)</code>: Component identifier</li>
<li><code>NFZ: integer &gt;= 1</code>: Number of points in the force/drag force coefficient versus vertical position table</li>
</ul>
<h4>Vertical position and corresponding vertical load and drag force coefficient, NFZ input lines.</h4>
<p>This feature is meant for modelling e.g. buoyancy modules that may float to the surface. </p>
<div class="fragment"><div class="line">Z(i)  Fz(i)  CDFz(i)</div>
</div><!-- fragment --><ul>
<li><code>Z: real</code>: Vertical position (global reference system). Dummy if <code>NFZ=1</code> <img class="formulaInl" alt="$[L]$" src="form_69.png"/></li>
<li><code>Fz: real</code>: Corresponding vertical force <img class="formulaInl" alt="$[F]$" src="form_148.png"/></li>
<li><code>CDFz: real</code>: Corresponding drag force coefficient <img class="formulaInl" alt="$[FT^2/L^2]$" src="form_144.png"/></li>
</ul>
<p>Interpolation within table. Constant values outside the table </p>
</div></div><!-- contents -->
	</body>
</html>