Bonnie Jonkman

You should build the OpenFAST for Simulink libraries using `make openfast` _before_ calling 'create_FAST_SFunc.m`: 1. Create build files using CMake 2. Run the build files with make 3. Run create_FAST_SFunc....

@andrew-platt , do you have any ideas? The C/C++ compiler and libraries used in Matlab (configured with mex) need to be compatible with the compiler and libraries used to build...

When you choose the "SMOOTH" turbulence model, the inputs you circled in red are not used. Please see the TurbSim User's Guide for more information regarding which inputs are used...

@rafmudaf, the first versions of FAST8 didn't run properly with MinGW, either. I built the executable with debugging symbols (`-g`), loaded it into Intel Inspector, and fairly quickly found the...

@ValentinChb , can you run your executable in Intel's Inspector program? It is extremely difficult to find memory problems like this without a tool like Inspector. As @ebranlard said, the...

Thanks, @ValentinChb . Inspector _can_ give false positives, particularly on file I/O and on internal libraries, but it does seem like we may have several things to look at in...

I fixed a few issues where FAST.Farm memory wasn't deallocated here: https://github.com/bjonkman/openfast/tree/b/FAST.Farm-memory. I am not sure that will fix any of the issues you are seeing, unless there was an...

We might have to 1. call `AD_CalcOutput` instead of `RotCalcOutput` in `Rot_JacobianPInput()` and `RotJacobianPContState()` or 2. move where `y%rotors(iR)%WriteOutput` is computed from `AD_CalcOutput` into `RotCalcOutput`.

FYI: at the moment it looks like some of the FAST.Farm source code in this PR has white-space changes (different line endings?) on every line. For example, see FAST_Farm_Subs.f90.

I think I would try to just convert the line endings of the affected source files in the next commit and then squash the two commits so just the main...