Dear @Jason.Jonkman
I was trying to run an OpenFast simulation and got the following error.
In the wind files and the .fst files and I couldn’t find the number 51.158m mentioned in the error.
Dear @Jason.Jonkman
I was trying to run an OpenFast simulation and got the following error.
In the wind files and the .fst files and I couldn’t find the number 51.158m mentioned in the error.
Dear @Karthik.Prakash,
The AeroDyn module of OpenFAST needs to be able to access ambient wind data at all aerodynamic analysis nodes along the blades and tower at all time steps. The undisplaced/undeflected positions of each aerodynamic analysis node are specified in the AeroDyn input file(s), but these positions will change as a result of turbine displacement/deflection over time. It is this displaced/deflected position that is mentioned in the error. In your case, it looks like a node is below the grid.
Best regards,
Dear @Jason.Jonkman
Thanks a lot for getting back. Which parameter in which file should be changed to remove this error. Is it the below Grid height and Grid Width paramter in .inp file for creating Wind from Turbsim that has to be changed. (Below, I don’t know the shaft length, so I assumed a much higher number than rotor dia to cover the rotor). I took the rotor dia. (or radius from ElastoDyn file, 63 TipRad - The distance from the rotor apex to the blade tip (meters)).
90 HubHt - Hub height [m] (should be > 0.5*GridHeight)
120 GridHeight - Grid height [m]
120 GridWidth - Grid width [m] (should be >= 2*(RotorRadius+ShaftLength))
Dear @Karthik.Prakash,
Your GridHeight
and GridWidth
are too small for the NREL 5-MW baseline wind turbine, which has a rotor diameter of 63*2 = 126 m. I would typically use a 10% margin to account for displacement/deflection, so, I would suggest using about 140 m.
Best regards,
Thanks a lot for getting back. I made the Grid height and Width to 150, but got the below error. Should The grid width and height cover the tower also, for example Grid height or width = Rotor dia + hub height ?
Dear @Karthik.Prakash,
If you have tower aerodynamics enabled, you likely have aerodynamic nodes that extend along the tower well below the rotor. You can generate wind there by setting GridHeight
larger than GridWidth
(see Figure 5 in the TurbSim documentation for more information: https://www.nrel.gov/wind/nwtc/assets/downloads/TurbSim/TurbSim_v2.00.pdf) or by outputting from TurbSim wind along the tower (WrADTWR
= TRUE). You can also eliminate tower aerodynamic nodes that extend below the wind domain.
Best regards,
Dear @Jason.Jonkman ,
Thanks a lot for getting back. I have few queries:
Dear @Karthik.Prakash,
Here are my responses:
The tower section of the AeroDyn input file is used when TwrPotent
> 0, TwrShadow
> 0, or TwrAero
= TRUE. TwrAero
is likely not important during operational conditions, but is likely important during parked/idling conditions. TwrPotent
is likely important for upwind rotors that are operational, TwrShadow
is likely important for downwind rotors that are operational.
It is up to you to make modeling choices that meet your needs. You must ensure that all aerodynamic analysis nodes, which are defined by you in the AeroDyn input file, fall within the wind domain, which is also defined by you.
The aerodynamic nodes along the tower are located via input TwrElev
in the tower section of the AeroDyn input file. The lowest value of TwrElev
must be above the lowest boundary of the wind domain.
Best regards,