openfast / r-test

OpenFAST

 

OpenFAST is a wind turbine simulation tool which builds on FAST v8. FAST.Farm extends the capability of OpenFAST to simulate multi-turbine wind farms. They were created with the goal of being community models developed and used by research laboratories, academia, and industry. They are managed by a dedicated team at the National Renewable Energy Lab. Our objective is to ensure that OpenFAST and FAST.Farm are sustainable software that are well tested and well documented. If you'd like to contribute, see the Developer Documentation and any open GitHub issues with the Help Wanted tag.

OpenFAST is under active development.

FAST v8 - OpenFAST

The transition from FAST v8 to OpenFAST represents the effort to better support an open-source developer community around FAST-based aero-hydro-servo- elastic engineering models of wind-turbines and wind-plants. OpenFAST is the next generation of FAST analysis tools. More information is available in the transition notes.

FAST v8, now OpenFAST, is a physics-based engineering tool for simulating the coupled dynamic response of wind turbines. OpenFAST joins aerodynamics models, hydrodynamics models for offshore structures, control and electrical system (servo) dynamics models, and structural (elastic) dynamics models to enable coupled nonlinear aero- hydro-servo-elastic simulation in the time domain. The OpenFAST tool enables the analysis of a range of wind turbine configurations, including two- or three-blade horizontal-axis rotor, pitch or stall regulation, rigid or teetering hub, upwind or downwind rotor, and lattice or tubular tower. The wind turbine can be modeled on land or offshore on fixed-bottom or floating substructures. OpenFAST is based on advanced engineering models derived from fundamental laws, but with appropriate simplifications and assumptions, and supplemented where applicable with computational solutions and test data.

With OpenFAST, you can run large numbers of nonlinear time-domain simulations in approximately real time to enable standards-based loads analysis for predicting wind system ultimate and fatigue loads. You can also linearize the underlying nonlinear model about an operating point to understand the system response and enable the calculation of natural frequencies, damping, and mode shapes; the design of controllers, and analysis of aero-elastic instabilities.

The aerodynamic models use wind-inflow data and solve for the rotor-wake effects and blade-element aerodynamic loads, including dynamic stall. The hydrodynamics models simulate the regular or irregular incident waves and currents and solve for the hydrostatic, radiation, diffraction, and viscous loads on the offshore substructure. The control and electrical system models simulate the controller logic, sensors, and actuators of the blade-pitch, generator-torque, nacelle-yaw, and other control devices, as well as the generator and power-converter components of the electrical drive. The structural-dynamics models apply the control and electrical system reactions, apply the aerodynamic and hydrodynamic loads, adds gravitational loads, and simulate the elasticity of the rotor, drivetrain, and support structure. Coupling between all models is achieved through a modular interface and coupler (glue code).

FAST.Farm extends the capabilities of OpenFAST to provide physics-based engineering simulation of multi-turbine land-based, fixed-bottom offshore, and floating offshore wind farms. With FAST.Farm, you can simulate each wind turbine in the farm with an OpenFAST model and capture the relevant physics for prediction of wind farm power performance and structural loads, including wind farm-wide ambient wind, super controller, and wake advection, meandering, and merging. FAST.Farm maintains computational efficiency through parallelization to enable loads analysis for predicting the ultimate and fatigue loads of each wind turbine in the farm.

Documentation

The full documentation is available at http://openfast.readthedocs.io/.

This documentation is stored and maintained alongside the source code. It is compiled into HTML with Sphinx and is tied to a particular version of OpenFAST. Readthedocs hosts the following versions of the documentation:

• latest - The latest commit on the main branch
• stable - Corresponds to the last tagged release
• dev - The latest commit on the dev branch

These can be toggled with the v: latest button in the lower left corner of the docs site.

Obtaining OpenFAST and FAST.Farm

OpenFAST and FAST.Farm are hosted entirely on GitHub so you are in the right place! The repository is structured with two branches following the "git-flow" convention:

• main
• dev

