Dynamic mooring simulation with Code_Aster with application to a floating wind turbine

Raffaello Antonutti*, Christophe Peyrard, Atilla Incecik, David M. Ingram, Lars Johanning

*Corresponding author for this work

Research output: Contribution to journalArticlepeer-review

Abstract

The design of reliable station-keeping systems for permanent floating structures such as offshore renewable energy devices is vital to their lifelong integrity. In highly dynamic and/or deep-water applications, including hydrodynamics and structural dynamics in the mooring analysis is paramount for the accurate prediction of the loading on the lines and hence their dimensioning. This article presents a new workflow based on EDF R&D's open-source, finite-element analysis tool Code_Aster, enabling the dynamic analysis of catenary mooring systems, with application to a floating wind turbine concept. The University of Maine DeepCwind-OC4 basin test campaign is used for validation, showing that Code_Aster can satisfactorily predict the fairlead tensions in both regular and irregular waves. In the latter case, all of the three main spectral components of tension observed in the experiments are found numerically. Also, the dynamic line tension is systematically compared with that provided by the classic quasi-static approach, thereby confirming its limitations. Robust dynamic simulation of catenary moorings is shown to be possible using this generalist finite-element software, provided that the inputs be organised consistently with the physics of offshore hydromechanics.

Original languageEnglish
Pages (from-to)366-377
Number of pages12
JournalOcean Engineering
DOIs
Publication statusPublished - 1 Mar 2018

ASJC Scopus subject areas

  • Environmental Engineering
  • Ocean Engineering

Keywords

  • Code_Aster
  • Dynamics
  • Finite-element
  • Floating wind
  • Moorings
  • OC4

Fingerprint

Dive into the research topics of 'Dynamic mooring simulation with Code_Aster with application to a floating wind turbine'. Together they form a unique fingerprint.

Cite this