You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Bug description
Pull request #982 changed the way the AeroDyn nacelle point mesh position was set (from
position = InitInp%HubPosition
toposition = 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.
The text was updated successfully, but these errors were encountered: