functions type about rosco HOT 4 CLOSED

Hi Rick,
Thanks for digging deep into the code and pointing this out. As you might have guessed by the use of REAL(8) instead of REAL(4) in most parts of the code, there is potential for precision errors in a few parts of ROSCO.

As far are shifting everything to be similar to OpenFAST in using ReKi, we have discussed this as a future update. Unfortunately, we just haven't had the bandwidth to make this change yet.

I'm going to keep this issue open and keep updating it as we move towards a long term solution for things regarding this.

Cheers,
Nikhar

from rosco.

This hardcoding of variable types also makes it impossible to compile ROSCO using Visual Studio and the FORTRAN Intel Compiler

from rosco.

We are addressing this issue in #64, which should make its way into develop in the next week or so.

from rosco.

This has been sorted in newer versions of ROSCO, closing this issues.

from rosco.