<?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 DYNMOD </div>  </div>
</div><!--header-->
<div class="contents">
<div class="toc"><h3>Table of Contents</h3>
<ul><li class="level1"><a href="#dynmod_general_information">General Information</a></li>
<li class="level1"><a href="#dynmod_a">Data Group A: Control Information</a><ul><li class="level2"><a href="#dynmod_a_principal">Principal run parameters</a><ul><li class="level3"><a href="#dynmod_a_principal_data">Data group identifier, one input line</a></li>
<li class="level3"><a href="#dynmod_a_principal_heading">Heading, three input lines</a></li>
<li class="level3"><a href="#dynmod_a_principal_options">Options and identifiers, one input line</a></li>
</ul>
</li>
<li class="level2"><a href="#dynmod_a_static">Static load condition</a><ul><li class="level3"><a href="#dynmod_a_static_data">Data group identifier, one input line</a></li>
<li class="level3"><a href="#dynmod_a_static_scaling">Scaling parameters, one line</a></li>
</ul>
</li>
</ul>
</li>
<li class="level1"><a href="#dynmod_b">Data Group B: Free Vibration Analysis</a><ul><li class="level2"><a href="#dynmod_b_free">Free vibration options</a><ul><li class="level3"><a href="#dynmod_b_free_data">Data group identifier, one input line</a></li>
<li class="level3"><a href="#dynmod_b_free_number">Number of eigenvalues and -vectors, one input line</a></li>
<li class="level3"><a href="#dynmod_b_free_computation">Computation parameters, one input line</a></li>
</ul>
</li>
<li class="level2"><a href="#dynmod_b_print">Print options for results</a><ul><li class="level3"><a href="#dynmod_b_print_data">Data group identifier, one input line</a></li>
<li class="level3"><a href="#dynmod_b_print_selection">Print selection parameters, one input line</a></li>
</ul>
</li>
<li class="level2"><a href="#dynmod_b_termination">Termination of input data</a></li>
</ul>
</li>
<li class="level1"><a href="#dynmod_c">Data Group C: Regular Wave, Time Domain Analysis</a><ul><li class="level2"><a href="#dynmod_c_parameters">Parameters for definition of analysis and further input</a><ul><li class="level3"><a href="#dynmod_c_parameters_data">Data group identifier, one input line</a></li>
<li class="level3"><a href="#dynmod_c_parameters_analysis">Analysis parameters, one input line</a></li>
</ul>
</li>
<li class="level2"><a href="#dynmod_c_load">Load modelling, regular waves</a><ul><li class="level3"><a href="#dynmod_c_load_data">Data group identifier, one input line</a></li>
<li class="level3"><a href="#dynmod_c_load_method">Method for wave load calculation, one input line</a></li>
</ul>
</li>
<li class="level2"><a href="#dynmod_c_regular">Regular vessel motion</a><ul><li class="level3"><a href="#dynmod_c_regular_data">Data group identifier, one input line</a></li>
<li class="level3"><a href="#dynmod_c_regular_definition">Definition of vessel motion, two lines for each vessel</a><ul><li class="level4"><a href="#dynmod_c_regular_definition_motion_amplitudes">Motion amplitudes of support vessel, one input line</a></li>
<li class="level4"><a href="#dynmod_c_regular_definition_motion_angles">Motion phase angles, one input line</a></li>
</ul>
</li>
</ul>
</li>
</ul>
</li>
<li class="level1"><a href="#dynmod_d">Data Group D: Irregular Wave, Time Domain Analysis</a><ul><li class="level2"><a href="#dynmod_d_parameters">Irregular time series parameters</a><ul><li class="level3"><a href="#dynmod_d_parameters_data">Data group identifier, one input line</a></li>
<li class="level3"><a href="#dynmod_d_parameters_parameters">Parameters, one input line</a></li>
</ul>
</li>
<li class="level2"><a href="#dynmod_d_analysis">Irregular response analysis and subsequent input</a><ul><li class="level3"><a href="#dynmod_d_analysis_data">Data group identifier, one input line</a></li>
<li class="level3"><a href="#dynmod_d_analysis_parameters">Analysis parameters, one input line</a></li>
<li class="level3"><a href="#dynmod_d_analysis_support">Support vessel motion scaling factors. Only given for ISCALE=1. One line for each vessel in system (NVES lines)</a></li>
</ul>
</li>
<li class="level2"><a href="#dynmod_d_irregular_waves">Irregular waves</a><ul><li class="level3"><a href="#dynmod_d_irregular_waves_data">Data group identifier, one input line</a></li>
<li class="level3"><a href="#dynmod_d_irregular_waves_procedure">Procedure for wave force calculation, one input line</a><ul><li class="level4"><a href="#dynmod_d_irregular_waves_procedure_trffile">Wave kinematics transfer function file name</a></li>
<li class="level4"><a href="#dynmod_d_irregular_waves_procedure_tsfile">Wave kinematics time series file name</a></li>
<li class="level4"><a href="#dynmod_d_irregular_waves_procedure_additional">Additional detailed specification of wave kinematics points (optional)</a></li>
</ul>
</li>
</ul>
</li>
<li class="level2"><a href="#dynmod_d_wave_and_motion">Wave and motion time series files</a><ul><li class="level3"><a href="#dynmod_d_wave_and_motion_time_series">Wave time series file</a><ul><li class="level4"><a href="#dynmod_d_wave_and_motion_time_series_data">Data group identifier, one input line</a></li>
<li class="level4"><a href="#dynmod_d_wave_and_motion_time_series_file">Wave time series file information</a></li>
<li class="level4"><a href="#dynmod_d_wave_and_motion_time_series_direction">Direction, location of measurement and cut-off for filtering</a></li>
</ul>
</li>
<li class="level3"><a href="#dynmod_d_wave_and_motion_frequency">Wave frequency motion time series file</a><ul><li class="level4"><a href="#dynmod_d_wave_and_motion_frequency_data">Data group identifier, one input line</a></li>
<li class="level4"><a href="#dynmod_d_wave_and_motion_frequency_motions">Wave frequency motions file information, NVES input lines</a></li>
</ul>
</li>
<li class="level3"><a href="#dynmod_d_wave_and_motion_low_frequency">Low frequency motion time series file</a><ul><li class="level4"><a href="#dynmod_d_wave_and_motion_low_frequency_data">Data group identifier, one input line</a></li>
<li class="level4"><a href="#dynmod_d_wave_and_motion_low_frequency_file">Low frequency motions file information, NVES input lines</a></li>
</ul>
</li>
</ul>
</li>
<li class="level2"><a href="#dynmod_d_print">Print options for FFT analysis</a><ul><li class="level3"><a href="#dynmod_d_print_data">Data group identifier, one input line</a></li>
<li class="level3"><a href="#dynmod_d_print_fourier">Fourier print options</a></li>
</ul>
</li>
<li class="level2"><a href="#dynmod_d_storage">Storage of irregular wave kinematics (optional)</a><ul><li class="level3"><a href="#dynmod_d_storage_data">Data group identifier, one input line</a></li>
<li class="level3"><a href="#dynmod_d_storage_wave">Wave kinematics storage options one input line</a></li>
</ul>
</li>
</ul>
</li>
<li class="level1"><a href="#dynmod_e">Data Group E: Time Domain Procedure and File Storage Parameters</a><ul><li class="level2"><a href="#dynmod_e_method">Method of analysis and subsequent input</a><ul><li class="level3"><a href="#dynmod_e_method_data">Data group identifier, one input line</a></li>
<li class="level3"><a href="#dynmod_e_method_method">Method and subsequent input, one input line</a></li>
<li class="level3"><a href="#dynmod_e_method_time">Time integration and damping parameters, one input line</a></li>
<li class="level3"><a href="#dynmod_e_method_non">Non-linear force model, one input line. Always submit for linear and non-linear analysis</a></li>
</ul>
</li>
<li class="level2"><a href="#dynmod_e_nonlinear">Nonlinear step by step integration</a><ul><li class="level3"><a href="#dynmod_e_nonlinear_data">Data group identifier, one input line</a></li>
<li class="level3"><a href="#dynmod_e_nonlinear_specification">Specification of incrementation procedure, one input line</a></li>
</ul>
</li>
<li class="level2"><a href="#dynmod_e_modification">Modification to water kinematics</a><ul><li class="level3"><a href="#dynmod_e_modification_data">Data group identifier, one input line</a></li>
<li class="level3"><a href="#dynmod_e_modification_data_rigid">Rigid moonpool column, one input line</a><ul><li class="level4"><a href="#dynmod_e_modification_data_rigid_number">Specification of number of moonpools, one input line</a></li>
<li class="level4"><a href="#dynmod_e_modification_data_rigid_support">Specification of support vessel moonpool, one input line.</a></li>
<li class="level4"><a href="#dynmod_e_modification_data_rigid_lines">Specification of lines within present moonpool, one input line</a></li>
</ul>
</li>
</ul>
</li>
<li class="level2"><a href="#dynmod_e_slug">Slug force calculations</a><ul><li class="level3"><a href="#dynmod_e_slug_data">Data group identifier, one input line</a></li>
<li class="level3"><a href="#dynmod_e_slug_specification">Specification of slug data, one input line</a></li>
</ul>
</li>
<li class="level2"><a href="#dynmod_e_import">Import of internal flow data from file</a><ul><li class="level3"><a href="#dynmod_e_import_data">Data group identifier, 1 input line</a></li>
<li class="level3"><a href="#dynmod_e_import_specification">Specification of input flow file, one input line</a></li>
</ul>
</li>
<li class="level2"><a href="#dynmod_e_dynamic_current">Dynamic current variation</a><ul><li class="level3"><a href="#dynmod_e_dynamic_current_data">Data group identifier, one input line</a></li>
<li class="level3"><a href="#dynmod_e_dynamic_current_file">File name</a></li>
</ul>
</li>
<li class="level2"><a href="#dynmod_e_dynamic_nodal">Dynamic nodal forces</a><ul><li class="level3"><a href="#dynmod_e_dynamic_nodal_data">Data group identifier, one input line</a></li>
<li class="level3"><a href="#dynmod_e_dynamic_nodal_number">Number of specified components specified by functions or by time series on file</a></li>
<li class="level3"><a href="#dynmod_e_dynamic_nodal_force">Force component description</a></li>
</ul>
</li>
<li class="level2"><a href="#dynmod_e_dynamic_tension">Dynamic tension variation</a><ul><li class="level3"><a href="#dynmod_e_dynamic_tension_data">Data group identifier, one input line</a></li>
<li class="level3"><a href="#dynmod_e_dynamic_tension_specification">Specification of dynamic tension variation</a></li>
</ul>
</li>
<li class="level2"><a href="#dynmod_e_time">Time domain loading</a><ul><li class="level3"><a href="#dynmod_e_time_data">Data group identifier, one input line</a></li>
<li class="level3"><a href="#dynmod_e_time_load">Load type to be activated, one input line</a></li>
<li class="level3"><a href="#dynmod_e_time_segment">Segment length variation, NLSPEC input lines for LOTYPE = SEGV</a></li>
<li class="level3"><a href="#dynmod_e_time_temperature">Temperature variation, NLSPEC input lines if LOTYPE = TEMP</a></li>
<li class="level3"><a href="#dynmod_e_time_pressure">Pressure variation, NLSPEC input lines if LOTYPE = PRES</a></li>
<li class="level3"><a href="#dynmod_e_time_boundary">Boundary change, 3 x NLSPEC input lines for LOTYPE = BOUN</a></li>
<li class="level3"><a href="#dynmod_e_time_viv">VIV load specification, one input line for LOTYPE = VIVA</a></li>
<li class="level3"><a href="#dynmod_e_time_winch">Winch run, NLSPEC input lines for LOTYPE = WINC</a></li>
<li class="level3"><a href="#dynmod_e_wind_event">Wind event specification, two or three input lines for LOTYPE = WIND</a></li>
<li class="level3"><a href="#dynmod_e_wt_shutdown">Wind turbine shutdown fault options</a></li>
<li class="level3"><a href="#dynmod_e_wt_blade_pitch_fault">Wind turbine blade pitch fault options</a></li>
</ul>
</li>
<li class="level2"><a href="#dynmod_e_displacement">File storage of displacement response</a><ul><li class="level3"><a href="#dynmod_e_displacement_data">Data group identifier, one input line</a></li>
<li class="level3"><a href="#dynmod_e_displacement_specification">Specification of displacements to be stored</a><ul><li class="level4"><a href="#dynmod_e_displacement_specification_amount">Amount of storage, one input line</a></li>
<li class="level4"><a href="#dynmod_e_displacement_specification_specification">Specification of nodes for displacement storage, NODISP input lines</a></li>
</ul>
</li>
</ul>
</li>
<li class="level2"><a href="#dynmod_e_internal">File storage for internal forces</a><ul><li class="level3"><a href="#dynmod_e_internal_data">Data group identifier, one input line</a></li>
<li class="level3"><a href="#dynmod_e_internal_specification">Specification of forces to be stored</a><ul><li class="level4"><a href="#dynmod_e_internal_specification_amount">Amount of storage, one input line</a></li>
<li class="level4"><a href="#dynmod_e_internal_specification_specification">Specification of elements for force storage, NOFORC input lines</a></li>
</ul>
</li>
</ul>
</li>
<li class="level2"><a href="#dynmod_e_curvature">File storage for curvature response</a><ul><li class="level3"><a href="#dynmod_e_curvature_data">Data group identifier, one input line</a></li>
<li class="level3"><a href="#dynmod_e_curvature_specification">Specification of curvature to be stored</a><ul><li class="level4"><a href="#dynmod_e_curvature_specification_amount">Amount of storage, one input line</a></li>
<li class="level4"><a href="#dynmod_e_curvature_specification_specification">Specification of elements for curvature storage, NOCURV input lines</a></li>
</ul>
</li>
</ul>
</li>
<li class="level2"><a href="#dynmod_e_envelope">Envelope curve specification</a><ul><li class="level3"><a href="#dynmod_e_envelope_data">Data group identifier, one line</a></li>
<li class="level3"><a href="#dynmod_e_envelope_specification">Specification</a><ul><li class="level4"><a href="#dynmod_e_envelope_specification_options">Options for calculation and printing</a></li>
</ul>
</li>
</ul>
</li>
<li class="level2"><a href="#dynmod_e_stroke">File storage for stroke response</a><ul><li class="level3"><a href="#dynmod_e_stroke_data">Data group identifier, one input line</a></li>
<li class="level3"><a href="#dynmod_e_stroke_specification">Specification of stroke calculation and storage</a></li>
</ul>
</li>
<li class="level2"><a href="#dynmod_e_sum">File storage for sum forces</a><ul><li class="level3"><a href="#dynmod_e_sum_data">Data group identifier, one input line</a></li>
<li class="level3"><a href="#dynmod_e_sum_specification">Specification of forces to be stored</a><ul><li class="level4"><a href="#dynmod_e_sum_specification_amount">Amount of storage, one input line</a></li>
<li class="level4"><a href="#dynmod_e_sum_specification_specification">Specification of elements for force storage, NOSFOR input lines</a></li>
</ul>
</li>
</ul>
</li>
<li class="level2"><a href="#dynmod_wt_resp">File storage for wind turbine responses</a><ul><li class="level3"><a href="#dynmod_wt_resp_id">Data group identifier, one input line</a><ul><li class="level4"><a href="#dynmod_wt_dt">Time interval for storage, one input line</a></li>
<li class="level4"><a href="#dynmod_no_wt">Amount of storage, one input line</a></li>
<li class="level4"><a href="#dynmod_wt_id">Wind turbine identification for storage, `NOTURB` input lines</a></li>
</ul>
</li>
</ul>
</li>
<li class="level2"><a href="#dynmod_wtbl_resp">File storage for wind turbine blade responses</a><ul><li class="level3"><a href="#dynmod_wtbl_resp_id">Data group identifier, one input line</a><ul><li class="level4"><a href="#dynmod_wtblresp_amount">Specification of the amount of responses, one input line</a></li>
<li class="level4"><a href="#dynmod_wtbl_dt">Time interval for storage, number of input lines and file format code, one input line</a></li>
<li class="level4"><a href="#dynmod_noblres_iel">Specification of elements for blade response storage, NOSPEC input lines</a></li>
</ul>
</li>
</ul>
</li>
<li class="level2"><a href="#dynmod_e_export">Export of element responses</a><ul><li class="level3"><a href="#dynmod_e_export_data">Data group identifier, one input line</a></li>
<li class="level3"><a href="#dynmod_e_export_amount">Amount of response storage and file format, one input line</a></li>
<li class="level3"><a href="#dynmod_e_export_detailed">Detailed specification of exported element responses</a></li>
</ul>
</li>
<li class="level2"><a href="#dynmod_e_termination">Termination of input data</a></li>
</ul>
</li>
<li class="level1"><a href="#dynmod_description">Description of Additional Input Files</a><ul><li class="level2"><a href="#dynmod_description_current">Dynamic Current Variation</a><ul><li class="level3"><a href="#dynmod_description_current_number">Number of specified time instants, one input line</a><ul><li class="level4"><a href="#dynmod_description_current_number_levels">Number of levels and time instant, one input line</a></li>
<li class="level4"><a href="#dynmod_description_current_number_velocity">Current velocity and direction, one input line per current level, i.e. NLCUR input lines</a></li>
</ul>
</li>
</ul>
</li>
<li class="level2"><a href="#dynmod_description_nodal">Dynamic Nodal Forces</a><ul><li class="level3"><a href="#dynmod_description_nodal_number">Number of specified time instants, one input line</a></li>
<li class="level3"><a href="#dynmod_description_nodal_number__load1">Number of load components and time instant, one input line</a></li>
<li class="level3"><a href="#dynmod_description_nodal_number_load2">Load components, MDCOMP input lines</a></li>
<li class="level3"><a href="#dynmod_description_nodal_number_load2_col">Time Step and Load Components, one line for each time step</a></li>
</ul>
</li>
<li class="level2"><a href="#dynmod_description_wave">Diffracted Wave Transfer Functions at Points</a><ul><li class="level3"><a href="#dynmod_description_wave_identification_data">Data group identifier, one input line</a></li>
<li class="level3"><a href="#dynmod_description_wave_identification_text">Text describing the linear incoming wave to diffracted wave transfer functions, two input lines</a></li>
<li class="level3"><a href="#dynmod_description_wave_identification_point1">Point reference, one input line</a></li>
<li class="level3"><a href="#dynmod_description_wave_identification_point2">Point coordinates, one input line</a></li>
<li class="level3"><a href="#dynmod_description_wave_identification_dimensioning">Dimensioning parameters, one input line</a></li>
<li class="level3"><a href="#dynmod_description_wave_unknown1_data">Data identification, one input line</a></li>
<li class="level3"><a href="#dynmod_description_wave_unknown1_directions">Directions, NDIR input lines</a></li>
<li class="level3"><a href="#dynmod_description_wave_unknown2_data">Data identification, one input line</a></li>
<li class="level3"><a href="#dynmod_description_wave_unknown2_frequencies">Frequencies, NFRE input lines</a></li>
<li class="level3"><a href="#dynmod_description_wave_unknown3_data">Data identification, one input line</a></li>
<li class="level3"><a href="#dynmod_description_wave_unknown3_ddimensioning">Diffracted wave transfer function, NDIR x NFRE input lines</a></li>
</ul>
</li>
<li class="level2"><a href="#dynmod_description_internal">Internal flow description</a><ul><li class="level3"><a href="#dynmod_description_internal_heading">Heading, one input line</a></li>
<li class="level3"><a href="#dynmod_description_internal_specification">Specification of internal flow conditions.</a><ul><li class="level4"><a href="#dynmod_description_internal_specification_time">Specification of time, one input line</a></li>
<li class="level4"><a href="#dynmod_description_internal_specification_flow">Specification of flow conditions, as many input lines as needed. (Zero input lines may be given.)</a></li>
</ul>
</li>
<li class="level3"><a href="#dynmod_description_internal_end">End, one input line</a></li>
</ul>
</li>
</ul>
</li>
</ul>
</div>
<div class="textblock"><h1><a class="anchor" id="dynmod_general_information"></a>
General Information</h1>
<p>The input description to the <code>DYNMOD</code> module is divided into 5 sections, each section describing one data-section referred to as A-E.</p>
<ul>
<li>Data Group A: <a class="el" href="a00014.html#dynmod_a">Control Information</a></li>
<li>Data Group B: <a class="el" href="a00014.html#dynmod_b">Free Vibration Analysis</a></li>
<li>Data Group C: <a class="el" href="a00014.html#dynmod_c">Regular Wave, Time Domain Analysis</a></li>
<li>Data Group D: <a class="el" href="a00014.html#dynmod_d">Irregular Wave, Time Domain Analysis</a></li>
<li>Data Group E: <a class="el" href="a00014.html#dynmod_e">Time Domain Procedure and File Storage Parameters</a></li>
</ul>
<p>Three different types of analysis are possible. Complete input for these types is shown in the list below.</p>
<ul>
<li>Type number 1, Free vibration, requires the data sections A and B.</li>
<li>Type number 2, Regular wave, requires the data sections A, C and E.</li>
<li>Type number 3, Irregular wave, requires the data sections A, D and E.</li>
</ul>
<h1><a class="anchor" id="dynmod_a"></a>
Data Group A: Control Information</h1>
<p>This data-group is mandatory for all types of analysis with <code>DYNMOD</code>. The prescribed sequence must be followed.</p>
<h2><a class="anchor" id="dynmod_a_principal"></a>
Principal run parameters</h2>
<h3><a class="anchor" id="dynmod_a_principal_data"></a>
Data group identifier, one input line</h3>
<div class="fragment"><div class="line">DYNMod CONTrol INFOrmation CHVERS</div>
</div><!-- fragment --><ul>
<li><code>CHVERS: character(8)</code>: RIFLEX input file version, e.g. 3.2</li>
</ul>
<h3><a class="anchor" id="dynmod_a_principal_heading"></a>
Heading, three input lines</h3>
<ul>
<li>Heading, line no 1</li>
<li>Heading, line no 2</li>
<li>Heading, line no 3</li>
</ul>
<p>Identification of the run by alphanumerical text</p>
<p>Always three input lines which may all be blank. Each line may contain up to 60 characters</p>
<h3><a class="anchor" id="dynmod_a_principal_options"></a>
Options and identifiers, one input line</h3>
<div class="fragment"><div class="line">IRUNCO IANAL IDRIS IDENV IDSTAT IDIRR IDRES</div>
</div><!-- fragment --><ul>
<li><code>IRUNCO: character(4), default: DATA</code>: Code for data check or executable run<ul>
<li><code>= FREM</code>: Data generation for <code>FREMOD</code></li>
<li><code>= DATA</code>: Data check</li>
<li><code>= ANALysis</code>: Analysis</li>
</ul>
</li>
<li><code>IANAL: character(4)</code>: Type of analysis to be performed<ul>
<li><code>= EIGEn</code>: Eigenvalue analysis.<ul>
<li>Data section B must be given</li>
</ul>
</li>
<li><code>= REGUlar</code>: Regular wave, time domain analysis.<ul>
<li>Data sections C and E must be given.</li>
</ul>
</li>
<li><code>= IRREgular</code>: Irregular wave, time domain analysis.<ul>
<li>Data sections D and E must be given.</li>
</ul>
</li>
</ul>
</li>
<li><code>IDRIS: character(6)</code>: Data set identifier corresponding to data for one riser system established by <code>INPMOD</code> and followed by a static analysis. See <a class="el" href="a00010.html#inpmod_data_group_b_single_riser_data">INPMOD: Data Group B: Single Riser Data</a> and <a class="el" href="a00012.html#stamod_a_principal_options">STAMOD: Options and print switches</a>.</li>
<li><code>IDENV: character(6)</code>: Environment identifier, corresponding to data for one environment on file established by <code>INPMOD</code>. See data-group <a class="el" href="a00010.html#inpmod_d_identification">INPMOD: Identification of the environment</a> of input description for <code>INPMOD</code>.<ul>
<li>Reference to actual wave case is given in a later data-group</li>
<li>Dummy for <code>IRUNCO=DATAcheck</code></li>
</ul>
</li>
<li><code>IDSTAT: character(6)</code>: Static condition identifier, corresponding to data on file established by <code>STAMOD</code>. See <a class="el" href="a00012.html#stamod_a_principal">STAMOD: Principal run parameters</a> of input description for <code>STAMOD</code>.</li>
<li><code>IDIRR: character(6)</code>: Data set identifier for irregular wave and motion data, either established by a previous run or used as reference to results stored on file by this run.</li>
<li><code>IDRES: character(6)</code>: Data set identifier for this run, used as reference to results stored on files</li>
</ul>
<h2><a class="anchor" id="dynmod_a_static"></a>
Static load condition</h2>
<p>For special purposes it may be convenient to change applied static loads at the start of dynamic analysis. This option should be used with care! One useful application is for analysing free vibration after scaling a static nodal force to zero (<code>SCALSF=0.0</code>).</p>
<p>Note that some static loads are applied and some modelling features are activated in dynamic analysis even if they were not applied nor activated in static analysis. 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="dynmod_a_static_data"></a>
Data group identifier, one input line</h3>
<div class="fragment"><div class="line">STATic LOAD CONDition</div>
</div><!-- fragment --><h3><a class="anchor" id="dynmod_a_static_scaling"></a>
Scaling parameters, one line</h3>
<div class="fragment"><div class="line">SCALVF SCALSF SCALCF</div>
</div><!-- fragment --><ul>
<li><code>SCALVF: real, default: 1</code>: Scaling of volume forces</li>
<li><code>SCALSF: real, default: 1</code>: Scaling of specified (nodal) forces</li>
<li><code>SCALCF: real, default: 1</code>: Scaling of current velocities</li>
</ul>
<p>All forces are scaled simultaneously as <img class="formulaInl" alt="$ \mathrm{ F_s = SCALiF \times F_s^0 }$" src="form_397.png"/> Only <code>SCALSF</code> is active in the present version of the program.</p>
<h1><a class="anchor" id="dynmod_b"></a>
Data Group B: Free Vibration Analysis</h1>
<p>This data-group is given if and only if <code>IANAL=EIGEn</code>, see <a class="el" href="a00014.html#dynmod_a_principal_options">Options and identifiers, one input line</a>.</p>
<h2><a class="anchor" id="dynmod_b_free"></a>
Free vibration options</h2>
<h3><a class="anchor" id="dynmod_b_free_data"></a>
Data group identifier, one input line</h3>
<div class="fragment"><div class="line">FREE VIBRation OPTIons</div>
</div><!-- fragment --><h3><a class="anchor" id="dynmod_b_free_number"></a>
Number of eigenvalues and -vectors, one input line</h3>
<div class="fragment"><div class="line">NEIG NVEC</div>
</div><!-- fragment --><ul>
<li><code>NEIG: integer</code>: Number of eigenvalues to be calculated and stored on file</li>
<li><code>NVEC: integer</code>: Number of eigenvectors to be calculated and stored on file</li>
</ul>
<h3><a class="anchor" id="dynmod_b_free_computation"></a>
Computation parameters, one input line</h3>
<p>The parameters below correspond to Lanczos' method for solution of eigenvalue problems. For a detailed discussion, see B. Nour-Omid, B.N. Parlett, R.L. Taylor: Lanczos versus Subspace Iteration for Solution of Eigenvalue Problems, International Journal for Numerical Methods in Engineering, Vol. 19, pp. 859-871, 1983. or B.N. Parlett: The Symmetric Eigenvalue Problem, Prentice-Hall, 1980.</p>
<div class="fragment"><div class="line">EPS1 EPS2 EPS3 KSR MAXIT KEX SHIFT MAXNIV</div>
</div><!-- fragment --><ul>
<li><code>EPS1: real, default: 0</code>: Maximum acceptable relative error in computed eigenvalues</li>
<li><code>EPS2: real, default: 0</code>: Limit value for singularity test during factorization</li>
<li><code>EPS3: real, default: 0</code>: Orthogonality limit:<ul>
<li>If <img class="formulaInl" alt="$ \mathrm{ \boldsymbol{\mathrm{v}}_i \, ^T \boldsymbol{\mathrm{v}}_i = \delta_{ii} }$" src="form_398.png"/> and <img class="formulaInl" alt="$ \mathrm{ \boldsymbol{\mathrm{v}}_i\,^T \boldsymbol{\mathrm{v}}_j = \delta_{ij} }$" src="form_399.png"/> and <img class="formulaInl" alt="$ \mathrm{| \delta_{ij} | < EPS3 \times \delta_{ii} }$" src="form_400.png"/>, <img class="formulaInl" alt="$ \mathrm{ \quad\boldsymbol{\mathrm{v}}_i } $" src="form_401.png"/> and <img class="formulaInl" alt="$ \mathrm{ \boldsymbol{\mathrm{v}}_j }$" src="form_402.png"/> are orthogonal</li>
</ul>
</li>
<li><code>KSR: integer, default: 1</code>: Start vector code:<ul>
<li><code>KSR =</code> <img class="formulaInl" alt="$ \pm $" src="form_403.png"/><code>1</code>: a pseudo-random start vector is generated by the eigenvalue solver</li>
<li><code>KSR =</code> <img class="formulaInl" alt="$ \pm $" src="form_403.png"/><code>2</code>: the diagonal of the mass matrix is used as start vector</li>
<li><code>KSR =</code> <img class="formulaInl" alt="$ \pm $" src="form_403.png"/><code>3</code>: a start vector of unit elements is used</li>
<li>For positive <code>KSR</code> the start vector is premultiplied with <b>H</b> before use; if a negative value is specified the start vector is used directly.</li>
</ul>
</li>
<li><code>MAXIT: integer, default: 5</code>: Maximum no of iterations in reorthogonalization.<ul>
<li>If a negative value is specified, reorthogonalization is not iterative; e.g. <code>MAXIT = -2</code> will cause a two-pass Gram-Smith orthogonalization to be employed to all new <img class="formulaInl" alt="$ \mathrm{ \boldsymbol{\mathrm{ v_{}}}_i } $" src="form_404.png"/> (i&gt;1), irrespective of <code>EPS3</code>.</li>
<li>For high values of <code>NEIG</code> (&gt;50) a doublepass orthogonalization is recommended (<code>MAXIT = -2</code>)</li>
</ul>
</li>
<li><code>KEX: integer, default: 0</code>: Parameter controlling the frequency with which the small tridiagonal eigenvalue problem is solved.<ul>
<li>Must be in the range of <code>0 &lt;= KEX &lt;= 5</code>.</li>
<li>If a zero value is specified, a default value of 2 is used</li>
</ul>
</li>
<li><code>SHIFT: real, default: 0</code>: The shift value <img class="formulaInl" alt="$ \sigma $" src="form_405.png"/></li>
<li><code>MAXNIV: integer, default: 0</code>: Number of Lanczos steps to be used.<ul>
<li>A default value suitable for the eigenvalue routines is automatically computed if a <code>0</code> is specified.</li>
<li><code>MAXNIV</code> should only be given a value <img class="formulaInl" alt="$ \neq $" src="form_96.png"/> <code>0</code> for small problems</li>
</ul>
</li>
</ul>
<p>If zero or negative values are specified for <code>EPS1-EPS3</code> default values are inserted</p>
<h2><a class="anchor" id="dynmod_b_print"></a>
Print options for results</h2>
<h3><a class="anchor" id="dynmod_b_print_data"></a>
Data group identifier, one input line</h3>
<div class="fragment"><div class="line">EIGEnvalue PRINt OPTIons</div>
</div><!-- fragment --><h3><a class="anchor" id="dynmod_b_print_selection"></a>
Print selection parameters, one input line</h3>
<div class="fragment"><div class="line">NPEIG NPVEC IPRESW</div>
</div><!-- fragment --><ul>
<li><code>NPEIG: integer</code>: Number of eigenvalues to be printed ( &lt;= <code>NEIG</code>)</li>
<li><code>NPVEC: integer</code>: Number of eigenvectors to be printed ( &lt;= <code>NVEC</code>)</li>
<li><code>IPRESW: integer, default: 0</code>: Debug print switch for eigenvalue routines</li>
</ul>
<h2><a class="anchor" id="dynmod_b_termination"></a>
Termination of input data</h2>
<p>To terminate an input data stream, simply give the following, which is interpreted as a data group identifier.</p>
<div class="fragment"><div class="line">END</div>
</div><!-- fragment --><p>Note that the <code>END</code> image cannot be omitted</p>
<h1><a class="anchor" id="dynmod_c"></a>
Data Group C: Regular Wave, Time Domain Analysis</h1>
<p>This data group is given for <code>IANAL = REGUlar</code>, see <a class="el" href="a00014.html#dynmod_a_principal_options">Options and identifiers, one input line</a>. Data-group A and E must also be given for complete definition of a regular time domain analysis.</p>
<h2><a class="anchor" id="dynmod_c_parameters"></a>
Parameters for definition of analysis and further input</h2>
<h3><a class="anchor" id="dynmod_c_parameters_data"></a>
Data group identifier, one input line</h3>
<div class="fragment"><div class="line">REGUlar WAVE ANALysis</div>
</div><!-- fragment --><h3><a class="anchor" id="dynmod_c_parameters_analysis"></a>
Analysis parameters, one input line</h3>
<div class="fragment"><div class="line">NPER NSTPPR IRWCN IMOTD</div>
</div><!-- fragment --><ul>
<li><code>NPER: integer</code>: Number of periods for regular wave analysis, referring to wave or motion periods (of first vessel)</li>
<li><code>NSTPPR: integer, default: 80</code>: Number of integration time steps per period, recommended value: 50-120</li>
<li><code>IRWCN: integer</code>: Wave parameter<ul>
<li><code>IRWCN = 0</code>: No wave acting, motions must be present</li>
<li><code>IRWCN = N</code>: Wave acting. Regular wave case N on actual environment used in present analysis</li>
<li>If no waves are acting, period for harmonic motions are specified in <a class="el" href="a00014.html#dynmod_c_regular_definition_motion_amplitudes">Motion amplitudes of support vessel, one input line</a></li>
</ul>
</li>
<li><code>IMOTD: integer</code>: Platform motion parameter<ul>
<li><code>IMOTD = 0</code>: No motions, waves must be present</li>
<li><code>IMOTD = 1</code>: Platform motion generated on the basis of wave data (wave period and amplitude) and motion transfer functions. Reference to transfer functions given in <a class="el" href="a00014.html#dynmod_a_principal_options">Options and identifiers, one input line</a>.</li>
<li><code>IMOTD = 2</code>: Platform motions specified in <a class="el" href="a00014.html#dynmod_c_regular">Regular vessel motion</a></li>
</ul>
</li>
</ul>
<p>The platform motions are independent of the wave loading parameters given in <a class="el" href="a00014.html#dynmod_c_load">Load modelling, regular waves</a>.</p>
<p>Extreme values of response parameters from last integration period will normally be stored on file (cfr. <a class="el" href="a00014.html#dynmod_e_displacement">File storage of displacement response</a>). In addition, displacement histories from selected nodes and force and curvature histories from selected elements can be stored if wanted. Specification of such data storage is given in data groups <a class="el" href="a00014.html#dynmod_e_displacement">File storage of displacement response</a>, <a class="el" href="a00014.html#dynmod_e_internal">File storage for internal forces</a> and <a class="el" href="a00014.html#dynmod_e_curvature">File storage for curvature response</a>.</p>
<h2><a class="anchor" id="dynmod_c_load"></a>
Load modelling, regular waves</h2>
<p>This data group is given if <code>IRWCN &gt;= 1</code> (data group <a class="el" href="a00014.html#dynmod_c_parameters_analysis">Analysis parameters, one input line</a> above).</p>
<h3><a class="anchor" id="dynmod_c_load_data"></a>
Data group identifier, one input line</h3>
<div class="fragment"><div class="line">REGUlar WAVE LOADing</div>
</div><!-- fragment --><h3><a class="anchor" id="dynmod_c_load_method"></a>
Method for wave load calculation, one input line</h3>
<div class="fragment"><div class="line">IWTYP ISURF IUPPOS</div>
</div><!-- fragment --><ul>
<li><code>IWTYP: integer, default: 1</code>: Wave theory parameter<ul>
<li><code>IWTYP = 1</code>: Airy linear wave theory</li>
<li><code>IWTYP = 2</code>: Stoke 5th order wave theory</li>
</ul>
</li>
<li><code>ISURF: integer, default: 1</code>: Sea surface definition, see the figure 'Definition of sea surface' below.<ul>
<li>Dummy if <code>IWTYP = 2</code></li>
<li><code>ISURF = 1</code>: Integration of wave forces to mean water level</li>
<li><code>ISURF = 2</code>: Integration of wave forces to wave surface, deformation of potential by stretching and compression</li>
<li><code>ISURF = 3</code>: Integration of wave forces to wave surface, move of potential to actual surface</li>
<li><code>ISURF = 4</code>: Integration of wave forces to wave surface by keeping the potential constant from mean water level to wave surface</li>
</ul>
</li>
<li><code>IUPPOS: integer, default: 2</code>: Riser position parameter<ul>
<li><code>IUPPOS = 0</code>: as 1, but the riser is kept fixed in static position, for computation of surface penetrating element.</li>
<li><code>IUPPOS = 1</code>: Wave induced velocities and accelerations calculated at static riser position</li>
<li><code>IUPPOS = 2</code>: Wave induced velocities and accelerations calculated at updated (dynamic) positions</li>
</ul>
</li>
</ul>
<p>Note: The option <code>IUPPOS = 0</code> cannot be combined with linear analysis, <code>ITDMET = 1</code>, or nonlinear analysis, <code>ITDMET = 2</code> and <code>SIMO</code> bodies.</p>
<div class="image">
<img src="um_id_fig203.svg" alt="um_id_fig203.svg"/>
<div class="caption">
Definition of sea surface</div></div>
<h2><a class="anchor" id="dynmod_c_regular"></a>
Regular vessel motion</h2>
<p>This data group is given only if <code>IMOTD=2</code> (see input group <a class="el" href="a00014.html#dynmod_c_parameters_analysis">Analysis parameters, one input line</a>).</p>
<h3><a class="anchor" id="dynmod_c_regular_data"></a>
Data group identifier, one input line</h3>
<div class="fragment"><div class="line">REGUlar VESSel MOTIon</div>
</div><!-- fragment --><h3><a class="anchor" id="dynmod_c_regular_definition"></a>
Definition of vessel motion, two lines for each vessel</h3>
<p>'Motion amplitudes of support vessel' and 'Motion phase angles' must be given for all <code>NVES</code> vessels in systems (totally 2x<code>NVES</code> lines).</p>
<h4><a class="anchor" id="dynmod_c_regular_definition_motion_amplitudes"></a>
Motion amplitudes of support vessel, one input line</h4>
<p>Forced displacements are specified for the support vessel. Forced displacements for the terminal points are found by transformations.</p>
<div class="fragment"><div class="line">XAMP YAMP ZAMP XRAMP YRAMP ZRAMP PER</div>
</div><!-- fragment --><ul>
<li><code>XAMP: real</code>: Motion amplitude, global x-direction <img class="formulaInl" alt="$ \mathrm{[L]}$" src="form_75.png"/></li>
<li><code>YAMP: real</code>: Motion amplitude, global y-direction <img class="formulaInl" alt="$ \mathrm{[L]}$" src="form_75.png"/></li>
<li><code>ZAMP: real</code>: Motion amplitude, global z-direction <img class="formulaInl" alt="$ \mathrm{[L]}$" src="form_75.png"/></li>
<li><code>XRAMP: real</code>: Motion amplitude, global x-rotation <img class="formulaInl" alt="$ \mathrm{[degrees]}$" src="form_406.png"/></li>
<li><code>YRAMP: real</code>: Motion amplitude, global y-rotation <img class="formulaInl" alt="$ \mathrm{[degrees]}$" src="form_406.png"/></li>
<li><code>ZRAMP: real</code>: Motion amplitude, global z-rotation <img class="formulaInl" alt="$ \mathrm{[degrees]}$" src="form_406.png"/></li>
<li><code>PER: real</code>: Period of motion <img class="formulaInl" alt="$ \mathrm{[T]}$" src="form_77.png"/></li>
</ul>
<p><code>PER</code> is dummy input if a regular wave is specified, i.e. <code>IRWCN &gt; 0</code> (data group <a class="el" href="a00014.html#dynmod_c_parameters_analysis">Analysis parameters</a>). In the case of multiple vessels, <code>PER</code> is only read for the first vessel and the specified period used for all vessels.</p>
<h4><a class="anchor" id="dynmod_c_regular_definition_motion_angles"></a>
Motion phase angles, one input line</h4>
<div class="fragment"><div class="line">XPHA YPHA ZPHA XRPHA YRPHA ZRPHA</div>
</div><!-- fragment --><ul>
<li><code>XPHA: real</code>: Phase angle, x-motion <img class="formulaInl" alt="$ \mathrm{[degrees]}$" src="form_406.png"/></li>
<li><code>YPHA: real</code>: Phase angle, y-motion <img class="formulaInl" alt="$ \mathrm{[degrees]}$" src="form_406.png"/></li>
<li><code>ZPHA: real</code>: Phase angle, z-motion <img class="formulaInl" alt="$ \mathrm{[degrees]}$" src="form_406.png"/></li>
<li><code>XRPHA: real</code>: Phase angle, x-rotation <img class="formulaInl" alt="$ \mathrm{[degrees]}$" src="form_406.png"/></li>
<li><code>YRPHA: real</code>: Phase angle, y-rotation <img class="formulaInl" alt="$ \mathrm{[degrees]}$" src="form_406.png"/></li>
<li><code>ZRPHA: real</code>: Phase angle, z-rotation <img class="formulaInl" alt="$ \mathrm{[degrees]}$" src="form_406.png"/></li>
</ul>
<p>All phase angles are defined as follows:</p>
<p>Positive angle: Forward phase shift; motion before sea surface at global origin.</p>
<p>Surface: <img class="formulaInl" alt="$ \mathrm{\eta = \eta_a sin(\omega t + \phi_p), \quad \phi_p = -kxcos(\beta) - kysin(\beta) }$" src="form_407.png"/></p>
<p>Motion: <img class="formulaInl" alt="$ \mathrm{x_i = x_{ai}sin(\omega t + \phi_i)}$" src="form_408.png"/></p>
<p>Where:</p>
<ul>
<li><img class="formulaInl" alt="$ \mathrm{x_i}$" src="form_409.png"/> is equation of motion</li>
<li><img class="formulaInl" alt="$ \mathrm{\eta_a}$" src="form_410.png"/> is wave amplitude</li>
<li><img class="formulaInl" alt="$ \mathrm{x_{ai}}$" src="form_411.png"/> is motion amplitude <code>XAMP</code>, <code>YAMP</code>, etc.</li>
<li><img class="formulaInl" alt="$ \mathrm{\phi_i}$" src="form_412.png"/> is phase angle, <code>XPHA</code>, <code>YPHA</code>, etc.</li>
<li><img class="formulaInl" alt="$ \mathrm{k}$" src="form_413.png"/> is wave number</li>
<li><img class="formulaInl" alt="$ \mathrm{\omega}$" src="form_414.png"/> is angular frequency</li>
<li><img class="formulaInl" alt="$ \mathrm{x, y}$" src="form_415.png"/> is global coordinates</li>
</ul>
<p>If the forward phase shift <img class="formulaInl" alt="$ \mathrm{\phi_i^{xy}}$" src="form_416.png"/> between wave and motion at the same point (x,y) is known, the phase into <code>RIFLEX</code> must be modified as follows:</p>
<p><img class="formulaInl" alt="$ \mathrm{\phi_i = \phi_i^{xy} + \phi_p}$" src="form_417.png"/></p>
<p>in order to obtain phase relation between motion at (x,y) and a wave with start at global origin as defined above.</p>
<h1><a class="anchor" id="dynmod_d"></a>
Data Group D: Irregular Wave, Time Domain Analysis</h1>
<p>This data group is given for <code>IANAL=IRREgular</code>, see <a class="el" href="a00014.html#dynmod_a_principal_options">Options and identifiers, one input line</a>. Data group A and E must also be given for complete definition of an irregular time domain analysis.</p>
<h2><a class="anchor" id="dynmod_d_parameters"></a>
Irregular time series parameters</h2>
<p>The input in this data group is used to specify the method used for computation of the underlaying irregular waves, i.e. the seed used for random number generation and the frequency resolution.</p>
<p>The data group may be skipped if default values are wanted. The data group is dummy if any floater force models are present in the model. (The analysis is done in combination with <code>SIMO</code>, so-called coupled analysis, and the irregular time series parameters defined by input to <code>SIMO</code>).</p>
<h3><a class="anchor" id="dynmod_d_parameters_data"></a>
Data group identifier, one input line</h3>
<div class="fragment"><div class="line">IRREgular TIMEseries PARAmeters</div>
</div><!-- fragment --><h3><a class="anchor" id="dynmod_d_parameters_parameters"></a>
Parameters, one input line</h3>
<div class="fragment"><div class="line">IRAND TIMGEN DTGEN CHFREQ CHAMP</div>
</div><!-- fragment --><ul>
<li><code>IRAND: integer, default: 1</code>: Starting parameter of random number generator</li>
<li><code>TIMGEN: real, defaul: 16384</code>: Length of prescribed wave and motion time series <img class="formulaInl" alt="$ \mathrm{[T]}$" src="form_77.png"/></li>
<li><code>DTGEN: real, defaul: 0.5</code>: Time increment of pre-sampled time series <img class="formulaInl" alt="$ \mathrm{[T]}$" src="form_77.png"/></li>
<li><code>CHFREQ: character(7), default: FFT</code>: Option for selecting wave frequency components<ul>
<li><code>= 'FFT'</code>: Wave frequency components are selected among the FFT frequencies given by <code>TIMEGEN</code> and <code>DTGEN</code>. The default criteria are used to find the first and last frequencies.</li>
</ul>
</li>
<li><code>CHAMP: character(5), default: DET</code>: Option for selecting wave component amplitudes<ul>
<li><code>= 'DET'</code>: Deterministic wave amplitudes are used.</li>
<li><code>= 'STOCH'</code>: Stochastic wave amplitudes are used.</li>
<li><code>= 0</code>: Interpreted as <code>DET</code>. Included for compatibility with earlier versions.</li>
</ul>
</li>
</ul>
<p>Note that this data group is dummy for coupled analysis.</p>
<p>Also note that:</p>
<ul>
<li><code>TIMGEN</code> should be equal or longer than the simulation length, <code>TIME</code>, given in <a class="el" href="a00014.html#dynmod_d_analysis">Irregular response analysis and subsequent input</a>.</li>
<li><code>TIMGEN</code> will, if necessary, be increased to give a power of 2 time steps (<code>DTGEN</code>).</li>
<li>The actual time increment used for time domain analysis is defined by the parameter <code>DT</code>, see <a class="el" href="a00014.html#dynmod_d_analysis">Irregular response analysis and subsequent input</a>.</li>
<li>To represent the wave surface- and motion time series properly, time increments, <code>DTGEN</code>, in the range 0.5-1 s are normally acceptable.</li>
</ul>
<h2><a class="anchor" id="dynmod_d_analysis"></a>
Irregular response analysis and subsequent input</h2>
<h3><a class="anchor" id="dynmod_d_analysis_data"></a>
Data group identifier, one input line</h3>
<div class="fragment"><div class="line">IRREgular RESPonse ANALysis</div>
</div><!-- fragment --><h3><a class="anchor" id="dynmod_d_analysis_parameters"></a>
Analysis parameters, one input line</h3>
<div class="fragment"><div class="line">IRCNO TIME DT CHWAV CHMOT CHLFM TBEG ISCALE</div>
</div><!-- fragment --><ul>
<li><code>IRCNO: integer/character</code>: Irregular wave case number in actual environment applied in this run<ul>
<li>or if <code>IRCNO = FILE</code>: Wave time series read from file. Data groups <a class="el" href="a00014.html#dynmod_d_irregular_waves">Irregular waves</a> and <a class="el" href="a00014.html#dynmod_d_wave_and_motion_time_series">Wave time series file</a> must be given</li>
<li>Dummy for coupled analysis.</li>
</ul>
</li>
<li><code>TIME: real, default: 11000</code>: Length of simulation <img class="formulaInl" alt="$ \mathrm{[T]} $" src="form_324.png"/></li>
<li><code>DT: real, default: 0.1</code>: Time step <img class="formulaInl" alt="$ \mathrm{[T]} $" src="form_324.png"/><ul>
<li>See below</li>
</ul>
</li>
<li><code>CHWAV: character(4), default: NEW</code>: Irregular wave indicator<ul>
<li><code>= 'NONE'</code>: No wave forces in present analysis. If specified the riser will have forced excitation at upper end and oscillate in undisturbed water or in constant current</li>
<li><code>= NEW</code>: Wave forces present. New data generated. Data group <a class="el" href="a00014.html#dynmod_d_irregular_waves">Irregular waves</a> must be given.</li>
</ul>
</li>
<li><code>CHMOT: character(4), default: STAT</code>: Irregular motion indicator<ul>
<li><code>= 'NONE'</code>: No irregular motions in present analysis</li>
<li><code>= STAT</code>: Forced irregular motions present. Computation of prescribed motions will be based on vessel position in final static position.</li>
<li><code>= NEW</code>: Interpreted as <code>CHMOT=STAT</code></li>
<li><code>= FILE</code>: Forced irregular motions present. Wave frequency motion time series read from file. Data group <a class="el" href="a00014.html#dynmod_d_wave_and_motion_frequency">Wave frequency motion time series file</a> must be given.</li>
</ul>
</li>
<li><code>CHLFM: character(4), default: 'NONE'</code>: Low frequency motion indicator<ul>
<li><code>= 'NONE'</code>: No low frequency irregular motions present</li>
<li><code>= FILE</code>: Forced low frequency irregular motions present. Low frequency motion time series read from file. Data group <a class="el" href="a00014.html#dynmod_d_wave_and_motion_low_frequency">Low frequency motion time series file</a> must be given.</li>
</ul>
</li>
<li><code>TBEG: real, default: 0</code>: Time in wave and motion time series that dynamic simulation will start from <img class="formulaInl" alt="$ \mathrm{[T]} $" src="form_324.png"/></li>
<li><code>ISCALE: integer, default: 0</code>: Switch for scaling of terminal point motions<ul>
<li><code>ISCALE = 0</code>: No scaling</li>
<li><code>ISCALE = 1</code>: Scaling: Input line <a class="el" href="a00014.html#dynmod_d_analysis_support">Support vessel motion scaling factors</a> has to be given</li>
</ul>
</li>
</ul>
<p><code>DT</code> will be adjusted to get an integer ratio between <code>DTGEN</code> and <code>DT</code>. <code>DT</code> given as negative integer defines the ratio between time step used in pre-simulation of waves and/or WF-motions and the time step to be used in the time simulation. (<code>DTGEN/DT &gt;= 1</code>)</p>
<p><code>TBEG</code> allows for arbitrary start point in the pre-generated time series. If the end of the time series is reached during dynamic integration, a warning is written and motions and water kinematics will be taken from the start. This can also be useful for elimination of transients from the time series statistics.</p>
<h3><a class="anchor" id="dynmod_d_analysis_support"></a>
Support vessel motion scaling factors. Only given for ISCALE=1. One line for each vessel in system (NVES lines)</h3>
<div class="fragment"><div class="line">SCALX SCALY SCALZ SCALXR SCALYR SCALZR</div>
</div><!-- fragment --><ul>
<li><code>SCALX: real, default: 1</code>: Scaling for global X-motion <img class="formulaInl" alt="$ \mathrm{[1]}$" src="form_291.png"/></li>
<li><code>SCALY: real, default: 1</code>: Scaling for global Y-motion <img class="formulaInl" alt="$ \mathrm{[1]}$" src="form_291.png"/></li>
<li><code>SCALZ: real, default: 1</code>: Scaling for global Z-motion <img class="formulaInl" alt="$ \mathrm{[1]}$" src="form_291.png"/></li>
<li><code>SCALXR: real, default: 1</code>: Scaling for global X-rotation <img class="formulaInl" alt="$ \mathrm{[1]}$" src="form_291.png"/></li>
<li><code>SCALYR: real, default: 1</code>: Scaling for global Y-rotation <img class="formulaInl" alt="$ \mathrm{[1]}$" src="form_291.png"/></li>
<li><code>SCALZR: real, default: 1</code>: Scaling for global Z-rotation <img class="formulaInl" alt="$ \mathrm{[1]}$" src="form_291.png"/></li>
</ul>
<p>The motions are scaled directly as <img class="formulaInl" alt="$ \mathrm{DISP_i = SCAL_i \times Motion_i}$" src="form_418.png"/> where <img class="formulaInl" alt="$ \mathrm{Motion_i}$" src="form_419.png"/> is the precomputed motion quantity <img class="formulaInl" alt="$ \mathrm{_i}$" src="form_420.png"/>.</p>
<h2><a class="anchor" id="dynmod_d_irregular_waves"></a>
Irregular waves</h2>
<p>This data group is omitted for <code>CHWAV='NONE'</code>, see data group <a class="el" href="a00014.html#dynmod_d_analysis_parameters">Analysis parameters, one input line</a>.</p>
<p>The data group also controls the method for computation of wave kinematics and motions of the support vessels. In this context FFT or FFT and cosine series combined means that the vessel motion is pre-generated by means of FFT, while the wave kinematics are either pre-generated (FFT) or computed during the actual simulation by use of cosine series. “Cosine series only” means that both vessel motion and wave kinematics are computed based on cosine series. It is possible to overrule the cosine series application for wave kinematics for parts of the the system by specifying FFT in the detailed specifications, see <a class="el" href="a00014.html#dynmod_d_irregular_waves_procedure_additional">Additional detailed specification of wave kinematics points (optional)</a>. (“FFT” or “FFT and cosine series combined only”.)</p>
<h3><a class="anchor" id="dynmod_d_irregular_waves_data"></a>
Data group identifier, one input line</h3>
<div class="fragment"><div class="line">IRREgular WAVE PROCedure</div>
</div><!-- fragment --><h3><a class="anchor" id="dynmod_d_irregular_waves_procedure"></a>
Procedure for wave force calculation, one input line</h3>
<div class="fragment"><div class="line">IUPPOS ISURF KINOFF CHSTEP NODSTP ZLOWER ZUPPER IOPDIF IOPWKI</div>
</div><!-- fragment --><ul>
<li><code>IUPPOS: integer, default: 1</code>: Position for calculation of irregular wave kinematics<ul>
<li><code>= 1</code>: Kinematics at static positions</li>
<li><code>= 2</code>: Kinematics at instantaneous positions calculated by summation of cosine components.</li>
<li><code>= -2</code>: Kinematics at static positions calculated by summation of cosine components. This option is mainly useful for testing.</li>
<li><code>= 0</code>: As 1 but riser fixed in static position, ("wet” elements also "wet" dynamic)</li>
</ul>
</li>
<li><code>ISURF: integer, default: 1</code>: Code for kinematics in wave zone<ul>
<li><code>= 1</code>: Integration of wave forces to mean water level</li>
<li><code>= 2</code>: Integration of wave forces to wave surface by stretching and compression of the wave potential</li>
<li><code>= 3</code>: Integration of wave forces to wave surface by moving the potential to actual surface</li>
<li><code>= 4</code>: Integration of wave forces to wave surface by keeping the potential constant from mean water level to wave surface</li>
<li><code>= 5</code>: 2nd order wave (integration of wave forces to wave surface)<ul>
<li>The formulation for 2nd order wave kinematics is based on the Stoke 2nd order wave theory. Only available for kinematics calculated at static position; <code>IUPPOS = 1 or IUPPOS = 0</code>.</li>
</ul>
</li>
</ul>
</li>
<li><code>KINOFF: integer, default: 0</code>: Code for default kinematics points procedure<ul>
<li><code>= 0</code>: Default procedure on. The initial selection of positions for computation of kinematics is determined by the parameters <code>NODSTP</code>, <code>ZLOWER</code> and <code>ZUPPER</code> for all lines in the system. Subsequent specification (see <a class="el" href="a00014.html#dynmod_d_irregular_waves_procedure_additional">Additional detailed specification of wave kinematics points (optional)</a>) will replace the initial selection.</li>
<li><code>= 1</code>: Default procedure off. Kinematics will only be computed at positions given by subsequent specification (see <a class="el" href="a00014.html#dynmod_d_irregular_waves_procedure_additional">Additional detailed specification of wave kinematics points (optional)</a>)</li>
</ul>
</li>
<li><code>CHSTEP: character(4)</code>: Code for interpretation of the next parameter<ul>
<li><code>= NODE</code>: Next parameter interpreted as <code>NODSTP</code></li>
</ul>
</li>
<li><code>NODSTP: integer</code>: Node step for calculating wave kinematics. (Dummy for <code>KINOFF = 1</code>)<ul>
<li>Kinematics calculated for every <code>NODSTP</code> node between <code>ZLOWER</code> and <code>ZUPPER</code> (see <a class="el" href="a00014.html#Definition_of_NODSTP_ZLOWER_and_ZUPPER">Definition of NODSTP, ZLOWER and ZUPPER</a>).</li>
<li>For intermediate nodes kinematics are derived by linear interpolation.</li>
<li>Wave kinematics will always be calculated at submerged supernodes.</li>
<li>Note that a negative value of <code>NODSTP</code> may be given. The distance between <code>ZUPPER</code> and <code>ZLOWER</code> is then divided into 4 (equal) intervals and <code>NODSTP</code> is increased from <code>ABS(NODSTP)</code> in the upper interval via <code>2xABS(NODSTP)</code> in the next interval and <code>4xABS(NODSTP</code>) to <code>8xABS(NODSTP)</code> in the two lower intervals, see <a class="el" href="a00014.html#Definition_of_NODSTP_ZLOWER_and_ZUPPER">Definition of NODSTP, ZLOWER and ZUPPER</a>.</li>
</ul>
</li>
<li><code>ZLOWER: real, default: -WDEPTH</code>: Z-coordinate indicating lowest node position for which wave kinematics are calculated <img class="formulaInl" alt="$ \mathrm{[L]}$" src="form_75.png"/><ul>
<li>See <a class="el" href="a00014.html#Definition_of_NODSTP_ZLOWER_and_ZUPPER">Definition of NODSTP, ZLOWER and ZUPPER</a>.</li>
<li>Dummy for <code>KINOFF = 1</code></li>
<li>For <code>WDEPTH</code>, see <a class="el" href="a00010.html#inpmod_d_water">INPMOD: Water depth and wave indicator</a></li>
</ul>
</li>
<li><code>ZUPPER: real, default: 4 x STD_WA</code>: Upper limit for wave kinematics <img class="formulaInl" alt="$ \mathrm{[L]}$" src="form_75.png"/><ul>
<li>Dummy for <code>KINOFF = 1</code></li>
<li><code>STD_WA</code> is the standard deviation of the total wave elevation</li>
</ul>
</li>
<li><code>IOPDIF: integer, default: 0</code>: Option for specification of wave kinematic transfer function.<ul>
<li><code>IOPDIF = 0</code>: No transfer function to be specified</li>
<li><code>IOPDIF = 1</code>: Read transfer functions from the file specified in <a class="el" href="a00014.html#dynmod_d_irregular_waves_procedure_trffile">Wave kinematics transfer function file name</a> (below).</li>
</ul>
</li>
<li><code>IOPWKI: integer, default: 0</code>: Option for specification of wave kinematic time series.<ul>
<li><code>IOPWKI = 0</code>: No wave kinematics time series to be specified</li>
<li><code>IOPWKI = 2</code>: Read wave kinematics time series from the file specified in <a class="el" href="a00014.html#dynmod_d_irregular_waves_procedure_tsfile">Wave kinematics time series file name</a> (below).</li>
</ul>
</li>
</ul>
<p><code>NODSTP</code>, <code>ZLOWER</code> and <code>ZUPPER</code> will normally be sufficient for specifying the selection of wave kinematics points.</p>
<p>Note that for large or complicated systems <a class="el" href="a00014.html#dynmod_d_irregular_waves_procedure_additional">Additional detailed specification of wave kinematics points (optional)</a> may be used to override the selection given by <code>NODSTP</code>, <code>ZLOWER</code> and <code>ZUPPER</code>; e.g. skip generation of wave kinematics for selected lines, generate kinematics at more points along an important line.</p>
<p><a class="anchor" id="Definition_of_NODSTP_ZLOWER_and_ZUPPER"></a></p>
<div class="image">
<img src="um_id_fig222.svg" alt="um_id_fig222.svg"/>
<div class="caption">
Definition of NODSTP, ZLOWER and ZUPPER</div></div>
<p>Note that the definition of ISURF is also used to determine where to apply wind forces to airfoil cross sections near the water line. That is, no wind forces are applied to wet sections of the element. The wind speed is nevertheless taken to be zero at or below the mean water level.</p>
<p>Note that the option <code>IUPPOS = 0</code> cannot be combined with linear analysis, <code>ITDMET = 1</code>, or nonlinear analysis, <code>ITDMET = 2</code> and <code>SIMO</code> bodies.</p>
<h4><a class="anchor" id="dynmod_d_irregular_waves_procedure_trffile"></a>
Wave kinematics transfer function file name</h4>
<p>This data group is omitted for <code>IOPDIF = 0</code> </p>
<div class="fragment"><div class="line">CHFDIF</div>
</div><!-- fragment --><ul>
<li><code>CHFDIF: character(80)</code>: File name with wave kinematic transfer function.<ul>
<li>The file format is described in <a class="el" href="a00014.html#dynmod_description_wave">Diffracted Wave Transfer Functions at Points</a>.</li>
</ul>
</li>
</ul>
<h4><a class="anchor" id="dynmod_d_irregular_waves_procedure_tsfile"></a>
Wave kinematics time series file name</h4>
<p>This data group is omitted for <code>IOPWKI = 0</code></p>
<p>Wave kinematics read from file will replace the corresponding wave kinematics calculated by <code>DYNMOD</code>. These kinematics will then be used in the calculation of Morison type hydrodynamic loads on <code>RIFLEX</code> elements. Loads on <code>SIMO</code> bodies will NOT be affected.</p>
<p><code>RIFLEX</code> vessel motions based on vessel motion transfer functions and MacCamy Fuchs and Potential flow loads on <code>RIFLEX</code> elements are per-generated from the wave Fourier components and are therefore NOT affected by the wave kinematics read from file. Elements with MacCamy Fuchs or Potential flow loads may not have kinematics read from file.</p>
<p>If kinematics read from file are used in a simulation with <code>SIMO</code> bodies, vessel motions based on vessel motion transfer functions or pre-generated hydrodynamic loads, the user must ensure that the kinematics are consistent with the Fourier components.</p>
<div class="fragment"><div class="line">CHFDIF</div>
</div><!-- fragment --><ul>
<li><code>CHFWKI: character(80)</code>: File name with wave kinematic time series.<ul>
<li>The file format is the sane as the kinematics files exported from DYNMOD using <a class="el" href="a00014.html#dynmod_d_storage">Storage of irregular wave kinematics</a></li>
</ul>
</li>
</ul>
<div class="fragment"><div class="line">ICOLMX ICOLTM</div>
</div><!-- fragment --><ul>
<li><code>ICOLMX: integer, default: 0</code>: Maximum number of columns on file</li>
<li><code>ICOLTM: integer, default: 2</code>: Column number on file for time</li>
</ul>
<h4><a class="anchor" id="dynmod_d_irregular_waves_procedure_additional"></a>
Additional detailed specification of wave kinematics points (optional)</h4>
<p>As many input lines as needed. Note three alternative formats.</p>
<h5>For wave kinematics calculated by the program from the undisturbed waves.</h5>
<div class="fragment"><div class="line">LINE-ID CHSTEP = NODE NODSTOP</div>
</div><!-- fragment --><ul>
<li><code>LINE-ID: character(8)</code>: Line identifier</li>
<li><code>CHSTEP: character(4)</code>: <code>= Node</code></li>
<li><code>NODSTP: integer</code>: Node step for calculating wave kinematics<ul>
<li><code>= 0</code>: No kinematics for this line</li>
<li><code>&gt; 0</code>: Kinematics for each <code>NODSTP</code> node</li>
</ul>
</li>
</ul>
<h5>For wave kinematics given by wave kinematics transfer functions (diffracted waves)</h5>
<div class="fragment"><div class="line">LINE-ID CHSTEP= DIFF ILSEG ILNODE IVES PTNOUS</div>
</div><!-- fragment --><ul>
<li><code>LINE-ID: character(8)</code>: Line identifier</li>
<li><code>CHSTEP: character(4)</code>: <code>= DIFF</code></li>
<li><code>ILSEG: integer</code>: Local segment number within line LINE-ID</li>
<li><code>ILNODE: integer</code>: Local node number within ILSEG</li>
<li><code>IVES: integer</code>:<ul>
<li><code>= 0</code>: Use undisturbed wave kinematics at this node</li>
<li><code>&gt; 0</code>: Support vessel number. Used as reference to transfer function for diffracted wave kinematics.</li>
</ul>
</li>
<li><code>PTNOUS: integer</code>: Point reference(s) to transfer function for diffracted wave kinematics</li>
</ul>
<p>Up to 30 values of PTNOUS may be given on each line. The diffracted kinematics at the specified node will be generated by interpolation based on the nearest point references.</p>
<h5>For wave kinematics given by wave kinematics time series</h5>
<div class="fragment"><div class="line">LINE-ID CHSTEP= WKFI ILSEG ILNODE ICOLST</div>
</div><!-- fragment --><ul>
<li><code>LINE-ID: character(8)</code>: Line identifier</li>
<li><code>CHSTEP: character(4)</code>: <code>= WKFI</code></li>
<li><code>ILSEG: integer</code>: Local segment number within line LINE-ID</li>
<li><code>ILNODE: integer</code>: Local node number within ILSEG</li>
<li><code>ICOLST: integer</code>: Column number for the first wave kinematics time series for this node</li>
</ul>
<h2><a class="anchor" id="dynmod_d_wave_and_motion"></a>
Wave and motion time series files</h2>
<h3><a class="anchor" id="dynmod_d_wave_and_motion_time_series"></a>
Wave time series file</h3>
<p>This data group is given only if <code>IRCNO = FILE</code>.</p>
<h4><a class="anchor" id="dynmod_d_wave_and_motion_time_series_data"></a>
Data group identifier, one input line</h4>
<div class="fragment"><div class="line">WAVE TIME SERIes</div>
</div><!-- fragment --><h4><a class="anchor" id="dynmod_d_wave_and_motion_time_series_file"></a>
Wave time series file information</h4>
<div class="fragment"><div class="line">CHFTSF IFORM ICOTIM ICOWAV</div>
</div><!-- fragment --><ul>
<li><code>CHFTSF: character(60)</code>: File name</li>
<li><code>IFORM: integer, default: 1</code>: File format code<ul>
<li><code>= ASCI</code>: Column organised ASCII file</li>
<li><code>= STAR</code>: Startimes file</li>
</ul>
</li>
<li><code>ICOTIM: integer, default: 1</code>: Column number for time<ul>
<li>Dummy for <code>IFORM = STAR</code></li>
</ul>
</li>
<li><code>ICOWAV: integer/real, default: 2</code>: Column or time series number for wave elevation</li>
</ul>
<p>The wave direction is given by the parameter <code>WADR1</code> given in <code>INPMOD</code> for the irregular wave case <code>IRCNO</code> referred to in <a class="el" href="a00014.html#dynmod_d_analysis_parameters">Analysis parameters, one input line</a>.</p>
<p><code>ICOTIM</code> and <code>ICOWAV</code> will refer to columns on an ASCII file; e.g. <code>ICOTIM=1</code> and <code>ICOWAV=2</code> if the time and wave elevation are in the first and second columns; or to a time series number on a Startimes file; e.g. <code>ICOWAV=10.01</code> for time series 10, version 1.</p>
<p>An arbitrary time step may be used on an ASCII file, while the Startimes file has a fixed step. Linear interpolation is used to get the motions at the time step (DTWF)</p>
<h4><a class="anchor" id="dynmod_d_wave_and_motion_time_series_direction"></a>
Direction, location of measurement and cut-off for filtering</h4>
<div class="fragment"><div class="line">WAVDIR XGWAV YGWAV TMIN TMAX</div>
</div><!-- fragment --><ul>
<li><code>WAVDIR: real, default: 0</code>: Wave direction <img class="formulaInl" alt="$ \mathrm{[deg]}$" src="form_76.png"/></li>
<li><code>XGWAV: real, default: 0</code>: Global x-coordinate for position where time series is measured</li>
<li><code>YGWAV: real, default: 0</code>: Global y-coordinate for position where time series is measured</li>
<li><code>TMIN: real, default: 0</code>: Period corresponding to cut-off frequency for filtering</li>
<li><code>TMAX: real, default: 0</code>: Period corresponding to cut-off frequency for filtering</li>
</ul>
<p>If <code>TMIN</code> and <code>TMAX</code> are both zero: No filtering</p>
<p>If <code>TMIN</code> and <code>TMAX</code> are both different from zero: band-pass filtering</p>
<p>Filtering is not implemented in present version</p>
<h3><a class="anchor" id="dynmod_d_wave_and_motion_frequency"></a>
Wave frequency motion time series file</h3>
<p>This data group is given only if <code>CHMOT=FILE</code>. Note that data must be given for all vessels in the system.</p>
<h4><a class="anchor" id="dynmod_d_wave_and_motion_frequency_data"></a>
Data group identifier, one input line</h4>
<div class="fragment"><div class="line">WFMOtion TIME SERIes</div>
</div><!-- fragment --><h4><a class="anchor" id="dynmod_d_wave_and_motion_frequency_motions"></a>
Wave frequency motions file information, NVES input lines</h4>
<div class="fragment"><div class="line">IVES CHFTSF IFORM IKIND IROT ICOTIM ICOXG ICOYG ICOZG ICOXGR ICOYGR ICOZGR</div>
</div><!-- fragment --><ul>
<li><code>IVES: integer</code>: Vessel Number</li>
<li><code>CHFTSF: character(60)</code>: File name</li>
<li><code>IFORM: character(4), default: ASCI</code>: File format code<ul>
<li><code>= ASCI</code>: Column organised ASCII file</li>
<li><code>= STAR</code>: Startimes file</li>
<li><code>= NONE</code>: No wave frequency motions for this vessel. The remainder of this input line is dummy</li>
</ul>
</li>
<li><code>IKIND: character(4), default: POSI</code>: Kind of motion time series input<ul>
<li><code>= POSI</code>: Global positions, i.e. global coordinates. The rotations are applied in the Euler sequence: Rz-Ry-Rx. Consistent with vessel motion time series from <code>SIMO</code>.</li>
<li><code>= DYND</code>: Global dynamic displacements; i.e. global coordinates minus the final static position. The rotations are applied in the Euler sequence: Rx-Ry-Rz</li>
</ul>
</li>
<li><code>IROT: character(4), default: DEGR</code>: Unit of rotations<ul>
<li><code>= DEGR</code>: Rotations given in degrees</li>
<li><code>= RADI</code>: Rotations given in radians</li>
</ul>
</li>
<li><code>ICOTIM: integer, default: 1</code>: Column number for time<ul>
<li>Dummy for <code>IFORM = STAR</code></li>
</ul>
</li>
<li><code>ICOXG: integer/real, default: 0</code>: Column or time series number for specification of global x-motion. Absolute position if <code>IKIND = POSI</code>, relative to static position if <code>IKIND = DYND</code>.</li>
<li><code>ICOYG: integer/real, default: 0</code>: Column or time series number for specification of global y-motion. Absolute position if <code>IKIND = POSI</code>, relative to static position if <code>IKIND = DYND</code>.</li>
<li><code>ICOZG: integer/real, default: 0</code>: Column or time series number for specification of global z-motion. Absolute position if <code>IKIND = POSI</code>, relative to static position if <code>IKIND = DYND</code>.</li>
<li><code>ICOXGR: integer/real, default: 0</code>: Column or time series number for specification of global x-rotation. Absolute position if <code>IKIND = POSI</code>, relative to static position if <code>IKIND = DYND</code>.</li>
<li><code>ICOYGR: integer/real, default: 0</code>: Column or time series number for specification of global y-rotation. Absolute position if <code>IKIND = POSI</code>, relative to static position if <code>IKIND = DYND</code>.</li>
<li><code>ICOZGR: integer/real, default: 0</code>: Column or time series number for specification of global z-rotation. Absolute position if <code>IKIND = POSI</code>, relative to static position if <code>IKIND = DYND</code>.</li>
</ul>
<p>Dofs may be omitted by giving <code>ICOxxx=0</code></p>
<p><code>ICOxxx</code> will refer to a column for an ASCII file; e.g. <code>ICOX=2</code> if the dynamic x motion time series is in the second column; or to a time series number for a Startimes file, e.g. <code>ICOX=1.02</code> for time series 1, version 2.</p>
<p>An arbitrary time step may be used on an ASCII file, while the Startimes file has a fixed time step. Linear interpolation is used to get the motions at the time step (<code>DTWF</code>).</p>
<p>Translational dofs are given in length units. Rotational dofs are given in degrees or radians, depending on the option <code>IROT</code>.</p>
<p>If only one rotation is nonzero or if all rotations are small, the order in which the rotations are applied will not be significant.</p>
<p>Please note that the line length of ASCII input files is currently limited to 260 characters, see <a class="el" href="a00008.html#how_to_run_formats">Formats</a> in <a class="el" href="a00008.html#how_to_run_input">How to Run the Program</a>. Note that a RIFLEX input line may be split into several lines on the input file.</p>
<h3><a class="anchor" id="dynmod_d_wave_and_motion_low_frequency"></a>
Low frequency motion time series file</h3>
<p>This data group is given only if <code>CHLFM=FILE</code>. Note that data must be given for all vessels in the system.</p>
<h4><a class="anchor" id="dynmod_d_wave_and_motion_low_frequency_data"></a>
Data group identifier, one input line</h4>
<div class="fragment"><div class="line">LFMOtion TIME SERIes</div>
</div><!-- fragment --><h4><a class="anchor" id="dynmod_d_wave_and_motion_low_frequency_file"></a>
Low frequency motions file information, NVES input lines</h4>
<div class="fragment"><div class="line">IVES CHFTSF IFORM IKIND IROT ICOTIM ICOXG ICOYG ICOZGR</div>
</div><!-- fragment --><ul>
<li><code>IVES: integer</code>: Vessel Number</li>
<li><code>CHFTSF: character(60)</code>: File name</li>
<li><code>IFORM: character(4), default: ASCI</code>: File format code<ul>
<li><code>= ASCI</code>: Column organised ASCII file</li>
<li><code>= STAR</code>: Startimes file</li>
<li><code>= NONE</code>: No wave frequency motions for this vessel. The remainder of this input line is dummy</li>
</ul>
</li>
<li><code>IKIND: character(4), default: POSI</code>: Kind of motion time series input<ul>
<li><code>= POSI</code>: Global positions, i.e. global coordinates. The rotations are applied in the Euler sequence: Rz-Ry-Rx. Consistent with vessel motion time series from <code>SIMO</code>.</li>
<li><code>= DYND</code>: Global dynamic displacements; i.e. global coordinates minus the final static position. The rotations are applied in the Euler sequence: Rx-Ry-Rz</li>
</ul>
</li>
<li><code>IROT: character(4), default: DEGR</code>: Unit of rotations<ul>
<li><code>= DEGR</code>: Rotations given in degrees</li>
<li><code>= RADI</code>: Rotations given in radians</li>
</ul>
</li>
<li><code>ICOTIM: integer, default: 1</code>: Column number for time<ul>
<li>Dummy for <code>IFORM = STAR</code></li>
</ul>
</li>
<li><code>ICOXG: integer/real, default: 0</code>: Column or time series number for specification of global x-motion. Absolute position if <code>IKIND = POSI</code>, relative to static position if <code>IKIND = DYND</code>.</li>
<li><code>ICOYG: integer/real, default: 0</code>: Column or time series number for specification of global y-motion. Absolute position if <code>IKIND = POSI</code>, relative to static position if <code>IKIND = DYND</code>.</li>
<li><code>ICOZGR: integer/real, default: 0</code>: Column or time series number for specification of global z-rotation. Absolute position if <code>IKIND = POSI</code>, relative to static position if <code>IKIND = DYND</code>.</li>
</ul>
<p>Dofs may be omitted by given <code>ICOxxx=0</code></p>
<p><code>ICOxxx</code> will refer to a column for an ASCII file; e.g. <code>ICOSUR=2</code> if the dynamic x motion time series is in the second column; or to a time series number for a Startimes file, e.g. <code>ICOX=1.02</code> for time series 1, version 2.</p>
<p>An arbitrary time step may be used on an ASCII file, while the Startimes file has a fixed time step. Linear interpolation is used to get the motions at the time step (<code>DTWF</code>).</p>
<p>Translational dofs are given in length units. Rotational dofs are given in degrees or radians, depending on the option <code>IROT</code>.</p>
<p>If only one rotation is nonzero or if all rotations are small, the order in which the rotations are applied will not be significant.</p>
<h2><a class="anchor" id="dynmod_d_print"></a>
Print options for FFT analysis</h2>
<h3><a class="anchor" id="dynmod_d_print_data"></a>
Data group identifier, one input line</h3>
<div class="fragment"><div class="line">IRREgular FOURier PRINt</div>
</div><!-- fragment --><h3><a class="anchor" id="dynmod_d_print_fourier"></a>
Fourier print options</h3>
<div class="fragment"><div class="line">IPMOTI IPWAFO IPHFTS IPLFTS IPTOMO IPVEAC</div>
</div><!-- fragment --><ul>
<li><code>IPMOTI: integer, default: 0</code>: Print option for the main routine<ul>
<li><code>&lt;= 0</code>: No print</li>
<li><code>&gt; 1</code>: Key information printed</li>
<li><code>&gt; 2</code>: Some more data printed</li>
<li><code>&gt; 5</code>: Low level debug print during numerical integration activated</li>
</ul>
</li>
<li><code>IPWAFO: integer, default: 0</code>: Print option for the wave fourier component generation<ul>
<li>Not active in present version</li>
</ul>
</li>
<li><code>IPHFTS: integer, default: 0</code>: Print option for HF-time series generation<ul>
<li><code>&lt;= 0</code>: No print</li>
<li><code>&gt; 0</code>: Print of wave frequency vessel motion time series</li>
</ul>
</li>
<li><code>IPLFTS: integer, default: 0</code>: Print option for LF-time series generation<ul>
<li><code>&lt;= 0</code>: No print</li>
<li><code>&gt; 0</code>: Print of low frequency vessel motion time series</li>
</ul>
</li>
<li><code>IPTOMO: integer, default: 0</code>: Print option for TOTAL motion time series generation<ul>
<li><code>&lt;= 0</code>: No print</li>
<li><code>&gt; 0</code>: Print of total vessel motion time series</li>
</ul>
</li>
<li><code>IPVEAC: integer, default: 0</code>: Print option for generation of water particle velocities and acceleration<ul>
<li><code>&lt;= 0</code>: No print</li>
<li><code>&gt; 1</code>: Key information printed</li>
<li><code>&gt; 2</code>: Some data printed</li>
<li><code>&gt; 5</code>: Extensive debug print of arrays with water particle velocities and accelerations</li>
</ul>
</li>
</ul>
<p>This data-group is normally supposed to be omitted. Increasing value of print options gives increasing amount of print.</p>
<h2><a class="anchor" id="dynmod_d_storage"></a>
Storage of irregular wave kinematics (optional)</h2>
<h3><a class="anchor" id="dynmod_d_storage_data"></a>
Data group identifier, one input line</h3>
<div class="fragment"><div class="line">IRREgular KINEmatics STORage</div>
</div><!-- fragment --><h3><a class="anchor" id="dynmod_d_storage_wave"></a>
Wave kinematics storage options one input line</h3>
<div class="fragment"><div class="line">NLKINE IKINFM</div>
</div><!-- fragment --><ul>
<li><code>NLKINE: integer, default: 0</code>: Number of specifications for storage of wave kinematics<ul>
<li><code>= 0</code>: Wave elevation, velocities and accelerations are stored for all kinematics nodes. Currently, no other value is allowed.</li>
</ul>
</li>
<li><code>IKINFM: integer, default: 2</code>: File format for kinematics storage<ul>
<li><code>= 1</code>: ASCII format</li>
<li><code>= 2</code>: Binary format</li>
</ul>
</li>
</ul>
<p>Pre-generated wave kinematics are written to <code>&lt;prefix&gt;_wavkin.asc</code> or <code>&lt;prefix&gt;_wavkin.bin</code>. Kinematics calculated during the simulation; <code>IUPPOS = 2 or -2</code>; are written to <code>&lt;prefix&gt;_updkin.asc</code> or <code>&lt;prefix&gt;_updkin.bin</code>.</p>
<p>The contents are described in <code>key_&lt;prefix&gt;_wavkin.txt</code> or <code>key_&lt;prefix&gt;_updkin.txt</code>.</p>
<h1><a class="anchor" id="dynmod_e"></a>
Data Group E: Time Domain Procedure and File Storage Parameters</h1>
<p>This data group must always be given for <code>IANAL = REGU</code> and <code>IRRE</code> (time domain analysis) specified in input line <a class="el" href="a00014.html#dynmod_a_principal_options">Options and identifiers, one input line</a>.</p>
<h2><a class="anchor" id="dynmod_e_method"></a>
Method of analysis and subsequent input</h2>
<h3><a class="anchor" id="dynmod_e_method_data"></a>
Data group identifier, one input line</h3>
<div class="fragment"><div class="line">TIME DOMAin PROCedure</div>
</div><!-- fragment --><h3><a class="anchor" id="dynmod_e_method_method"></a>
Method and subsequent input, one input line</h3>
<div class="fragment"><div class="line">ITDMET INEWIL</div>
</div><!-- fragment --><ul>
<li><code>ITDMET: integer, default: 1</code>: Method indicator<ul>
<li><code>ITDMET = 0</code>: Prestochastic analysis only. The rest of the data in input groups E are irrelevant</li>
<li><code>ITDMET = 1</code>: Linear analysis</li>
<li><code>ITDMET = 2</code>: Nonlinear analysis. More information to define method is given in <a class="el" href="a00014.html#dynmod_e_nonlinear">Nonlinear step by step integration</a></li>
</ul>
</li>
<li><code>INEWIL: integer, default: 1</code>: Procedure indicator<ul>
<li><code>INEWIL = 1</code>: Newmark's procedure</li>
<li><code>INEWIL = 2</code>: Wilson’s procedure, illegal for non-linear analysis</li>
</ul>
</li>
</ul>
<h3><a class="anchor" id="dynmod_e_method_time"></a>
Time integration and damping parameters, one input line</h3>
<p>This data group can be omitted if default values are wanted.</p>
<div class="fragment"><div class="line">BETIN GAMMA TETHA A1 A2 A1T A1TO A1B A2T A2TO A2B</div>
</div><!-- fragment --><ul>
<li><code>BETIN: real, default: 4/6</code>: Inverse value of beta-parameter of the Newmark beta-family of integration operators<ul>
<li><code>BETIN = 4.0</code> gives beta=1/4,i.e. constant average acceleration method</li>
</ul>
</li>
<li><code>GAMMA: real, default: 0.5</code>: Value of the parameter gamma of the Newmark operators (usually equal to 0.5)</li>
<li><code>TETHA: real, default: See below</code>: Value of the parameter tetha in Wilson's integration method</li>
<li><code>A1: real, default: 0</code>: Global mass proportional damping factor <img class="formulaInl" alt="$ \mathrm{a_1}$" src="form_421.png"/>, see definition below</li>
<li><code>A2: real, default: 0.001/0</code>: Global stiffness proportional damping factor <img class="formulaInl" alt="$ \mathrm{a_2}$" src="form_422.png"/></li>
<li><code>A1T: real, default: 0</code>: Local mass proportional damping factor <img class="formulaInl" alt="$ \mathrm{a_{1t}}$" src="form_423.png"/> for tension</li>
<li><code>A1TO: real, default: 0</code>: Local mass proportional damping factor <img class="formulaInl" alt="$ \mathrm{a_{1to}}$" src="form_424.png"/> for torsion</li>
<li><code>A1B: real, default: 0</code>: Local mass proportional damping <img class="formulaInl" alt="$ \mathrm{a_{1b}}$" src="form_425.png"/> for bending</li>
<li><code>A2T: real, default: 0</code>: Local stiffness proportional damping factor <img class="formulaInl" alt="$ \mathrm{a_{2t}}$" src="form_426.png"/> for tension</li>
<li><code>A2TO: real, default: 0</code>: Local stiffness proportional damping factor <img class="formulaInl" alt="$ \mathrm{a_{2to}}$" src="form_427.png"/> for torsion</li>
<li><code>A2B: real, default: 0</code>: Local stiffness proportional damping factor <img class="formulaInl" alt="$ \mathrm{a_{2b}}$" src="form_428.png"/> for bending</li>
</ul>
<p>Default values:</p>
<ul>
<li>For <code>INEWIL=1</code> (Newmark) the following alternative default values are: <code>BETIN=4.0</code>, <code>THETA=1.0</code>, <code>A2=0.001</code></li>
<li>For <code>INEWIL=2</code> (Wilson) default values are: <code>BETIN=6.0</code>, <code>TETHA=1.4</code> (linear)</li>
</ul>
<h4>Global proportional damping formulation:</h4>
<p><img class="formulaInl" alt="$ \mathrm{\boldsymbol{\mathrm C} = a_1 \boldsymbol{\mathrm M} + a_2 \boldsymbol{\mathrm K} }$" src="form_429.png"/></p>
<p>This means that the global damping matrix <img class="formulaInl" alt="$ \mathrm{\boldsymbol{\mathrm C} }$" src="form_430.png"/> is established as a linear combination of the global mass ( <img class="formulaInl" alt="$ \mathrm{ \boldsymbol {\mathrm M}}$" src="form_431.png"/>) and stiffness ( <img class="formulaInl" alt="$ \mathrm{\boldsymbol {\mathrm K} }$" src="form_432.png"/>) matrices.</p>
<h4>Numerical values of <img class="formulaInl" alt="$ \mathrm{a_1} $" src="form_433.png"/> and <img class="formulaInl" alt="$ \mathrm{a_2} $" src="form_434.png"/>:</h4>
<p>Let the structural damping to critical damping ratio, <img class="formulaInl" alt="$ \mathrm{c/(2m \omega) }$" src="form_435.png"/>, at two natural frequencies <img class="formulaInl" alt="$ \mathrm{\omega_1 }$" src="form_436.png"/> and <img class="formulaInl" alt="$ \mathrm{\omega_2 }$" src="form_437.png"/> be <img class="formulaInl" alt="$ \mathrm{\lambda_1 }$" src="form_438.png"/> and <img class="formulaInl" alt="$ \mathrm{\lambda_2 }$" src="form_439.png"/>, respectively. Then <code>A1</code> and <code>A2</code> can be computed as:</p>
<ul>
<li><img class="formulaInl" alt="$ \mathrm{a_1 = \frac{2 \omega_1 \omega_2 }{ \omega_2^2 - \omega_1^2}(\lambda_1 \omega_2 - \lambda_2 \omega_1) }$" src="form_440.png"/></li>
<li><img class="formulaInl" alt="$ \mathrm{a_2 = \frac{2( \omega_2 \lambda_2 - \omega_1 \lambda_1) }{ \omega_2^2 - \omega_1^2} }$" src="form_441.png"/></li>
</ul>
<h4>Local proportional damping formulation:</h4>
<p>In this approach, the damping coefficients are introduced in the local degrees of freedom in order to allow for different damping levels in bending, torsion and tension. The element damping matrix can the be written as</p>
<p><img class="formulaInl" alt="$ \mathrm{\boldsymbol{\mathrm c} = a_{1t} \boldsymbol{\mathrm m}_t + a_{1to} \boldsymbol{\mathrm m}_{to} + a_{1b} \boldsymbol{\mathrm m}_b + a_{2t} \boldsymbol{\mathrm k}_t + a_{2to} \boldsymbol{\mathrm k}_{to} + a_{2b} \boldsymbol{\mathrm k}_{b} }$" src="form_442.png"/></p>
<p>where subscripts <img class="formulaInl" alt="$ \mathrm{ _t }$" src="form_443.png"/>, <img class="formulaInl" alt="$ \mathrm{ _{to} }$" src="form_444.png"/> and <img class="formulaInl" alt="$ \mathrm{_b }$" src="form_445.png"/> refer to tension, torsion and bending contributions, respectively, and the matrices <img class="formulaInl" alt="$ \boldsymbol{\mathrm c_{} }$" src="form_446.png"/>, <img class="formulaInl" alt="$ \boldsymbol{\mathrm m }$" src="form_447.png"/> and <img class="formulaInl" alt="$ \boldsymbol{\mathrm k_{} }$" src="form_448.png"/> are local element matrices; e.g. <img class="formulaInl" alt="$ \mathrm {\boldsymbol{\mathrm k}_b} $" src="form_449.png"/> includes all bending deformation terms in the local element stiffness matrix.</p>
<p>Note that for CRS7 the matrix <img class="formulaInl" alt="$ \boldsymbol{\mathrm k_{} }$" src="form_448.png"/> includes only the material stiffness matrix. The geometric stiffness matrix is not included as this would introduce damping of the rigid body motion.</p>
<p>One should be careful with global mass proportional damping as this may introduce internal damping from rigid body motion.</p>
<p>If <img class="formulaInl" alt="$ \mathrm{a_1 = }$" src="form_450.png"/> <code>0</code>, <img class="formulaInl" alt="$ \mathrm{a_2}$" src="form_422.png"/> simply becomes <img class="formulaInl" alt="$ \mathrm{2 \lambda / \omega}$" src="form_451.png"/>.</p>
<p>Note that proportional damping (global and local) adds to a possible structural damping arising from hysteresis in bending moment/curvature relation.</p>
<h3><a class="anchor" id="dynmod_e_method_non"></a>
Non-linear force model, one input line. Always submit for linear and non-linear analysis</h3>
<div class="fragment"><div class="line">INDINT INDHYD MAXHIT EPSHYD TRAMP INDREL ICONRE ISTEPR LDAMP</div>
</div><!-- fragment --><ul>
<li><code>INDINT: integer, default: 1</code>: Indicator for modelling forces from internal slug flow<ul>
<li>Nonlinear analysis only.</li>
<li><code>INDINT = 1</code>: Forces from internal slug flow not considered</li>
<li><code>INDINT = 2</code>: Forces from internal slug flow considered.</li>
<li>Data group <a class="el" href="a00014.html#dynmod_e_slug">Slug force calculations</a> or <a class="el" href="a00014.html#dynmod_e_import">Import of internal flow data from file</a> must be given.</li>
</ul>
</li>
<li><code>INDHYD: integer, default: 1</code>: Indicator for hydrodynamic force model. Linear analysis only.<ul>
<li>(see 'Dynamic Time Domain Analysis' in the Theory Manual).</li>
<li><code>INDHYD = 1</code>: No force iteration, use of displacements and velocities at previous time step</li>
<li><code>INDHYD = 2</code>: No force iteration, use of displacements, velocities and accelerations at previous time step (not recommended)</li>
<li><code>INDHYD = 3</code>: Force iteration performed</li>
</ul>
</li>
<li><code>MAXHIT: integer, default: 5</code>: Maximum number of load iterations. Linear analysis only.<ul>
<li>A negative value gives print of convergence for each step, then <code>MAXHIT = ABS(MAXHIT)</code></li>
</ul>
</li>
<li><code>EPSHYD: real, default: 0.01</code>: Convergence control parameter for force iteration. Linear analysis only.<ul>
<li>Dummy for <code>INDHYD = 1, 2</code> <img class="formulaInl" alt="$ \mathrm{[1]}$" src="form_291.png"/></li>
</ul>
</li>
<li><code>TRAMP: real, default: 10</code>: Duration of start-up procedure <img class="formulaInl" alt="$ \mathrm{[T]}$" src="form_77.png"/></li>
<li><code>INDREL: integer, default: 0</code>: Indicator for rupture/release<ul>
<li><code>INDREL = 0</code>: No riser rupture/release</li>
<li><code>INDREL = 1</code>: Riser rupture/release will be simulated</li>
</ul>
</li>
<li><code>ICONRE: integer, default: 0</code>: Ball joint connector no. to be released<ul>
<li><code>ICONRE = 0</code>: All ball joint connectors in the system are released simultaneously</li>
<li><code>ICONRE = i</code>: Ball joint connector no. i is released. See reference number ("ref no") in the table Components on the <code>STAMOD</code> result file for connector numbering. The connectors are normally numbered from the first end as 1, 2 etc. following the <code>FEM</code> model.</li>
</ul>
</li>
<li><code>ISTEPR: integer, default: 0</code>: Time step no. for release (nonlinear analysis only)<ul>
<li>In linear analysis the ball joint connector will be released at the first step</li>
</ul>
</li>
<li><code>LDAMP: integer, default: 0</code>: Option for calculation of proportional damping matrix in nonlinear analysis.<ul>
<li>Irrelevant for linear analyses</li>
<li><code>LDAMP = 0</code>: Use constant proportional damping matrix calculated at static position</li>
<li><code>LDAMP = 1</code>: Use updated proportional damping matrix according to instantaneous mass and stiffness matrices</li>
</ul>
</li>
</ul>
<p>For non-linear analysis (<code>ITDMET = 2</code>, see <a class="el" href="a00014.html#dynmod_e_method_method">Method and subsequent input, one input line</a>) <code>INDHYD</code> can have the values 1 or 2. Input of 3 will be interpreted as 2. Load iteration for non-linear analysis will always be performed in connection with equilibrium iteration, but not during equilibrium correction.</p>
<p>If load convergence is not obtained after <code>MAXHIT</code> iteration, computation will proceed after output of warning.</p>
<p>As a release/rupture analysis is very sensitive, a short time step and rather firm convergence limit is required. If the response of part of the system is not of interest after the release, the <a class="el" href="a00014.html#dynmod_e_time_boundary">Boundary change option</a> may be used to fix the nodes in this part of the system.</p>
<p><a class="anchor" id="Definition_of_clutch_start_up_procedure"></a></p>
<div class="image">
<img src="um_id_fig237.svg" alt="um_id_fig237.svg"/>
<div class="caption">
Definition of clutch (start up procedure)</div></div>
<h2><a class="anchor" id="dynmod_e_nonlinear"></a>
Nonlinear step by step integration</h2>
<p>This data group is only given for <code>ITDMET=2</code> (input group <a class="el" href="a00014.html#dynmod_e_method_method">Method and subsequent input, one input line</a>).</p>
<h3><a class="anchor" id="dynmod_e_nonlinear_data"></a>
Data group identifier, one input line</h3>
<div class="fragment"><div class="line">NONLinear INTEgration PROCedure</div>
</div><!-- fragment --><h3><a class="anchor" id="dynmod_e_nonlinear_specification"></a>
Specification of incrementation procedure, one input line</h3>
<div class="fragment"><div class="line">ITFREQ ISOLIT MAXIT DACCU ICOCOD IVARST ITSTAT CHNORM EACCU</div>
</div><!-- fragment --><ul>
<li><code>ITFREQ: integer, default: 1</code>: Frequency of equilibrium iteration<ul>
<li><code>ITFREQ &lt;= 0</code>: Iteration will not be performed</li>
<li><code>ITFREQ &gt;= 1</code>: Iteration will be performed every <code>ITFREQ</code> time step. For steps without iteration equilibrium correction will be performed.</li>
<li>The remaining variables in this input line are dummy if <code>ITFREQ &lt;= 0</code></li>
</ul>
</li>
<li><code>ISOLIT: integer, default: 1</code>: Type of iteration if iteration is to be performed<ul>
<li><code>ISOLIT = 1</code>: True Newton-Raphson, updating of geometric stiffness from axial force</li>
<li><code>ISOLIT = 2</code>: Modified Newton-Raphson iteration</li>
<li>Modified Newton-Raphson iteration is not included in the current version of the program</li>
</ul>
</li>
<li><code>MAXIT: integer, default: 10</code>: Maximum number of iterations for steps with iteration</li>
<li><code>DACCU: real, default:</code> <img class="formulaInl" alt="$ 10^{-6}$" src="form_452.png"/>: Desired accuracy for equilibrium iteration measured by a modified Euclidean displacement norm (norm of squared translations)<ul>
<li>Recommended values: <img class="formulaInl" alt="$ 10^{-6} - 10^{-5} $" src="form_453.png"/> cfr. <code>STAMOD</code> analysis <img class="formulaInl" alt="$ \mathrm{[1]}$" src="form_291.png"/></li>
</ul>
</li>
<li><code>ICOCOD: integer, default: 1</code>: Code for continuation after iteration<ul>
<li><code>ICOCOD = 0</code>: Computations interrupted if accuracy requirements are not fulfilled</li>
<li><code>ICOCOD = 1</code>: Computations continue even if accuracy requirements are not fulfilled. Warning is printed</li>
</ul>
</li>
<li><code>IVARST: integer, default: 0</code>: Code for automatic subdivision of time step<ul>
<li><code>IVARST = 0</code>: No subdivision</li>
<li><code>IVARST &gt; 0</code>: Automatic subdivision of time step if required accuracy is not obtained with original time step or if incremental rotations are to large.</li>
<li>Maximum number of subdivisions: <img class="formulaInl" alt="$ \mathrm{ 2^{IVARST} }$" src="form_454.png"/></li>
</ul>
</li>
<li><code>ISTAT: integer, default: 1</code>: Code for time integration information<ul>
<li><code>ITSTAT = 0</code>: No information</li>
<li><code>ITSTAT &gt; 1</code>: Number of iterations, subdivisions and obtained accuracy are presented</li>
</ul>
</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>EACCU: 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>
<h2><a class="anchor" id="dynmod_e_modification"></a>
Modification to water kinematics</h2>
<p>Modification to water kinematics due to moonpool kinematics may be specified. The water kinematics will be based on the velocities and acceleration of the actual support vessel or floater force model specified.</p>
<h3><a class="anchor" id="dynmod_e_modification_data"></a>
Data group identifier, one input line</h3>
<div class="fragment"><div class="line">WATEr KINEmatic CONDition</div>
</div><!-- fragment --><h3><a class="anchor" id="dynmod_e_modification_data_rigid"></a>
Rigid moonpool column, one input line</h3>
<div class="fragment"><div class="line">RIGId MOONpool COLumn</div>
</div><!-- fragment --><h4><a class="anchor" id="dynmod_e_modification_data_rigid_number"></a>
Specification of number of moonpools, one input line</h4>
<div class="fragment"><div class="line">NLSPEC</div>
</div><!-- fragment --><ul>
<li><code>NLSPEC: integer</code>: Number of Rigid Moonpool Columns</li>
</ul>
<h4><a class="anchor" id="dynmod_e_modification_data_rigid_support"></a>
Specification of support vessel moonpool, one input line.</h4>
<div class="fragment"><div class="line">CHSUPP IVES ZLLOW ZLUP</div>
</div><!-- fragment --><ul>
<li><code>CHSUPP: character</code>: Type of support vessel<ul>
<li><code>= VESSEL</code>: <code>RIFLEX</code> support vessel (Prescribed motions)</li>
<li><code>= FLOATER</code>: Floater force model</li>
</ul>
</li>
<li><code>IVES: integer</code>: Support vessel number</li>
<li><code>ZLLOW: real</code>: Lower Z limit (local vessel system) <img class="formulaInl" alt="$ \mathrm{[L]}$" src="form_75.png"/></li>
<li><code>ZLUP: real</code>: Upper Z limit (local vessel system) <img class="formulaInl" alt="$ \mathrm{[L]}$" src="form_75.png"/></li>
</ul>
<p>One input line</p>
<h4><a class="anchor" id="dynmod_e_modification_data_rigid_lines"></a>
Specification of lines within present moonpool, one input line</h4>
<div class="fragment"><div class="line">LINE-ID1 LINE-ID2 ....... LINE-IDi .........LINE-IDn</div>
</div><!-- fragment --><ul>
<li><code>LINE-ID: character(8)</code>: Line identifiers within moon pool</li>
</ul>
<p>The data groups 'Specification of support vessel moonpool' and 'Specification of lines within present moonpool' are to be repeated <code>NLSPEC</code> times.</p>
<ul>
<li>Rigid moonpool column may not be combined with CHMOT='NONE': No irregular motions, for irregular wave analysis .</li>
<li>Rigid moonpool column may not be combined with IMOTD = 0: No motions, for regular wave analysis.</li>
<li>If current is loaded in static analysis, the current forces will be removed at start of dynamic analysis for lines within moonpool and may create a transient.</li>
</ul>
<h2><a class="anchor" id="dynmod_e_slug"></a>
Slug force calculations</h2>
<p>This data group is only given for <code>INDINT=2</code> (<a class="el" href="a00014.html#dynmod_e_method_non">Non-linear force model, one input line. Always submit for linear and non-linear analysis</a>), and slug forces can only be specified for single risers.</p>
<h3><a class="anchor" id="dynmod_e_slug_data"></a>
Data group identifier, one input line</h3>
<p>Restrictions</p>
<ul>
<li>The main riser line has to be modelled by beam elements</li>
<li>Consistent formulation (Lumped mass option is prohibited)</li>
</ul>
<p>Assumptions</p>
<ul>
<li>The total slug mass is constant, <img class="formulaInl" alt="$\boldsymbol{\mathrm{M_S}}$" src="form_455.png"/>. Initial length is <img class="formulaInl" alt="$\boldsymbol{\mathrm{L_{S0}}}$" src="form_456.png"/></li>
<li>The specified velocity refers to the gravity centre of the slug, initially at the half length.</li>
<li>The slug specification is superimposed on the riser mass, including any internal fluid flow.</li>
<li>The internal cross-section area is not used in the slug modelling</li>
<li>The slug length is divided into sections. Initially the sections are of equal length <img class="formulaInl" alt="$\boldsymbol{\mathrm{dl_{S,0}}}$" src="form_457.png"/>. The density, (mass per unit length) is constant within each section. Initially the mass per unit length is <img class="formulaInl" alt="$\boldsymbol{\mathrm{m_0 = M_S/L_{S0}}}$" src="form_458.png"/></li>
</ul>
<h4>Input description for slug force specification</h4>
<div class="fragment"><div class="line">SLUG FORCe SPECification</div>
</div><!-- fragment --><h3><a class="anchor" id="dynmod_e_slug_specification"></a>
Specification of slug data, one input line</h3>
<div class="fragment"><div class="line">TSLUG ICOSLG SLGLEN SLGMAS SLGVEL IDENS IVEL NCYCLE CYCTIM</div>
</div><!-- fragment --><ul>
<li><code>TSLUG: real, default: 0</code>: Time when slug enters first end of main riser line <img class="formulaInl" alt="$ \mathrm{[T]}$" src="form_77.png"/></li>
<li><code>ICOSLG: integer, default: 1</code>: Interruption parameter<ul>
<li><code>=0</code>: Analysis termination controlled by slug</li>
<li><code>=1</code>: Analysis termination controlled by specified length of simulation (TIME)</li>
</ul>
</li>
<li><code>SLGLEN: real</code>: Initial slug length <img class="formulaInl" alt="$ \mathrm{[L]}$" src="form_75.png"/></li>
<li><code>SLGMAS: real</code>: Slug mass <img class="formulaInl" alt="$ \mathrm{[M]}$" src="form_232.png"/></li>
<li><code>SLGVEL: real</code>: Initial slug velocity <img class="formulaInl" alt="$ \mathrm{[L/T]}$" src="form_68.png"/></li>
<li><code>IDENS: integer, default: 0</code>: Control parameter density<ul>
<li><code>= 0</code>: Constant density</li>
<li><code>= 1</code>: Variable density with vertical position</li>
</ul>
</li>
<li><code>IVEL: integer, default: 0</code>: Control parameter velocity<ul>
<li><code>= 0</code>: Constant velocity</li>
<li><code>= 1</code>: Variable velocity</li>
<li>The specified velocity refers to the gravity centre of the slug</li>
</ul>
</li>
<li><code>NCYCLE: integer, default: 1</code>: Number of slug cycles</li>
<li><code>CYCTIM: real</code>: Slug cycle time (dummy if <code>NCYCLE = 1</code>) <img class="formulaInl" alt="$ \mathrm{[T]}$" src="form_77.png"/></li>
</ul>
<h4>if <code>IDENS = 1</code>:</h4>
<div class="fragment"><div class="line">Z2 SLGMA2 ZREF</div>
</div><!-- fragment --><ul>
<li><code>Z2: real</code>: Second vertical position where the slug unit mass is specified <img class="formulaInl" alt="$ \mathrm{[L]}$" src="form_75.png"/></li>
<li><code>SLGMA2: real</code>: Slug unit mass at <code>Z2</code> <img class="formulaInl" alt="$ \mathrm{[M/L]}$" src="form_459.png"/></li>
<li><code>ZREF: real &lt; 0</code>: Reference depth <img class="formulaInl" alt="$ \mathrm{[L]}$" src="form_75.png"/><ul>
<li><code>ZREF</code> &lt; <img class="formulaInl" alt="$\mathrm{Z_{MIN}}$" src="form_460.png"/>, where <img class="formulaInl" alt="$\mathrm{Z_{MIN}}$" src="form_460.png"/> is lowest vertical position along the main riser line</li>
</ul>
</li>
</ul>
<p>The unit mass at a specific z-position is calculated according to the following equation:</p>
<p><img class="formulaInl" alt="$ \mathrm{m(Z_i) = A(Z_i-Z_{REF})^\alpha }$" src="form_461.png"/></p>
<p>where</p>
<ul>
<li><img class="formulaInl" alt="$\mathrm{ \alpha = \frac{ln(m_1/m_2)}{ln(\frac{Z_1 - Z_{REF}}{Z_2 - Z_{REF}})}}$" src="form_462.png"/></li>
<li><img class="formulaInl" alt="$\mathrm{A = \frac{m_1}{(Z_1 - Z_{REF})^\alpha } }$" src="form_463.png"/></li>
<li><img class="formulaInl" alt="$ \mathrm{m_1}$" src="form_464.png"/>: <code>SLGMAS/SLGLEN</code></li>
<li><img class="formulaInl" alt="$ \mathrm{m_2}$" src="form_465.png"/>: <code>SLGMA2</code></li>
<li><img class="formulaInl" alt="$ \mathrm{Z_1}$" src="form_466.png"/>: Vertical coordinate at inlet, end 1 of main riser line</li>
</ul>
<div class="image">
<img src="um_fig_244.svg" alt="um_fig_244.svg"/>
<div class="caption">
Internal slug flow</div></div>
<h4>if <code>IVEL = 1</code>:</h4>
<div class="fragment"><div class="line">DELVEL VEXP</div>
</div><!-- fragment --><ul>
<li><code>DELVEL: real</code>: Velocity specification</li>
<li><code>VEXP: real</code>: Exponent for velocity</li>
</ul>
<p>The unit mass at a specific z-position is calculated according to the following equation:</p>
<p><img class="formulaInl" alt="$ \mathrm{V(Z_i) = V_1 - \Delta V |Z_i - Z_1|^\alpha}\quad $" src="form_467.png"/> for <img class="formulaInl" alt="$\quad \mathrm{(Z_i - Z_1) >= 0}$" src="form_468.png"/></p>
<p><img class="formulaInl" alt="$ \mathrm{V(Z_i) = V_1 + \Delta V |Z_i - Z_1|^\alpha}\quad $" src="form_469.png"/> for <img class="formulaInl" alt="$\quad \mathrm{(Z_i - Z_1) < 0}$" src="form_470.png"/></p>
<p>Where:</p>
<ul>
<li><img class="formulaInl" alt="$ \mathrm{V_1}$" src="form_471.png"/>: Initial slug velocity (Velocity at inlet)</li>
<li><img class="formulaInl" alt="$ \mathrm{\Delta V}$" src="form_472.png"/>: <b>DELVEL</b></li>
<li><img class="formulaInl" alt="$ \mathrm{Z_i}$" src="form_473.png"/>: Vertical coordinate at inlet, end 1 of main riser line</li>
<li><img class="formulaInl" alt="$ \mathrm{\alpha}$" src="form_474.png"/>: <b>VEXP</b></li>
</ul>
<h2><a class="anchor" id="dynmod_e_import"></a>
Import of internal flow data from file</h2>
<p>This data group is only given for <code>INDINT=2</code> (see <a class="el" href="a00014.html#dynmod_e_method_non">Non-linear force model, one input line. Always submit for linear and non-linear analysis</a>)</p>
<h3><a class="anchor" id="dynmod_e_import_data"></a>
Data group identifier, 1 input line</h3>
<div class="fragment"><div class="line">IMPOrt FLOW DATA</div>
</div><!-- fragment --><h3><a class="anchor" id="dynmod_e_import_specification"></a>
Specification of input flow file, one input line</h3>
<div class="fragment"><div class="line">IMRL CHOPAD CHFFLW</div>
</div><!-- fragment --><ul>
<li><code>IMRL: integer, default: 0</code>: Main riser line number<ul>
<li><code>= 0</code>: All lines</li>
</ul>
</li>
<li><code>CHOPAD: character(4), default: REPL</code>: Fluid contents option<ul>
<li><code>= REPL</code>: Specified flow replaces that given in the Main Riser Line definition</li>
<li><code>= ADDI</code>: Specified flow is in addition to that given in the Main Riser Line definition</li>
</ul>
</li>
<li><code>CHFFLW: character(70)</code>: Name of flow data file</li>
</ul>
<p>The flow input file is described in <a class="el" href="a00014.html#dynmod_description_internal">See Internal flow description</a></p>
<h2><a class="anchor" id="dynmod_e_dynamic_current"></a>
Dynamic current variation</h2>
<p>Available for nonlinear dynamic analysis, but only when the current profile is specified explicitly on the <code>INPMOD</code> input file. This means that this data group can not be given when the current is specified on a <code>CURMOD</code> input file. However, dynamic current conditions can alternatively be specified using <code>CURMOD</code>.</p>
<p>Varying current velocity and direction are specified at the current levels defined in the preceding static analysis. The varying current is to be described in a separate file. For description of the file format, confer chapter <a class="el" href="a00014.html#dynmod_description_current">Description of Additional Input Files: Dynamic Current Variation</a>.</p>
<h3><a class="anchor" id="dynmod_e_dynamic_current_data"></a>
Data group identifier, one input line</h3>
<div class="fragment"><div class="line">DYNAmic CURRent VARIation</div>
</div><!-- fragment --><h3><a class="anchor" id="dynmod_e_dynamic_current_file"></a>
File name</h3>
<div class="fragment"><div class="line">CHFCUR</div>
</div><!-- fragment --><ul>
<li><code>CHFCUR: character(80)</code>: File name with current velocity and direction</li>
</ul>
<p>ASCII file containing current velocity and direction at specified time instants. The velocity and directions have to be given at all levels defined in the preceding static analysis.</p>
<h2><a class="anchor" id="dynmod_e_dynamic_nodal"></a>
Dynamic nodal forces</h2>
<p>This data group enables the user to specify additional dynamic nodal force components. The force components may either be described by simple functions or read from a separate input file. For file description, see chapter <a class="el" href="a00014.html#dynmod_description_nodal">Description of Additional Input Files: Dynamic Nodal Forces</a>.</p>
<h3><a class="anchor" id="dynmod_e_dynamic_nodal_data"></a>
Data group identifier, one input line</h3>
<div class="fragment"><div class="line">DYNAmic NODAl FORCes</div>
</div><!-- fragment --><h3><a class="anchor" id="dynmod_e_dynamic_nodal_number"></a>
Number of specified components specified by functions or by time series on file</h3>
<div class="fragment"><div class="line">NDCOMP CINPUT CHFLOA</div>
</div><!-- fragment --><ul>
<li><code>NDCOMP: integer</code>: Number of load components to be specified</li>
<li><code>CINPUT: character(6), default: 'NOFILE'</code>: Type of force specification<ul>
<li><code>CINPUT = NOFILE</code>: Forces described by simple expression</li>
<li><code>CINPUT = FILE</code>: Forces described by time series on file</li>
</ul>
</li>
<li><code>CHFLOA: character(80)</code>: File name for time series of force components.<ul>
<li>Dummy if <code>CINPUT = NOFILE</code></li>
</ul>
</li>
</ul>
<h3><a class="anchor" id="dynmod_e_dynamic_nodal_force"></a>
Force component description</h3>
<div class="fragment"><div class="line">LINE-ID ILSEG ILNOD ILDOF CHICOO IFORTY TIMEON TIMEOF P1 P2 P3</div>
</div><!-- fragment --><ul>
<li><code>LINE-ID: character(8)</code>: Line identifier</li>
<li><code>ILSEG: integer</code>: Segment number within actual line</li>
<li><code>ILNOD: integer</code>: Local node/element number within segment</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>CHICOO: character(6)</code>: Coordinate system code<ul>
<li><code>CHICOO = GLOBAL</code>: Force component refers to global system, unless the node has skew or vessel boundaries. If the node has skew or vessel boundaries, <code>CHICOO=GLOBAL</code> means that the load component acts in the skew (vessel) 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>
</ul>
</li>
<li><code>IFORTY: integer</code>: Force component type<ul>
<li><code>IFORTY = 1</code>: Constant force</li>
<li><code>IFORTY = 2</code>: Harmonic force</li>
<li><code>IFORTY = 3</code>: Ramp</li>
</ul>
</li>
<li><code>TIMEON: real</code>: Time for switching component on</li>
<li><code>TIMOFF: real</code>: Time for switching component off</li>
<li><code>P1: real</code>: Force component parameter<ul>
<li><code>IFORTY = 1</code>: Magnitude, <img class="formulaInl" alt="$\mathrm{[F, FL]}$" src="form_475.png"/></li>
<li><code>IFORTY = 2</code>: Amplitude, <img class="formulaInl" alt="$\mathrm{[F, FL]}$" src="form_475.png"/></li>
<li><code>IFORTY = 3</code>: Force derivative, <img class="formulaInl" alt="$\mathrm{[F/T, FL/T]}$" src="form_476.png"/></li>
</ul>
</li>
<li><code>P2: real</code>: Force component parameter<ul>
<li><code>IFORTY = 1</code>: Dummy</li>
<li><code>IFORTY = 2</code>: Period <img class="formulaInl" alt="$\mathrm{[T]}$" src="form_477.png"/></li>
<li><code>IFORTY = 3</code>: Dummy</li>
</ul>
</li>
<li><code>P3: real</code>: Force component parameter<ul>
<li><code>IFORTY = 1</code>: Dummy</li>
<li><code>IFORTY = 2</code>: Phase <img class="formulaInl" alt="$\mathrm{[deg]}$" src="form_56.png"/></li>
<li><code>IFORTY = 3</code>: Dummy</li>
</ul>
</li>
</ul>
<p><code>IFORTY, TIMEON, TIMEOFF, P1, P2</code> and <code>P3</code> are dummy for <code>CINPUT = FILE</code>, time series on file. For file description, see chapter <a class="el" href="a00014.html#dynmod_description_nodal">Description of Additional Input Files: Dynamic Nodal Forces</a>.</p>
<p>For simulation time, t, <code>TIMEON</code> &lt;= t &lt;= <code>TIMOFF</code> the force component <img class="formulaInl" alt="$\mathrm{(F)}$" src="form_478.png"/> will be applied as:</p>
<ul>
<li><code>IFORTY = 1</code>: <img class="formulaInl" alt="$\mathrm{F = P1}$" src="form_479.png"/></li>
<li><code>IFORTY = 2</code>: <img class="formulaInl" alt="$\mathrm{F = P1 \times sin(\frac{2\pi}{P2}\times (t- TIMEON) +P3 \frac{\pi}{180} ) }$" src="form_480.png"/></li>
<li><code>IFORTY = 3</code>: <img class="formulaInl" alt="$\mathrm{F = P1 \times (t - TIMEON)}$" src="form_481.png"/></li>
</ul>
<h2><a class="anchor" id="dynmod_e_dynamic_tension"></a>
Dynamic tension variation</h2>
<h3><a class="anchor" id="dynmod_e_dynamic_tension_data"></a>
Data group identifier, one input line</h3>
<div class="fragment"><div class="line">DYNAmic TENSion VARIation</div>
</div><!-- fragment --><h3><a class="anchor" id="dynmod_e_dynamic_tension_specification"></a>
Specification of dynamic tension variation</h3>
<div class="fragment"><div class="line">SNOD-ID TCX TCV TCA IOPDTV</div>
</div><!-- fragment --><ul>
<li><code>SNOD-ID: character(8)</code>: Supernode identifier for dynamic tension variation.<ul>
<li>Must be identical to the last node-id in stroke storage specification if stroke storage is specified.</li>
</ul>
</li>
<li><code>TCX: real, default: 0</code>: Coefficient for tension variation due to relative displacement between vessel and riser <img class="formulaInl" alt="$\mathrm{[F/L]}$" src="form_482.png"/></li>
<li><code>TCV: real, default: 0</code>: Coefficient for tension variation due to relative velocity between vessel and riser <img class="formulaInl" alt="$\mathrm{[FT/L]}$" src="form_483.png"/></li>
<li><code>TCA: real, default: 0</code>: Coefficient for tension variation due to relative acceleration between vessel and riser <img class="formulaInl" alt="$\mathrm{\left[ FT^2/L\right] }$" src="form_484.png"/></li>
<li><code>IOPDTV: integer, default: 0</code>: Option for updating tension during iterations (relevant for nonlinear time domain analysis only):<ul>
<li><code>= 0</code>: Not updated</li>
<li><code>= 1</code>: Updated</li>
</ul>
</li>
</ul>
<p>The resulting dynamic tension is given by:</p>
<p><img class="formulaInl" alt="$\mathrm{\Delta T = TCX \times x + TCV \times \dot{x} + TCA \times \ddot{x} }$" src="form_485.png"/></p>
<p>where <img class="formulaInl" alt="$\mathrm{x}$" src="form_486.png"/> is the relative vertical displacement between the vessel and the riser. The vertical riser displacements are directly available in a nonlinear time domain analysis. In a linear analysis, the vertical displacements are estimated from the displacements along lines <code>ILIN1</code> .... <code>ILINN</code> (as in linear stroke calculations). <a class="el" href="a00014.html#dynmod_e_stroke">File storage for stroke response</a> must be given if specification of dynamic tension variation is included. In both linear and nonlinear analyses platform motions will be modified for platform setdown if <code>SETLEN &gt; 0</code> in <a class="el" href="a00014.html#dynmod_e_stroke">File storage for stroke response</a>.</p>
<h2><a class="anchor" id="dynmod_e_time"></a>
Time domain loading</h2>
<h3><a class="anchor" id="dynmod_e_time_data"></a>
Data group identifier, one input line</h3>
<div class="fragment"><div class="line">TIME DOMain LOADing</div>
</div><!-- fragment --><h3><a class="anchor" id="dynmod_e_time_load"></a>
Load type to be activated, one input line</h3>
<div class="fragment"><div class="line">LOTYPE NLSPEC CINPUT CHFLOA IFORM</div>
</div><!-- fragment --><ul>
<li><code>LOTYPE: character</code>:<ul>
<li><code>= SEGV</code>: Segment length variation (Nonlinear analysis only)</li>
<li><code>= TEMP</code>: Temperature variation (Nonlinear analysis only)</li>
<li><code>= PRES</code>: Pressure variation (Nonlinear analysis only)</li>
<li><code>= BOUN</code>: Boundary change (Nonlinear analysis only)</li>
<li><code>= VIVA</code>: Time domain VIV (Nonlinear analysis only)</li>
<li><code>= WINC</code>: Winch run (Nonlinear analysis only)</li>
<li><code>= WIND</code>: Wind event. Only available for <code>IWITYP=14</code>, Stationary uniform wind with shear.</li>
<li><code>= SHUT</code>: Wind turbine shutdown fault options (Nonlinear analysis only)</li>
<li><code>= BLAD</code>: Wind turbine blade pitch fault options (Nonlinear analysis only)</li>
</ul>
</li>
<li><code>NLSPEC: integer, default: See below</code>: Number of load specification to follow</li>
<li><code>CINPUT: character, default: 'NOFILE'</code>:<ul>
<li><code>= NOFILE</code>: All load specification given below</li>
<li><code>= FILE</code>: Load specification read from file <code>CHFLOA</code></li>
</ul>
</li>
<li><code>CHFLOA: character, default: See below</code>: Load specification file.<ul>
<li>Dummy for <code>CINPUT = NOFILE</code></li>
</ul>
</li>
<li><code>IFORM: integer, default: 1</code>: File format</li>
</ul>
<p>For <code>LOTYPE = VIVA</code>:</p>
<ul>
<li><code>NLSPEC = 1, CINPUT=FILE</code> and <code>IFORM=1</code></li>
<li>The default value of <code>CHFLOA</code> is <code>&lt;prefix&gt;_ifnviv.ffi</code></li>
</ul>
<p>For <code>LOTYPE = WIND</code>:</p>
<ul>
<li><code>NLSPEC = 1, CINPUT=NOFILE</code></li>
</ul>
<p>For <code>LOTYPE = SHUT</code>:</p>
<ul>
<li><code>NLSPEC = 1, CINPUT=NOFILE</code></li>
</ul>
<p>For <code>LOTYPE = BLAD</code>:</p>
<ul>
<li><code>NLSPEC = 1, CINPUT=NOFILE</code></li>
</ul>
<h3><a class="anchor" id="dynmod_e_time_segment"></a>
Segment length variation, NLSPEC input lines for LOTYPE = SEGV</h3>
<div class="fragment"><div class="line">LINE-ID ISEG TBEG TENO SLRATE</div>
</div><!-- fragment --><ul>
<li><code>LINE-ID: character(8)</code>: Line identifier</li>
<li><code>ISEG: integer</code>: Local segment within line <code>LINE-ID</code></li>
<li><code>TBEG: real</code>: Start time for segment length variation <img class="formulaInl" alt="$\mathrm{[T]}$" src="form_477.png"/></li>
<li><code>TEND: real</code>: End time for segment length variation <img class="formulaInl" alt="$\mathrm{[T]}$" src="form_477.png"/><ul>
<li><code>TEND &gt; TBEG</code></li>
</ul>
</li>
<li><code>SLRATE: real</code>: Segment length variation per time unit <img class="formulaInl" alt="$\mathrm{[L/T]}$" src="form_487.png"/></li>
</ul>
<h3><a class="anchor" id="dynmod_e_time_temperature"></a>
Temperature variation, NLSPEC input lines if LOTYPE = TEMP</h3>
<div class="fragment"><div class="line">LINE-ID ISEG IEL TBEG TEND TEMP</div>
</div><!-- fragment --><ul>
<li><code>LINE-ID: character(8)</code>: Line identifier</li>
<li><code>ISEG: integer/character</code>: Local segment number within line <code>LINE-ID</code><ul>
<li><code>= 0 / ALL</code>: All segments in specified line</li>
</ul>
</li>
<li><code>IEL: integer/character</code>: Local element number within segment <code>ISEG</code><ul>
<li><code>= 0 / ALL</code>: All elements in specified segment</li>
</ul>
</li>
<li><code>TBEG: real</code>: Start time for temperature variation <img class="formulaInl" alt="$\mathrm{[T]}$" src="form_477.png"/></li>
<li><code>TEND: real</code>: End time for temperature variation <img class="formulaInl" alt="$\mathrm{[T]}$" src="form_477.png"/><ul>
<li><code>TEND &gt; TBEG</code></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 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>
<h3><a class="anchor" id="dynmod_e_time_pressure"></a>
Pressure variation, NLSPEC input lines if LOTYPE = PRES</h3>
<div class="fragment"><div class="line">MRL-ID TBEG TEND PRESSI DPRESS VVELI</div>
</div><!-- fragment --><ul>
<li><code>MRL-ID: character(8)</code>: Reference to Main Riser Line identifier</li>
<li><code>TBEG: real</code>: Start time for pressure variation <img class="formulaInl" alt="$\mathrm{[T]}$" src="form_477.png"/></li>
<li><code>TEND: real</code>: End time for pressure variation <img class="formulaInl" alt="$\mathrm{[T]}$" src="form_477.png"/><ul>
<li><code>TEND &gt; TBEG</code></li>
</ul>
</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_488.png"/></li>
<li><code>DPRESS: real, default: 0</code>: Final pressure drop <img class="formulaInl" alt="$\mathrm{\left[ F/L^3\right ]}$" src="form_489.png"/></li>
<li><code>VVELI: real, default: 0</code>: Final fluid velocity <img class="formulaInl" alt="$\mathrm{\left[ L^3/T\right] }$" src="form_490.png"/><ul>
<li>Dummy in present version</li>
</ul>
</li>
</ul>
<h3><a class="anchor" id="dynmod_e_time_boundary"></a>
Boundary change, 3 x NLSPEC input lines for LOTYPE = BOUN</h3>
<h4>Time for boundary change</h4>
<div class="fragment"><div class="line">TIMCHG</div>
</div><!-- fragment --><ul>
<li><code>TIMCHG: real</code>: Time for boundary change <img class="formulaInl" alt="$\mathrm{[T]}$" src="form_477.png"/></li>
</ul>
<h4>Identification of node for boundary change</h4>
<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>
<h4>Status for nodal degrees of freedom if <code>IOP = 0</code></h4>
<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>
<h4>Identification of master node if <code>IOP = 1</code></h4>
<div class="fragment"><div class="line">LINE-ID ILSEG ILNODE</div>
</div><!-- fragment --><ul>
<li><code>LINE-ID: character(8)</code>: 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>
<h3><a class="anchor" id="dynmod_e_time_viv"></a>
VIV load specification, one input line for LOTYPE = VIVA</h3>
<div class="fragment"><div class="line">CHFRQ ALIM ISEED TPLOT</div>
</div><!-- fragment --><ul>
<li><code>CHFRQ: character, default: DOMI</code>:<ul>
<li><code>= ALL</code>: All responses frequencies from <code>VIVANA</code> included</li>
<li><code>= AMIN</code>: Response frequencies with normalized cross flow response larger than <code>AMIN</code> included</li>
<li><code>= DOMI</code>: Only the dominating response frequency included</li>
</ul>
</li>
<li><code>ALIM: real, default: 0</code>: Cross flow displacement to diameter ratio <img class="formulaInl" alt="$\mathrm{[1]}$" src="form_491.png"/><ul>
<li>Dummy for <code>CHFRQ</code> <img class="formulaInl" alt="$ \neq $" src="form_96.png"/> <code>ALIM</code></li>
</ul>
</li>
<li><code>ISEED: integer, default: 280495</code>: Seed</li>
<li><code>TPLOT: real, default: 2</code>: <code>VIV</code> response plot interval. Key <code>VIV</code> results from the last <code>TPLOT</code> interval of the simulation are stored on the <code>_dynmod.mpf</code> file<ul>
<li><code>TPLOT &gt; 0</code>: Given as number of whole response periods</li>
<li><code>TPLOT &lt; 0</code>: Given as time <img class="formulaInl" alt="$\mathrm{[T]}$" src="form_477.png"/></li>
</ul>
</li>
</ul>
<h3><a class="anchor" id="dynmod_e_time_winch"></a>
Winch run, NLSPEC input lines for LOTYPE = WINC</h3>
<div class="fragment"><div class="line">IWINCH TBEG TEND WIVEL</div>
</div><!-- fragment --><ul>
<li><code>IWINCH: integer</code>: Winch number</li>
<li><code>TBEG: real</code>: Start time for winch run <img class="formulaInl" alt="$\mathrm{[T]}$" src="form_477.png"/></li>
<li><code>TEND: real</code>: End time for winch run <img class="formulaInl" alt="$\mathrm{[T]}$" src="form_477.png"/></li>
<li><code>WIVEL: real</code>: Winch velocity <img class="formulaInl" alt="$\mathrm{[L/T]}$" src="form_487.png"/><ul>
<li><code>WIVEL &gt; 0</code>: Winching out, i.e. the winch run will increase the active line length.</li>
</ul>
</li>
</ul>
<h3><a class="anchor" id="dynmod_e_wind_event"></a>
Wind event specification, two or three input lines for LOTYPE = WIND</h3>
<p>In the following IEC 2005 refers to the standard "IEC 61400-1 Wind turbines – Part 1: Design requirements – 2005".</p>
<p>An IEC 2005 extreme wind event may only be applied to a stationary uniform wind with shear, <code>IWITYP=14</code>.</p>
<h4>Start time and wind turbine reference</h4>
<div class="fragment"><div class="line">TIME WIND-TURBINE-ID</div>
</div><!-- fragment --><ul>
<li><code>TIME: real</code>: Start time for wind event <img class="formulaInl" alt="$\mathrm{[T]}$" src="form_477.png"/></li>
<li><code>WIND-TURBINE-ID: character(8)</code>: Wind turbine identifier given in <code>INPMOD</code>. <code>NONE</code> may be given to skip the wind turbine reference for the events ECD, EOG and EDC with <code>CLASS = NONE</code>; i.e. detailed specification of event.</li>
</ul>
<h4>Extreme wind event</h4>
<div class="fragment"><div class="line">CHEVEN CLASS CHDIR</div>
</div><!-- fragment --><ul>
<li><code>CHEVEN: character(12)</code>: Extreme wind event. The following values are currently available:<ul>
<li><code>= IEC2005_ECD</code>: IEC 2005 extreme coherent gust with direction change</li>
<li><code>= IEC2005_EWSV</code>: IEC 2005 extreme vertical wind shear</li>
<li><code>= IEC2005_EWSH</code>: IEC 2005 extreme horizontal wind shear</li>
<li><code>= IEC2005_EOG</code>: IEC 2005 extreme operating gust</li>
<li><code>= IEC2005_EDC</code>: IEC 2005 extreme direction change</li>
</ul>
</li>
<li><code>CLASS: character(4)</code>: Wind turbine class, ref IEC 2005. Legal values are <code>IA</code>, <code>IIA</code>, <code>IIIA</code>, <code>IB</code>, <code>IIB</code>, <code>IIIB</code>, <code>IC</code>, <code>IIC</code>, <code>IIIC</code>, <code>S</code> or <code>NONE</code>, detailed specification of event parameters.</li>
<li><code>CHDIR: character(4)</code>: Direction of event. Dummy for <code>CHEVEN = IEC2005_EOG</code>.<ul>
<li><code>= POS</code>: For ECD and EDC, the wind shifts clockwise (viewed from above). For EWSV, the wind increases at the top of the rotor disk and decrease at the bottom. For EWSH, the wind increases on the left side of the rotor disk and decrease on the right side when viewed along the shaft from the hub.</li>
<li><code>= NEG</code>: For ECD and EDC, the wind shifts counter-clockwise (viewed from above). For EWSV, the wind decreases at the top of the rotor disk and increases at the bottom. For EWSH, the wind decreases on the left side of the rotor disk and increases on the right side when viewed along the shaft from the hub.</li>
<li><code>= NONE</code>: Only allowed for <code>CHEVEN = IEC2005_EOG</code>.</li>
</ul>
</li>
</ul>
<h4>Additional input for wind turbine class S</h4>
<p>If <code>CLASS = S</code>, the following additional input line is given:</p>
<div class="fragment"><div class="line">VREF IREF</div>
</div><!-- fragment --><ul>
<li><code>VREF: real</code>: Reference wind speed average over 10 min <img class="formulaInl" alt="$\mathrm{[L/T]}$" src="form_487.png"/></li>
<li><code>IREF: real</code>: Expected value of the turbulence intensity at 15 m/s <img class="formulaInl" alt="$\mathrm{[1]}$" src="form_491.png"/></li>
</ul>
<h4>Detailed specification of IEC2005 ECD event</h4>
<p>If <code>CLASS = NONE</code> and <code>CHEVEN = IEC2005_ECD</code>, the following additional input line is given:</p>
<div class="fragment"><div class="line">VEL_EVENT DIR_EVENT TIME_EVENT</div>
</div><!-- fragment --><ul>
<li><code>VEL_EVENT: real, default: 0.0</code>: Velocity change <img class="formulaInl" alt="$\mathrm{[L/T]}$" src="form_487.png"/></li>
<li><code>DIR_EVENT: real, default: 0.0</code>: Direction change <img class="formulaInl" alt="$\mathrm{[deg]}$" src="form_56.png"/></li>
<li><code>TIME_EVENT: real &gt; 0</code>: Duration of event <img class="formulaInl" alt="$\mathrm{[T]}$" src="form_477.png"/></li>
</ul>
<h4>Detailed specification of IEC2005 EWSV or EWSH event</h4>
<p>If <code>CLASS = NONE</code> and <code>CHEVEN = IEC2005_EWSV or IEC2005_EWSH</code>, the following additional input line is given:</p>
<div class="fragment"><div class="line">VEL_EVENT TIME_EVENT</div>
</div><!-- fragment --><ul>
<li><code>VEL_EVENT: real, default: 0.0</code>: Velocity change <img class="formulaInl" alt="$\mathrm{[L/T]}$" src="form_487.png"/></li>
<li><code>TIME_EVENT: real &gt; 0</code>: Duration of event <img class="formulaInl" alt="$\mathrm{[T]}$" src="form_477.png"/></li>
</ul>
<h4>Detailed specification of IEC2005 EOG event</h4>
<p>If <code>CLASS = NONE</code> and <code>CHEVEN = IEC2005_EOG</code>, the following additional input line is given:</p>
<div class="fragment"><div class="line">VEL_EVENT TIME_EVENT</div>
</div><!-- fragment --><ul>
<li><code>VEL_EVENT: real, default: 0.0</code>: Range of velocity from minimum to maximum during the event <img class="formulaInl" alt="$\mathrm{[L/T]}$" src="form_487.png"/></li>
<li><code>TIME_EVENT: real &gt; 0</code>: Duration of event <img class="formulaInl" alt="$\mathrm{[T]}$" src="form_477.png"/></li>
</ul>
<h4>Detailed specification of IEC2005 EDC event</h4>
<p>If <code>CLASS = NONE</code> and <code>CHEVEN = IEC2005_EDC</code>, the following additional input line is given:</p>
<div class="fragment"><div class="line">DIR_EVENT TIME_EVENT</div>
</div><!-- fragment --><ul>
<li><code>DIR_EVENT: real, default: 0.0</code>: Direction change <img class="formulaInl" alt="$\mathrm{[deg]}$" src="form_56.png"/></li>
<li><code>TIME_EVENT: real &gt; 0</code>: Duration of event <img class="formulaInl" alt="$\mathrm{[T]}$" src="form_477.png"/></li>
</ul>
<h3><a class="anchor" id="dynmod_e_wt_shutdown"></a>
Wind turbine shutdown fault options</h3>
<p>The specifications given for turbine shutdown will overrule commanded blade pitch and torque, given by the wind turbine control system. Wind turbine blade pitch faults will override the wind turbine shutdown options.</p>
<h4>Start time and wind turbine reference</h4>
<div class="fragment"><div class="line">TSTART WIND-TURBINE-ID</div>
</div><!-- fragment --><ul>
<li><code>TSTART: real</code>: Start time for shutdown <img class="formulaInl" alt="$\mathrm{[T]}$" src="form_477.png"/></li>
<li><code>WIND-TURBINE-ID: character(8)</code>: Reference to wind turbine identifier</li>
</ul>
<h4>Number of pairs in rate of change in pitch and maximum pitch</h4>
<div class="fragment"><div class="line">NPAIR</div>
</div><!-- fragment --><ul>
<li><code>NPAIR: integer</code>: Number of pairs in tabulated rate of pitch change and maximum pitch at the rate of pitch change</li>
</ul>
<h4>Rate of change in pitch and maximum pitch at the rate of change in pitch, NPAIR input lines</h4>
<div class="fragment"><div class="line">RATE  MAX_PITCH</div>
</div><!-- fragment --><ul>
<li><code>RATE: real</code>: Rate of change in pitch angle (absolute value) <img class="formulaInl" alt="$\mathrm{[deg/T]}$" src="form_492.png"/><ul>
<li><code>RATE &gt; 0</code></li>
</ul>
</li>
<li><code>MAX_PITCH: real</code>: Maximum pitch angle for the rate of change in pitch <img class="formulaInl" alt="$\mathrm{[deg]}$" src="form_56.png"/><ul>
<li><code>MAXPITCH &gt; 0</code></li>
</ul>
</li>
</ul>
<p><code>MAX_PITCH</code> values must be given in increasing order.</p>
<p>Example:</p>
<table class="doxtable">
<tr>
<th>Type of shutdown </th><th>Pitch change rate </th><th>Maximum pitch  </th></tr>
<tr>
<td>normal </td><td>1.0 deg/T to </td><td>90.0 deg </td></tr>
</table>
<p>Example:</p>
<table class="doxtable">
<tr>
<th>Type of shutdown </th><th>Pitch change rate </th><th>Maximum pitch  </th></tr>
<tr>
<td>open-loop </td><td>8.0 deg/T to </td><td>40.0 deg </td></tr>
<tr>
<td>- </td><td>4.0 deg/T to </td><td>90.0 deg </td></tr>
</table>
<p>Example:</p>
<table class="doxtable">
<tr>
<th>Type of shutdown </th><th>Pitch change rate </th><th>Maximum pitch  </th></tr>
<tr>
<td>emergency </td><td>8.0 deg/T to </td><td>90.0 deg </td></tr>
</table>
<h4>Generator torque fault options</h4>
<div class="fragment"><div class="line">CHFAULT</div>
</div><!-- fragment --><ul>
<li><code>CHFAULT: character(6)</code>:<ul>
<li><code>= NONE</code>: No generator torque</li>
<li><code>= LOSS</code>: Total loss of generator torque</li>
<li><code>= BACKUP</code>: Backup power, generator torque will follow scaled torque control</li>
</ul>
</li>
</ul>
<h5>Scale factor for generator torque, One input line for <code>CHFAULT = BACKUP</code></h5>
<div class="fragment"><div class="line">SF</div>
</div><!-- fragment --><ul>
<li><code>SF: real</code>: Scale factor for generator torque<ul>
<li><code>SF &gt;= 0</code></li>
</ul>
</li>
</ul>
<h4>Mechanical brake option</h4>
<div class="fragment"><div class="line">CHBRAKE</div>
</div><!-- fragment --><ul>
<li><code>CHBRAKE: character(6)</code>:<ul>
<li><code>= NONE</code>: No mechanical brake</li>
<li><code>= BRAKE</code>: Mechanical brake (Linear damping)</li>
</ul>
</li>
</ul>
<h5>Torque damping coefficient and brake uploading duration, One input line for <code>CHBRAKE = BRAKE</code></h5>
<div class="fragment"><div class="line">TORQUE_DAMP UPL_DURATION</div>
</div><!-- fragment --><ul>
<li><code>TORQUE_DAMP: real</code>: Linear torque damping coefficient <img class="formulaInl" alt="$\mathrm{[FLT/deg]}$" src="form_493.png"/><ul>
<li><code>TORQUE_DAMP &gt;= 0</code></li>
</ul>
</li>
<li><code>UPL_DURATION: real</code>: Brake uploading duration to full braking torque <img class="formulaInl" alt="$\mathrm{[T]}$" src="form_477.png"/><ul>
<li><code>UPL_DURATION &gt;= 0</code></li>
</ul>
</li>
</ul>
<h3><a class="anchor" id="dynmod_e_wt_blade_pitch_fault"></a>
Wind turbine blade pitch fault options</h3>
<p>Wind turbine blade pitch faults will override commanded blade pitch given by the wind turbine control system or by the wind turbine shutdown options.</p>
<h4>Wind turbine reference</h4>
<div class="fragment"><div class="line">WIND-TURBINE-ID</div>
</div><!-- fragment --><ul>
<li><code>WIND-TURBINE-ID: character(8)</code>: Reference to wind turbine identifier</li>
</ul>
<h4>Number of blades for fault specification</h4>
<div class="fragment"><div class="line">NBL_FAULT</div>
</div><!-- fragment --><ul>
<li><code>NBL_FAULT: integer</code>: Number of blades for fault specification<ul>
<li><code>NBL_FAULT &gt;= 0</code></li>
</ul>
</li>
</ul>
<p>The subsequent input specification must be given per blade with pitch fault</p>
<h4>Start time and line (foil blade) reference for fault specification</h4>
<div class="fragment"><div class="line">TSTART LINE-ID</div>
</div><!-- fragment --><ul>
<li><code>TSTART: real</code>: Start time for blade pitch fault <img class="formulaInl" alt="$\mathrm{[T]}$" src="form_477.png"/></li>
<li><code>LINE-ID: character(8)</code>: Reference to line identifier</li>
</ul>
<h4>Type of blade pitch fault</h4>
<div class="fragment"><div class="line">CHFAULT</div>
</div><!-- fragment --><ul>
<li><code>CHFAULT: character(4)</code>:<ul>
<li><code>= SEIZ</code>: Seized - Fixed pitch from time of occurrence</li>
<li><code>= RUNA</code>: Runaway - Pitch change rate from time of occurrence to final pitch</li>
<li><code>= BIAS</code>: Actuator bias - Fixed pitch fault from time of occurrence</li>
</ul>
</li>
</ul>
<h5>Rate of change in pitch and final pitch, One input line for <code>CHFAULT = RUNA</code></h5>
<div class="fragment"><div class="line">RATE  FINAL_PITCH</div>
</div><!-- fragment --><ul>
<li><code>RATE: real</code>: Rate of change in pitch (absolute value) <img class="formulaInl" alt="$\mathrm{[deg/T]}$" src="form_492.png"/><ul>
<li><code>RATE &gt;= 0</code></li>
</ul>
</li>
<li><code>FINAL_PITCH: real</code>: Final pitch <img class="formulaInl" alt="$\mathrm{[deg]}$" src="form_56.png"/></li>
</ul>
<h5>Pitch deviation from required pitch, One input line for <code>CHFAULT = BIAS</code></h5>
<div class="fragment"><div class="line">DEL_PITCH UPL_DURATION</div>
</div><!-- fragment --><ul>
<li><code>DEL_PITCH: real</code>: Fixed pitch deviation from required pitch <img class="formulaInl" alt="$\mathrm{[deg]}$" src="form_56.png"/></li>
<li><code>UPL_DURATION: real</code>: Bias uploading duration to full pitch deviation <img class="formulaInl" alt="$\mathrm{[T]}$" src="form_477.png"/><ul>
<li><code>UPL_DURATION &gt;= 0</code></li>
</ul>
</li>
</ul>
<h2><a class="anchor" id="dynmod_e_displacement"></a>
File storage of displacement response</h2>
<p>Before specifying file storage of response, note that meaningful output from <code>OUTMOD</code> can be dependent on which and how much information that is stored on file from <code>DYNMOD</code>. Examples of such output options in <code>OUTMOD</code> are time series of element angles and distance between elements, see <a class="el" href="a00016.html#outmod_c_element">Element angle time series from time domain analysis</a> and <a class="el" href="a00016.html#outmod_c_distance">Distance time series calculated from the time domain analyses</a>.</p>
<p>There are limitations in storage capacity due to:</p>
<ul>
<li>Disk/user size</li>
<li>Maximum number of arrays that may be stored on the <code>ifndyn.ffi</code> file. A message is printed if this limit is exceeded. The maximum number of arrays on the file may be changed using the environmental variable RIFLEX_MAXDYN_IFNDYN. The minimum value is 50000 and the maximum is 2000000. The default is 200000.</li>
</ul>
<h3><a class="anchor" id="dynmod_e_displacement_data"></a>
Data group identifier, one input line</h3>
<div class="fragment"><div class="line">DISPlacement RESPonse STORage</div>
</div><!-- fragment --><h3><a class="anchor" id="dynmod_e_displacement_specification"></a>
Specification of displacements to be stored</h3>
<h4><a class="anchor" id="dynmod_e_displacement_specification_amount"></a>
Amount of storage, one input line</h4>
<div class="fragment"><div class="line">IDISP NODISP IDISFM</div>
</div><!-- fragment --><ul>
<li><code>IDISP: integer</code>: Code for storage of nodal displacements. Storage for every <code>IDISP</code> time step (<code>IDISP=2</code> gives storage for every second step).</li>
<li><code>NODISP: integer &gt; 0</code>: Number of input lines given specifying node numbers where displacements are stored.</li>
<li><code>IDISFM: integer, default: 0: integer</code>: Format code for storage and/or output of nodal displacements.<ul>
<li><code>IDISFM = 0</code>: Storage only on <code>ifndyn</code> file.</li>
<li><code>IDISFM = 1</code>: Storage on <code>ifndyn</code> file and additional file in ASCII format.</li>
<li><code>IDISFM = 2</code>: Storage on <code>ifndyn</code> file and additional file in BINARY format.</li>
<li><code>IDISFM = -1</code>: Storage only on additional file in ASCII format. Results are not available in <code>OUTMOD</code>.</li>
<li><code>IDISFM = -2</code>: Storage only on additional file in BINARY format. Results are not available in <code>OUTMOD</code>.</li>
</ul>
</li>
</ul>
<p>Note that data must be stored on the <code>ifndyn</code> file in order to be available for <code>OUTMOD</code>.</p>
<p>If <code>IDISFM</code> <img class="formulaInl" alt="$ \neq $" src="form_96.png"/> <code>0</code> is specified, an additional result file and a key file will be created. The file names will be based on the name of the <code>DYNMOD</code> result file; <code>&lt;prefix&gt;_dynmod.res</code>. An additional ASCII file will be <code>&lt;prefix&gt;_noddis.asc</code> and an additional binary file will be <code>&lt;prefix&gt;_noddis.bin</code>. The key file <code>key_&lt;prefix&gt;_noddis.txt</code> will describe how data is stored on the additional output file. The key file may be viewed in a text editor.</p>
<h4><a class="anchor" id="dynmod_e_displacement_specification_specification"></a>
Specification of nodes for displacement storage, NODISP input lines</h4>
<div class="fragment"><div class="line">LINE-ID ISEG INOD</div>
</div><!-- fragment --><ul>
<li><code>LINE-ID: character(8)</code>: Line identifier</li>
<li><code>ISEG: integer</code>: Segment number of line</li>
<li><code>INOD: integer/character</code>: Local node number on actual segment</li>
</ul>
<p>Consecutively numbered nodes may be specified implicitly by assigning a negative value to the last of two adjacent <code>INOD</code>. In this case <code>LINE-ID</code> and <code>ISEG</code> must be the same for the two nodes.</p>
<p>All nodes within one segment may be specified by simply giving <code>ALL</code> as input to <code>INOD</code>.</p>
<h2><a class="anchor" id="dynmod_e_internal"></a>
File storage for internal forces</h2>
<h3><a class="anchor" id="dynmod_e_internal_data"></a>
Data group identifier, one input line</h3>
<div class="fragment"><div class="line">FORCe RESPonse STORage</div>
</div><!-- fragment --><h3><a class="anchor" id="dynmod_e_internal_specification"></a>
Specification of forces to be stored</h3>
<h4><a class="anchor" id="dynmod_e_internal_specification_amount"></a>
Amount of storage, one input line</h4>
<div class="fragment"><div class="line">IFOR NOFORC IFORFM IELTFM</div>
</div><!-- fragment --><ul>
<li><code>IFOR: integer</code>: Code for file storage of internal forces. Forces are stored for every <code>IFOR</code> time step. (<code>IFOR=3</code> gives storage for every third step)</li>
<li><code>NOFORC: integer &gt; 0</code>: Number of input lines given to specify elements for which forces are stored.</li>
<li><code>IFORFM: integer, default: 0</code>: Format code for storage and / or output of element forces<ul>
<li><code>IFORFM = 0</code>: Storage only on <code>ifndyn</code> file</li>
<li><code>IFORFM = 1</code>: Storage on <code>ifndyn</code> file and additional file in ASCII format</li>
<li><code>IFORFM = 2</code>: Storage on <code>ifndyn</code> file and additional file in BINARY format</li>
<li><code>IFORFM = -1</code>: Storage only on additional file in ASCII format. Results are not available in <code>OUTMOD</code>.</li>
<li><code>IFORFM = -2</code>: Storage only on additional file in BINARY format. Results are not available in <code>OUTMOD</code>.</li>
</ul>
</li>
<li><code>IELTFM: integer, default: 0</code>: Format code for or output of element transformation matrices<ul>
<li><code>IEKTFM = 0</code>: No output</li>
<li><code>IELTFM = ±1</code>: Output on additional file in ASCII format</li>
<li><code>IELTFM = ±2</code>: Output on additional file in BINARY format</li>
</ul>
</li>
</ul>
<p>Note that data must be stored on the <code>ifndyn</code> file in order to be available for <code>OUTMOD</code>.</p>
<p>If <code>IFORFM</code> <img class="formulaInl" alt="$ \neq $" src="form_96.png"/> <code>0</code> is specified, an additional result file and a key file will be created. The file names will be based on the name of the <code>DYNMOD</code> result file; <code>&lt;prefix&gt;_dynmod.res</code>. An additional ASCII file will be <code>&lt;prefix&gt;_elmfor.asc</code> and an additional binary file will be <code>&lt;prefix&gt;_elmfor.bin</code>. The key file <code>key_&lt;prefix&gt;_elmfor.txt</code> will describe how data is stored on the additional output file. The key file may be viewed in a text editor.</p>
<p>For nonlinear analysis with pipe-in-pipe elements, the contact forces will be written to <code>&lt;prefix&gt;_cntfor.asc</code> or <code>.bin</code> if <code>IFORFM</code> <img class="formulaInl" alt="$ \neq $" src="form_96.png"/> <code>0</code>. The contents are described on the corresponding key file <code>key_&lt;prefix&gt;_cntfor.txt</code>.</p>
<p>Roller contact forces will be stored on separate result files if <code>IDCOM = LAYFLX</code>, see <a class="el" href="a00010.html#inpmod_b_riser_type_specification_selection_of_riser">INPMOD: Selection of riser type and identifier</a> .</p>
<p>If <code>IELTFM</code> <img class="formulaInl" alt="$ \neq $" src="form_96.png"/> <code>0</code> is specified, an additional result file and a key file will be created. The file names will be based on the name of the <code>DYNMOD</code> result file; <code>&lt;prefix&gt;_dynmod.res</code>. An additional ASCII file will be <code>&lt;prefix&gt;_elmtra.asc</code> and an additional binary file will be <code>&lt;prefix&gt;_elmtra.bin</code>. The key file <code>key_&lt;prefix&gt;_elmtra.txt</code> will describe how data is stored on the additional output file. The key file may be viewed in a text editor.</p>
<h4><a class="anchor" id="dynmod_e_internal_specification_specification"></a>
Specification of elements for force storage, NOFORC input lines</h4>
<div class="fragment"><div class="line">LINE-ID ISEG IEL</div>
</div><!-- fragment --><ul>
<li><code>LINE-ID: character(8)</code>: Line identifier</li>
<li><code>ISEG: integer</code>: Segment number of line</li>
<li><code>IEL: integer/character</code>: Local node number of actual segment</li>
</ul>
<p>Consecutively numbered elements may be specified implicitly by assigning a negative value to the last of two adjacent elements, <code>IEL</code>. In this case <code>LINE-ID</code> and <code>ISEG</code> must be the same for the two elements.</p>
<p>All elements within one segment may be specified by simply giving <code>ALL</code> as input to <code>IEL</code>.</p>
<h2><a class="anchor" id="dynmod_e_curvature"></a>
File storage for curvature response</h2>
<p>Curvature estimates based on nodal displacements may be generated by <code>OUTMOD</code> (see <a class="el" href="a00016.html#outmod_c_curvature_nodal">Curvature time series calculated from dynamic nodal displacements</a>) even though curvatures are not stored from <code>DYNMOD</code>.</p>
<h3><a class="anchor" id="dynmod_e_curvature_data"></a>
Data group identifier, one input line</h3>
<div class="fragment"><div class="line">CURVature RESPonse STORage</div>
</div><!-- fragment --><h3><a class="anchor" id="dynmod_e_curvature_specification"></a>
Specification of curvature to be stored</h3>
<h4><a class="anchor" id="dynmod_e_curvature_specification_amount"></a>
Amount of storage, one input line</h4>
<div class="fragment"><div class="line">ICURV NOCURV ICURFM</div>
</div><!-- fragment --><ul>
<li><code>ICURV: integer</code>: Code for storage of curvature response. Curvature is stored for every <code>ICURV</code> time step</li>
<li><code>NOCURV: integer &gt; 0</code>: Number of input lines given to specify elements for which curvatures are stored.</li>
<li><code>ICURFM: integer, default: 0: integer</code>: Format code for storage and/or output of element curvature.<ul>
<li><code>ICURFM = 0</code>: Storage only on <code>ifndyn</code> file.</li>
<li><code>ICURFM = 1</code>: Storage on <code>ifndyn</code> file and additional file in ASCII format.</li>
<li><code>ICURFM = 2</code>: Storage on <code>ifndyn</code> file and additional file in BINARY format.</li>
<li><code>ICURFM = -1</code>: Storage only on additional file in ASCII format. Results are not available in <code>OUTMOD</code>.</li>
<li><code>ICURFM = -2</code>: Storage only on additional file in BINARY format. Results are not available in <code>OUTMOD</code>.</li>
</ul>
</li>
</ul>
<p>Note that data must be stored on the <code>ifndyn</code> file in order to be available for <code>OUTMOD</code>.</p>
<p>If <code>ICURFM</code> <img class="formulaInl" alt="$ \neq $" src="form_96.png"/> <code>0</code> is specified, an additional result file and a key file will be created. The file names will be based on the name of the <code>DYNMOD</code> result file; <code>&lt;prefix&gt;_dynmod.res</code>. An additional ASCII file will be <code>&lt;prefix&gt;_elmcur.asc</code> and an additional binary file will be <code>&lt;prefix&gt;_elmcur.bin</code>. The key file <code>key_&lt;prefix&gt;_elmcur.txt</code> will describe how data is stored on the additional output file. The key file may be viewed in a text editor.</p>
<h4><a class="anchor" id="dynmod_e_curvature_specification_specification"></a>
Specification of elements for curvature storage, NOCURV input lines</h4>
<div class="fragment"><div class="line">LINE-ID ISEG IEL</div>
</div><!-- fragment --><ul>
<li><code>LINE-ID: character(8)</code>: Line identifier</li>
<li><code>ISEG: integer</code>: Segment number of line</li>
<li><code>IEL: integer/character</code>: Local element number of actual segment</li>
</ul>
<p>Consecutively numbered elements may be specified implicitly by assigning a negative value to the last of two adjacent elements, <code>IEL</code>. In this case <code>LINE-ID</code> and <code>ISEG</code> must be the same for the two elements.</p>
<p>All elements within one segment may be specified by simply giving <code>ALL</code> as input to <code>IEL</code>.</p>
<h2><a class="anchor" id="dynmod_e_envelope"></a>
Envelope curve specification</h2>
<p>This data group enables the user to compute envelopes from both regular and irregular analysis. For irregular analysis mean and standard deviation of response will be printed on the _dynmod.res file.</p>
<h3><a class="anchor" id="dynmod_e_envelope_data"></a>
Data group identifier, one line</h3>
<div class="fragment"><div class="line">ENVElope CURVe SPECification</div>
</div><!-- fragment --><h3><a class="anchor" id="dynmod_e_envelope_specification"></a>
Specification</h3>
<h4><a class="anchor" id="dynmod_e_envelope_specification_options"></a>
Options for calculation and printing</h4>
<div class="fragment"><div class="line">IENVD IENVF IENVC TENVS TENVE NPREND NPRENF NPRENC IFILMP</div>
</div><!-- fragment --><ul>
<li><code>IENVD: integer, default: 1</code>: Calculation option for displacement envelopes<ul>
<li><code>= 0</code>: not calculated</li>
<li><code>= 1</code>: calculated</li>
</ul>
</li>
<li><code>IENVF: integer, default: 1</code>: Calculation option for force envelopes<ul>
<li><code>= 0</code>: not calculated</li>
<li><code>= 1</code>: calculated</li>
</ul>
</li>
<li><code>IENVC: integer, default: 1</code>: Calculation option for curvature envelopes<ul>
<li><code>= 0</code>: not calculated</li>
<li><code>= 1</code>: calculated</li>
</ul>
</li>
<li><code>TENVS: real</code>: Simulation start time for calculating envelopes <img class="formulaInl" alt="$\mathrm{[T]}$" src="form_477.png"/></li>
<li><code>TENVE: real, default:</code> <img class="formulaInl" alt="$10^{6}$" src="form_494.png"/>: Simulation end time for calculating envelopes <img class="formulaInl" alt="$\mathrm{[T]}$" src="form_477.png"/></li>
<li><code>NPREND: integer, default: 0</code>: Print option for displacement envelopes<ul>
<li><code>= 0</code>: Not printed</li>
<li><code>= 1</code>: print</li>
</ul>
</li>
<li><code>NPRENF: integer, default: 0</code>: Print option for force envelopes<ul>
<li><code>= 0</code>: not printed</li>
<li><code>= 1</code>: print</li>
</ul>
</li>
<li><code>NPRENC: integer, default: 0</code>: Print option for curvature envelopes<ul>
<li><code>= 0</code>: not printed</li>
<li><code>= 1</code>: print</li>
</ul>
</li>
<li><code>IFILMP: integer, default: 2</code>: MatrixPlot file option; specifies amount of results written to the file <code>&lt;prefix&gt;_dynmod.mpf</code>. <code>0 &lt;= IFILMP &lt;= 4</code>.<ul>
<li><code>= 0</code>: No print</li>
<li><code>= 1</code>: Minimum values, maximum values and standard deviations</li>
<li><code>= 2</code>: Minimum values, maximum values and standard deviations (identical to specifying <code>IFILMP = 1</code>)</li>
<li><code>= 3</code>: Minimum values, maximum values, standard deviations, mean values and mean-crossing periods</li>
<li><code>= 4</code>: Minimum values, maximum values, standard deviations, mean values, mean-crossing periods, skewness and kurtosis</li>
</ul>
</li>
</ul>
<p>Note that the mean-crossing period, skewness and kurtosis will be inaccurate for time series with constant or near constant values.</p>
<h2><a class="anchor" id="dynmod_e_stroke"></a>
File storage for stroke response</h2>
<p>The stroke is stored for presentation and / or post-processing in <code>OUTMOD</code></p>
<h3><a class="anchor" id="dynmod_e_stroke_data"></a>
Data group identifier, one input line</h3>
<div class="fragment"><div class="line">STROke RESPonse STORage</div>
</div><!-- fragment --><h3><a class="anchor" id="dynmod_e_stroke_specification"></a>
Specification of stroke calculation and storage</h3>
<div class="fragment"><div class="line">ISTRO SNOD-ID IOPSTR SETLEN XRSTRO YRSTRO NLINST LINE-ID1 .. LINE-IDnlinst</div>
</div><!-- fragment --><ul>
<li><code>ISTRO: integer, default: 1</code>: Code for storage of stroke response. Storage for every <code>ISTRO</code> time step (<code>ISTRO=2</code> gives storage for every second step)</li>
<li><code>SNOD-ID: character(8)</code>: Supernode identifier for stroke calculation</li>
<li><code>IOPSTR: integer, default: 0</code>: Option for reference coordinates<ul>
<li><code>= 0</code>: Initial stressfree configuration used as reference</li>
<li><code>= 1</code>: Final static configuration used as reference (under implementation)</li>
</ul>
</li>
<li><code>SETLEN: real, default: 0</code>: Tendon length for set-down correction</li>
<li><code>XRSTRO: real, default: 0</code>: Global X coordinate of node <code>INODST</code>’s reference point for set-down calculations.<ul>
<li>Dummy of <code>SETLEN = 0</code>.</li>
</ul>
</li>
<li><code>YRSTRO: real, default: 0</code>: Global Y coordinate of node <code>INODST</code>’s reference point for set-down calculations.<ul>
<li>Dummy of <code>SETLEN = 0</code>.</li>
</ul>
</li>
<li><code>NLINST: integer, default: 0</code>: Number of lines used in calculating stroke<ul>
<li>Dummy for nonlinear analysis</li>
</ul>
</li>
<li>Lines (line identifiers) used in stroke calculation<ul>
<li>Dummy for nonlinear analysis</li>
<li><code>LINE-ID1: character(8)</code>:</li>
<li>.</li>
<li>.</li>
<li>.</li>
<li><code>LINE-IDnlinst: character(8)</code>:</li>
</ul>
</li>
</ul>
<p>Stroke may only be calculated for supernodes. No set-down correction if <code>SETLEN = 0.0</code></p>
<h2><a class="anchor" id="dynmod_e_sum"></a>
File storage for sum forces</h2>
<p>The element sum forces are the sum of the axial stiffness, damping and inertia forces.</p>
<h3><a class="anchor" id="dynmod_e_sum_data"></a>
Data group identifier, one input line</h3>
<div class="fragment"><div class="line">SUMFORCe RESPonse STORage</div>
</div><!-- fragment --><h3><a class="anchor" id="dynmod_e_sum_specification"></a>
Specification of forces to be stored</h3>
<h4><a class="anchor" id="dynmod_e_sum_specification_amount"></a>
Amount of storage, one input line</h4>
<div class="fragment"><div class="line">ISFOR NOSFOR ISFOFM</div>
</div><!-- fragment --><ul>
<li><code>ISFOR: integer</code>: Code for file storage of sum forces. Forces are stored for every <code>ISFOR</code> time step (<code>ISFOR=3</code> gives storage for every third step)</li>
<li><code>NOSFOR: integer &gt; 0</code>: Number of input lines given to specify elements for which sum forces are stored.</li>
<li><code>ISFORM: integer, default: -1: integer</code>: Format code for storage and/or output of sum element forces.<ul>
<li><code>ISFORM = -1</code>: Storage on additional file in ASCII format only.</li>
<li><code>ISFORM = -2</code>: Storage on additional file in BINARY format only.</li>
</ul>
</li>
</ul>
<p>This data group is available for nonlinear time domain analysis only.</p>
<p>If <code>ISFORM</code> <img class="formulaInl" alt="$ \neq $" src="form_96.png"/> <code>0</code> is specified, an additional result file and a key file will be created. The file names will be based on the name of the <code>DYNMOD</code> result file; <code>&lt;prefix&gt;_dynmod.res</code>. An additional ASCII file will be <code>&lt;prefix&gt;_elmsfo.asc</code> and an additional binary file will be <code>&lt;prefix&gt;_elmsfo.bin</code>. The key file <code>key_&lt;prefix&gt;_elmsfo.txt</code> will describe how data is stored on the additional output file. The key file may be viewed in a text editor.</p>
<h4><a class="anchor" id="dynmod_e_sum_specification_specification"></a>
Specification of elements for force storage, NOSFOR input lines</h4>
<div class="fragment"><div class="line">LINE-ID ISEG IEL</div>
</div><!-- fragment --><ul>
<li><code>LINE-ID: character(8)</code>: Line identifier</li>
<li><code>ISEG: integer</code>: Segment number of line</li>
<li><code>IEL: integer/character</code>: Local node number of actual segment</li>
</ul>
<p>Consecutively numbered elements may be specified implicitly by assigning a negative value to the last of two adjacent elements, <code>IEL</code>. In this case <code>LINE-ID</code> and <code>ISEG</code> must be the same for the two elements.</p>
<p>All elements within one segment may be specified by simply giving <code>ALL</code> as input to <code>IEL</code>.</p>
<h2><a class="anchor" id="dynmod_wt_resp"></a>
File storage for wind turbine responses</h2>
<p>This option enables export of wind turnine key responses to file in binary or ASCII format</p>
<h3><a class="anchor" id="dynmod_wt_resp_id"></a>
Data group identifier, one input line</h3>
<div class="fragment"><div class="line">TURBine RESPonse STORage</div>
</div><!-- fragment --><h4><a class="anchor" id="dynmod_wt_dt"></a>
Time interval for storage, one input line</h4>
<div class="fragment"><div class="line">DT_WTR</div>
</div><!-- fragment --><ul>
<li><code>DT_WTR: real</code>: Desired time interval for storage [T]<ul>
<li><code>DT_WTR = 0</code>: Storage at each simulation time step</li>
</ul>
</li>
</ul>
<p>Note that <code>DT_WTR</code> will be adjusted to get an integer ratio between the simulation time step <code>DT</code> and the specified storage interval <code>DT_WTR</code>.</p>
<h4><a class="anchor" id="dynmod_no_wt"></a>
Amount of storage, one input line</h4>
<div class="fragment"><div class="line">NOTURB ITURBFM</div>
</div><!-- fragment --><ul>
<li><code>NOTURB: integer</code>: Number of wind turbines for storage</li>
<li><code>ITURBFM: integer</code>: File format code for storage<ul>
<li><code>ITURBFM = 1</code>: Storage on file in ASCII format.</li>
<li><code>ITURBFM = 2</code>: Storage on file in binary format.</li>
</ul>
</li>
</ul>
<p>Note that <code>NOTURB</code> has to be set to 1 in present program version</p>
<p>The wind turbine responses are written to <code>&lt;prefix&gt;_witurb.asc</code> or <code>&lt;prefix&gt;_witurb.bin</code>.</p>
<p>The contents are described in <code>key_&lt;prefix&gt;_witurb.txt</code></p>
<h4><a class="anchor" id="dynmod_wt_id"></a>
Wind turbine identification for storage, `NOTURB` input lines</h4>
<div class="fragment"><div class="line">TURB-ID</div>
</div><!-- fragment --><ul>
<li><code>TURB-ID: character(8)</code>: Wind turbine identifier</li>
</ul>
<h2><a class="anchor" id="dynmod_wtbl_resp"></a>
File storage for wind turbine blade responses</h2>
<p>This option enables export of wind turbine blade responses to file in binary or ASCII format.</p>
<h3><a class="anchor" id="dynmod_wtbl_resp_id"></a>
Data group identifier, one input line</h3>
<div class="fragment"><div class="line">WTBLade RESPonse STORage</div>
</div><!-- fragment --><h4><a class="anchor" id="dynmod_wtblresp_amount"></a>
Specification of the amount of responses, one input line</h4>
<div class="fragment"><div class="line">AMOUNT</div>
</div><!-- fragment --><ul>
<li><code>AMOUNT: character(3)</code>: Amount of blade responses storage<ul>
<li><code>AMOUNT = MIN</code>: Minimum amount of responses:<ul>
<li>Drag and lift force intensities in foil system</li>
<li>Relative wind velocity in foil system</li>
<li>Angle of attack in foil system</li>
</ul>
</li>
<li><code>AMOUNT = MED</code>: Medium amount of responses. In addition to minimum amount:<ul>
<li>Drag-, lift and moment coefficients in foil system</li>
<li>Induced wind speed in foil system</li>
<li>Remote incoming wind speed including tower effect in foil system</li>
<li>Separation point position in foil system</li>
<li>Axial and tangential induction factors in rotor system</li>
<li>Axial and tangential load intensities in rotor system</li>
<li>Annulus average axial- and tangential induction velocity</li>
</ul>
</li>
<li><code>AMOUNT = MAX</code>: Maximum amount of responses. In addition to medium amount:<ul>
<li>Transformation matrix between foil and rotor systems</li>
</ul>
</li>
</ul>
</li>
</ul>
<h4><a class="anchor" id="dynmod_wtbl_dt"></a>
Time interval for storage, number of input lines and file format code, one input line</h4>
<div class="fragment"><div class="line">DT_TBR  NOSPEC  IBLADFM</div>
</div><!-- fragment --><ul>
<li><code>DT_TBR: real</code>: Desired time interval for storage [T]<ul>
<li><code>DT_TBR = 0</code>: Storage at each simulation time step</li>
</ul>
</li>
<li><code>NOSPEC: integer &gt; 0</code>: Number of input lines given to specify elements for which blade responses are stored.</li>
<li><code>IBLADFM: integer</code>: File format code for storage<ul>
<li><code>IBLADFM = 1</code>: Storage on file in ASCII format.</li>
<li><code>IBLADFM = 2</code>: Storage on file in binary format.</li>
</ul>
</li>
</ul>
<p>Note that <code>DT_TBR</code> will be adjusted to get an integer ratio between the simulation time step <code>DT</code> and the specified storage interval <code>DT_TBR</code>.</p>
<p>The wind turbine responses are written to <code>&lt;prefix&gt;_blresp.asc</code> or <code>&lt;prefix&gt;_blresp.bin</code>. &lt;</p>
<p>The contents are described in <code>key_&lt;prefix&gt;_blresp.txt</code></p>
<h4><a class="anchor" id="dynmod_noblres_iel"></a>
Specification of elements for blade response storage, NOSPEC input lines</h4>
<div class="fragment"><div class="line">LINE-ID  ISEG  IEL</div>
</div><!-- fragment --><ul>
<li><code>LINE-ID: character(8)</code>: Line identifier</li>
<li><code>ISEG: integer/character</code>: Local segment number within line <code>LINE-ID</code></li>
<li><code>IEL: integer/character</code>: Local element number within segment <code>ISEG</code></li>
</ul>
<p>All elements within the line may be specified by simply giving <code>ALL</code> as input to <code>ISEG</code>. Thus <code>IEL</code> will be dummy input.</p>
<p>All elements within one segment may be specified by giving <code>ALL</code> as input to <code>IEL</code>.</p>
<h2><a class="anchor" id="dynmod_e_export"></a>
Export of element responses</h2>
<p>This option enables export of element responses for subsequent communication with general advanced animation tools. The instruction is applicable for non-linear dynamic analysis only.</p>
<h3><a class="anchor" id="dynmod_e_export_data"></a>
Data group identifier, one input line</h3>
<div class="fragment"><div class="line">STORe VISUalisation RESPonses</div>
</div><!-- fragment --><h3><a class="anchor" id="dynmod_e_export_amount"></a>
Amount of response storage and file format, one input line</h3>
<div class="fragment"><div class="line">TCONDS TCONDE DELT CHFORM</div>
</div><!-- fragment --><ul>
<li><code>TCONDS: real, default: 0</code>: Start time for export</li>
<li><code>TCONDE: real, default:</code> <img class="formulaInl" alt="$ 10^5$" src="form_495.png"/>: End time for export</li>
<li><code>DELT: real, default: See below</code>: Time increment for export</li>
<li><code>CHFORM: character</code>:<ul>
<li><code>= VIS</code>: Export to file format used by the computer program SIMVIS for response visualization subsequent to dynamic analysis</li>
<li><code>= RAF</code>: Export to file format of type RAF</li>
</ul>
</li>
</ul>
<p>Default values of <code>DELT</code>:</p>
<ul>
<li><code>DTWF</code>: Time increment used for pre-sampling of irregular waves and prescribed motions</li>
<li><code>DT</code>: Time increment used in time integration for regular analysis</li>
</ul>
<h3><a class="anchor" id="dynmod_e_export_detailed"></a>
Detailed specification of exported element responses</h3>
<p>This data group is optionally given for <code>CHFORM = VIS</code></p>
<p>In present version it is possible to specify element responses in form of effective tension, resulting curvature and longitudinal stress (if available). By default all available element responses for all lines will be exported. This input line makes it possible 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>: Line identifier</li>
<li><code>= ALL</code>: All lines</li>
</ul>
</li>
</ul>
<h2><a class="anchor" id="dynmod_e_termination"></a>
Termination of input data</h2>
<p>To terminate an input data stream, simply give the following, which is interpreted as a data-group identifier.</p>
<div class="fragment"><div class="line">END</div>
</div><!-- fragment --><h1><a class="anchor" id="dynmod_description"></a>
Description of Additional Input Files</h1>
<h2><a class="anchor" id="dynmod_description_current"></a>
Dynamic Current Variation</h2>
<p>The file "CHFCUR" specified in <a class="el" href="a00014.html#dynmod_e_dynamic_current">Dynamic current variation</a>, contains the description of dynamic current variation. The file is a free format sequential ASCII-file.</p>
<p>The current velocity and direction have to be specified at all levels defined in the preceding static analysis. The static current profile is interpreted as the current profile at time equal to zero. The dynamic current profile is described at an arbitrary number of time instants, given by increasing values. Linear interpolation is used for intermediate values. If the last defined time instant is exceeded during simulation, the current profile is assumed constant and equal to the last specification for the continued simulation.</p>
<p>File description</p>
<h3><a class="anchor" id="dynmod_description_current_number"></a>
Number of specified time instants, one input line</h3>
<div class="fragment"><div class="line">NDYCUR</div>
</div><!-- fragment --><ul>
<li><code>NDYCUR: integer &gt; 1</code>: The number of time instants for which current profile is given.</li>
</ul>
<p>The input data in 'Number of levels and time instant, one input line' and 'Current velocity and direction, one input line per current level, i.e. NLCUR input lines' (below) must be given in one block for each defined time instant.</p>
<h4><a class="anchor" id="dynmod_description_current_number_levels"></a>
Number of levels and time instant, one input line</h4>
<div class="fragment"><div class="line">NLCUR TIMDCU</div>
</div><!-- fragment --><ul>
<li><code>NLCUR: integer</code>: Number of levels in current profile. The number of levels has to be equal the number used in the preceding static analysis</li>
<li><code>TIMDCU: real &gt; 0</code>: Time instant for the specified current profile <img class="formulaInl" alt="$ \mathrm{[T]} $" src="form_324.png"/></li>
</ul>
<h4><a class="anchor" id="dynmod_description_current_number_velocity"></a>
Current velocity and direction, one input line per current level, i.e. NLCUR input lines</h4>
<div class="fragment"><div class="line">CURDIR CURVEL CURVEZ</div>
</div><!-- fragment --><ul>
<li><code>CURDIR: real</code>: Direction of current velocity.<ul>
<li>The angle is measured in degrees from global x-axis counter clockwise to the current vector, confer <a class="el" href="a00010.html#inpmod_d_current">Current parameters</a></li>
</ul>
</li>
<li><code>CURVEL: real, default: 0</code>: Current velocity <img class="formulaInl" alt="$ \mathrm{[L/T]} $" src="form_348.png"/></li>
<li><code>CURVEZ: real, default: 0</code>: Vertical current velocity <img class="formulaInl" alt="$ \mathrm{[L/T]} $" src="form_348.png"/></li>
</ul>
<h2><a class="anchor" id="dynmod_description_nodal"></a>
Dynamic Nodal Forces</h2>
<p>The file "CHFLOA" specified in <a class="el" href="a00014.html#dynmod_e_dynamic_nodal">Dynamic nodal forces</a>, contains the description of dynamic nodal load components (i.e. external dynamic loads given as time series). The file is a free format sequential ASCII-file.</p>
<p>The dynamic nodal load components are described by values at specified time instants, which must be increasing. Intermediate values are found by linear interpolation. Between the start of the simulation and the first time instant with specified loads, the loads are linearly increased from zero to the first values given. If the simulation continues after the last defined time instant, the nodal load components are kept constant at the last values given.</p>
<p>The number of nodal load components, location and direction are defined in <a class="el" href="a00014.html#dynmod_e_dynamic_nodal">Dynamic nodal forces</a>. This data group also defines the order in which the load components are to be specified on the file.</p>
<h3>File description - original format</h3>
<h3><a class="anchor" id="dynmod_description_nodal_number"></a>
Number of specified time instants, one input line</h3>
<div class="fragment"><div class="line">NTDFO</div>
</div><!-- fragment --><ul>
<li><code>NTDFO: integer &gt;= 1</code>: Number of time instants for which nodal load components are specified.</li>
</ul>
<p>The input data in 'Number of load components and time instant, one input line' and 'Load components, MDCOMP input lines' (below) must be given in one block for each defined time instant.</p>
<h3><a class="anchor" id="dynmod_description_nodal_number__load1"></a>
Number of load components and time instant, one input line</h3>
<div class="fragment"><div class="line">MDCOMP TIMDFO</div>
</div><!-- fragment --><ul>
<li><code>MDCOMP: integer</code>: Number of load components.<ul>
<li>Used for control: <code>MDCOMP = NDCOMP</code></li>
<li><code>NDCOMP</code> is specified in <a class="el" href="a00014.html#dynmod_e_dynamic_nodal">Dynamic nodal forces</a></li>
</ul>
</li>
<li><code>TIMDFO: real &gt; 0</code>: Time instant for the specified load components <img class="formulaInl" alt="$ \mathrm{[T]} $" src="form_324.png"/></li>
</ul>
<h3><a class="anchor" id="dynmod_description_nodal_number_load2"></a>
Load components, MDCOMP input lines</h3>
<div class="fragment"><div class="line">RLMAG</div>
</div><!-- fragment --><ul>
<li><code>RLMAG: real</code>: Magnitude of load component <img class="formulaInl" alt="$ \mathrm{[F]} $" src="form_122.png"/>, <img class="formulaInl" alt="$ \mathrm{[FL]} $" src="form_125.png"/></li>
</ul>
<h3>File description - column format</h3>
<h3><a class="anchor" id="dynmod_description_nodal_number_load2_col"></a>
Time Step and Load Components, one line for each time step</h3>
<div class="fragment"><div class="line">TIMDFO  RLMAGi ..... RLMAGn</div>
</div><!-- fragment --><ul>
<li><code>TIMDFO: real &gt; 0</code>: Time instant for the specified load components <img class="formulaInl" alt="$ \mathrm{[T]} $" src="form_324.png"/></li>
<li><code>RLMAGi: real</code>: Magnitude of load component <img class="formulaInl" alt="$ \mathrm{[F]} $" src="form_122.png"/>, <img class="formulaInl" alt="$ \mathrm{[FL]} $" src="form_125.png"/></li>
</ul>
<p><code>RLMAGi</code> must be repeated n=<code>MDCOMP</code> times.</p>
<h2><a class="anchor" id="dynmod_description_wave"></a>
Diffracted Wave Transfer Functions at Points</h2>
<p>The file "CHFDIF" specified in <a class="el" href="a00014.html#dynmod_d_irregular_waves">Irregular Waves</a> contains the wave kinematics transfer functions.</p>
<h3><a class="anchor" id="dynmod_description_wave_identification_data"></a>
Data group identifier, one input line</h3>
<div class="fragment"><div class="line">FIRSt ORDEr DIFFracted wave transfer functions</div>
</div><!-- fragment --><h3><a class="anchor" id="dynmod_description_wave_identification_text"></a>
Text describing the linear incoming wave to diffracted wave transfer functions, two input lines</h3>
<div class="fragment"><div class="line">TXDI1</div>
</div><!-- fragment --><ul>
<li><code>TXDI1: character(60)</code>: Character string</li>
</ul>
<h3><a class="anchor" id="dynmod_description_wave_identification_point1"></a>
Point reference, one input line</h3>
<div class="fragment"><div class="line">PTNOUS IVES</div>
</div><!-- fragment --><ul>
<li><code>PTNOUS: integer</code>: Point number defined by user</li>
<li><code>IVES: integer</code>: Support vessel number</li>
</ul>
<h3><a class="anchor" id="dynmod_description_wave_identification_point2"></a>
Point coordinates, one input line</h3>
<div class="fragment"><div class="line">XBDY YBDY ZBDY</div>
</div><!-- fragment --><ul>
<li><code>XBDY: real</code>: x-coordinate of where transfer function is calculated, given in support vessel coordinate system <img class="formulaInl" alt="$ \mathrm{[L]} $" src="form_95.png"/></li>
<li><code>YBDY: real</code>: y-coordinate of where transfer function is calculated, given in support vessel coordinate system <img class="formulaInl" alt="$ \mathrm{[L]} $" src="form_95.png"/></li>
<li><code>ZBDY: real</code>: z-coordinate of where transfer function is calculated, given in support vessel coordinate system <img class="formulaInl" alt="$ \mathrm{[L]} $" src="form_95.png"/></li>
</ul>
<h3><a class="anchor" id="dynmod_description_wave_identification_dimensioning"></a>
Dimensioning parameters, one input line</h3>
<div class="fragment"><div class="line">NDIR NFRE ITYPIN</div>
</div><!-- fragment --><ul>
<li><code>NDIR: integer</code>: Total number of wave directions (for this point)</li>
<li><code>NFRE: integer</code>: Total number of frequencies (for this point)</li>
<li><code>ITYPIN: integer</code>: Code for which format the transfer functions are given in<ul>
<li><code>= 1</code>: Complex form</li>
<li><code>= 2</code>: Amplitude ratio <img class="formulaInl" alt="$ \mathrm{[1]} $" src="form_65.png"/> and phase <img class="formulaInl" alt="$ \mathrm{[deg]} $" src="form_97.png"/></li>
<li><code>= 3</code>: Amplitude ratio <img class="formulaInl" alt="$ \mathrm{[1]} $" src="form_65.png"/> and phase <img class="formulaInl" alt="$ \mathrm{[rad]} $" src="form_496.png"/></li>
</ul>
</li>
</ul>
<h3><a class="anchor" id="dynmod_description_wave_unknown1_data"></a>
Data identification, one input line</h3>
<div class="fragment"><div class="line">WAVE DIREctions DIFFracted wave transfer functions</div>
</div><!-- fragment --><h3><a class="anchor" id="dynmod_description_wave_unknown1_directions"></a>
Directions, NDIR input lines</h3>
<div class="fragment"><div class="line">IDIR DIR</div>
</div><!-- fragment --><ul>
<li><code>IDIR: integer</code>: Direction number (between 1 and <code>NDIR</code>)</li>
<li><code>DIR: real</code>: Propagation direction of incoming wave, <img class="formulaInl" alt="$ \mathrm{[deg]} $" src="form_97.png"/></li>
</ul>
<h3><a class="anchor" id="dynmod_description_wave_unknown2_data"></a>
Data identification, one input line</h3>
<div class="fragment"><div class="line">WAVE FREQuencies DIFFracted wave transfer functions</div>
</div><!-- fragment --><h3><a class="anchor" id="dynmod_description_wave_unknown2_frequencies"></a>
Frequencies, NFRE input lines</h3>
<div class="fragment"><div class="line">IFRE FRE</div>
</div><!-- fragment --><ul>
<li><code>IFRE: integer</code>: Frequency number (between 1 and <code>NFRE</code>)</li>
<li><code>FRE: real</code>: Angular frequency of incoming wave, <img class="formulaInl" alt="$ \mathrm{[rad/T]} $" src="form_343.png"/></li>
</ul>
<h3><a class="anchor" id="dynmod_description_wave_unknown3_data"></a>
Data identification, one input line</h3>
<div class="fragment"><div class="line">WAVE ELEVation DIFFracted wave transfer <span class="keyword">function</span></div>
</div><!-- fragment --><p>or</p>
<div class="fragment"><div class="line">XVELocity DIFFracted WAVE transfer <span class="keyword">function</span></div>
</div><!-- fragment --><div class="fragment"><div class="line">YVELocity DIFFracted WAVE transfer <span class="keyword">function</span></div>
</div><!-- fragment --><div class="fragment"><div class="line">ZVELocity DIFFracted WAVE transfer <span class="keyword">function</span></div>
</div><!-- fragment --><h3><a class="anchor" id="dynmod_description_wave_unknown3_ddimensioning"></a>
Diffracted wave transfer function, NDIR x NFRE input lines</h3>
<div class="fragment"><div class="line">IDIR IFRE A B</div>
</div><!-- fragment --><ul>
<li><code>IDIR: integer</code>: Direction number</li>
<li><code>IFRE: integer</code>: Frequency number</li>
<li><code>A: real</code>: Interpretation according to value of <code>ITYPIN</code><ul>
<li><code>ITYPIN = 1</code>: Real part</li>
<li><code>ITYPIN = 2</code>: Amplitude ratio <img class="formulaInl" alt="$ \mathrm{[1],[rad/m]} $" src="form_497.png"/></li>
<li><code>ITYPIN = 3</code>: Amplitude ratio <img class="formulaInl" alt="$ \mathrm{[1],[rad/m]} $" src="form_497.png"/></li>
</ul>
</li>
<li><code>B: real</code>: Interpretation according to value of <code>ITYPIN</code><ul>
<li><code>ITYPIN = 1</code>: Imaginary part</li>
<li><code>ITYPIN = 2</code>: Phase angle <img class="formulaInl" alt="$ \mathrm{[deg]} $" src="form_97.png"/></li>
<li><code>ITYPIN = 3</code>: Phase angle <img class="formulaInl" alt="$ \mathrm{[rad]} $" src="form_496.png"/></li>
</ul>
</li>
</ul>
<p>Transfer functions for accelerations will be calculated based on velocity transfer functions</p>
<h2><a class="anchor" id="dynmod_description_internal"></a>
Internal flow description</h2>
<p>The file "CHFFLW" specified in <a class="el" href="a00014.html#dynmod_e_import">Import of internal flow data from file (Deprecated functionality)</a> contains a description of the time-varying internal flow.</p>
<h3><a class="anchor" id="dynmod_description_internal_heading"></a>
Heading, one input line</h3>
<ul>
<li><code>&lt;TEXT&gt;: character(78)</code>:</li>
</ul>
<p>The heading will be echoed on the <code>&lt;prefix&gt;_dynmod.res</code> result file.</p>
<h3><a class="anchor" id="dynmod_description_internal_specification"></a>
Specification of internal flow conditions.</h3>
<p>Data groups 'Specification of time...' and 'Specification of flow conditions...' (below) are repeated as many times as necessary. At least two time steps must be given.</p>
<h4><a class="anchor" id="dynmod_description_internal_specification_time"></a>
Specification of time, one input line</h4>
<div class="fragment"><div class="line">CHIDEN TIME</div>
</div><!-- fragment --><ul>
<li><code>CHIDEN: character(4)</code>:<ul>
<li><code>= TIME</code></li>
</ul>
</li>
<li><code>TIME: real</code>: Time for the following specified flow conditions</li>
</ul>
<h4><a class="anchor" id="dynmod_description_internal_specification_flow"></a>
Specification of flow conditions, as many input lines as needed. (Zero input lines may be given.)</h4>
<div class="fragment"><div class="line">IFE1 IFE2 DEN VEL</div>
</div><!-- fragment --><ul>
<li><code>IFE1: integer</code>: First flow element with these conditions</li>
<li><code>IFE2: integer</code>: Last flow element with these conditions</li>
<li><code>DEN: real</code>: Density of contents <img class="formulaInl" alt="$ \mathrm{\left[ M/L^3 \right]} $" src="form_498.png"/></li>
<li><code>VEL: real</code>: Velocity of contents <img class="formulaInl" alt="$ \mathrm{[L/T]} $" src="form_348.png"/></li>
</ul>
<p>The elements in the MRL(s) are numbered consecutively along the MRL. A table of the flow element numbering may be found on the <code>&lt;prefix&gt;_stamod.res</code> file.</p>
<h3><a class="anchor" id="dynmod_description_internal_end"></a>
End, one input line</h3>
<div class="fragment"><div class="line">END</div>
</div><!-- fragment --> </div></div><!-- contents -->
	</body>
</html>