Discussed in #3334
Originally posted by gxyanwork-byte May 15, 2026
Hello,
I am using the RotMotionFileName feature in AeroDyn and I noticed a row-misalignment issue with the Azimuth data in the generated .out file.
Specifically:
At t = 0s, the output Azimuth seems to read the value from the next time step.
For all subsequent time steps, the output Azimuth shows the value from the previous time step.
However, the rotor speed (omega / RotSpeed) is perfectly aligned and normal.
For reference:
Figure 1 (below) shows the data imported from the RotMotionFile.
Figure 2 (below) shows the resulting data in the generated .out file.
Could you please help clarify what might be causing this discrepancy? Is this the expected behavior in the time-stepping/interpolation logic, or could it be an issue?
Thank you for your time and help!
Best regards
Discussed in #3334
Originally posted by gxyanwork-byte May 15, 2026
Hello,
I am using the RotMotionFileName feature in AeroDyn and I noticed a row-misalignment issue with the Azimuth data in the generated .out file.
Specifically:
At t = 0s, the output Azimuth seems to read the value from the next time step.
For all subsequent time steps, the output Azimuth shows the value from the previous time step.
However, the rotor speed (omega / RotSpeed) is perfectly aligned and normal.
For reference:
Figure 1 (below) shows the data imported from the RotMotionFile.
Figure 2 (below) shows the resulting data in the generated .out file.
Could you please help clarify what might be causing this discrepancy? Is this the expected behavior in the time-stepping/interpolation logic, or could it be an issue?
Thank you for your time and help!
Best regards