Skip to content

[BugFix] Nacelle position set inconsistently by glue code and AeroDyn driver#1009

Merged
andrew-platt merged 7 commits intoOpenFAST:devfrom
hkross:bug/AD_Driver_NacelleRef
Mar 1, 2022
Merged

[BugFix] Nacelle position set inconsistently by glue code and AeroDyn driver#1009
andrew-platt merged 7 commits intoOpenFAST:devfrom
hkross:bug/AD_Driver_NacelleRef

Conversation

@hkross
Copy link
Contributor

@hkross hkross commented Feb 18, 2022

This pull request is ready to be merged.

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

Related issue, if one exists
This pull request will close issue #1005.

Impacted areas of the software
AeroDyn driver

Test results
All tests have been updated and pass. A corresponding pull request (#51) has been added to the r-test repository.

Documentation
Relevant documentation has been updated.

@andrew-platt
Copy link
Collaborator

Thanks for fixing this!

I noticed that only 4 of the AeroDyn driver test input files were changed. Are the other cases not affected?

@andrew-platt andrew-platt self-requested a review March 1, 2022 19:01
@andrew-platt andrew-platt self-assigned this Mar 1, 2022
@hkross
Copy link
Contributor Author

hkross commented Mar 1, 2022

Thanks for fixing this!

I noticed that only 4 of the AeroDyn driver test input files were changed. Are the other cases not affected?

Yes, I changed only the affected tests. Tests that use the BasicHAWTFormat = True setup needed the additional Twr2Shft parameter to define the location of the tower top. Tests that use the BasicHAWTFormat = False already have the nacelle origin defined explicitly at the tower top.

Copy link
Collaborator

@andrew-platt andrew-platt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me! Thanks!

@andrew-platt andrew-platt merged commit 8b1b6b0 into OpenFAST:dev Mar 1, 2022
@hkross hkross deleted the bug/AD_Driver_NacelleRef branch March 1, 2022 19:45
@rafmudaf rafmudaf mentioned this pull request Mar 2, 2022
11 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments