Open andrew-platt opened 1 year ago
Thanks, @andrew-platt.
I agree that FASTWrapper needs to pass the instantaneous rotor diameter (projected along a flat disk representing the rotor plane) from OpenFAST to FAST.Farm for use by WakeDynamics. This and other variables that need to be transferred from OpenFAST to FAST.Farm are listed in the Outputs section of the FASTWrapper registry file: https://github.com/OpenFAST/openfast/blob/dev/glue-codes/fast-farm/src/FASTWrapper_Registry.txt. We should ensure all of these variables are calculated properly when OLAF is enabled as well.
Bug description Running a multi-turbine
FAST.Farm
simulation with OLAF enabled in AD15 results in a segmentation fault. This was reported on the forum (https://forums.nrel.gov/t/fvw-for-multiple-turbines-in-openfast-fast-farm/4303/3).To Reproduce Steps to reproduce the behavior:
TSinflow
FAST.Farm regression case with OLAF enabledLine 591 of
FASTWrapper.f90
is:This corresponds to line 601 in dev: https://github.com/OpenFAST/openfast/blob/dev/glue-codes/fast-farm/src/FASTWrapper.f90#L601
Root Cause When OLAF is enabled AD15, BEMT is not used. Therefore, the
BEMT_u
array is not allocated, and neither is therLocal
contained in it.When OLAF was added to OpenFAST, testing with FAST.Farm was apparently not done as this would have been noticed then.
Additional concerns and fix The
rLocal
array fromBEMT
contains the radius of blade nodes in the disk plane from the center of a flat rotor disk projection. They%D_rotor
value calculated from it isused in theWakeDynamics
module, which may have some assumptions on how this calculation is done.Two possible fixes:
However, there may be some additional assumptions in the
WakeDynamics
module that are not valid for OLAF -- this will need to be checked.OpenFAST Version Any version of OpenFAST that includes OLAF will likely trigger this bug.