Resolve BeamDyn initial strain for rotated blade #1796
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request is ready to be merged. Copy of PR #1663 applied to the
rc-3.5.1
branch.Feature or improvement description
In the BeamDyn driver, and likely in the glue-code, if the blade was initially rotated then an initial strain was introduced which produced forces when no loads or gravity had been applied. The cause was traced to the calculation of R0 (initial rotation) at the quadrature points which was interpolated via the shape functions from the element nodal rotations. The shape function interpolation is not exact and introduced strains on the order of 1e-7, but with the large stiffness of the blade, forces of 6200 N could be produced at the root for the IEA 15MW blade. This was resolved by directly calculating the quadrature point initial rotations in uu0(4:6) via interpolated tangent and twist, which are well behaved. This was only a problem for non-straight blades such as the IEA 15MW.
This commit also fixes a bug where the parameter UsePitchAct wasn't initialized from the input file until after it was used in SetOutParam. The initialization has been moved to SetParameters.
Related issue, if one exists
This changes resolves Issue #366 when QuasiStaticInit is set to False.
Impacted areas of the software
BeamDyn
Test results, if applicable
The BeamDyn unit test test_BD_QuadraturePointData.F90 was updated to account for the slight difference in R0, E1, Stiffness that resulted from this change.