Error while running the model with BeamDyn enabled

[JAMMIASHOK]

Hi,
When running with BeamDyn - I am getting the following error

Is there any wrong with the mappings?

[JAMMIASHOK]

Found out the issue.
The Elastodyn blade has 30 stations where as Beamdyn blade has only 19 stations. That's the incompatibility

Can you please update the BeamDyn blade input file with 30 stations ?

[mayankchetan]

Hi @JAMMIASHOK,

Thank you for pointing this out! Having different number of nodes between ED and BD should not be a problem.

It looks like there is a discrepancy between the AeroDyn and BeamDyn reference definition resulting in the ~0.5m difference between the AD and BD nodes. See below:

AD: https://github.com/IEAWindSystems/IEA-10.0-198-RWT/blob/master/openfast/IEA-10.0-198-RWT_AeroDyn15_blade.dat#L36

BD: https://github.com/IEAWindSystems/IEA-10.0-198-RWT/blob/master/openfast/IEA-10.0-198-RWT_BeamDyn.dat#L43

I'll consult with @ptrbortolotti, and push a fix soon.

Thanks,
Mayank

[ptrbortolotti]

hi @JAMMIASHOK, thanks for your patience. I realized that I had a fix in a branch that I never merged into main. it should be working now

[JAMMIASHOK]

Hi @ptrbortolotti
Thanks for the fix. Now the mesh mismatch error goes away, but the solution does not converge when using BeamDyn.
I tried 0.001, 0.0025, 0.0001 time steps - but OpenFAST aborts.
I am using ROSCO 2.9.4 with OpenFAST 4.0.0.
Can you please check if you are able to achieve convergence using BeamDyn ?

[ptrbortolotti]

hi @JAMMIASHOK , I'm sorry about the continuous issues here. I am trying to find the time to debug what's going on here, I will share updates as I get them

[ptrbortolotti]

hi again, I've finally found the time to look into the model, but I'm puzzled. it seems to be running on my end. when does the solution abort? is the controller maybe doing something weird? is the initial condition good enough? what about the inflow?