Skip to content

Large number of Craig Bampton modes for flexible floating systems #3085

@RBergua

Description

@RBergua

I'm simulating one floating offshore wind turbine as follows:
Image

The floating plaform and tower (not shown in the above image) are modeled in SubDyn. For this numerical model, I use the new rigid-body reference point available in SubDyn.

The system uses horizontal pretensioned lines included in MAP++.

When considering a wave-only condition with a regular wave applied along the x-direction, I can observe that the loads within the platform are quite sensitive to the number of Craig Bampton modes included in SubDyn. This seems to be specially true for the axial and vertical forces. See the loads at the upwind and downwind pontoons below.

Edit: the wave spectrum has been low-pass filtered with a cut-off frequency = 0.5 Hz. Time step used for the solver: Nmodes = 8 (dt = 0.01 s), Nmodes = 15 (dt = 0.01 s), Nmodes = 50 (dt = 0.01 s), Nmodes = 75 (dt = 0.0025 s), Nmodes = 100 (dt = 0.0025 s), and Nmodes = 125 (dt = 0.001 s).
Image
Image

I understand that the static-improvement method treats higher-frequency modes quasi-statically. As can be observed above, in this system a large number of modes (~100) has to be included to have close to a converged solution. For reference, the total number of DOFs in the structure is 180.

For these simulations I'm using the OpenFAST tight-coupling (current OpenFAST dev-tc). When accounting for a strip theory approach for the hydro, I can solve 2500 seconds of simulation in 17 h (in a powerful computer) using 100 modes in SubDyn and a time step of 0.001 s for the solver. However, for a hydro model that uses potential flow, the same simulation increases the computational time to 28 days. I understand that this very large computational time when using potential flow bodies is related to this issue: #2936 (comment).

I'm wondering if there is any workaround or solution for this.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions