<?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">RIFLEX Release Notes </div>  </div>
</div><!--header-->
<div class="contents">
<div class="textblock"><h1>RIFLEX 4.16.0 (2019-05-06)</h1>
<p>Initial release of <code>RIFLEX</code> 4.16.</p>
<h2>RIFLEX 4.16.0 Known issues</h2>
<h3>Wave kinematics at updated position in coupled analysis</h3>
<p>Currently, the FFT wave method must be selected in <code>SIMO</code> to allow wave kinematics at updated position to be used in <code>RIFLEX</code> for a coupled analysis.</p>
<h3>Main Riser Line inner pressure</h3>
<p>The Main Riser Line (MRL) input allows the pressure to be specified at either end of the MRL. The specified inner pressure is, however, always applied at end 1 of the MRL. This will give errors in true wall tension and some stress components calculated in OUTMOD.</p>
<p>Long-standing error.</p>
<h3>Specified loads at nodes with skew boundary conditions</h3>
<p>Specified nodal loads at nodes with user-defined skew boundary conditions are not handled correctly. The loads in the global directions are applied in the skew system. A warning is written to the .res file.</p>
<p>Nodes connected to a flex-joint will have degrees of freedom in a skew system. Specified loads at these nodes are not handled correctly. An error message will be written to the .res file and the analysis stopped.</p>
<h2>RIFLEX 4.16.0 New / improved functionality</h2>
<h3>Visualization of airfoil profiles</h3>
<p>Visualization is now enabled also for foil profiles not part of a wind turbine. The foil profiles have all to be described in a airfoil-library file.</p>
<h3>Time domain fatigue calculations in OUTMOD</h3>
<p>A thickness correction based on a reference thickness and an exponent may now be included in the calculation of the fatigue capacity.</p>
<p>The calculated fatigue damage is now printed on the _outmod.mpf file.</p>
<p>The user may now specify an identifier for the fatigue calculations and may also specify all segments / elements / ends for fatigue calculations.</p>
<p>The criteria for skipping fatigue calculations and print at the first end of elements has been modified. Fatigue is now always calculated for all locations specified in OUTMOD. If fatigue is calculated for all elements with stored forces; i.e. NSECT = 0; fatigue calculation at the first end of an element is skipped if calculation was performed at the second end of the neighbouring element in the same segment.</p>
<p>Previously, fatigue was only calculated at the first end of the first element with fatigue calculation in each segment. As forces may not be stored for all elements within a segment, this may skip more nodes than intended.</p>
<h3>OUTMOD input array size</h3>
<p>The size of the integer and real input arrays in OUTMOD has previously been fixed to 1000 and 500 places. This is now increased to a minimum of 10000 and 6000 places and will be linearly increased if the OUTMOD work array size is larger than the default size.</p>
<p>This change decreases the available space for other arrays and may cause a previously successful OUTMOD run to fail. Increasing RIFLEX_OUTMOD_MEM by one (million Bytes); e.g. from the default 32 to 33; will solve this.</p>
<h3>External wind turbine controller measurements</h3>
<p>The coordinate system for the measurements is now based on the stress-free orientation of the shaft element where the electrical torque is applied. It was previously based on this element's orientation at the end of static analysis. No change in results unless the shaft rotates around the global z-axis during the static analysis.</p>
<p>A minor change has been made to the additional nodal measurements for an external wind turbine controller that were added in RIFLEX 4.14.0. The nodal rotations are changed from the updated orientation of the neighbouring element to the rotations of the specified node from the stress-free to the current orientation.</p>
<h3>Wave loads on elements</h3>
<p>The case that wave loads on elements are specified but no points for computation of wave kinematics are detected, will no longer lead to controlled program termination.</p>
<h3>Extended specification of pre-curved line type</h3>
<p>Transverse offsets may now also be specified for the second end of the last segment within a line type. See <a class="el" href="a00010.html#inpmod_b_line_transverse">Transverse offset</a>specification" in INPMOD.</p>
<h3>Boundary change for supenodes</h3>
<p>Boundary change may be specified directly for a supernode. This is in addition to the existing boundary change for local segment nodes.</p>
<h3>Simo body system element</h3>
<p>The Simo body system element is introduced to make it possible to acount for hydrodynamic interaction between bodies in a Riflex "coupled" analysis. The element nodes are of Simo body type, a new type of supernode. One Simo body is automatically attached to one simo body node having the same number of degrees of freedom as the Simo body. The Simo body system element may have one or more simo body nodes dependig how many bodies that interact.</p>
<p>The simo body supernode may be attaced to any already existing FE-node, or be used as master in a rigid super node connection.</p>
<h3>New file format for external dynamic nodal forces</h3>
<p>The nodal forces can be given in a column format.</p>
<h3>Rigid supernode connections in linear time domain analysis</h3>
<p>Rigid supernode connections may now be used in in linear time domain analysis</p>
<h3>Visualization for linear time domain analysis</h3>
<p>Visualization is enabled for linear time domain analysis.</p>
<h3>Bash shell script for running coupled analysis</h3>
<p>A Bash shell script for running a complete coupled analysis has been added to the share/bin folder.</p>
<h2>RIFLEX 4.16.0 Corrected errors</h2>
<h3>Eccentric mass center CRS7 (General Cross Section)</h3>
<p>Error in system set up. Local line segment number used instead of global segment number for eccentric mass center; Cross sections of type CRS7.</p>
<p>This caused incorrect results if eccentric mass was specified for CRS7 cross-sections on lines other than the first line specified. The error has been corrected.</p>
<p>Error since 4.10.0</p>
<h3>No wave forces in combination with export for visualization</h3>
<p>The combination of no wave forces acting on elements and export for visualization leads to uncontrolled program termination. The error has been corrected.</p>
<h3>Nodal component at end 2 in linear time domain</h3>
<p>Include loads for nodal components at end 2 of a segment in linear time domain simulation. These were previously not included if the segment had more than one element.</p>
<p>Long-standing error</p>
<h3>Potential flow and MacCamy-Fuchs loads</h3>
<p>Neither Potential flow loads nor MacCamy-Fuchs loads are currently implemented for regular wave analysis. The is now checked and DYNMOD will give an error message and stop.</p>
<p>An alternative is to replace the regular wave with a tabulated ("numerical") wave spectrum with a single frequency component.</p>
<h3>Kinematic viscosity in air is changed</h3>
<p>The default value for viscosity in air is set to 1.516E-5, air temperature 20 degree centigrades.</p>
<h3>Error in boundary change during parameter variation in static analysis</h3>
<p>Error in static analysis if boundary change was specified during parameter variation. The error normally caused program termination, but could give error in results if the energy norm was used for solution accuracy.</p>
<p>Error since 4.12.0</p>
<h3>Error in boundary change during parameter variation in static analysis</h3>
<p>Error if a node is specified to become a slave node during static parameter variation.</p>
<p>Long-standing error</p>
<h3>IEC extreme wind events with detailed specification</h3>
<p>Corrected an error in the initialization of the IEC 2005 wind events</p>
<ul>
<li>extreme vertical wind shear, EWSV</li>
<li>extreme horizontal wind shear, EWSH</li>
<li>extreme operating gust, EOG</li>
<li>extreme direction change, EDC The wind events were incorrectly initialized when defined by a detailed specification; i.e. velocity or direction change and event duration. The error resulted in the event duration being zero and no change in wind.</li>
</ul>
<p>Error since RIFLEX 4.12.0.</p>
<h3>IEC extreme wind events for wind turbine class S</h3>
<p>Corrected an error in the initialization of the IEC 2005 wind events for wind turbine class S. The expected turbulence intensity, Iref, was incorrectly set to the reference wind speed, Vref.</p>
<p>Error since RIFLEX 4.12.0.</p>
<h3>Error in time domain fatigue for systems with only bar elements</h3>
<p>Corrected an error in fatigue calculations for systems with only bar elements.</p>
<p>Long-standing error.</p>
<h3>Correct echo of Froude-Krylov scaling factor for time domain VIV</h3>
<p>The echo on the _inpmod.res file of the Froude-Krylov scaling factor in the normal direction was incorrectly identified as in the tangential direction.</p>
<p>Note that the time domain VIV load model is currently restricted functionality and that a license is required.</p>
<p>Error since RIFLEX 4.14.0.</p>
<h3>Time domain VIV loads and consistent formulation (restricted functionality)</h3>
<p>The time domain VIV loads may now be used with consistent mass / load formulation.</p>
<p>Note that the time domain VIV load model is currently restricted functionality and that a license is required.</p>
<p>Error since RIFLEX 4.14.0.</p>
<h2>RIFLEX 4.16.0 Input changes</h2>
<p>Most input files used in version 4.14 can be used unchanged. The exception is described below.</p>
<h3>Coupled analysis with IUPPOS = 0</h3>
<p>The option IUPPOS = 0, hydrodynamic loads calculated with lines kept fixed in static position and no update of surface penetration, is no longer available for analyses with SIMO bodies.</p>
<h2>RIFLEX 4.16.0 Removed functionality</h2>
<p>No previously available functionality have been removed in this version.</p>
<h2>RIFLEX 4.16.0 Deprecated functionality</h2>
<h3>Default values for air and water density (INPMOD)</h3>
<p>The default values for air and water density in the ENVIRONMENT CONSTANTS data group in INPMOD will be changed. The current default values of 1.3 and 1025 for air and water respectively are only applicable if the units 'm' and 'kg' are used.</p>
<p>In RIFLEX 4.18.0, the current default values will be used if 'kg' is specified for the mass unit. Alternative default values will be used if 'Mg' is specified. For other mass unit names, teh air and water density must be specified by thee user.</p>
<h3>Default values in CODE CHECK CURVES (OUTMOD)</h3>
<p>Two default values will be removed in the OUTMOD data group CODE CHECK CURVES in RIFLEX 4.18.0.</p>
<ul>
<li>minimum yield stress, SMYS, and</li>
<li>modulus of elasticity, EMOD.</li>
</ul>
<p>The current default values of 220.0E3 and 2.1E8 are only applicable if the units 'm' and 'kN' are used.</p>
<h3>CARISIMA riser-seafloor contact (restricted functionality)</h3>
<p>The CARISIMA riser-seafloor contact is deprecated and will be removed in the future.</p>
<h3>Old OUTMOD fatigue data group</h3>
<p>The old, undocumented OUTMOD data group TIME FATIGUE LIFE will be removed following the 4.16 release.</p>
<p>The OUTMOD data group TIME FATIGUE DAMAGE should be used instead.</p>
<h1>RIFLEX licensing</h1>
<p><code>RIFLEX</code> is license-managed using the FLEXlm / FLEXlnet software license management system. If you want <code>RIFLEX</code> to be used from any networked computer on your site, you must run a license manager on a server in your network. Alternatively, <code>RIFLEX</code> may be run on a single computer using a standalone license file.</p>
<p><b>Please note that version 4.2 and higher requires a licence file with a feature version that is equal or larger than the link date.</b></p>
<p>In order to issue a server license or a standalone license file, SINTEF Ocean or DNV GL needs the following info on your server:</p>
<ul>
<li>License type (server or standalone)</li>
<li>Operating system and version (Windows 7, Windows XP, HP-UX and Linux currently supported)</li>
<li>MAC address / FLEXlm hosted of the computer.</li>
</ul>
<p>Your IT-staff is probably already familiar with this procedure as FLEXlm is used by a large number of other applications (e.g. Matlab).</p>
<h1>RIFLEX version numbers</h1>
<p>The version number consists of three numbers separated by periods, e.g. 4.16.0. The two first are the version. The third is updated for each subsequent (bug fix) release.</p>
<p>Even numbered versions, e.g. 4.14, 4.16, are reserved for official versions.</p>
<p>Odd numbered versions, e.g. 4.15, 4.17, are reserved for development versions. The next official release will therefore be 4.18.</p>
<h1>RIFLEX 4.14.0 (2018-11-01)</h1>
<h2>RIFLEX 4.14.0 New / improved functionality</h2>
<h3>Scaling of tangential Froude-Krylov loads</h3>
<p>A scaling factor for the tangential Froude-Krylov load term has been added for Morison or potential flow loads. The scaling factor is available for the CRS0, CRS1, CRS2 and CRS7 cross-sections.</p>
<p>The option to specify no hydrodynamic loads has also been added for these cross-sections.</p>
<h3>MacCamy &amp; Fuchs - Simplified radiation force</h3>
<p>The input is extended in order to make the loads on bottom-fixed cylindrical monopiles to be applicable for floating single column systems by including a simple load model representing the radiation forces.</p>
<p>The (horizontal) radiation loads will be based on an added mass coefficient and a damping coefficient, AMY and DAMP.</p>
<p>In the vertical direction the wave excitation forces is calculated in a similar manner as the corresponding load term in the Morison equation. A user specified added mass coefficient will be input and used for the vertical direction, CAX.</p>
<p>Example of input (with default values):</p>
<div class="fragment"><div class="line"><span class="stringliteral">&#39;------------------------------------------------------</span></div>
<div class="line"><span class="stringliteral">&#39;</span>chtype</div>
<div class="line">MACF</div>
<div class="line"><span class="stringliteral">&#39;------------------------------------------------------</span></div>
<div class="line"><span class="stringliteral">&#39;</span>cqx             cqy             cax  icode hydrod    </div>
<div class="line"> 0.550000000e+00 9.000000000e-01  0.    2     /</div>
<div class="line"><span class="stringliteral">&#39;</span></div>
<div class="line"><span class="stringliteral">&#39;</span>Simplified radiation force:</div>
<div class="line"><span class="stringliteral">&#39;amy damp</span></div>
<div class="line"><span class="stringliteral"> 0.0 0.0</span></div>
<div class="line"><span class="stringliteral">&#39;</span>------------------------------------------------------</div>
</div><!-- fragment --><p>Note that the extension of the MacCacmy &amp; Fuchs input in Riflex 4.14.0 is not compatible with earlier versions.</p>
<h3>External wind turbine controller</h3>
<p>Additional nodal or element responses may now be made available as additional measurements to an external wind turbine controller. This functionality is currently under implementation.</p>
<h3>Irregular simulation with vessel transfer function NONE</h3>
<p>Irregular simulations with vessel transfer function NONE are now permitted. The vessel motions must be read from file or not be applied, i.e. the irregular motion indicator must be FILE or NONE.</p>
<h3>The Wind turbine BEM code</h3>
<p>The BEM code has been made less time-consuming. Automatic reshaping of matrices when calling subroutines have been avoided.</p>
<h3>Hydrodynamic loads based on potential theory</h3>
<p>Improved memory handling to avoid program termination for analyses with large amount of input data.</p>
<h3>3D seafloor geometry file</h3>
<p>Improved accuracy for 3D grids with very short distances between grid points. Improved data checking and warnings when reading the seafloor geometry file.</p>
<h2>RIFLEX 4.14.0 Corrected errors</h2>
<h3>Error in water plane stiffness for lumped loads</h3>
<p>The water plane stiffness was zero if current was present and the element crossing the water line did not have attached nodal components.</p>
<p>Long-standing error.</p>
<p>Minor changes in convergence for cases with lumped formulation and current are expected.</p>
<h3>Low frequency motions from file</h3>
<p>Corrected a long-standing error for low frequency vessel motions from file. The specified low frequency motions were only applied if wave frequency motions were also specified.</p>
<h3>External wind turbine controller</h3>
<p>Corrected the calculation of the "measurement" accumulated aerodynamic torsional load which is made available to external wind turbine controllers. Previously, the accumulated global x-moment was exported to the control system.</p>
<p>No error in applied aerodynamic loads.</p>
<p>Error since 4.12.0.</p>
<h2>RIFLEX 4.14.0 Known issues</h2>
<h3>Wave kinematics at updated position in coupled analysis</h3>
<p>Currently, the FFT wave method must be selected in <code>SIMO</code> to allow wave kinematics at updated position to be used in <code>RIFLEX</code> for a coupled analysis.</p>
<h3>Main Riser Line inner pressure</h3>
<p>The Main Riser Line (MRL) input allows the pressure to be specified at either end of the MRL. The specified inner pressure is, however, always applied at end 1 of the MRL. This will give errors in true wall tension and some stress components calculated in OUTMOD.</p>
<p>Long-standing error.</p>
<h2>RIFLEX 4.14.0 Input changes</h2>
<h3>MacCamy Fuchs loading</h3>
<p>The MacCacmy &amp; Fuchs input has been changed in RIFLEX 4.14.0. Old input must be updated.</p>
<p>Example of input (with default values):</p>
<div class="fragment"><div class="line"><span class="stringliteral">&#39;------------------------------------------------------</span></div>
<div class="line"><span class="stringliteral">&#39;</span>chtype</div>
<div class="line">MACF</div>
<div class="line"><span class="stringliteral">&#39;------------------------------------------------------</span></div>
<div class="line"><span class="stringliteral">&#39;</span>cqx             cqy             cax  icode hydrod    </div>
<div class="line"> 0.550000000e+00 9.000000000e-01  0.    2     /</div>
<div class="line"><span class="stringliteral">&#39;</span></div>
<div class="line"><span class="stringliteral">&#39;</span>Simplified radiation force:</div>
<div class="line"><span class="stringliteral">&#39;amy damp</span></div>
<div class="line"><span class="stringliteral"> 0.0 0.0</span></div>
<div class="line"><span class="stringliteral">&#39;</span>------------------------------------------------------</div>
</div><!-- fragment --><h2>RIFLEX 4.14.0 Removed functionality</h2>
<p>No previously available functionality have been removed in this version.</p>
<h2>RIFLEX 4.14.0 Deprecated functionality</h2>
<p>No functionality is deprecated in this version.</p>
<h1>RIFLEX 4.12.5</h1>
<h2>RIFLEX 4.12.5 Corrected errors</h2>
<h3>Avoid array overwriting in dynmod</h3>
<p>Avoid overwriting the beginning of the array containing element forces and moments in nonlinear time domain simulation. The values for the first seven elements were temporarily zero during the time step. No consequence for normal analyses as the correct values were used in the calculation of geometric stiffness and in reporting.</p>
<h1>RIFLEX 4.12.3</h1>
<h2>RIFLEX 4.12.3 Improved functionality</h2>
<h3>Increase the model size that can be read by INPMOD</h3>
<p>The maximum number of DMS arrays is increased from 10503 to 20003 to allow larger models to be read by INPMOD. The INPMOD work array size is increased to 2 million integer words.</p>
<h2>RIFLEX 4.12.3 Corrected errors</h2>
<h3>Error for SIMO generic external control systems in Coupled models</h3>
<p>An error introduced in version 4.12.0 made it impossible to run generic external control systems in a <code>RIFLEX</code> Coupled model. This has now been resolved.</p>
<h3>Application of marine growth</h3>
<p>Restrict application of marine growth to CRS0, CRS1, CRS2. CRS3, CRS4 and CRS7 cross-sections. Volume loads and Morison hydrodynamic loads will be modified. The modifications are calculated with the assumption that the cross-section is circular.</p>
<p>The modification of Morison coefficients is now based on the increase in hydrodynamic diameter so that it is consistent with the initial non-dimensional coefficients.</p>
<p>Numerical errors and not-a-number ("NaN") results are avoided by skipping modification of the volume loads if the external area is zero.</p>
<p>Modification of the Morison coefficients is skipped if the initial hydrodynamic diameter is zero.</p>
<h1>RIFLEX 4.12.2</h1>
<h2>RIFLEX 4.12.2 Corrected errors</h2>
<h3>Error when calculating eigenvalues for model with SIMO bodies</h3>
<p>An error has been fixed where <code>RIFLEX</code> would crash when eigenvalues was calculated for a model with <code>SIMO</code> bodies (coupled model).</p>
<p>Error since 4.12.0.</p>
<h3>Application of marine growth</h3>
<p>The drag coefficients are corrected for marine growth.</p>
<h3>Error exit for MacCamy-Fuchs loads and a wave condition containing swell</h3>
<p>The MacCamy-Fuchs loads are only calculated for the wind-sea part of a wave condition. An error exit is therefore added if a wave condition containing swell is specified for a case with MacCamy-Fuchs loads.</p>
<h1>RIFLEX 4.12.1</h1>
<h2>RIFLEX 4.12.1 Corrected errors</h2>
<h3>Application of marine growth</h3>
<p>The application of marine growth in static analysis for systems with non-consistent units has been corrected. No error for analyses with consistent units; i.e. gcons = 1.0.</p>
<p>The error caused the volume loads of the whole system to be scaled by a factor of 1/gcons when growth was applied in static analysis. As the typical value of gcons for non-consistent units is 0.001, the error gave clearly non-physical results.</p>
<p>The error occurred even if a growth scaling factor of zero was specified.</p>
<h3>Wave kinematics at updated position in coupled analysis</h3>
<p>Wave kinematics may now be calculated at updated dynamic positions in a coupled simulation. This resulted in an error exit from <code>RIFLEX</code> <code>DYNMOD</code> in 4.12.0.</p>
<h3>Hydrodynamic loads based on potential theory</h3>
<p>Error corrections and enhanced funtionality to allow for swell and short-crested waves. The functionality is currently under testing.</p>
<h1>RIFLEX 4.12.0</h1>
<h2>RIFLEX 4.12.0 New / improved functionality</h2>
<h3>Wind turbine response storage</h3>
<p>Wind turbine response storage is available based on user input specification.</p>
<h3>MacCamy-Fuchs wave loads</h3>
<p>The drag force input specification has been expanded to allow for dimensional drag force coefficients.</p>
<h3>Energy convergence criterion</h3>
<p>A convergence criterion based on energy has been implemented in Stamod and Dynmod. The rotational degrees of freedom are included, as opposed to the existing displacement convergence criterion. The new convergence criterion is approximate because the unbalanced loads refer to the configuration at the previous equilibrium iteration. Hence, false convergence may occur for problems with oscillating convergence behavior. The energy convergence criterion can therefore not be applied without also using the displacement convergence criterion.</p>
<h3>Wind turbine blade bending moment measurements passed to external controller</h3>
<p>The blade root (at end 1 of the first element of the foil line) bending moments about the local x, y, z axes are now available to the external wind turbine controller.</p>
<h3>Hydrodynamic drag on cross section with 2 symmetry planes</h3>
<p>The Morison drag term has been modified to be in accordance with the drag term used for axis symmetric cross sections. Please confer the user documentation.</p>
<h3>Implementation of stochastic wave amplitudes</h3>
<p>The wave components of a realization of an irregular seastate may now have stochastic amplitudes. The new option CHAMP is used to specify deterministic ('DET') or stochastic ('STOCH') amplitudes.</p>
<p>Note that using stochastic wave amplitudes will cause the significant wave height to vary between realizations.</p>
<h3>Wave kinematics at updated position</h3>
<p>Wave kinematics may now be calculated at updated dynamic positions during a time domain simulation by specifying IUPPOS = 2.</p>
<p>Wave kinematics can be calculated during the simulation for ISURF &lt;=4; i.e. potential fixed at mean water level (ISURF &lt;= 1 and ISURF = 4), potential stretched / compressed to instantaneous wave surface (ISURF = 2) and potential moved to instantaneous wave surface (ISURF = 3). Wave kinematics may not be calculated during the simulation for second order waves (ISURF = 5).</p>
<p>Except for very short simulations, this will be significantly slower than pre-generating the wave kinematics at the static position. This is because complete wave kinematics time series may be generated using FFT, while wave kinematics at individual time steps are calculated as a sum of all the non-zero wave components.</p>
<p>The option IUPPOS = -2; calculate wave kinematics at the static positions during the simulation; is added for verification and comparison.</p>
<h3>Storage of wave kinematics on additional file</h3>
<p>Wave kinematics may now alternatively be stored on an additional file in ASCII format. Previously, only the binary format was available.</p>
<p>Wave kinematics calculated during a simulation; IUPPOS = 2 or IUPPOS = -2; are stored on files &lt;prefix&gt;_updkin.asc / &lt;prefix&gt;_updkin.bin.</p>
<h3>Undo changes to PATH at the end of riflex.bat</h3>
<p>When riflex.bat is called with CALL, variables such as PATH will also be changed in the calling environment. Multiple calls to riflex.bat will thus increase the length of the PATH variable, which may lead to the execution stopping if it becomes too long.</p>
<p>Calling riflex.bat with "CMD /C" will ensure that variables in the calling environment will not be changed. This is therefore recommended, e.g.: </p>
<div class="fragment"><div class="line">CMD /C C:/SINTEF/riflex_simo-4.10.4.BIWR-46-win64/Riflex/bin/riflex.bat i stdin</div>
<div class="line">CMD /C C:/SINTEF/riflex_simo-4.10.4.BIWR-46-win64/Riflex/bin/riflex.bat s stdin</div>
<div class="line">CMD /C C:/SINTEF/riflex_simo-4.10.4.BIWR-46-win64/Riflex/bin/riflex.bat d stdin</div>
</div><!-- fragment --><p> Either backward slashes ( "\" ) or forward slashes ( "/" ) may be used in the path to the riflex.bat file.</p>
<p>riflex.bat has been modified so that the PATH variable is now set back to its initial value after running RIFLEX.</p>
<p>Also included in <code>RIFLEX</code> 4.10.5.</p>
<h3>Wind force as separate load group in Stamod</h3>
<p>The wind load was earlier activated together with specified forces. Now the wind load on turbine blades and and the rest of the structure may be activated as a separate load group in Stamod.</p>
<p>Example of input:</p>
<div class="fragment"><div class="line">LOAD GROUP DATA</div>
<div class="line">WIND   1</div>
<div class="line"><span class="stringliteral">&#39;WindOnTurbineBlades</span></div>
<div class="line"><span class="stringliteral">ON</span></div>
</div><!-- fragment --><h3>Improved bending hysteresis model</h3>
<p>The numerical performance of the hysteresis bending model for CRS1 with IEJ=1 and IMF=1 has been improved. A new procedure for updating the hysteresis bending moments based on Backward-Euler integration was implemented, which allows for a fully consistent tangent stiffness matrix that is expected to improve the convergence properties of the solution procedure.</p>
<h3>Displacement storage for duplicated nodes also</h3>
<p>A duplicated node occurs when the last node of a line segment is the first node of the next segment. This shared node has one unique global node id but has two local node ids known to the user: <code>lineid-segm1-lastnode</code> and <code>lineid-segm2-1</code>.</p>
<p>Previously, only the data for the first of these were written to the ascii or binary storage file. The other was skipped. This occured even if both were requested part of the <code>DISPLACEMENT RESPONSE STORAGE</code> card. Now, both will be written - if requested.</p>
<h3>New stationary uniform wind with shear</h3>
<p>Wind type 14, stationary uniform wind with shear, has been added. A power or logarithmic shear profile may be specified.</p>
<p>This wind type differs from wind type 10, stationary uniform wind with shear, values interpolated at grid points, in that the shear profile is used directly.</p>
<h3>Extreme wind events in dynamic analysis</h3>
<p>An extreme wind event from "IEC 61400-1 Wind turbines – Part 1: Design
requirements – 2005" may be applied in a time domain simualtion. The wind event can be applied to a stationary uniform wind with shear, IWITYP = 14, in both <code>RIFLEX</code> analyses and in coupled <code>RIFLEX</code> - <code>SIMO</code> analyses. The following extreme wind events are available:</p>
<ul>
<li>IEC 2005 extreme coherent gust with direction change, ECD</li>
<li>IEC 2005 extreme vertical wind shear, EWSV</li>
<li>IEC 2005 extreme horizontal wind shear, EWSH</li>
<li>IEC 2005 extreme operating gust, EOG</li>
<li>IEC 2005 extreme direction change, EDC</li>
</ul>
<p>The EWSV and EWSH events can only be used for systems which include a <code>RIFLEX</code> wind turbine. The ECD, EOG and EDC events may be used for systems without a wind turbine, but some event parameters must then be specified; e.g. velocity change, direction change and duration of event for an ECD event.</p>
<h3>Wind turbine shutdown with generator fault conditions</h3>
<p>Wind turbine shutdown with generator fault conditions may be applied in a time domain analysis. The shutdown event can be applied to a RIFLEX modelled wind turbine in both <code>RIFLEX</code> analyses and in coupled <code>RIFLEX</code> - <code>SIMO</code> analyses. The generator fault options include total loss of generator torque and bakup power formulated as following scaled torque control. In addition a mechanical brake in form of linear torque damping may be modelled.</p>
<h3>Wind turbine blade pitch fault conditions</h3>
<p>Wind turbine blade pitch fault conditions may be applied in a time domain analysis. The fault conditions can be applied to a RIFLEX modelled wind turbine in both <code>RIFLEX</code> analyses and in coupled <code>RIFLEX</code> - <code>SIMO</code> analyses. The following blade pitch fault types may modelled:</p>
<ul>
<li>Seized, i.e. fixed blade pitch from a specific time</li>
<li>Runaway, i.e. blade pitch change at a specific rate until reach of final pitch angle</li>
<li>Actuator bias, i.e. constant pitch deviation from required pitch</li>
</ul>
<p>The blade pitch fault conditions are modelled individually for blades with pitch fault.</p>
<h3>Pipe-In-pipe contact forces in global system</h3>
<p>Pipe-in-pipe contact forces and moments in the global system are now stored on the file &lt;pref&gt;_cntfor.asc / &lt;pref&gt;_cntfor.bin along with the forces and moment in the local system. The contact forces are stored if element forces are stored on an additional ascii or binary file; i.e. IFORFM /= 0; and pipe-in-pipe elements are present in the system.</p>
<h3>Visualization of wind speeds and forces for wind turbine blades</h3>
<p>Wind speeds and aerodynamic forces acting on wind turbine blades are made available for visualization in SIMA and SimVis.</p>
<h3>Hydrodynamic loads based on potential theory</h3>
<p>A test version of hydrodynamic loads based on potential theory (WAMIT) has been implemented. The functionality is currently under testing.</p>
<h3>Marine growth</h3>
<p>The marine growth is defined by specifying the thickness and density for a range of depths.</p>
<p>Example of input:</p>
<div class="fragment"><div class="line"><span class="stringliteral">&#39;---------------------------</span></div>
<div class="line"><span class="stringliteral">NEW COMPonent GROWth</span></div>
<div class="line"><span class="stringliteral">&#39;</span>---------------------------</div>
<div class="line"><span class="stringliteral">&#39;ID NumbOfLevels</span></div>
<div class="line"><span class="stringliteral">NOR300    5</span></div>
<div class="line"><span class="stringliteral">&#39;</span>---------------------------</div>
<div class="line"><span class="stringliteral">&#39; MGLEV  MG   MDENS</span></div>
<div class="line"><span class="stringliteral">&#39;</span>---------------------------</div>
<div class="line">  2.0  0.06  1.325</div>
<div class="line"> 40.0  0.06  1.325</div>
<div class="line">-40.1  0.03  1.325</div>
<div class="line">-300.0  0.03  1.325</div>
<div class="line">-700.0  0.03  1.325</div>
<div class="line"><span class="stringliteral">&#39;---------------------------</span></div>
</div><!-- fragment --><p>Marine growth is defined as a new static load group. During the load steps in this load group, the mass and diameter properties of the elements in this zone will be modified based on their current location. These properties will be fixed in the rest of the static analysis and in the dynamic analysis. The user may thus select the static configuration that is most representative for the conditions for which the marine growth is accumulated.</p>
<p>An overall scaling factor for the accumulated thickness will allow the user more easily to switch between no marine growth, partly accumulated marine growth and fully developed marine growth.</p>
<p>Example of input:</p>
<div class="fragment"><div class="line"><span class="stringliteral">&#39;---------------------------</span></div>
<div class="line"><span class="stringliteral">LOAD GROUP DATA</span></div>
<div class="line"><span class="stringliteral">&#39;</span>---------------------------</div>
<div class="line"><span class="stringliteral">&#39;nstep maxit raco</span></div>
<div class="line"><span class="stringliteral">4 50 1.1e-5</span></div>
<div class="line"><span class="stringliteral">&#39;</span>lotype NLSPEC</div>
<div class="line">GROWTH    1</div>
<div class="line"><span class="stringliteral">&#39;MGFAC</span></div>
<div class="line"><span class="stringliteral">1.0</span></div>
<div class="line"><span class="stringliteral">&#39;</span>--------------</div>
</div><!-- fragment --><h2>RIFLEX 4.12.0 Corrected errors</h2>
<h3>Wind turbine with number of blades different from 3</h3>
<p>Riflex failed or gave incorrect results if the number of foil blades was different from 3.</p>
<p>Corrected in <code>RIFLEX</code> 4.10.4.</p>
<h3>Hydrodynamic drag on CRS2 and CRS7 cross-sections, lumped formulation</h3>
<p>Corrected a long-standing error in hydrodynamic drag loads on CRS2 and CRS7 cross-sections when the lumped load formulation is chosen; i.e. LCONS = 0 in STAMOD.</p>
<p>Corrected in RIFLEX 4.10.5.</p>
<h3>Scaling of the Froude-Krilov term for CRS2 and CRS7 cross-sections, consistent formulation</h3>
<p>The input scaling factor for the Froude-Krilov term was not used for for CRS2 and CRS7 cross-sections if the consistent load formulation was chosen. Error in applied loads if</p>
<ul>
<li>consistent load formulation was chosen; LCONS = 1 in STAMOD; and</li>
<li>CRS2 or CRS7 cross-sections with SCFK /= 1.0 were used.</li>
</ul>
<h3>Corrected the line length used in result presentation</h3>
<p>The accumulated line length used in result presentation is now calculated from the actual stress-free segment lengths given in the line type definition in INPMOD; i.e. parameter SLGTH0 if it is given, otherwise SLGTH.</p>
<p>The line length is mainly used for results on the MatrixPlot files.</p>
<p>Previously, the line length was calculated from the updated stress-free element lengths in STAMOD and DYNMOD and from the final static nodal coordinates in VIVANA and OUTMOD.</p>
<p>The change in line length will be small for cases without</p>
<ul>
<li>length changes due to temperature or pressure changes</li>
<li>element length modification for elements on / leaving a winch</li>
<li>large static elongation / compression</li>
</ul>
<h3>Elctrical torque in wind turbine</h3>
<p>A minor error in the application of the torque from the wind turbine controller has been corrected. The torque was applied in the flex-joint local element system and not in the skew system at the flex-joint nodes. The difference between the systems is small and the correction gives insignificant changes to the results.</p>
<p>Corrected in <code>RIFLEX</code> 4.10.2.</p>
<h3>Airfoil forces</h3>
<p>A long-standing error (since version RIFLEX 4.4) has caused incorrect results or uncontrolled error termination when computing airfoil forces on cross-sections that were not part of a wind turbine. The error has been corrected.</p>
<p>Corrected in <code>RIFLEX</code> 4.10.2.</p>
<h3>Reporting of wind at wind turbine hub</h3>
<p>For coupled analyses with <code>SIMO</code> wind type <code>IWITYP &gt;= 10</code>:</p>
<ul>
<li><code>=10</code>: Stationary uniform wind with shear</li>
<li><code>=11</code>: Fluctuating uniform 2-component wind</li>
<li><code>=12</code>: Fluctuating 3-component wind read from files (IECWind format)</li>
<li><code>=13</code>: Fluctuating 3-component wind read from files (TurbSim format)</li>
</ul>
<p>The wind at the updated coordinates of the <code>RIFLEX</code> hub supernode is now reported on the wind turbine result file. Previously, the wind at the <code>SIMO</code> body <code>WIND_REF</code> was reported. The reported wind is also sent into the external control system, but is otherwise not used in the analyses. The incoming wind on the blades is found using the updated nodal coordinates along the blades and has not been changed.</p>
<p>No changes for coupled analyses with <code>SIMO</code> wind type <code>IWITYP &lt; 10</code>; the wind at the <code>SIMO</code> body <code>WIND_REF</code> is reported. Note that this wind is calculated at the wind force coefficient height <code>ZCOEFF</code>. This wind is also used as the incoming wind along the wind turbine blades .</p>
<p>Possible change in response for wind turbines with external control system and <code>SIMO</code> wind type <code>IWITYP &gt;= 10</code>.</p>
<p>Corrected in <code>RIFLEX</code> 4.10.2.</p>
<h3>Ball-joint release for systems with flex-joints</h3>
<p>Corrected an error that could occur when releasing a ball-joint in a nonlinear time domain simulation for a system that also contained one or more flex-joints. The error occurred if</p>
<ul>
<li>a single, specified ball-joint was released and the system contained a flex-joint with the same reference number as the ball-joint</li>
<li>all ball-joints were released and the system contained any flex-joints</li>
</ul>
<p>The error caused <code>DYNMOD</code> to terminate with an error message when the ball-joint connector was released. Error since flex-joints were introduced in <code>RIFLEX 3.6.0</code>.</p>
<p>Corrected in <code>RIFLEX</code> 4.10.2.</p>
<h3>Export of water depth for DeepC animation</h3>
<p>The export of hydrodynamic water depth to the .vtf file for animation in Xtract has been corrected.</p>
<p>Error in RIFLEX 4.10.0 and 4.10.1, corrected in RIFLEX 4.10.2.</p>
<h3>Strain-dependent cross-sectional axial damping</h3>
<p>The input of strain-dependent cross-sectional axial damping has been corrected. The table is given as <code>IDMPAXI</code> pairs of strain and damping coefficient values. All values are given on a single input line, as described in the User Manual. The table has previously been incorrectly read as two values on each input line.</p>
<p>This input may still be given as two values on each input line in <code>RIFLEX 4.10.x</code>. This may be chenged in later versions.</p>
<p>Corrected in <code>RIFLEX</code> 4.10.2.</p>
<h3>Empty pipe-in-pipe contact force file</h3>
<p>The contact force file &lt;pref&gt;_cntfor.asc / &lt;pref&gt;_cntfor.bin was empty if seafloor contact elements were present. The contents were instead written to the Fortran file 80.</p>
<p>Error since <code>RIFLEX</code> 4.10.0. Also corrected in <code>RIFLEX</code> 4.10.4.</p>
<h3>Allow several vessels without motion transfer functions</h3>
<p>Several support vessels may now be specified without motion transfer function, i..e with <code>IDWFTR = NONE</code>. Previously, only one vessel in a system could be specified without motion transfer functions.</p>
<h3>Avoid error for some cases of visualization with several vessels</h3>
<p>Corrected errors that could cause a dynamic simulation to fail during initialization of visualization. The error occurred if the simulation included several vessels and either</p>
<ul>
<li>no vessel motions were included; CHMOT = NONE; or</li>
<li>vessel motions read from file; CHMOT = FILE; and several vessels did not have transfer functions.</li>
</ul>
<h2>RIFLEX 4.12.0 Input changes</h2>
<h3>Wind turbine response storage</h3>
<p>Storage of wind turbine responses requires user input specification.</p>
<h3>MacCamy-Fuchs wave loads</h3>
<p>Since the input specification has been expanded to allow for dimensional drag force coefficients, an input code for hydrodynamic drag coefficients has to be specified. As a consequence the input is not back-compatible for MacCamy-Fuchs wave loads.</p>
<h3>Static wind loads</h3>
<p>Static wind loads on RIFLEX elements will now only be applied in static analysis if WIND is specified as a static load. Previously, the static wind loads were activated together with specified forces. Add the load type WIND to the static load group with SFOR, specified forces, to get the same static loading as before.</p>
<p>See the section Wind force as separate load group in Stamod below for more deals.</p>
<h3>Require compatible wind type in coupled analysis with wind loads</h3>
<p>The <code>SIMO</code> wind types that are not available in standalone <code>RIFLEX</code>; <code>IWITYP &lt; 10</code>, are now only allowed in coupled analysis if wind loads are only applied to <code>SIMO</code> bodies and wind turbine blades. If the case includes non-blade elements with wind force coefficients <code>IWITYP &gt;= 10</code> is required.</p>
<p>Previously, the wind time series at the first <code>SIMO</code> body with wind coefficients was used for all non-blade elements with wind coefficients. The analysis stopped with an error if none of the <code>SIMO</code> bodies had wind coefficients.</p>
<h2>RIFLEX 4.12.0 Known issues</h2>
<h3>Specified loads at nodes with skew boundary conditions</h3>
<p>Specified nodal loads at nodes with user-defined skew boundary conditions are not handled correctly. The loads in the global directions are applied in the skew system. A warning is written to the .res file.</p>
<p>Nodes connected to a flex-joint will have degrees of freedom in a skew system. Specified loads at these nodes are not handled correctly. An error message will be written to the .res file and the analysis stopped.</p>
<h2>RIFLEX 4.12.0 Removed functionality</h2>
<h3>Generation of LF-motions from spectra</h3>
<p>Generation of low frequency motions from spectra has been removed in <code>RIFLEX 4.11.3</code>. The data groups <code>LFMOTION SPECTRUM SURGE</code>, <code>LFMOTION SPECTRUM SWAY</code> and <code>LFMOTION SPECTRUM YAW</code> have been removed and the options <code>CHLFM = GEN</code> and <code>CHLFM = NEW</code> are no longer allowed in <code>IRREGULAR RESPONSE ANALYSIS</code>.</p>
<p>Time series of low frequency motions may be read from file.</p>
<h2>RIFLEX 4.12.0 Deprecated functionality</h2>
<p>No functionality is deprecated in the 4.12.0 version.</p>
<h1>RIFLEX 4.10.0</h1>
<h2>RIFLEX 4.10.0 Input changes</h2>
<p>Most input files from version 4.8 can be used unchanged. The exceptions are noted below. Input for new functionality is described in the User Manual.</p>
<h3>Bottom tangent option</h3>
<p>The bottom tangent option for SB and AR systems, <code>IBTANG</code>, has been changed. <code>IBTANG = 1</code> will now specify the 3D bottom formulation.</p>
<p>Note that the outer contact radius, <code>R_EXTCNT</code>, of the cross-section is used in the 3D bottom formulation while it was not used in the flat bottom formulation.</p>
<p>The 3D seafloor formulation gives contact on all nodes that are below <code>Z &lt; ZBOT + R_EXTCNT</code>; i.e. contact at the outer contact radius. The original flat bottom formulation gives contact for nodes with <code>Z &lt; ZBOT</code>; i.e. contact at the centreline. Insignificant changes are expected for cases in which <code>R_EXTCNT = 0</code> for the segments in contact with the seafloor.</p>
<p>Results will change for cases where segments with <code>R_EXTCNT &gt; 0</code> had contact with the flat seafloor formulation. This may be handled in four alternative ways:</p>
<ul>
<li>If the segments do not have other contact, set <code>R_EXTCNT = 0</code></li>
<li>If <code>R_EXTCNT</code> is the same for all segments with seafloor contact, lower the seafloor by <code>R_EXTCNT</code>.</li>
<li>Raise the final static coordinates of the nodes with specified position on the seafloor by <code>R_EXTCNT</code>. The total line length may have to be modified to obtain the same configuration and tension.</li>
<li>Continue using the original flat bottom formulation (see below), but note that this will not be available permanently.</li>
</ul>
<p>The original flat bottom formulation may be chosen by specifying <code>IBTANG = -9</code>. This option has been made available to allow investigation of differences between the two formulations and will be removed in a later version.</p>
<h3>Seafloor friction contribution to torsional load</h3>
<p>Previously, the seafloor friction contribution to torsional load was activated in <code>STAMOD</code> by specifying the load type <code>FRIT</code>. This is now specified though the seafloor contact parameter <code>ILTPR</code> given in <code>INPMOD</code>. Specifying <code>FRIT</code> in <code>STAMOD</code> will now result in an error message.</p>
<h3>Modified input for Carisima seafloor contact</h3>
<p>The Carisima <code>INPMOD</code> data group <code>NEW COMPonent SOIL</code> has been renamed <code>NEW COMPONENT SEAFloorcontact</code> and will now be used for other seafloor contact types as well. The first line of input has therefore been split into two lines and a the parameter <code>CHSFCT</code> added to specify the seafloor contact component type.</p>
<p>Example of old Carisima input:</p>
<div class="fragment"><div class="line">NEW  COMP SOIL</div>
<div class="line"><span class="stringliteral">&#39; cmpty UFA1,UFA2,IPRSO,IPREL,IPRPO</span></div>
<div class="line"><span class="stringliteral">  10     1 1</span></div>
</div><!-- fragment --><p>Example of new input:</p>
<div class="fragment"><div class="line">NEW  COMP SEAF</div>
<div class="line"><span class="stringliteral">&#39; cmpty chsfct</span></div>
<div class="line"><span class="stringliteral">  10     CARI</span></div>
<div class="line"><span class="stringliteral">&#39;</span> UFA1,UFA2,IPRSO,IPREL,IPRPO</div>
<div class="line">  1 1</div>
</div><!-- fragment --><h2>RIFLEX 4.10.0 Corrected errors</h2>
<h3>File storage of element forces for cases with pipe-in-pipe contact</h3>
<p>An error has been corrected in the storage of element forces for cases with pipe-in-pipe contact. The error could lead to specified element curvatures not being stored as expected.</p>
<p>Storage of element forces is specified in the <code>DYNMOD</code> data group <code>FORCE RESPONSE STORAGE</code>. If <code>IFORFM</code>, Format code for storage and / or output of element forces, is not 0, the element forces for the specified elements are output to the additional file; &lt;prefix&gt;_elmfor.asc or &lt;prefix&gt;_elmfor.bin. If the model contains pipe-in-pipe contact elements, the contact forces for all pipe-in-pipe elements are written to the file &lt;prefix&gt;_cntfor.asc or &lt;prefix&gt;_cntfor.bin.</p>
<p>No error if forces were not stored on additional Ascii or binary files; i.e. if the data group <code>FORCE RESPONSE STORAGE</code> was not given or if <code>IFILFM</code> = 0. No error if the number of elements for which force storage was specified was at least 40% of the number of pipe-in-pipe elements.</p>
<p>Error since <code>RIFLEX</code> 3.6.</p>
<h3>Element-airfoil correspondence outside of wind turbines</h3>
<p>An error in the selection of airfoil characteristics for elements which are not part of a wind turbine blade has been corrected. In previous versions, the airfoil characteristics for complex lines could be assigned out of order in some cases.</p>
<h3>Calculation of zero wind</h3>
<p>The calculation of wind velocity could fail if all resulting wind components at a point and time were exactly zero. Scaling of the components resulted in a division by zero and an illegal number (NaN) was returned. This has been corrected.</p>
<h2>RIFLEX 4.10.0 New / improved functionality</h2>
<h3>Visualization of seafloor contact</h3>
<p>Contact forces from all non-Carisima seafloor contact may be exported from <code>STAMOD</code> and <code>DYNMOD</code> for visualization in <code>SimVis</code>.</p>
<h3>General cross-section</h3>
<p>A new cross-section type CRS7 has been implemented which accounts for eccentric shear center, mass center and area center.</p>
<p>The CRS7 cross-section also employs a new element geometric stiffness matrix that accounts for the change of internal loads due to element rigid body rotation. This is expected to improve the Newton convergence properties and increase the maximum step size for simulations with large rigid body rotations and low tension.</p>
<h3>Coupled bending and torsion model</h3>
<p>A coupled bending and torsion model has been implemented for CRS0, CRS1, CRS2 and CRS7. The model employs a second order approximation of both the cross-section rotation and the longitudinal Green strain, and may therefore allow for increased element lengths in certain problems.</p>
<h3>MacCamy-Fuchs loads on <code>RIFLEX</code> elements</h3>
<p>MacCamy-Fuchs loads (with additional quadratic drag) may be applied to vertical cross sections, which are assumed to be circular. The input format for CRS0, CRS1, and CRS2 cross sections is modified, existing files may be used without modification.</p>
<h3>3D Seafloor contact</h3>
<p>The 3D seafloor contact formulation has been improved in order to increase the numerical robustness. The modification will give minor changes to the results for some cases.</p>
<h3>Line tension measurements in DP system</h3>
<p>A new option has been added that allows the <code>SIMO</code> DP system to receive line tension measurements from <code>RIFLEX</code> lines in a coupled simulation. Previously this has only been possible for <code>SIMO</code> catenary lines. See the the <code>SIMO</code> userguide for more details.</p>
<h3>Option to remove induction calculation for a wind turbine</h3>
<p>An advanced aerodynamic option is included in order to remove the induction calculation on a wind turbine. This option is useful for a parked or idling wind turbine, where the aerodynamic loading is better described by quasi-static airfoil loads.</p>
<h3>Control of Prandtl factor calculation options</h3>
<p>An aerodynamic option is included in order to user control of the Prandtl correction options. This is done by introducing on/off switches for correction at the blade tip, at the blade root, and a switch for how these correction factors are modified in yawed inflow.</p>
<h3>Seafloor contact specification</h3>
<p>The data group Seafloor contact specification may be given to specify which segments in an AR-system have contact with the seafloor. Different segments can have different spring-friction contact or have contact modelled using the new riser-soil contact formulation.</p>
<p>A single-node contact element is generated at each end of each beam or bar element in the specified segments.</p>
<h3>2nd order waves</h3>
<p>The 2nd order wave calculations have been made more efficient. Slight, but not significant, changes in the results are expected.</p>
<h3>Short-crested sea</h3>
<p>The restriction limiting the number of short-crested directions to a maximum of 17 has been removed. This applies to both standalone <code>RIFLEX</code> analyses and to coupled <code>RIFLEX</code> - <code>SIMO</code> analyses.</p>
<h3>Maximum number of line types and components</h3>
<p>The maximum number of line types is increased from 200 to 500 and the maximum number of components from 200 to 500.</p>
<h2>RIFLEX 4.10.0 Removed functionality</h2>
<p>No previously available functionality have been removed in version 4.10.0.</p>
<h2>RIFLEX 4.10.0 Deprecated functionality</h2>
<h3>Original flat bottom formulation</h3>
<p>The original flat bottom formulation will be removed in a later version. It may be specified with <code>IBTANG = -9</code> in <code>RIFLEX 4.10.x</code>.</p>
<h3>LF-motion response spectrum</h3>
<p>Generation of low frequency motions from spectra will be removed in a later version of <code>RIFLEX</code>. This functionality is currently available by setting <code>CHLFM = GEN</code> in <code>IRREGULAR RESPONSE ANALYSIS</code> and then giving the date groups <code>LFMOTION SPECTRUM</code>.</p>
<h3>Kill and choke lines</h3>
<p>The simplified modelling of kill and choke lines attached to a tensioned riser by including them in the riser elements will be removed in a later version of <code>RIFLEX</code>. This functionality is currently available through the variable <code>NAKC</code> in <code>ARBITRARY SYSTEM AR</code> and then giving the input described in Description of kill and choke lines.</p>
<h1>RIFLEX 4.8</h1>
<h2>RIFLEX 4.8 Input changes</h2>
<p>Input files used in version 4.6 can be used unchanged in version 4.8 with the following exceptions:</p>
<ul>
<li>Local element axes must now be defined for all fish net elements (CRS6)</li>
</ul>
<p>Input for new functionality is described in the User Manual.</p>
<h2>RIFLEX 4.8 Corrected errors</h2>
<h3>Aerodynamic pitching moment</h3>
<p>The sign of the applied pitching moment on airfoils which are not a part of a wind turbine was incorrect. This has been corrected.</p>
<p>Corrected in <code>RIFLEX</code> 4.8.4.</p>
<h3>Linux binary files</h3>
<p>The record length of the binary files was set to four times the correct value. The .ffi, .sam, .raf, .bin and .ts files were therefore four time their necessary size. The .bin and .ts files were not comparable with their documentation and pre-existing tools for reading them.</p>
<p>Error since 4.8.0.</p>
<p>Corrected in <code>RIFLEX</code> 4.8.3.</p>
<h3>Flex-joint with free torsional rotation</h3>
<p>An error in the dynamic implementation of flex-joint has been corrected. The error concerned flex-joints where the torsional rotation was free while the bending degrees of freedom were locked. This type of flex-joint is typically used in wind turbine modelling.</p>
<p>The error led to incorrect results if the local x-axis of the flex-joint did not coincide with the global x-axis. The error was negligible if the deviation from global x-axis was small. For larger deviations, the solution tended to diverge and the simulation stopped.</p>
<p>Consequences for wind turbine simulations where the flex-joint x-axis was close to aligned with the global x-axis: Except torsional moment, this error affects all reaction forces/moments in the first element in the shaft (between the hub and the flex-joint). Responses in the rest of the system are only slightly affected.</p>
<p>Corrected in <code>RIFLEX</code> 4.8.2.</p>
<h3>Drag amplification input to STAMOD</h3>
<p>The reading of the drag amplification factors from the specified MatrixPlot file has assumed that there were five lines between the line </p>
<div class="fragment"><div class="line">MATRIX    Drag amplification factor</div>
</div><!-- fragment --><p> and the first line with drag amplification values. This will not always be the case; the current version of <code>VIVANA</code>, for example, has four lines here.</p>
<p>The decoding now follows the description of the MatrixPlot file format in the MatrixPlot User Guide.</p>
<p>Corrected in <code>RIFLEX</code> 4.8.2.</p>
<h3>3D seafloor friction</h3>
<p>An error in the 3D seafloor friction forces has been corrected. In the transformation of relative displacements and velocities from the global to local seafloor system the transformation matrix for the first node of an element was used for both nodes of the element. No error if the seafloor slope was the same at both ends of the element. The consequences of the error are expected to be insignificant for most cases.</p>
<p>Corrected in <code>RIFLEX</code> 4.8.1.</p>
<h3>Correct wave kinematics node selection</h3>
<p>A possible error in selection of kinematics nodes for lines that cross the upper or lower limit for wave kinematics has been corrected. The error could cause incorrect kinematics at nodes with interpolated kinematics near the limit. Previously, the node with interpolated kinematics nearest a supernode without kinematics was selected as a kinematics node. This is now only done if there are no kinematics nodes between this node and the supernode. This correction may lead to less accurate kinematics. Please note that the selected kinematics nodes are printed on the <code>*_dynmod.res</code> file, so any change in behavior can be detected in this way.</p>
<p>Corrected in <code>RIFLEX</code> 4.8.0.</p>
<h3>Error in vessel transfer functions and short-crested waves</h3>
<p>A long-standing error could give extrapolation in direction of the vessel motion transfer functions for short-crested wave components. The error occurred if the average propagation direction, <code>WADR1</code> or <code>WADR2</code>, was less than</p>
<div class="fragment"><div class="line">180/(IWADR+1) * (IWADR-1)/2</div>
</div><!-- fragment --><p>from the first or last direction that the transfer functions were given for. <code>IWADR</code> is the number of directions used in the spreading function, <code>IWADR1</code> or <code>IWADR2</code> in data group <code>NEW IRREgular SEAState</code>.</p>
<p>For <code>IWADR</code> = 5; the transfer function will be extrapolated if the average wave direction is within 60 degrees of the first or last direction the transfer function is given for.</p>
<p>For <code>IWADR</code> = 11; the transfer function will be extrapolated if the average wave direction is within 75 degrees of the first or last direction the transfer function is given for.</p>
<p>Corrected in <code>RIFLEX</code> 4.8.0.</p>
<h3>Avoid extrapolation of vessel transfer function direction</h3>
<p>Previously, the vessel motion transfer functions could be extrapolated in direction if the first and last transfer function directions did not cover a full circle; i.e. <code>HEAD(NDHFTR)</code> - <code>HEAD(1)</code> &lt; 360 for <code>ISYMHF</code> = 0 or <code>HEAD(1)</code> not 0 for for <code>ISYMHF</code> &gt; 0.</p>
<p>To avoid extrapolation, the first direction will now be repeated for the direction <code>HEAD(1) + 360</code> if the specified directions do not cover a full circle.</p>
<p>Corrected in <code>RIFLEX</code> 4.8.0.</p>
<h3>Irregular simulation without waves</h3>
<p>Irregular simulation without waves may now be run. This previously led to an error termination at the beginning of the analysis.</p>
<p>Corrected in <code>RIFLEX</code> 4.8.0.</p>
<h3>Irregular simulation with only low frequency motions</h3>
<p>Irregular simulation with low frequency motions and no wave frequency motions may now be run. This previously led to an error termination during generation of motion time series in <code>DYNMOD</code>.</p>
<p>Corrected in <code>RIFLEX</code> 4.8.0.</p>
<h3>Visualization of regular waves for coupled analysis</h3>
<p><code>SIMA</code> and <code>SimVis</code> have always visualized regular waves with zero degrees direction, regardless of the wave direction specified. This error has been corrected. The error has no consequences for other results.</p>
<p>Corrected in <code>RIFLEX</code> 4.8.0.</p>
<h3>Non-linear Buoyancy Correction (NBC) available for coupled analysis</h3>
<p>The functionality Nonlinear Buoyancy Correction (NBC) has been made available for coupled analysis. This was not the case in the RIFLEX version 4.6.</p>
<p>Corrected in <code>RIFLEX</code> 4.8.0.</p>
<h3>Fish net load model, CRS6</h3>
<p>The fish net load model requires that the net plane is defined. The plane is defined by the local element X-axis and a reference vector specified in the input group: LOCAL ELEMENT AXIS DEFINITION.</p>
<p>If the local reference vector was not given, an uncontrolled program termination occurred in STAMOD. The program will now check whether a reference vector is given for all fish net elements. In this case, the program terminates in a controlled way giving an appropriate error message.</p>
<p>Corrected in <code>RIFLEX</code> 4.8.0.</p>
<h3>Pipe-in-pipe sheltered closed option</h3>
<p>Several errors regarding the sheltered closed option for pipe-in-pipe contact have been corrected. This could cause errors in the calculation of the inner fluid load effects. Error in version 4.6 only.</p>
<p>Corrected in <code>RIFLEX</code> 4.8.0.</p>
<h3>Time domain VIV</h3>
<p>The input value of the seed for the phase angles of the different frequency components from <code>VIVANA</code> has previously not been used. This has been corrected in <code>DYNMOD</code>.</p>
<p>Corrected in <code>RIFLEX</code> 4.8.0.</p>
<h2>RIFLEX 4.8 New / improved functionality</h2>
<h3>Second order wave kinematics for short-crested seas</h3>
<p>Second order wave kinematics may now be used together with short-crested seas (irregular waves with directional spreading).</p>
<h3>Upwind tower shadow modifications</h3>
<p>The tower shadow influence for upwind wind turbines is modified such that the drag coefficient and Bak correction factor may be taken into account. If these inputs are zero (default), the same tower shadow as before is used.</p>
<h3>Downwind wind turbine modelling</h3>
<p>Downwind wind turbine modelling is enabled, including correct default blade orientation and control system actions. A cosine-squared type tower shadow for downwind wind turbines is implemented.</p>
<h3>Morison-type aerodynamic drag forces</h3>
<p>Morison-type aerodynamic drag forces may be applied to the dry part of CRS0, CRS1, CRS2, CRS3, and CRS4 elements.</p>
<h3>IEC turbulent wind for Linux</h3>
<p>Wind files generated by WASP Engineering's IEC Turbulence Simulator can now also be read by RIFLEX built for Linux.</p>
<h3>New Linux release</h3>
<p>The new Linux release of <code>SIMO</code>, <code>RIFLEX</code> and <code>VIVANA</code> is 64-bit and solves several issues. Unfortunately, this means that 32-bit Linux operating systems are no longer supported.</p>
<ul>
<li>Supports more than the 32-bit imposed limit of 2 GB of RAM</li>
<li>No need to install 32-bit support libraries separately</li>
<li>No special considerations are needed for writing output files larger than 2 GB</li>
<li>The necessary runtime libraries are included in the installation package and no special consideration is needed for installation; the package is now fully relocatable</li>
<li>Added man page for the <code>vrr</code> runner script</li>
</ul>
<p>The package has been tested on the following Linux distributions:</p>
<ul>
<li>CentOS 7</li>
<li>Ubuntu 14.04 LTS</li>
<li>Linux Mint 17</li>
</ul>
<h2>RIFLEX 4.8 Removed functionality</h2>
<p>No previously available functionality have been removed in version 4.8.</p>
<h2>RIFLEX 4.8 Deprecated functionality</h2>
<p>No functionality is deprecated in the 4.8 version.</p>
<h1>RIFLEX 4.6</h1>
<h2>RIFLEX 4.6 Input changes</h2>
<p>Most 4.4 input files may be used unchanged.</p>
<p><code>INPMOD</code> now checks that the specified pipe-in-pipe identifiers are unique. The maximum length of a pipe-in-pipe ID has been increased from 8 to 16.</p>
<p>Input for new functionality is described in the User Manual.</p>
<p>Alphanumeric identifiers may now be used for main riser lines (MRL). Old inputs with numbered main riser lines may still be used.</p>
<p>The alphanumeric identifiers for pipe-in-pipe specifications must mow be unique. Note that they have a maximum length of eight characters.</p>
<p>Beam cross-sections with linear stiffness must now have positive, nonzero axial, bending and torsional stiffness. Specifying zero stiffness will result in an error in <code>INPMOD</code>.</p>
<h2>RIFLEX 4.6 Corrected errors</h2>
<h3>Pipe-in-pipe corrections</h3>
<p>The friction stiffness along the pipe surface has been corrected. This is expected to improve convergence in dynamic analysis.</p>
<p>The unit of STIFFR, spring stiffness associated with the static friction coefficient, was incorrect in both the User Manual and the echo on the <code>_inpmod.res</code> file. The correct unit is <code>F / L^2</code>.</p>
<p>Corrected in <code>RIFLEX</code> 4.6.2.</p>
<h3>Main riser line as master in pipe-in-pipe pairs</h3>
<p>An error that prevented the master pipe of a pipe-in-pipe pair to be a main riser line has been corrected. The error resulted in an controlled error termination before start of time integration when running dynamic analysis.</p>
<p>Corrected in <code>RIFLEX</code> 4.6.2.</p>
<h3>Multiple main riser lines (MRL)</h3>
<p>Corrected an error that prevented more than one main riser line being defined. Error since 4.0.</p>
<h3>Waves from multiple directions in coupled simulation</h3>
<p>Corrected an error in wave loading on RIFLEX elements from numerically defined (tabulated) spectra with multiple directions in coupled <code>SIMO</code>-<code>RIFLEX</code> simulations.</p>
<h3>Tubular contact</h3>
<p>Corrected errors in calculation of tubular contact modelled using <code>ELASTIC CONTACT SURFACE</code> and <code>NEW COMPONENT TUBULAR CONTACT</code>. Changes in results are expected.</p>
<p>No chnage for pipe-in-pipe contact.</p>
<h2>RIFLEX 4.6 New / improved functionality</h2>
<h3>Pipe-in-pipe improvements</h3>
<p>In both static and dynamic analysis, the stiffness terms along the pipe surface have been modified to improve convergence. The applied forces were not changed, so no significant change is expected in results with good convergence. Included in <code>RIFLEX</code> 4.6.2.</p>
<h3>Fluid loading on the inner pipe in a pipe in pipe pair</h3>
<p>An option has been added to the pipe in pipe specification to allow the user to specify whether the inner pipe is exposed to the external environmental loads or is shielded by the outer pipe.</p>
<p>The default is that the inner pipe is exposed to the external environmental loads; i.e. buoyancy based on the water density given for the selected environment and wave loading based on the waves and current. Old input files will therefore give unchanged behaviour.</p>
<h3>Pipe in pipe contact with reference to main riser line</h3>
<p>The pipes in a pipe-in-pipe pair may now be defined by main riser lines (MRL), lines or a combination of MRL and line.</p>
<h3>Improved interface for external wind turbine controller</h3>
<p>Wind velocity at hub height in global coordinates is added to available measurements for the external wind turbine controller. Existing external wind turbine controllers can be used unchanged.</p>
<h3>Improved dynamic stall initialization options</h3>
<p>The internal initialization of dynamic stall parameters may fail for non-typical airfoils. The search methods have been made more robust, and error messages have been improved. The user is also given the option to specify the dynamic stall initialization parameters.</p>
<h3>Identifiers in modeling</h3>
<p>Alphanumeric identifiers may now be used for main riser lines (MRL). Old inputs with numbered main riser lines may still be used.</p>
<h2>RIFLEX 4.6 Removed functionality</h2>
<p>No <code>RIFLEX</code> 4.4 functionality has been removed in <code>RIFLEX</code> 4.6.</p>
<h2>RIFLEX 4.6 Deprecated functionality</h2>
<p>The following functionality was also deprecated in <code>RIFLEX</code>4.2 and 4.4.</p>
<h3>Kill and choke lines (INPMOD)</h3>
<p>The simplified modelling of kill and choke lines attached to a tensioned riser by including them in a riser elements will be removed in the next version of RIFLEX. In RIFLEX 4.0 this functionality is available through the variable NAKC in ARBITRARY SYSTEM AR and then giving the data in B6.9.</p>
<h3>LF-motion response spectrum (DYNMOD)</h3>
<p>Generation of low frequency motions from spectra will be removed in the next version of RIFLEX. In RIFLEX 4.0 this functionality is available by setting CHLFM = GEN in IRREGULAR RESPONSE ANALYSIS and then giving the date groups LFMOTION SPECTRUM.</p>
<h3>Import of internal flow data from file (DYNMOD)</h3>
<p>The restricted functionality to import internal flow data from file will be removed in the next version of RIFLEX. In RIFLEX 4.4 this functionality is available for some users by setting INDINT=2 in data group E1.4 and then giving the data group IMPORT FLOW DATA.</p>
<h1>RIFLEX 4.4</h1>
<h2>RIFLEX 4.4 Input changes</h2>
<p>4.2 input files may be used unchanged, except for the case of regular analysis with multiple vessels and no wave selected, see Specified regular motions for multiple vessels.</p>
<p>Input for new functionality is described in the User Manual.</p>
<h3>Specified regular motions for multiple vessels</h3>
<p>The motion period must now be the same for all vessels.</p>
<h2>RIFLEX 4.4 Corrected errors</h2>
<h3>Specified regular motions for multiple vessels</h3>
<p>If no regular wave is specified, regular motions must be given in a regular analysis. If the system contained multiple vessels, the motions were incorrect for vessels 2 - <code>NVES</code>. This is now corrected. Note that the motion period must be the same for all vessels.</p>
<p>Corrected in <code>RIFLEX</code> 4.4.0.</p>
<h3>Fatigue damage for stresses outside the S-N curve range (OUTMOD)</h3>
<p>The <code>OUTMOD</code> data group TIMEDOMAIN FATIGUE DAMAGE has previously reported zero fatigue damage if the stresses exceeded the stress level corresponding to failure after a single cycle. This is now handled as an error. The most probable cause of this occurring is that the units of the S-N curve and the calculated stresses are not compatible.</p>
<p>Also corrected in RIFLEX 4.4.2.</p>
<h3>Corrected radius of gyration for CRS0 cross section</h3>
<p>The expression for radius of gyration that is used for the moment of inertia around the local X-axis has been corrected. This concerns cross section type CRS0 and also cross sections created based on a stress joint specification. Further, the coating contribution to moment of inertia was not previously included. The radius of gyration has been calculated to be 71% of the correct value without coating. For cross sections with coating, the difference is larger. For normal riser analysis, the error had minor or insignificant influence on the results. However, this is system-dependent. The error has been corrected and the updated expression also accounts for the coating contribution to the moment of inertia.</p>
<p>Corrected in RIFLEX 4.4.1.</p>
<h3>Corrected an error in the storage of animation for DeepC</h3>
<p>Corrected an error in the storage of dynamic analysis animation for DeepC. Error in 4.4.0 only.</p>
<p>Corrected in RIFLEX 4.4.1.</p>
<h3>Corrected error in specification of detailed wave kinematics</h3>
<p>Corrected an error in the specification of explicitly selected nodes for undisturbed wave kinematics. This may be done by specifying <code>DIFF</code> combined with <code>IVES = 0</code> in the <code>DYNMOD</code> data group IRREgular WAVE PROCedure. Error in 4.4.0 only, where an error exit was caused.</p>
<p>Corrected in RIFLEX 4.4.1.</p>
<h3>Corrected error with multiple support forces in OUTMOD</h3>
<p>An error caused <code>OUTMOD</code> to fail if the <code>OUTMOD</code> data group SUPPf TIME SERIes was given more than once. The error has been corrected.</p>
<p>Corrected in RIFLEX 4.4.2.</p>
<h2>RIFLEX 4.4 New / improved functionality</h2>
<h3>Improved wind turbine results</h3>
<p>Blade pitch results are now presented for simulations which include an external control system.</p>
<p>Improved in RIFLEX 4.4.1.</p>
<h3>Friction stiffness for internal friction moment</h3>
<p>The factor adjusting initial stiffness for the friction moment functionality has been added as user input. See <a class="el" href="a00010.html#inpmod_c_crs1_stiffness_properties">Stiffness properties classification</a> in INPMOD.</p>
<h3>Pre-curved line types</h3>
<p>The line type definition may now include specification of a curved stress-free configuration. See <a class="el" href="a00010.html#inpmod_b_line_transverse">Transverse displacement specification</a> in INPMOD.</p>
<h3>TurbSim 3D wind files</h3>
<p>TurbSim 3D wind files may now be read by RIFLEX. See <a class="el" href="a00010.html#inpmod_d_wind_specification_turbsim">Fluctuating 3-component wind field read from TurbSim file</a>.</p>
<h3>Airfoil forces</h3>
<p>Static airfoil forces may now be applied to CRS2 cross sections that are not blades in a wind turbine.</p>
<h3>Read wave kinematics from file</h3>
<p>A new option to read in and use wave kinematics from file has been added, see <a class="el" href="a00014.html#dynmod_d_irregular_waves_procedure_additional">Additional detailed specification of wave kinematics points (optional)</a>.</p>
<h3>Improved stability for coupled analysis with the old SIMO DP-system</h3>
<p>The SIMO DP system is now called only at every SIMO time increment (Sampling time interval). Previously, the old SIMO DP system was called at each time step (Time integration step) while the new DP system was correctly called at the sampling time interval.</p>
<p>The correction will possibly increase the computational robustness when the old DP-system (marked deprecated) is applied.</p>
<h3>Improved wind turbine results</h3>
<p>Improved selection and presentation of results for wind turbines. The results are now presented for all blades in the non-rotating shaft system.</p>
<h3>Minor improvements</h3>
<p>Blank space is added around some numbers printed on the .res files. This has been done to increase readability and to facilitate comparison of numerical results.</p>
<p>Minor improvements in error handling and layout.</p>
<h2>RIFLEX 4.4 Removed functionality</h2>
<p>No <code>RIFLEX</code> 4.2 functionality has been removed in <code>RIFLEX</code> 4.4.</p>
<h2>RIFLEX 4.4 Miscellaneous</h2>
<h3>Run time environment</h3>
<p>Windows versions 4.4 and higher are 64 bit executables and therefore require different Fortran and Java DLLs than earlier version. The necessary DLLs are included in the download package. The preformance is improved.</p>
<h1>RIFLEX 4.2</h1>
<h2>RIFLEX 4.2 Input changes</h2>
<p>4.0 input files may be used unchanged.</p>
<p>Input for new functionality is described in the User Manual.</p>
<h3>Changed default values for irregular analysis (DYNMOD)</h3>
<p>The default sampling step of the pre-generated time series, <code>DTGEN</code>, is decreased to 0.5 s. The default length of the pre-generated time series, <code>TIMGEN</code>, is increased to 4.6 hours. The default simulation length for irregular analysis, <code>TIME</code>, is increased to 3.06 hours.</p>
<h3>Changed default value for subdivision of time step (DYNMOD)</h3>
<p>The default value of the <code>DYNMOD</code> parameter <code>IVARST</code>, Code for automatic subdivision of time step, is changed from 2 to 0. If a simulation fails to run, check if it previously used subdivision and if the default value of <code>IVARST</code> was used.</p>
<h2>RIFLEX 4.2 Corrected errors</h2>
<p>The following errors have been corrected in RIFLEX 4.2 versions.</p>
<h3>Pipe-in-Pipe Contact Search Bug</h3>
<p>Fixed a long-standing bug in pipe-in-pipe contact search that caused the search to fail in the vicinity of flex joints and ball joints. Users with pipe in pipe models that contains flex joints and/or ball joints should consider rerunning the simulations.</p>
<p>Corrected in <code>RIFLEX</code> 4.2.1.</p>
<h3>Coupled analysis</h3>
<p>Error in hydrodynamic drag forces on slender elements</p>
<p>If depth dependent current was applied and wind also was specified in the environmental condition, the computed drag forces on slender elements were in error. This was due to an incorrect z-position being used to interpolate the shear profile. The error has been present since version 4.2.0. The consequence is incorrect drag forces on the slender elements. <b>Analysis done with this combination by version 4.2.0 should be re-run!</b> The error has been corrected.</p>
<p>For other SIMO bugfixes, please refer to the SIMO Release Notes.</p>
<p>Corrected in <code>RIFLEX</code> 4.2.1.</p>
<h3>Instability in prescribed displacements when vessel motions are imported from file Coupled analysis</h3>
<p>Simulations occasionally failed when vessel motions were imported from external file. The algorithm for prescribed (vessel) rotation induced translation for nodes attached to the vessel has been modified to have improved numerical robustness. No or insignificant changes to results.</p>
<p>Corrected in <code>RIFLEX</code> 4.2.0.</p>
<h3>Exported vessel velocity and accelerations in coupled analyses (DYNMOD)</h3>
<p>An error in the exported vessel velocity and accelerations for coupled analysis with both <code>SIMO</code> bodies and <code>RIFLEX</code> support vessel was corrected. No error found in analysis results. No error for standalone <code>RIFLEX</code> or for coupled analyses with only SIMO bodies,</p>
<p>Corrected in <code>RIFLEX</code> 4.2.0.</p>
<h3>Winch modelling</h3>
<p>A long-standing error in the winch formulation has been detected and corrected. Analysis based on previous versions of RIFLEX should be re-run.</p>
<p>Corrected in <code>RIFLEX</code> 4.2.0.</p>
<h3>Linear drag coefficients not applied in linearized time domain analysis</h3>
<p>Linear drag coefficients have not been applied in linearized time domain analysis. Linear drag coefficients are seldom used, so the consequences are assumed to be minimal. The error has been corrected.</p>
<p>Corrected in <code>RIFLEX</code> 4.2.0.</p>
<h3>Regular wave analysis with prescribed vessel motions</h3>
<p>Error for combined regular wave loading with specified harmonic displacements (<code>IMOTD</code> = 2). The motions after the first wave period were incorrect if a different period was specified for the motions than the wave period (and the wave period was mot a multiple of the motion period). . Error since <code>RIFLEX</code> 3.6.7.</p>
<p>No error if motions are calculated from vessel transfer functions (IMOTD = 1).</p>
<p>Corrected in <code>RIFLEX</code> 4.2.0.</p>
<h2>RIFLEX 4.2 New functionality</h2>
<h3>Geotechnical model</h3>
<p>New modelling features have been added to model transverse contact between a vertical pipe and the soil. The new <code>INPMOD</code> data group <code>GEO SPRING SPECIFICATIONS</code> is used to give the input to the model.</p>
<h3>Scaling of Froude-Kriloff term in Morison's equation</h3>
<p>Extend the generalized Morison's equation by optionally scaling the term associated with the Froude-Kriloff load. This to enhance the area of application of Morison's equation, i.e. allow for larger structural diameter versus wave length. Note that only loads normal to the principal axis of an element are scaled. Additional, optional input is added for cross section typed <code>CRS0</code>, <code>CRS1</code>, <code>CRS2</code>, <code>CRS3</code> and <code>CRS4</code>.</p>
<h3>2nd order wave kinematics</h3>
<p>2nd order wave kinematics for long-crested waves have been added to <code>RIFLEX</code>. 2nd order wave kinematics are obtained by setting the <code>DYNMOD</code> input parameter <code>ICOSIM</code> to <code>5</code>.</p>
<h3>Store wave kinematics on additional file</h3>
<p>Generated wave kinematics may now be stored on additional binary file from <code>DYNMOD</code>. Data group <code>IRREGULAR KINEMATICS STORAGE</code> to store wave kinematics on an additional file <code>&lt;prefix&gt;_wavkin.bin</code>. The contents are described in the text file <code>key_&lt;prefix&gt;_wavkin.txt</code>.</p>
<h3>Wind turbine control system and results</h3>
<p>The specified control interval for internal wind turbine control system has been activated. In addition the value of the integrator gain are kept within saturation limit. The reason for this implementation is to improve the behaviour of the internal control system.</p>
<p>Wind turbine results may now be stored on additional text file or binary file <code>&lt;prefix&gt;_witurb.asc</code> or <code>&lt;prefix&gt;_witurb.bin</code>. The contents are described in the text file <code>key_&lt;prefix&gt;_witurb.txt</code>. There is no special input for storing the wind turbine results. The results storage is based on storage specification for element forces, i.e. time interval for sampling and file format.</p>
<h3>Detailed kinematic specification</h3>
<p>Allow NODSTP = 0 i.e. no kinematics for this line in the detailed kinematic specification.</p>
<p>Available from <code>RIFLEX</code> 4.2.1.</p>
<h2>RIFLEX 4.2 Removed functionality</h2>
<p>No <code>RIFLEX</code> 4.0 functionality has been removed in <code>RIFLEX</code> 4.2.</p>
<h2>RIFLEX 4.2 Miscellaneous</h2>
<h3>Java and HLALIB.jar</h3>
<p>The included Java folder and the <code>HLALIB.jar</code> file have been updated in the Windows installation <code>.zip</code> file. </p>
</div></div><!-- contents -->
	</body>
</html>