You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I made some modifications to example.NREL5MW.ALMAdvancedFAST8 and added HydroDyn modules to OpenFAST. It was found that the overall calculation result was small. When the wind speed reached 11.4m/s, the output power was only about 2.6MW. Later, it was found that by modifying the bladeForceProjectionDirection option in turbineArrayProperties and changing "sampledVelocityAligned" to "localVelocityAligned", i can get a more correct power output (reached 4.5MW, the calculation results are similar to those when OpenFAST is run alone). However, when I checked the flow field information, I found that the effect of the blade could not be displayed. Has anyone ever encountered this situation? How to deal with it?
Or does anyone use SOWFA and OpenFAST coupling to solve the floating turbines problems? How do you deal with the power problem?
The text was updated successfully, but these errors were encountered:
hello, I install the SOWFA and OpenFAST2.6, but the test case in the gitHub cann't run, could you share your test case and help me to test the solver of "pisoFoamTurbine.ALMAdvancedOpenFAST".
Recently, I have started researching this issue again, and as I delve deeper into the source code, I have found that in line 2385 of HorizontalAxisWindTurbinesALMOpenFAST.C, the calculation formulas for localityAligned and localityAlignedCorrected have been annotated. Is this the reason why the flow field cannot update the volume force caused by the blades when using localVelocityAligned?
When I observe HorizontalAxisWindTurbinesALMAdvanced.C, it was found that this section was not annotated. Does this mean that when using the OpenFAST coupled solver, the option of localVelocityAligned cannot be selected? What kind of modifications should I make to the source code if I want to use the localVelocityAligned option? Thank you very much for your reply. @ewquon@mchurchf@gantech
hello, I install the SOWFA and OpenFAST2.6, but the test case in the gitHub cann't run, could you share your test case and help me to test the solver of "pisoFoamTurbine.ALMAdvancedOpenFAST".
Hello, I would like to ask which article you previously uploaded the pisoFoamTurbine.ALMA AdvancedOpenFAST test case in. Could you please remind me? Or provide a link
I made some modifications to example.NREL5MW.ALMAdvancedFAST8 and added HydroDyn modules to OpenFAST. It was found that the overall calculation result was small. When the wind speed reached 11.4m/s, the output power was only about 2.6MW. Later, it was found that by modifying the bladeForceProjectionDirection option in turbineArrayProperties and changing "sampledVelocityAligned" to "localVelocityAligned", i can get a more correct power output (reached 4.5MW, the calculation results are similar to those when OpenFAST is run alone). However, when I checked the flow field information, I found that the effect of the blade could not be displayed. Has anyone ever encountered this situation? How to deal with it?
Or does anyone use SOWFA and OpenFAST coupling to solve the floating turbines problems? How do you deal with the power problem?
The text was updated successfully, but these errors were encountered: