I am using FAST v8.15 with AeroDyn v15.
I have questions about the transfer of the motions from the mesh of ElastoDyn to the mesh used by AeroDyn.
The angular velocities of the blade elements are not computed in ElastoDyn, because they are not used either in ElastoDyn nor AeroDyn. However, they are used when transferring the translation velocities in the routine Transfer_Motions_Line2_to_Point in the module ModMesh_Mapping. So not taking them into account would lead to a small error on the results ?
Therefore I uncommented the computation of AngVelHM done in CalculateAngularPosVelPAcc in the module ElastoDyn, and transferred the array to BladeLn2Mesh%RotationVel at the end of ED_CalcOutput. Do you agree with this approach ? Is there a reason for not computing those angular velocities ?
(note that I also need the angular velocities for the coupling of FAST with my own aerodynamic module)
In the routine Transfer_Motions_Line2_to_Point, the computation of the direction cosine matrix has been replaced with a new version, apparently intended to save one matrix multiplication, and I guess, improve the performances. However, with this version, I get small oscillations in the orientation arrays every time the azimuth angle is close to 180°, which can also be observed on other variables such as the torque, even if the amplitude is very small. Have you ever observed such an issue ? Does this version of the DCM computation lead to significant improvement of the performances of the code ?