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

Bug report: Nacelle position set inconsistently by glue code and AeroDyn driver #1005

Closed
hkross opened this issue Feb 17, 2022 · 3 comments
Closed

Comments

@hkross
Copy link
Contributor

hkross commented Feb 17, 2022

Bug description
Pull request #982 changed the way the AeroDyn nacelle point mesh position was set (from position = InitInp%HubPosition to position = InitInp%NacellePosition). The nacelle point mesh position is now defined by the tower top (i.e., yaw bearing) location when AeroDyn is driven by OpenFAST. The AeroDyn driver does not output the nacelle position, so it is set to (0,0,0) when using the driver. This can be fixed by outputting the nacelle position from the AeroDyn driver (see this commit). However, the driver defines the nacelle position as (0,0,HubHt+overhang*sin(shftTilt)), which is not equivalent to the definition that is passed from the glue code. This causes an inconsistent definition of the nacelle mesh position when using the glue code vs driver. This is a problem for the buoyancy calculations (PR #957), since the center of buoyancy of the nacelle is defined by the user relative to the tower top position.

Potential solution
A possible solution is to change the way the nacelle position is set by the AeroDyn driver, but I believe this would require an additional driver input to define the distance between the HubHt and TwrHt.

@andrew-platt
Copy link
Collaborator

Good catch! I think the best solution is to add the driver input as suggested and pass that through to AD as the glue-code does.

@ebranlard
Copy link
Contributor

(sorry I forgot to answer the comment on the other thread). I agree, I think we would need another input in the AeroDyn driver indeed.

@hkross
Copy link
Contributor Author

hkross commented Feb 17, 2022

Sounds good, thanks! I will make the needed changes and submit a pull request for this.

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

3 participants