Skip to content
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

A Question About Inflow Wind #2137

Open
shipors opened this issue Apr 2, 2024 · 7 comments
Open

A Question About Inflow Wind #2137

shipors opened this issue Apr 2, 2024 · 7 comments

Comments

@shipors
Copy link

shipors commented Apr 2, 2024

hello everyone,

I want to set the input wind speed position of wind turbine to 100 meters in front of the machine, can I set the WindVxiList parameter in the InflowWind INPUT FILE to -100 to achieve it?

In addition, when turbsim generates the BTS file, can I set the parameter Z0 to achieve different surface roughness?

thanks.

@jjonkman
Copy link
Collaborator

jjonkman commented Apr 2, 2024

Dear @shipors,

InflowWind input WindVxiList sets the location of the sensors used by InflowWind to output ambient wind through the OutList. InflowWind doesn't allow you to specify the x-location of the wind field coming from TurbSim, if that is what you are asking about.

Regarding TurbSim input Z0, this input defines the surface roughness length if you've selected the logarithmic vertical wind profile (WindProfileType = "LOG").

Best regards,

@shipors
Copy link
Author

shipors commented Apr 3, 2024

dear @jjonkman

I wonder if it is possible to set the X-direction position of the input wind when generating a wind speed file using TurbSim, meaning I would like to shift the generated wind from the hub location to 100 meters ahead of the turbine. Is this achievable?

Best wishes.

@jjonkman
Copy link
Collaborator

jjonkman commented Apr 3, 2024

Dear @shipors,

InflowWind input XOffset is supported for HAWC-formatted wind data files to shift the wind data along the X axis, but I don't recall why this feature was not added for TurbSim-formatted wind data files when XOffset was implemented. My guess is the implementation would not be too difficult, but would require a source code change.

Best regards

@shipors
Copy link
Author

shipors commented Apr 4, 2024

Dear @jjonkman,

Ok thanks for your reply. I have two more queries that I would like to seek help.

First, I noticed that when selecting WindType as HAWC format in the InflowWind INPUT FILE, I need to enter u, v, w-component fluctuating wind. If all wind speeds in the v and w directions are set to 0m/s, will it affect the wind speed input in the X direction?

Secondly, I would like to know if the wind speed and turbulence intensity changes between the positions (100, 0, 0) and (200, 0, 0)? The above question assumes that there is no wind turbine drawing kinetic energy from the turbulent wind, and is not affected by other conditions, and that the wind speed starts at (0, 0, 0).

Best wishes.

@jjonkman
Copy link
Collaborator

jjonkman commented Apr 4, 2024

Dear @shipors,

Regarding (1), the u, v, and w components are specified independently, so, zeroing v and w will not change u.

Regarding (2), the Mann box is a rectangular box in 3D containing frozen turbulence (that does not change in time). In InflowWind, this box is made 4D (3D space + 1D time) by propagating the box along the mean wind direction at the hub-height wind speed. So at a fixed (Y,Z) point at different X locations (assuming X is along the mean wind direction), the wind speed will change in time and the TI will remain constant. The TI may change between different (Y,Z) points.

Best regards,

@shipors
Copy link
Author

shipors commented Apr 7, 2024 via email

@jjonkman
Copy link
Collaborator

jjonkman commented Apr 8, 2024

Dear @shipors,

I'm not sure I fully understand your question. Just a couple comments:

If you use Mod_AmbWind = 2 or 3 in FAST.Farm, using InflowWind to set the wind data, and are using WindType = 1 or 2, the wind will be spatially uniform throughout the farm. If you use WindType = 3, 4, 5, or 7, the wind will propagate based on Taylor's frozen turbulence assumption. If you use WindType = 6 (user defined), you can define your own wind function (requiring a recompile of FAST.Farm).

If you use Mod_AmbWind = 1 in FAST.Farm, the wind inflow is expected to be four dimensional (u, v, and w defined in 3D space + time).

Best regards,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants