-
Notifications
You must be signed in to change notification settings - Fork 457
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
Possible Bug in BeamDyn -- Root Pitching Moment Doesn't Match Pitching Moment from First Node? #248
Comments
@rafmudaf -- Yes, I agree, which is why I was surprised Ryan Walker raised the issue again (you'll notice in the forum that my first question to Ryan was which OpenFAST version was being used). |
It was also mentioned that he started with |
Hi @jjonkman @rafmudaf ,
Best, |
The issues addressed in the the previous post were resolved after I simulated with compiled version commit ed9daba-dirty obtained from (git clone https://github.com/bjonkman/openfast.git --branch b/BD-loads) However, while calculating blade spanwise DELs (using NREL 5MW model), there is bump towards the end of the tip. We see a similar bump from our input files as well. It would be really helpful to know if there is a way to validate the spanwise loads distribution towards the tip. Note: the DEL calculations are done using only 1 sim at 12 mps windspeed. However, the bump towards the tip is consistent with our input files as well. Thank you. Best, |
In a topic on the forum related to BeamDyn, Ryan Walker has raised concerns that the pitching moment (Mz) at the root doesn't match the pitching moment at the first node, when the first node is located at the root. I have not confirmed this result myself. Perhaps the issue has been fixed in the yet-to-be merged pull request #163?
Ryan has also reported that Figures 6.7, 6.8, and 6.9 do not show up in the readthedocs user documentation for BeamDyn.
See the following topic on the forum for more information: https://wind.nrel.gov/forum/wind/viewtopic.php?f=4&t=2215.
The text was updated successfully, but these errors were encountered: