I'm currently coupling ROSCO to an in-house C code and encountered an unexpected behaviour of the yaw module: ROSCO returned completely inconsistent yaw angle commands. After digging a little into the code I found out that this behaviour arised from what looks like an incorrect typecast.
Updating the REAL FUNCTION wrap_360(x) and REAL FUNCTION wrap_180(x) functions to REAL(DbKi) FUNCTION wrap_360(x) and REAL(DbKi) FUNCTION wrap_180(x) (thus following the same signature as other functions of Functions.f90) apparently solved this issue on my side.
The bug occurred on Rosco 2.8.0 but I believe it is still present in ROSCO 2.9.0 (I did not replicate it though).
I'm currently coupling ROSCO to an in-house C code and encountered an unexpected behaviour of the yaw module: ROSCO returned completely inconsistent yaw angle commands. After digging a little into the code I found out that this behaviour arised from what looks like an incorrect typecast.
Updating the
REAL FUNCTION wrap_360(x)
andREAL FUNCTION wrap_180(x)
functions toREAL(DbKi) FUNCTION wrap_360(x)
andREAL(DbKi) FUNCTION wrap_180(x)
(thus following the same signature as other functions ofFunctions.f90
) apparently solved this issue on my side.The bug occurred on Rosco 2.8.0 but I believe it is still present in ROSCO 2.9.0 (I did not replicate it though).