Question regarding Azimuth data misalignment when using RotMotionFileName in AeroDyn

[gxyanwork-byte]

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

[andrew-platt]

This is indeed a bug! I'm creating an issue for this.

Thank you for bringing this to our attention! We'll fix this in an upcoming release.

[gxyanwork-byte]

Thank you for confirming this and for creating the issue! I really appreciate your quick response.

Just out of curiosity, do you have a rough estimate of when the next release might be published?

Looking forward to the update! Thanks again for your great work.

[gxyanwork-byte]

I have a quick follow-up question regarding the impact of this bug.

Does this misalignment only affect the Azimuth values written to the .out file (i.e., just a logging/display issue)? Or does it mean that the actual aerodynamic load calculations at each time step are using the misaligned Azimuth values, and are therefore incorrect?

Knowing this will help me determine if my current aerodynamic results are still valid. Thanks again for your time!