-
Notifications
You must be signed in to change notification settings - Fork 458
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
BeamDyn initialization with non-zero initial azimuth produces strange results #26
Comments
@michaelasprague - Has there been any progress on this issue? |
@bjonkman , sorry, no. @rafaelmudafort is taking lead on this now; plan is to address this by exposing the problem in the testing harness and to then pursue the fix. |
In the CalcIC routine, the calculation of the translational velocity is incorrectly referenced. The root node position needs to be subtracted otherwise the distance used in the cross product is relative to the original root position, not the rotated root position. We (Envision) have a fix for this that we will give you. BTW: the fix we have for this appears to help get a larger timestep. |
@andrew-platt, it would be great if this could be submitted as a pull request -- please let us know if there's another mechanism you'd prefer. Thanks! |
…al azimuth The initial translation velocity calculation didn't remove the location of the root node when taking the cross product with the rotational velocity. This fixes OpenFAST#26
This issue was fixed in pull request #114 |
Check if restart frequency is > 0 to avoid dividing by 0
repository name must be lowercase
See attached file for description of the problem.
BeamDyn_InitializationBug.pdf
The text was updated successfully, but these errors were encountered: