Closed ArnoldTUB closed 4 months ago
The diameter of each turbine is 130 meters if this info is required
Dear @ArnoldTUB,
Can you share the full message written to the command prompt when you execute FAST.Farm?
Which version of FAST.Farm are you running. Does switching to the newest version (currently within OpenFAST v3.5.2) resolve the issue?
Best regards,
Dear @jjonkman,
here is the full message:
**************************************************************************************************
FAST.Farm
Copyright (C) 2024 National Renewable Energy Laboratory
Copyright (C) 2024 Envision Energy USA LTD
This program is licensed under Apache License Version 2.0 and comes with ABSOLUTELY NO WARRANTY.
See the "LICENSE" file distributed with this software for details.
**************************************************************************************************
FAST.Farm-v3.5.2
Compile Info:
- Compiler: GCC version 11.4.0
- Architecture: 64 bit
- Precision: single
- OpenMP: Yes, number of threads: 112/112
- Date: Feb 15 2024
- Time: 17:18:04
Execution Info:
- Date: 02/27/2024
- Time: 15:01:23+0000
Heading of the FAST.Farm input file:
Simulation with three wind turbines, controlled by MPC
Running AWAE.
Running InflowWind.
Running Super Controller.
Running WakeDynamics.
Running FASTWrapper.
Running OpenFAST.
OpenFAST input file heading:
Generated with AeroElasticSE FAST driver
Running ElastoDyn.
Running AeroDyn.
Warning: Turning off Unsteady Aerodynamics because polar has constant data. (node 1, blade 1)
Warning: Turning off Unsteady Aerodynamics because polar has constant data. (node 1, blade 2)
Warning: Turning off Unsteady Aerodynamics because polar has constant data. (node 1, blade 3)
Running InflowWind.
Running ServoDyn.
Running ServoDyn Interface for Bladed Controllers (using GNU Fortran for Linux).
Using legacy Bladed DLL interface.
Running OpenFAST.
OpenFAST input file heading:
Generated with AeroElasticSE FAST driver
Running ElastoDyn.
Running AeroDyn.
Warning: Turning off Unsteady Aerodynamics because polar has constant data. (node 1, blade 1)
Warning: Turning off Unsteady Aerodynamics because polar has constant data. (node 1, blade 2)
Warning: Turning off Unsteady Aerodynamics because polar has constant data. (node 1, blade 3)
Running InflowWind.
Running ServoDyn.
Running ServoDyn Interface for Bladed Controllers (using GNU Fortran for Linux).
Using legacy Bladed DLL interface.
Running OpenFAST.
OpenFAST input file heading:
Generated with AeroElasticSE FAST driver
Running ElastoDyn.
Running AeroDyn.
Warning: Turning off Unsteady Aerodynamics because polar has constant data. (node 1, blade 1)
Warning: Turning off Unsteady Aerodynamics because polar has constant data. (node 1, blade 2)
Warning: Turning off Unsteady Aerodynamics because polar has constant data. (node 1, blade 3)
Running InflowWind.
Running ServoDyn.
Running ServoDyn Interface for Bladed Controllers (using GNU Fortran for Linux).
Using legacy Bladed DLL interface.
Farm_Initialize:Farm_ValidateInput:OutFmt produces a column width of 10 instead of 20 characters.
Time: 0 of 300 seconds.
T1:FARM_InitialCO:FWrap_t0:FAST_Solution0:CalcOutputs_And_SolveForInputs:SolveOption2:SolveOption2
c_Inp2AD_SrvD:InflowWind_CalcOutput:CalculateOutput:IfW_FlowField_GetVelAcc:Grid4DField_GetVel:Out
side the grid bounds.
T2:FARM_InitialCO:FWrap_t0:FAST_Solution0:CalcOutputs_And_SolveForInputs:SolveOption2:SolveOption2
c_Inp2AD_SrvD:InflowWind_CalcOutput:CalculateOutput:IfW_FlowField_GetVelAcc:Grid4DField_GetVel:Out
side the grid bounds.
T3:FARM_InitialCO:FWrap_t0:FAST_Solution0:CalcOutputs_And_SolveForInputs:SolveOption2:SolveOption2
c_Inp2AD_SrvD:InflowWind_CalcOutput:CalculateOutput:IfW_FlowField_GetVelAcc:Grid4DField_GetVel:Out
side the grid bounds.
Aborting FAST.Farm.
As I understand from the first few lines, I am using OpenFAST v3.5.2
Dear @ArnoldTUB,
I looked more closely at your FAST.Farm input file and believe I found the issue. The high-resolution domain of each turbine must full encompass all aerodynamic analysis nodes of the turbine. But your high-resolution domain is not tall enough for your turbine. That is, your high-resolution domains extend from 5 to 145 m above the ground, which is not sufficient given that the IEA Wind 3.4.MW reference wind turbine you are simulating has a hub height of 110 m and a 130-m rotor diameter.
Best regards,
Dear @jjonkman,
Thanks for pointing this out. The high-resolution domain in Z direction being too small makes sense to me. Once I fixed this I received the following error message:
As far as I understand there are issues with the low-resolution domain now which is why I increased the number of low-resolution spatial nodes in X direction. However, I am still left with the following error message
Do you have any idea what's causing this?
Dear @ArnoldTUB,
The warnings about the wake planes leaving the upper-most X boundary of the low-resolution domain are not a big concern because the wakes will simply leave and not affect the response of the wakes and turbines that remain in the domain. You can extend the domain to eliminate these warnings, but that would add computational expense for little benefit.
I'm not sure why you are receiving the same error about the high-resolution domain that you did before, but now 102 seconds into the simulation. There seems to now be a large enough spatial buffer of each high-resolution domain around each turbine so that the turbine deflections/displacements would not cause the turbines to leave the high-resolution domains. And I don't see any warnings about exceeding small angle approximation limits, which often implies unrealistic deflections. Can you confirm that the turbine deflections/displacements are not excessive? Do the errors go away if disable all structural degrees of freedom of the OpenFAST models?
Best regards,
Dear @jjonkman,
Thanks for the clarification regarding the warning messages. I adjusted the low-resolution domain to only encapsulate the volume of interest.
I am not sure how to disable all structural degrees of freedom. I found a DEGREES OF FREEDOM section in the ElastoDyn file, where I set all flags to false (FlapDOF1 and 2, EdgeDOF, DrTrDOF, GenDOF, TwFADOF1 and 2 and TwSSDOF1 and 2 were set to true before). However, the error prevailed. I switched turbine controllers and the error vanished. So apparently, something about how the turbines were controlled caused these issues. I would like to use the initial controllers, though. Do you have an idea how to debug this situation? I know I can switch an Echo flag in some files to true to get some insight but I am not sure what to look for. Perhaps something like hub or blade tip positions?
Dear @ArnoldTUB,
If disabling the structural DOFs did not resolve the issue, it is not large displacements that are causing the issue.
Can you clarify what you are changing in the controller? Are the two controllers you are using provided by NREL or something you developed yourself? Are the controllers trying to access wind at points that may reside outside the high-resolution domains?
Best regards,
Dear @jjonkman
The controller with which I receive no errors is based the variable-speed generator torque and collective pitch PI controller developed by NREL. The controller with which I do receive errors is an LQR that takes
as inputs. So to my knowledge none of them try to access wind at specific points but only wind provided by avrSWAP.
Dear @ArnoldTUBm
I'm not sure, but it sounds like the issue only occurs when using your own super controller and DISCON controller. Can you reproduce the error if you disable the super controller and use an NREL-provided controller such as the one for the NREL 5-MW baseline turbine or ROSCO?
Best regards,
Dear @jjonkman
I have access to the following controllers:
super controller (wind farm level)
wind turbine controller
I've run some tests and it seems like both super controllers, SC1 and SC2, work fine with WT2. I receive no errors. However, both super controllers yield similar error messages when run with WT1. Interestingly, both super controllers yield errors at 104 seconds run time. So it seems like WT1 is causing issues so I will try to analyze how this controller affects the turbines using the .ech files. Since my .fstf and inflow files seem fine, I am going to close this issue.
Thanks for your help!
Dear @jjonkman
just letting you know that I was able to solve this issue. The super controller miscalculated the demanded power such that the turbines were asked to generate more than what would be possible. I am not sure how exactly this caused the errors I received but after fixing the calculations I no longer receive these errors.
P.S.: The erros occured around 100 seconds simulation time because that's roughly the time frame where the downstream turbine is 'being hit' by the wakes caused by upstream turbines
I have a question: does the low-resolution pre-resolution need to be smaller than the wind field as the high-resolution?
Dear @3sdb,
I'm not sure I fully understand your question. We generally recommend for the low- and high-resolution domains in FAST.Farm to be aligned with the inflow data used as input to FAST.Farm. But certainly, the boundaries of the low- and high-resolution domains cannot reside outside the bounds of the inflow data used as input to FAST.Farm.
Best regards,
I'm sorry I didn't quite get it right. I'm having the same question, I've tried for a long time and still haven't solved it, please take a look at some of my errors and files. IEA-15-240-RWT_InflowFile.txt 13C.txt
Dear @3sdb,
I haven't fully reviewed your model set up, but as with your related question (https://github.com/OpenFAST/openfast/issues/2221), we generally recommend using the OpenFAST toolbox (https://github.com/OpenFAST/openfast_toolbox/tree/main/openfast_toolbox/fastfarm) when generating inflow and setting up FAST.Farm input files to ensure that you are following the FAST.Farm modeling guidance: https://openfast.readthedocs.io/en/main/source/user/fast.farm/ModelGuidance.html. From my quick glance at your files, it doesn't appear that are using the Python scripts to follow the modeling guidance.
Best regards,
Hello everyone!
I am trying to run a simulation FAST.Farm but end up receiving the following error:
I understand that there must be something wrong with how I set up the simulation grid but I have a hard time understanding what exactly causes this error, i.e., which of my input files needs to be updated. I also took a look at the Modeling Guidance section in the documentation but have a hard time to understand where I made a mistake regarding my input files.
Could you help me figuring out which parameters to adjust? Here are my primary FAST.Farm input file and my InflowWind file
threeTurbineCaseStudy.fstf (click to expand)
``` ------- FAST.Farm for OpenFAST INPUT FILE ------------------------------------------------- Simulation with three wind turbines, controlled by MPC --- SIMULATION CONTROL --- False Echo - Echo input data toInflowWind.dat (click to expand)
``` ------- InflowWind INPUT FILE ------------------------------------------------------------------------- 10 m/s steady wind without turbulence for case study --------------------------------------------------------------------------------------------------------------- False Echo - Echo input data toIf you need any other information please let me know!