The main branch is stable, well tested, and represents the most up to date released versions of OpenFAST and FAST.Farm. The latest commit on main contains a tag with version info and brief release notes. The tag history can be obtained with the git tag command and viewed in more detail on GitHub Releases. For general use, the main branch is highly recommended.

The dev branch is generally stable and tested, but not static. It contains new features, bug fixes, and documentation updates that have not been compiled into a production release. Before proceeding with new development, it is recommended to explore the dev branch. This branch is updated regularly through pull requests, so be sure to git fetch often and check outstanding pull requests.

For those not familiar with git and GitHub, there are many resources:

• https://guides.github.com
• https://try.github.io
• https://help.github.com/categories/bootcamp/
• https://desktop.github.com/
• http://nvie.com/posts/a-successful-git-branching-model/

Compilation, Usage, and Development

Details for compiling compiling, using, and developing OpenFAST and FAST.Farm on Unix-based and Windows machines are available at readthedocs.

Help

Please use GitHub Issues to:

• ask usage questions
• report bugs
• request code enhancements

Users and developers may also be interested in the NREL National Wind Technology Center (NWTC) phpBB Forum, which is still maintained and has a long history of FAST-related questions and answers.

Acknowledgments

OpenFAST and FAST.Farm are maintained and developed by researchers and software engineers at the National Renewable Energy Laboratory (NREL), with support from the US Department of Energy's Wind Energy Technology Office. NREL gratefully acknowledges development contributions from the following organizations:

• Envision Energy USA, Ltd
• Brigham Young University
• The University of Massachusetts
• Intel® Parallel Computing Center (IPCC)

r-test's Issues

DISCON.dll

where can I download the DISCON.dll without compiling,thank you very much

Aerodynamic calculation using AeroDyn standalone

I am trying to perform the aerodynamic calculation for the wind turbine blade. I use AeroDyn standalone to perform the analysis. While giving the input, I got the error "error reading NumAlf". Is it necessary to have an equal number of data lines for the aerodynamic coefficient table and aerofoil data file(I consider the NREL input dataset for calculation with 400 lines of airfoil data and 146 lines of aerodynamic coefficient data)?
Any suggestions you can give me will be constructive.

Incorrect Unstead Airfoil Aerodynamic Input Parameters

I would normally expect the unsteady airfoil aerodynamics (UA) model of OpenFAST / AeroDyn to influence the variations of lift about the mean, but not to directly influence the mean lift itself. However, Mehran Saeedi on our forum noticed that the mean lift is being impacted for some airfoils, e.g., the DU25 airfoil in the NREL 5-MW baseline models--see the figure below.

This is likely the result of inconsistencies between the UA parameters and the the static airfoil data in the AeroDyn v15 airfoil data file. These inconsistencies should be fixed in the sample OpenFAST models provided in the r-test. I'm not sure where the UA parameters originated from for all airfoils, but I would guess a mistake was made when the AeroDyn v15 airfoil data input files were first made, at least for some airfoils.

I know that there are scripts floating around that can be used to derive the UA parameters from the static airfoil data. It would be great if these scripts could be used to update the AeroDyn v15 airfoil data files.

For more information, see the related discussion on the forum: https://wind.nrel.gov/forum/wind/viewtopic.php?f=2&t=2492.

`Tailfin_FreeYaw1DOF_PolarBased` airfoil has linear cl curve

When running the OpenFAST Tailfin_FreeYaw1DOF_PolarBased case, this warning appears:

FAST_InitializeAll:AD_Init:Init_AFIparams:AFI_Init:ReadAFfile:Airfoil data should go from -180
degrees to 180 degrees and the coefficients at the ends should be the same.

It looks like the airfoil file in that case has a linear cl curve instead of something periodic. See
https://github.com/OpenFAST/r-test/blob/main/glue-codes/openfast/Tailfin_FreeYaw1DOF_PolarBased/Polar_2PiAlpha.dat

fast on mpi

Hi,
I am facing an issue with executing openfast on mpi. unfortunately it is unable to find the .fst file even when located in the very same directory that its being launched in. I have checked the launch script very carefully multiple times. there seems to be no errors in it.
error-
FAST_InitializeALL:FAST_Init:FAST_ReadPrimaryFile:OpenFInputFile:The input file,"./" , was not found.

Is fast compatible with mpi?

Add Test case for flexible platforms

No test cases were added to the regression tests when platform flexibility was added (OpenFAST/openfast#537).

Add a test case using a publicly available structure that has been validated to some extent:

1. Simple spar based on OC3
2. paper by Borg et al that includes a model of a flexible spar. This is a model of the DTU 10-MW turbine atop a fictitious spar: https://iopscience.iop.org/article/10.1088/1742-6596/753/8/082024/pdf

TurbSim manual

Hi,
recently i had see a manual where, step by step, i can set all the parameter of the 90m_12mps_twr.INP for TurbSim like type of turbolence, WindProfileType, Power law exponent and Surface roughness length for offshore.
Now, i can't find this manual.
Can you help me?
Best regards,

Andrea

FAST Error: invalid logical input when I use Turbsim file for the wind flow

Am trying to implement a TurbSim file into Fast but it keeps giving me the error

Can Anyone Help ?

Is there a detail description of the wind turbine models?

I currently only have an introduction of 5-MW Reference Wind Turbine for Offshore, the other model such as 5MW_OC4Semi_WSt_WavesWN, where can I find a description of other wind turbines?

Grid too small in Y direction.

Dear all,
i want to use r-test-3.0.0 to simulate a wind farm with power of 50 MW in the form of two rows with 5 turbines in each row,but every time i add turbines i encounter this error.

FAST.Farm-v3.0.0
Compile Info:

• Compiler: Intel(R) Fortran Compiler 1900
• Architecture: 64 bit
• Precision: single
• OpenMP: No
• Date: Jun 23 2021
• Time: 21:41:28
  Execution Info:
• Date: 08/17/2022
• Time: 10:07:33+0430

Heading of the FAST.Farm input file:
Sample FAST.Farm input file
Running AWAE.
Running InflowWind.

Reading a 101x35 grid (1000 m wide, 5 m to 345 m above ground) with a characteristic wind
speed of 9.243 m/s. This full-field file was generated by TurbSim (v2.00.07a-bjj, 14-Jun-2016)
on 24-Sep-2019 at 16:18:09.

Processed 2000 time steps of 10-Hz full-field data (period of 200 seconds).

Farm_Initialize:Farm_ValidateInput:OutFmt produces a column width of 10 instead of 20 characters.
Farm_Initialize:For efficiency, NumPlanes has been reduced to the number of time steps (134).
Farm_Initialize:InflowWind_CalcOutput:CalcOutput:IfW_FFWind_CalcOutput [position=(4810.4, 1510,
345) in wind-file coordinates]: FF wind array boundaries violated: Grid too small in Y
direction. Y=1510; Y boundaries = [-500, 500]

Aborting FAST.Farm.

I would greatly appreciate if you could help me with this problem.

Best regards,
Maede

OpenFAST v4.0 deprecates AD 14

The release of OpenFAST v3.0.0 will deprecate AeroDyn 14, and the module will be removed in a subsequent release. The regression tests using AeroDyn 14 will need to be modified to use AeroDyn 15.

An existing pull request starts the process: #18.

SWRT tests cases with tail fin do not match FAST7 results

The SWRT cases now include a new tail fin model that theoretically is similar to the FAST7 cases (see PR #126).

Comparing the results for the cases with FAST7 shows some notable differences. There have been significant improvements to the AeroDyn that may account for the differences. Someone should double check this though.

Example from the SWRT_YFree_VS_EDC01 case (Test16.out from the FAST7 CertTest). Note that SubAxInd has been turned off in the FAST7 run since TFinIndMod=1 is not available in the current dev branch of OpenFAST (3d476c595).

@abhineet-gupta may have some insights here.

invalid logical input to read SumPrint

Dear all,

I have a problem in running the OPENfast with FFTest_WT1.fst input files. I receive an error on reading the input files "FFTest_WT1.fst". The error is as follows:
Invalid logical input for file ".\FFTest_WT1.fst" occurred while trying to read SumPrint.

FAST.Farm-v3.0.0
Compile Info:

• Compiler: Intel(R) Fortran Compiler 1900
• Architecture: 64 bit
• Precision: single
• OpenMP: No
• Date: Jun 23 2021
• Time: 21:41:28
  Execution Info:
• Date: 07/21/2022
• Time: 09:22:15+0430

Heading of the FAST.Farm input file:
Sample FAST.Farm input file
Running AWAE.
Running WakeDynamics.
Running FASTWrapper (v1.00.00, 7-Feb-2017).
Running OpenFAST.
OpenFAST input file heading:
FAST Certification Test #26: NREL 5.0 MW Baseline Wind Turbine (Onshore)

Farm_Initialize:Farm_ValidateInput:OutFmt produces a column width of 10 instead of 20 characters.
Farm_Initialize:For efficiency, NumPlanes has been reduced to the number of time steps (16).
Farm_Initialize:T1:Farm_InitFAST:FWrap_Init:FAST_InitializeAll:FAST_Init:FAST_ReadPrimaryFile:Inva
lid logical input for file ".\FFTest_WT1.fst" occurred while trying to read SumPrint.

Aborting FAST.Farm.

I would greatly appreciate if you could help me with this problem.

Best regards,
Maede

issue with running MD V2 farm branch

I am trying to use the new moordyn V2 with added bending stiffness but unfortunately there's an error which i am having a hard time figuring it out.

FAST_InitializeAll:FAST_Init:FAST_ReadPrimaryFile:Invalid logical input for file
".\5MW_OC4Semi_WSt_WavesWN.fst" occurred while trying to read SumPrint.

I am aware of the new .fst file with added environmental conditions which i am currently trying to use. If anyone has had the same issue and been able to solve it . It would be helpful if you shared your approach.

Path to DISCON.dll library

Hi,

I tried running the 5MW_Land_BD_DLL_WTurb.fst input file and it died with an error:

FAST_InitializeAll:SrvD_Init:BladedInterface_Init:The dynamic library
./../5MW_Baseline/ServoData/DISCON.dll could not be loaded. Check that the file exists in the
specified location and that it is compiled for 64-bit applications.
FAST encountered an error during module initialization.
 Simulation error level: FATAL ERROR
 Aborting OpenFAST.

I found that if I change the DLL_FileName path in the following file to include "build", then it runs successfully.

diff --git a/glue-codes/openfast/5MW_Land_BD_DLL_WTurb/NRELOffshrBsline5MW_Onshore_ServoDyn.dat b/glue-codes/openfast/5MW_Land_BD_DLL_WTurb/NRELOffshrBsline5MW_Onshore_ServoDyn.dat
index 6083fef..46d20a9 100644
--- a/glue-codes/openfast/5MW_Land_BD_DLL_WTurb/NRELOffshrBsline5MW_Onshore_ServoDyn.dat
+++ b/glue-codes/openfast/5MW_Land_BD_DLL_WTurb/NRELOffshrBsline5MW_Onshore_ServoDyn.dat
@@ -63,7 +63,7 @@ False         CompNTMD     - Compute nacelle tuned mass damper {true/false} (fla
 False         CompTTMD     - Compute tower tuned mass damper {true/false} (flag)
 "../5MW_Baseline/NRELOffshrBsline5MW_ServoDyn_TMD.dat"    TTMDfile     - Name of the file for tower tuned mass damper (quoted string) [unused when CompTTMD is false]
 ---------------------- BLADED INTERFACE ---------------------------------------- [used only with Bladed Interface]
-"../5MW_Baseline/ServoData/DISCON.dll"    DLL_FileName - Name/location of the dynamic library {.dll [Windows] or .so [Linux]} in the Bladed-DLL format (-) [used only with Bladed Interface]
+"../5MW_Baseline/ServoData/DISCON/build/DISCON.dll"    DLL_FileName - Name/location of the dynamic library {.dll [Windows] or .so [Linux]} in the Bladed-DLL format (-) [used only with Bladed Interface]^M
 "DISCON.IN"    DLL_InFile   - Name of input file sent to the DLL (-) [used only with Bladed Interface]
 "DISCON"      DLL_ProcName - Name of procedure in DLL to be called (-) [case sensitive; used only with DLL Interface]
 "default"     DLL_DT       - Communication interval for dynamic library (s) (or "default") [used only with Bladed Interface]

Lift coefficients in BAR airfoil files

While debugging some differences in a new method of calculating default unsteady airfoil coefficients, I noticed some unusual characteristics in the lift coefficients in several of the aerodyn/BAR_Baseline files (1-6).

./modules/aerodyn/BAR_Baseline/Airfoils/BAR0_AeroDyn15_Polar_01.dat
./modules/aerodyn/BAR_Baseline/Airfoils/BAR0_AeroDyn15_Polar_02.dat
./modules/aerodyn/BAR_Baseline/Airfoils/BAR0_AeroDyn15_Polar_03.dat
./modules/aerodyn/BAR_Baseline/Airfoils/BAR0_AeroDyn15_Polar_04.dat
./modules/aerodyn/BAR_Baseline/Airfoils/BAR0_AeroDyn15_Polar_05.dat
./modules/aerodyn/BAR_Baseline/Airfoils/BAR0_AeroDyn15_Polar_06.dat

I am not sure what those local minima just below alpha=0 are:

Other aerodyn/BAR_Baseline airfoils look more normal. For example

./modules/aerodyn/BAR_Baseline/Airfoils/BAR0_AeroDyn15_Polar_07.dat
./modules/aerodyn/BAR_Baseline/Airfoils/BAR0_AeroDyn15_Polar_08.dat
./modules/aerodyn/BAR_Baseline/Airfoils/BAR0_AeroDyn15_Polar_09.dat

Here are values for 7-9:

If those local minima are expected, we will have to look into some different methods for computing values for c_lalpha and c_nalpha. Also, I'm not sure how the UA models will handle it.

Let me know what you think.

version 2.4.0 5MW_OC3Mnpl_DLL_WTurb_WavesIrr not working with windows x64 binaries

Hi Rafael,

I tried to run the r-test 5MW_OC3Mnpl_DLL_WTurb_WavesIrr (v2.4.0) with 2.4.0 windows 64x binaries and I got some errors. There might be an issue with mismatching line numbers in the input files. I didn't have any issues running this r-test with v 2.2.0 and 2.3.0. Please find attached the FAST console output.

log.txt

Best,
Manuela

FAST: How can I get the force and moments in an exact location of the tower?

I'm trying to get the forces and the moments in the middle of the wind turbine tower, any advice on how to change the location of results from the hub to the desired point?

The dynamic library ./../5MW_Baseline/ServoData/DISCON.dll could not be loaded.

Hello everyone,

I'm trying to run OpenFAST on an m1 MacBook Air (on MacOS Monterey). But some of the regression tests fail with the following output:

(openfast_test) MacBook-Air-2 5MW_Land_DLL_WTurb % openfast 5MW_Land_DLL_WTurb.fst 

 **************************************************************************************************
 OpenFAST

 Copyright (C) 2021 National Renewable Energy Laboratory
 Copyright (C) 2021 Envision Energy USA LTD

 This program is licensed under Apache License Version 2.0 and comes with ABSOLUTELY NO WARRANTY.
 See the "LICENSE" file distributed with this software for details.
 **************************************************************************************************

 OpenFAST-v3.0.0-324-g7a59bec8
 Compile Info:
  - Compiler: GCC version 9.3.0
  - Architecture: 64 bit
  - Precision: single
  - OpenMP: No
  - Date: Sep 30 2021
  - Time: 19:38:10
 Execution Info:
  - Date: 11/03/2021
  - Time: 15:00:26+0100

 OpenFAST input file heading:
     FAST Certification Test #18: NREL 5.0 MW Baseline Wind Turbine (Onshore)

 Running ElastoDyn.
 Nodal outputs section of ElastoDyn input file not found or improperly formatted.
 Running AeroDyn.
 AD15 Nodal Outputs: Nodal output section of AeroDyn input file not found or improperly formatted.
 Skipping nodal outputs.
 Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil
 (airfoil has likely has constant polars). (node 1, blade 1)
 Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil
 (airfoil has likely has constant polars). (node 2, blade 1)
 Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil
 (airfoil has likely has constant polars). (node 3, blade 1)
 Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil
 (airfoil has likely has constant polars). (node 4, blade 1)
 Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil
 (airfoil has likely has constant polars). (node 1, blade 2)
 Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil
 (airfoil has likely has constant polars). (node 2, blade 2)
 Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil
 (airfoil has likely has constant polars). (node 3, blade 2)
 Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil
 (airfoil has likely has constant polars). (node 4, blade 2)
 Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil
 (airfoil has likely has constant polars). (node 1, blade 3)
 Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil
 (airfoil has likely has constant polars). (node 2, blade 3)
 Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil
 (airfoil has likely has constant polars). (node 3, blade 3)
 Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil
 (airfoil has likely has constant polars). (node 4, blade 3)
 Running InflowWind.

    Reading a 31x31 grid (145 m wide, 17.5 m to 162.5 m above ground) with a characteristic wind
    speed of 12 m/s. This full-field file was generated by TurbSim (v1.06.00, 21-Sep-2012) on
    07-Jan-2014 at 12:50:45.

    Processed 1442 time steps of 20-Hz full-field data (72.05 seconds).
 Running ServoDyn.
 Running ServoDyn Interface for Bladed Controllers (using GNU Fortran for Linux, ).

 FAST_InitializeAll:SrvD_Init:BladedInterface_Init:The dynamic library
 ./../5MW_Baseline/ServoData/DISCON.dll could not be loaded. Check that the file exists in the
 specified location and that it is compiled for 64-bit applications.

 OpenFAST encountered an error during module initialization.
  Simulation error level: FATAL ERROR

  Aborting OpenFAST.

I inspected the dll using file but everything seems fine.

(openfast_test) MacBook-Air-2 5MW_Land_DLL_WTurb % file ./../5MW_Baseline/ServoData/DISCON.dll
./../5MW_Baseline/ServoData/DISCON.dll: Mach-O 64-bit dynamically linked shared library arm64

How to reproduce the error

I installed OpenFAST using conda by following the instructions:

1. Create a new environment: conda create -n openfast_test
2. Activate the newly created environment: conda activate openfast_test
3. Install OpenFAST: conda install -c conda-forge openfast=3.0.0=hefb7bc6_11

Verifying installation:

(openfast_test) MacBook-Air-2 ~ % which openfast
/opt/homebrew/anaconda3/envs/openfast_test/bin/openfast
(openfast_test) MacBook-Air-2 ~ % openfast -v

 **************************************************************************************************
 OpenFAST

 Copyright (C) 2021 National Renewable Energy Laboratory
 Copyright (C) 2021 Envision Energy USA LTD

 This program is licensed under Apache License Version 2.0 and comes with ABSOLUTELY NO WARRANTY.
 See the "LICENSE" file distributed with this software for details.
 **************************************************************************************************

 OpenFAST-v3.0.0-418-g34ef10ef
 Compile Info:
  - Compiler: GCC version 9.3.0
  - Architecture: 64 bit
  - Precision: single
  - OpenMP: No
  - Date: Oct 29 2021
  - Time: 16:38:00
 Execution Info:
  - Date: 11/03/2021
  - Time: 11:36:11+0100


  OpenFAST terminated normally.

(openfast_test) MacBook-Air-2 ~ % which hydrodyn_driver
/opt/homebrew/anaconda3/envs/openfast_test/bin/hydrodyn_driver
(openfast_test) MacBook-Air-2 ~ % hydrodyn_driver -v

 **************************************************************************************************
 HydroDyn Driver

 Copyright (C) 2021 National Renewable Energy Laboratory
 Copyright (C) 2021 Envision Energy USA LTD

 This program is licensed under Apache License Version 2.0 and comes with ABSOLUTELY NO WARRANTY.
 See the "LICENSE" file distributed with this software for details.
 **************************************************************************************************

 HydroDyn Driver-v3.0.0-418-g34ef10ef
 Compile Info:
  - Compiler: GCC version 9.3.0
  - Architecture: 64 bit
  - Precision: single
  - OpenMP: No
  - Date: Oct 29 2021
  - Time: 16:38:00
 Execution Info:
  - Date: 11/03/2021
  - Time: 11:37:54+0100


  HydroDyn Driver terminated normally.

But when I try to run the regression tests using the matlab script, some tests fail. To run the tests I clone the repository and compile the three dll files as described in the instructions.

Clone r-test github repository:
git clone https://github.com/OpenFAST/r-test.git

cd r-test/glue-codes/openfast/5MW_Baseline/ServoData
Compile 'DISCON', 'DISCON_ITI', and 'DISCON_OC3'

Below is the output for DISCON.dll. The output for the other two is analogously without errors.

(openfast_test) MacBook-Air-2 ServoData % cd DISCON
(openfast_test) MacBook-Air-2 DISCON % mkdir build
(openfast_test) MacBook-Air-2 DISCON % cd build
(openfast_test) MacBook-Air-2 build % cmake ..
-- The C compiler identification is AppleClang 13.0.0.13000029
-- The CXX compiler identification is AppleClang 13.0.0.13000029
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /Library/Developer/CommandLineTools/usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /Library/Developer/CommandLineTools/usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- The Fortran compiler identification is GNU 11.1.0
-- Checking whether Fortran compiler has -isysroot
-- Checking whether Fortran compiler has -isysroot - yes
-- Checking whether Fortran compiler supports OSX deployment target flag
-- Checking whether Fortran compiler supports OSX deployment target flag - yes
-- Detecting Fortran compiler ABI info
-- Detecting Fortran compiler ABI info - done
-- Check for working Fortran compiler: /opt/homebrew/bin/gfortran - skipped
-- Checking whether /opt/homebrew/bin/gfortran supports Fortran 90
-- Checking whether /opt/homebrew/bin/gfortran supports Fortran 90 - yes
-- Configuring done
-- Generating done
-- Build files have been written to: r-test/glue-codes/openfast/5MW_Baseline/ServoData/DISCON/build
(openfast_test) MacBook-Air-2 build % make
Scanning dependencies of target DISCON
[ 50%] Building Fortran object CMakeFiles/DISCON.dir/DISCON.F90.o
[100%] Linking Fortran shared library DISCON.dll
ld: warning: dylib (/opt/homebrew/Cellar/gcc/11.2.0/lib/gcc/11/libgfortran.dylib) was built for newer macOS version (11.4) than being linked (11.0)
[100%] Built target DISCON
(openfast_test) MacBook-Air-2 build % ls
CMakeCache.txt          CMakeFiles              DISCON.dll              Makefile                cmake_install.cmake
(openfast_test) MacBook-Air-2 build % cp DISCON.dll ../..

The DISCON.dll now lies under along with the other dlls:
'.../r-test/glue-codes/openfast/5MW_Baseline/ServoData/DISCON.dll'

(openfast_test) MacBook-Air-2 ServoData % ls
DISCON			DISCON_ITI		DISCON_OC3
DISCON.dll		DISCON_ITIBarge.dll	DISCON_OC3Hywind.dll

Now, running the failing tests individually produces the error message at the beginning. I attempted to reproduce the error on Linux (CentOS Linux release 7.4.1708 (Core)) but was not able to reproduce it. I also tried reproducing it on an older x86 MacBook where I was not able to reproduce the issue either. I'm thinking it has something to do with the M1 chip. Does anybody have any suggestions what the issue could be?

Best regards

Folder where to clone r-test and pFUnit after installing OpenFAST

Good evening,

I'm new to OpenFAST and I've been able to successfully install it on my Ubuntu machine. The next step would then be to test OpenFAST and for that, as I interpret it from the documentation, I'm supposed to clone the r-test and pFUnit git submodules to somewhere but I cannot understand from the documentation to where I should clone them. Could you let me know?

P.S: There is a similar issue on the openfast "issues" (number 401) but it does NOT precise the folders so the answer is not there. I already read the documentation several times and tried go with my gut but I've reached a dead end so I'm going to reinstall everything again.

Out of date TurbSim input files

The input files for TurbSim given in https://github.com/OpenFAST/r-test/tree/dev/glue-codes/openfast/5MW_Baseline/Wind are out of date (version 1.5 whereas TurbSim is at version 2.x.

r test download issue

when cloning ,it took much time and after sometime aborted. next when downloading the zip file and when unzip it, it shows "this archive is corrupted"

kindly solve it @andrew-platt

.fst input files

In the case-specific directories inside r-test/glue-codes/openfast/ I cannot find .fst files. Any help? Or am I looking at the wrong directories?

Error: Executable does not have proper permissions

Hello everybody!
I am new to OpenFAST and have been trying to run some regression tests. I am using Cygwin method to simulate the cases.
I trying to run the executable 'executeOpenfastRegressionCase.py ' with Python3.
when I am entering all the required arguments, I am getting an error as the attached screenshot.

How do I solve this? Any help is appreciated 👍
Thanks!

aerodyne.dat file is missing

primary aerodyne.dat file is missing

although it has NRELOffshrBsline5MW_AeroDyn_Equil_noTwr.dat but after run the .fst file,it shows aerodyn.dat file is missing

Add test example case of earthquake simulation of jacket structure

It would be nice to include a simple test case showing a time-series force input at the base of a jacket structure.

This case can be used as a starting point (based on OC4 Jacket, with a 4 Hz force input at base starting at 10 seconds). This can be run both with and without HD enabled with OpenFAST 3.0.0.

SeismicExample.zip

This is related to OpenFAST/openfast#739

AeroAcoustic files

When comparing some of the input files for the AeroAcoustic module in IEA_LB_RWT-AeroAcoustics, I have noticed that some of the boundary-layer input files use "delta" while others use "theta". If I'm reading the documentation and code correctly, these should be using Delta_SS and Delta_PS instead of Theta_SS and Theta_PS:

• AF05_BL.txt
• AF06_BL.txt
• AF07_BL.txt
• AF08_BL.txt
• AF09_BL.txt

I am not sure if this is a matter of just the headers having a typo or if the data needs to be converted.

Many case folders are missing

Hello everyone
When I tried to download a clean t-main folder, I found that many cases at ..\glue-codes\openfast were missing. There were 43 cases in that folder, but now there are only 8 cases left. I can see them on the website, but they are not in the downloaded folder. I have tried this many times and I don't know if there is something wrong with the web server.

Error in r-test/glue-codes/openfast/5MW_Land_ModeShapes

Hello,
I was trying to run this case using openfast_x64.exe and 5MW_Land_ModeShapes.fst as the input file but it's showed multiple errors in NRELOffshrBsline5MW_Onshore_AeroDyn15.dat file one of them was misaligned AFAeroMod, but after I corrected that.... compAA was missing and further I corrected that keyword, soon many other errors popped up. Do I need to modify these files before running example test cases or they should be running as it is?

Thank you for your time and guidance.