-
Notifications
You must be signed in to change notification settings - Fork 97
OpenFAST 4.1.0: changes to ExtInfw #1665
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Haven't tried it out yet. This is just following Andy's comments. |
Couldn't find any instances of ExtLoads - I'm guessing that isn't used by AMR-Wind. |
Thanks for doing this. Could you also modify the cmake? https://github.com/Exawind/amr-wind/blob/main/CMakeLists.txt#L181 I think we can also add some checks there so that we don't let people build with 4.0. |
Corresponding spack update: spack/spack-packages#327 |
I am getting:
|
The cmake works as expected though, so that's good:
|
Pushed a fix, so it now builds. Want to make sure I didn't also break OF 3.5 and non-OF builds. |
Building with 3.5 seems ok. Let's get: spack/spack-packages#327 merged and then update exawind-manager with the updated package repo and then merge this? |
I realized the spack package logic will be a bit more complex. For any version of amr-wind >= 2.0, we allow in general, openfast >= 3.5.
I think we can capture this with this:
but that assumes our next version of amr-wind (3.5.1) is the one that is going to contain this commit. Feels weird to have a patch version of amr-wind need that kind of logic. So what should it be? 3.6? And we only merge this when we are ready for that release? |
Game plan: wait for OF to release more tags (based on some bug fixes), merge this, tag AMR-Wind, immediately update the spack PR with all the tags, merge that, update exawind-manager with latest spack. |
a55994c
to
01c3f81
Compare
OpenFAST 4.1.1 is now out: https://github.com/OpenFAST/openfast/releases/tag/v4.1.1 This includes a fix from @marchdf for the C++ interfacing |
01c3f81
to
59b184e
Compare
Summary
Pull request type
Please check the type of change introduced:
Checklist
The following is included:
This PR was tested by running:
Additional background
Issue Number: