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

BeamDyn initialization with non-zero initial azimuth produces strange results #26

Closed
bjonkman opened this issue May 10, 2017 · 5 comments

Comments

@bjonkman
Copy link
Contributor

See attached file for description of the problem.

BeamDyn_InitializationBug.pdf

@bjonkman
Copy link
Contributor Author

bjonkman commented Aug 1, 2017

@michaelasprague - Has there been any progress on this issue?

@michaelasprague michaelasprague assigned ghost Aug 1, 2017
@michaelasprague
Copy link
Contributor

@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.

@andrew-platt
Copy link
Collaborator

andrew-platt commented Aug 10, 2017

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.

@michaelasprague
Copy link
Contributor

@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!

bjonkman added a commit to bjonkman/openfast that referenced this issue Aug 14, 2017
…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
@rafmudaf rafmudaf assigned rafmudaf and unassigned ghost Nov 9, 2017
@rafmudaf
Copy link
Collaborator

This issue was fixed in pull request #114

psakievich pushed a commit to psakievich/openfast that referenced this issue Oct 26, 2023
Check if restart frequency is > 0 to avoid dividing by 0
andrew-platt added a commit that referenced this issue Nov 8, 2024
repository name must be lowercase
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

4 participants