NWTC

I suspect that the code isn't linking with the new compiled version of the FAST_types.f90/ElastoDyn_Types.f90 files, which is what causes the access violations. (I have had this problem before, myself. I am not sure if this is a Visual Studio problem or if there is something wrong in the way the FAS...

Your TIMESR input is rotated 180 from the mean wind direction. The mean u component should almost always be positive, but you've defined them to all be negative in your input file. TurbSim's output is actually equivalent to your input file, though. It uses the convenction that u is positive in the m...

Anup,

Is the wind direction at the hub 0 degrees? You should be able to see this in the TurbSim summary file.

If it is 0, I would not expect any difference in the wind time series output, including the sign.

Hi, Paul. I don't see anything in your code that would be problematic. I suspect that the code isn't linking with the new compiled version of the FAST_types.f90 files, which is what causes the access violations. (I have had this problem before, myself. I am not sure if this is a Visual Studio proble...

Juan, You need to tell the compiler to preprocess the source file. With gfortran, you add the "-cpp" option to the build command that you used (on Intel Fortran, you use '-fpp'): gfortran -cpp -c -fPIC DISCONChanges.f90 In these particular source files, though, the preprocessor directives ...

Hi Anup, You should get exactly the same time series output at the single point that you input; I would assume that you set that point to be at the hub. If you are not getting that output, check the time-series input file to make sure your measurement point is exactly on a grid point and that it's r...

Hi, Jan. I think this bug has been fixed in the latest version of OpenFAST (https://github.com/openfast/openfast). It might be in the master branch, but I'm pretty certain it was merged into the dev branch. Let me know if that doesn't fix the problem. When you set nComp to 2, though, it just sets w ...

That should be the only line you have to change. Your $(BIN_DIR) is set to ../bin at the top of that makefile, so I would set MAP_lib = /usr/lib/libmap-1.20.10.dylib or if you changed it to have a .so extension, you would use MAP_lib = /usr/lib/libmap-1.20.10.so I don't think the file extension that...

Hi, Astrid. There is a single stability parameter, RICH_NO, for each TurbSim simulation. Stability could, of course, vary with height, but that was not what was implemented in the code. You'd have to ask Neil Kelley, who originally pulled together the theory for TurbSim (and its predecessor codes), ...

gfortran: error: ../bin/libmap-1.20.10.so: No such file or directory This error message indicates that it is looking for a file called ../bin/libmap-1.20.10.so ; however you seem to have named that file /usr/lib/libmap-1.20.10.dylib . You should be able to either copy your file to the location the ...

Ruiliang, I think this issue is related to https://github.com/OpenFAST/openfast/issues/152. You can get the error about not finding a label in {openfast}\vs-build\RunRegistry.bat if it does not contain Windows line endings. GitHub or git may have converted this file to use linux or mac line endings ...

Zahir, The first errors about InflowWind's UniformWind submodule might be due to something wrong in the auto-generated IfW_UniformWind_Types.f90 file. If you add a space in the IfW_UniformWind.txt file, it should regenerate that file. (If that doesn't work, you could probably grab this file , but I'...

Array bounds checking won't necessarily help with the Bladed-style DLL. The arrays between FAST/Bladed and the controller DLL pass an address, so the compiler isn't going to be able to provide bounds checking that way. The aeroelastic code that calls the Bladed DLL indicates how long the array is al...

Hi Xiaomin,

There should be a Visual Studio project in the FAST8 archive for compiling the FAST library. Please read the instructions in the FAST8 ReadMe (see page 54) for help in compiling with it.

Hi, Xioming. The pre-compiled FAST Library was really designed to be used with Simulink, which is why it is linking with Matlab libraries. If you aren't going to be using this in Matlab, you can compile with the SysIVF.f90 file instead of SysMatlab.f90 and then remove the Matlab libraries from the l...