-
Notifications
You must be signed in to change notification settings - Fork 466
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
ExtLd: require use of InflowWind #2412
Conversation
- Remove wind calculations inside ExtLd. These variables removed: - vel_mean - wind_dir - z_ref - shear_exp - Require use of InflowWind - remove following from OF library interface: - vel_mean_c - wind_dir_c - z_ref_c - shear_exp_c
0de1c54
to
fb4a656
Compare
fb4a656
to
2786175
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for getting this done Andy. After going through the implementation, I checked the 5MW_Restart
regression test against the output of the fortran driver with CompAero
set to 2. All channel diff norms are within 1e-12. This is good to go and a welcome reduction in complexity for blade-resolved FSI cases.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me
Ready to merge. Requires testing with FSI CFD (after update to interface on that side).
Feature or improvement description
Originally the ExtLoad module was designed to provide a set of steady wind parameters to OpenFAST from FSI CFD (not sure if this is AMR-Wind or NALU-Wind). These parameters were used to calculate a steady wind profile for AeroDyn to use during the initial few rotations where AeroDyn and ExtLoad loads were blended (this was for initializing the CFD better).
However, after merging in the InflowWind pointers change, there was a bug with how this worked. After some discussion with @gantech and others, it was decided that the best approach would be to now require InflowWind with ExtLoad (previously this was not allowed) and have InflowWind handle all the wind for AeroDyn throughout the simulation. The following changes were made:
FAST_ExtLoads_Init
):Related issue, if one exists
Issue brought up in discussions, not GH.
Impacted areas of the software
The C++ interface is affected.
Additional supporting information
Test results, if applicable
We still don't have a test case for this...