This directory is for developers who build OpenFAST, maintained by NLR (National Laboratory of the Rockies, formerly NREL), with CableDyn as CompMooring = 5. Users who only run coupled cases should use the released openfast.exe and the OpenFAST guide.

The patches in patches/ apply to the public OpenFAST upstream commit 2895884d2be01862173c88d70f86b358d2f1a50a (the OpenFAST v5.0.0 release, used by CableDyn v0.3.0). They add only the OpenFAST host integration; the CableDyn sources come from this repository.

git clone https://github.com/OpenFAST/openfast.git openfast-cabledyn
git -C openfast-cabledyn checkout 2895884d2be01862173c88d70f86b358d2f1a50a
./integration/openfast/prepare_openfast_source.ps1 -OpenFASTRoot ./openfast-cabledyn

The script stops if the revision differs, the worktree carries other changes, or a patch does not apply. On a checkout where the whole series is already applied it reports that and changes nothing, so it can be rerun. Configure the patched tree with CMake and pass -DCABLEDYN_ROOT=<CableDyn checkout> (optionally -DCABLEDYN_BUILD_DIR=<CableDyn build> to link a prebuilt core). Then check the build:

./integration/openfast/openfast_build_gate.ps1 -BuildDir <openfast-build> -CaseFst <case.fst>

The script fails unless openfast.exe builds, the smoke case initialises the CableDyn module, and the output is finite to the last row. An openfast.exe built through CMake does not embed the UTF-8 active-code-page manifest, so on Windows it may not open input files in folders whose names the system code page cannot spell; the static release build embeds it.

For the static Windows release, pass a clean, unpatched checkout to release/build_static_windows.ps1; it applies the series itself (see Installation). Its Visual Studio project compiles the CableDyn adapter with /heap-arrays:1024, as the static CMake build compiles the CableDyn core, so arrays whose size is known only at run time are placed on the heap rather than on the openfast.exe stack.

The patches modify OpenFAST source files licensed under the Apache License, Version 2.0. The changed files are modified files in the sense of Section 4(b) of that license: upstream copyright and license notices are retained, and the changed files and the nature of the changes are identified here and in the top-level NOTICE.