Skip to content

WRF 4.6 windfarm new bug #2200

Closed
Closed
@DingZL1207

Description

@DingZL1207

I found that in WRF version 4.6, there is more support for the WINDFARM module, so I followed the tutorial in c50bf2a to fill in the namelist.input file. After doing so, I noticed that when windfarm_opt (max_dom) = 2, there is completely no wind farm wake effect. This is because when I set it to 1, I could clearly observe the wake effect, as shown in Figure 1 (windfarm_opt=1) and Figure 2 (windfarm_opt=2):

Image

Image

Attached is the &physics section from my namelist.inpt:
&physics
physics_suite = 'CONUS'
mp_physics = -1, -1,-1,
cu_physics = -1, -1,-1,
ra_lw_physics = -1, -1,-1,
ra_sw_physics = -1, -1,-1,
bl_pbl_physics = -1, -1,-1,
sf_sfclay_physics = -1, -1,-1,
sf_surface_physics = -1, -1,-1,
radt = 15, 15,15,
bldt = 0, 0,0,
cudt = 0, 0,0,
icloud = 1,
num_land_cat = 21,
sf_urban_physics = 0, 0,0,
fractional_seaice = 1,
windfarm_opt = 2, 2, 2,
windfarm_ij = 0
windfarm_wake_model = 2,
windfarm_overlap_method = 4,
windfarm_deg = 0,
windfarm_tke_factor = 0.25 ,

Also, I don't know if it's a problem with windfarm_ij because in the description in the link above:

“windfarm_ij = 0 ! whether to use lat-lon or i-j coordinate as wind turbine locations
! 0 = The coordinate of the turbines are defined in terms of lat-lon
! 1 = The coordinate of the turbines are defined in terms of grid points
! 2 = Valid only with windfarm_opt=2. The coordinate of the turbines are defined
in terms of lat-lon with the filename of 'windturbines-ll.txt'“

Above mentioned that when windfarm_opt is set to 2, should set windfarm_ij=2, at the same time also needs a 'windturbines-ll.txt' file, but I do not know what the internal format of 'windturbines-ll.txt' looks like, need a clearer description.
Summarize the problems as follows:
1.windfarm_opt =2, windfarm_ij=0, did not find the wind farm's wake;
2.windfarm_ij setting problem, when windfarm_opt=2, windfarm_ij tried to set to 2, and I renamed 'windturbines.txt' to ''windturbines-ll.txt'' then directly reported an error;

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions