Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Numerical Instability in SubDyn Module with Retained DOFs for Monopile Offshore Wind Turbine #2512

Closed
ccccsdcc opened this issue Nov 13, 2024 · 4 comments

Comments

@ccccsdcc
Copy link

Hello everyone,

I'm running a numerical simulation of a monopile-based offshore wind turbine in OpenFAST. In the SubDyn module, I’ve configured the model to retain all degrees of freedom (DOFs) for the foundation by setting CBMod to False. However, I’m encountering numerical instability at the start of the simulation. The only way I’ve found to achieve stability is to significantly reduce the time step, which unfortunately slows down the simulation considerably.

Could anyone help me understand why retaining all DOFs for the foundation in SubDyn leads to this initial instability? Additionally, are there best practices or alternative approaches to stabilize the simulation without having to use such a small time step?

Thank you for your assistance!

page1

@jjonkman
Copy link
Collaborator

Dear @ccccsdcc,

If you set CBMod to FALSE in SubDyn, the full set of SubDyn finite-element degrees of freedom (DOFs) will be retained, including many of high frequency. To avoid numerical instability of the model, these high frequencies will need to be resolved through the use of small time steps (with the typical rule of thumb, DT < 1 / ( 10*MAX(f_n) ), where MAX(f_n) is the highest natural frequency in the OpenFAST model) by the time-integrator of SubDyn and the OpenFAST glue code.

This issue will be addressed in the upcoming release of OpenFAST v5 that introduces a tight coupling algorithm around the structural modules of OpenFAST (including BeamDyn, ElastoDyn, and SubDyn) based on the generalized alpha method (see PR # #2439 for more information), which will enable computational efficiency by allowing the use of much larger time steps than the rule of thumb I stated above.

That said, there is really no need to retain all of the finite-element DOFs of the SubDyn model. SubDyn is purposely designed to reduce the need to retain all finite-element DOFs through the use of a Craig-Bampton reduction (CBMod = TRUE) and static-improvement method (SttcSolve = TRUE). We typically recommend only retaining Craig-Bampton modes in SubDyn across a frequency range that could get excited by the wind, waves, and rotor rotation (typically up to a few Hz), and treating all higher-frequency modes through the static-improvement method, which will enable the use of much more reasonable time steps.

Best regards,

@ccccsdcc
Copy link
Author

Dear @jjonkman ,

Thank you for the detailed explanation! I understand now the challenges with retaining all finite-element DOFs in SubDyn.

Could you please clarify the theoretical basis for the coupling method currently used in the latest version of OpenFAST to integrate structural modules like BeamDyn, ElastoDyn, and SubDyn? Specifically, I’m interested in understanding the theory or principles behind the time integration and stability management approach in the current version, before the generalized alpha method is introduced in v5.

Thank you again for your insights!

Best regards,

@jjonkman
Copy link
Collaborator

Dear @ccccsdcc,

There are few documents under "Modularization Framework" and "Glue Code and Mesh Mapping" on readthedocs that describe how the current coupling scheme in the OpenFAST glue code works: https://openfast.readthedocs.io/en/main/source/user/index.html#modularization-framework and https://openfast.readthedocs.io/en/main/source/user/index.html#glue-code-and-mesh-mapping. A high-level description is also provided in various OpenFAST overview presentations, such as what was presented at our recent OpenFAST workshop held in conjunction with NAWEA / WindTech: https://openfast.readthedocs.io/en/main/source/user/index.html#glue-code-and-mesh-mapping.

As part of the development of tight coupling, we've also drafted a journal article that we intend to submit in conjunction with the release of OpenFAST v5 (which is due out soon (in the next month or two)) that explains the coupling procedure of the original OpenFAST glue code as well as its extension to tight coupling.

Best regards,

@ccccsdcc
Copy link
Author

Dear @jjonkman ,

Thank you so much for your detailed response and for sharing the references on the coupling scheme in the OpenFAST glue code.

Best regards,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants