WRF Domain wizard

R

Rajib Lochan Ram

New member
I want to create a nested domain using wrf domain wizard since i am facing difficulties in designing domain myself. Pls help how do i do it using wrf domain wizard using ubuntu?
 
Rajib Lochan Ram said:
I want to create a nested domain using wrf domain wizard since i am facing difficulties in designing domain myself. Pls help how do i do it using wrf domain wizard using ubuntu?
Click to expand...
first you need to know your map projection, after that you need to select area for first domain also configure the resolution as you need, after that you can go to nesting domain if you need to make more than 1 domain, make sure the nesting domain have integers number when it devide by the parent domain. other think like geog data and resolution of that data depands on your research
i ever make online domain wizard tutorial on my yt chanel you can watch that if you still need to figure it out
 
Ioga Lazuardi said:
first you need to know your map projection, after that you need to select area for first domain also configure the resolution as you need, after that you can go to nesting domain if you need to make more than 1 domain, make sure the nesting domain have integers number when it devide by the parent domain. other think like geog data and resolution of that data depands on your research
i ever make online domain wizard tutorial on my yt chanel you can watch that if you still need to figure it out
Click to expand...
Hii,
I want to create a nested domain to run wrf urban. the finest domain kml is provided. how do i do its parent domains? i want to know the basics of creaing the domain i.e how do i take the edges of the domain and all
 

Attachments

Rajib Lochan Ram said:
Hii,
I want to create a nested domain to run wrf urban. the finest domain kml is provided. how do i do its parent domains? i want to know the basics of creaing the domain i.e how do i take the edges of the domain and all
Click to expand...
looks like you want to create domain using 2 nested (3 domain) and for the third domain must be like what you send, usually i will make my last domain spatial resolution in 1km to create optimum result.

to create nesting domain we need to know that the recomended ratio between parent and nest is in ratio 3 or 5, larger than that it can be create error on interpolation the downscalling model also make the model unstable because the gap each domain to large,
some recomended nesting domain is 15km 5km 1km the ratio is 1:3:5, other is 9km, 3km, 1km the ratio is 1:3:3, the size that i said is about size on each grid like 15kmx15km each grid on first domain as parent for second domain, 5kmx5km each grid as second domain and the parent for third domain, 1kmx1km each grid for the third domain.

for the domain actually you can create random on first and second domain because all you need just the third domain, but i suggest for not to create large area on first domain and second because you not use it, so that can minimum your memory usage

the namelist.wps will automaticaly created after you process the selected area on domain wizard.

here some simple domain that i create using online domain wizard:
first
&share
wrf_core = 'ARW'
max_dom = 3
start_date = '2024-09-01_03:00:00', '2024-09-01_03:00:00', '2024-09-01_03:00:00'
end_date = '2024-09-01_18:00:00', '2024-09-01_18:00:00', '2024-09-01_18:00:00'
interval_seconds = 21600
io_form_geogrid = 2
debug_level = 0
/

&geogrid
parent_id = 1, 1, 2
parent_grid_ratio = 1, 5, 3
i_parent_start = 1, 11, 43
j_parent_start = 1, 8, 40
e_we = 41, 96, 49
e_sn = 33, 91, 46
geog_data_res = '2m', 'default', 'default'
dx = 15000
dy = 15000
map_proj = 'mercator'
ref_lat = 28.677
ref_lon = 77.064
truelat1 = 27.866
pole_lat = 90
pole_lon = 0
geog_data_path = 'geog'
opt_geogrid_tbl_path = './geogrid/'
/

&ungrib
out_format = 'WPS'
prefix = 'FILE'
/

&metgrid
fg_name = 'FILE'
io_form_metgrid = 2
opt_metgrid_tbl_path = './metgrid'
/

second
&share
wrf_core = 'ARW'
max_dom = 3
start_date = '2024-09-01_03:00:00', '2024-09-01_03:00:00', '2024-09-01_03:00:00'
end_date = '2024-09-01_18:00:00', '2024-09-01_18:00:00', '2024-09-01_18:00:00'
interval_seconds = 21600
io_form_geogrid = 2
debug_level = 0
/

&geogrid
parent_id = 1, 1, 2
parent_grid_ratio = 1, 3, 3
i_parent_start = 1, 9, 23
j_parent_start = 1, 8, 22
e_we = 36, 58, 49
e_sn = 31, 55, 46
geog_data_res = '2m', 'default', 'default'
dx = 9000
dy = 9000
map_proj = 'mercator'
ref_lat = 28.597
ref_lon = 77.018
truelat1 = 27.866
pole_lat = 90
pole_lon = 0
geog_data_path = 'geog'
opt_geogrid_tbl_path = './geogrid/'
/

&ungrib
out_format = 'WPS'
prefix = 'FILE'
/

&metgrid
fg_name = 'FILE'
io_form_metgrid = 2
opt_metgrid_tbl_path = './metgrid'
/

i make in 45km y axis and 48km on x axis on the third domain to get all the area that you use, for the geog data res, that depands on resolution that you need in high resolution or low resolution on static geographical data also the geographical data that you need to calculate (you can check that on WPS_GEOG), also on the namelist.wps theres 4 section, you can learn that from wps manual book, usualy just the first and second section that need to edit, on first on the time and interval data, and second on the geog data that will be use.

here some information that i can give to you about creating domain based on my experience as beginner on wrf
 
William.Hatheway said:
Try this:

WRF Domain Wizard

HTML implementation of GUI for the WRF Preprocessor System (WPS) and namelist.input
wrfdomainwizard.net wrfdomainwizard.net

This is something I have been developing with a colleague
Click to expand...
I am using this currently. For the dx and dy parameters for the outermost grid - I am usng the gfs 0.25 x0.25 file is this the appropriate value 27750 ?

111 kms is the distance between latitudes and when you multiply by 0.25 degrees you get 27.75 km which is 27750 meters and this is for the lat lon grid/
 
No not really. I am a bit confused between the definition of dx and how you apply it for each domain. My GFS grid is 0.25 x 0.25 degrees. How does that grid spacing relate to the definition of the dx and dy variable for each domain ?
 
Please run official WPS to create WRF domain. We know that the domain-wizard sometimes may cause issues and we don't support this option.
 
Thanks for answering many questions in the Forum.
Yes please recommend users to employ the standard WPS package to create WRF domain.
 
Ming Chen said:
Thanks for answering many questions in the Forum.
Yes please recommend users to employ the standard WPS package to create WRF domain.
Click to expand...
I'm going to say that user generated content shouldn't even be allowed here. If it isn't from ncar then it shouldn't be allowed and if it is no longer being developed it shouldn't be supported any more by users or the forum.

I also feel that there needs to be more clear transition to mpas and away from wrf completely. Meaning the wrf section is not the primary focus of this forum.
 
We would this Forum to be a place for discussion and a resource for users to ultimately help themselves.

NCAR continues to provide support for WRF because of the large number of WRF users. Also, it takes time for the community to adapt to MPAS.
 
RCarpenter said:
This is a very nice tool that I was not aware of. Another tool you might be interested in QGIS with the GIS4WRF GIS4WRF plugin.
Click to expand...
Ioga Lazuardi said:
looks like you want to create domain using 2 nested (3 domain) and for the third domain must be like what you send, usually i will make my last domain spatial resolution in 1km to create optimum result.

to create nesting domain we need to know that the recomended ratio between parent and nest is in ratio 3 or 5, larger than that it can be create error on interpolation the downscalling model also make the model unstable because the gap each domain to large,
some recomended nesting domain is 15km 5km 1km the ratio is 1:3:5, other is 9km, 3km, 1km the ratio is 1:3:3, the size that i said is about size on each grid like 15kmx15km each grid on first domain as parent for second domain, 5kmx5km each grid as second domain and the parent for third domain, 1kmx1km each grid for the third domain.

for the domain actually you can create random on first and second domain because all you need just the third domain, but i suggest for not to create large area on first domain and second because you not use it, so that can minimum your memory usage

the namelist.wps will automaticaly created after you process the selected area on domain wizard.

here some simple domain that i create using online domain wizard:
first
&share
wrf_core = 'ARW'
max_dom = 3
start_date = '2024-09-01_03:00:00', '2024-09-01_03:00:00', '2024-09-01_03:00:00'
end_date = '2024-09-01_18:00:00', '2024-09-01_18:00:00', '2024-09-01_18:00:00'
interval_seconds = 21600
io_form_geogrid = 2
debug_level = 0
/

&geogrid
parent_id = 1, 1, 2
parent_grid_ratio = 1, 5, 3
i_parent_start = 1, 11, 43
j_parent_start = 1, 8, 40
e_we = 41, 96, 49
e_sn = 33, 91, 46
geog_data_res = '2m', 'default', 'default'
dx = 15000
dy = 15000
map_proj = 'mercator'
ref_lat = 28.677
ref_lon = 77.064
truelat1 = 27.866
pole_lat = 90
pole_lon = 0
geog_data_path = 'geog'
opt_geogrid_tbl_path = './geogrid/'
/

&ungrib
out_format = 'WPS'
prefix = 'FILE'
/

&metgrid
fg_name = 'FILE'
io_form_metgrid = 2
opt_metgrid_tbl_path = './metgrid'
/

second
&share
wrf_core = 'ARW'
max_dom = 3
start_date = '2024-09-01_03:00:00', '2024-09-01_03:00:00', '2024-09-01_03:00:00'
end_date = '2024-09-01_18:00:00', '2024-09-01_18:00:00', '2024-09-01_18:00:00'
interval_seconds = 21600
io_form_geogrid = 2
debug_level = 0
/

&geogrid
parent_id = 1, 1, 2
parent_grid_ratio = 1, 3, 3
i_parent_start = 1, 9, 23
j_parent_start = 1, 8, 22
e_we = 36, 58, 49
e_sn = 31, 55, 46
geog_data_res = '2m', 'default', 'default'
dx = 9000
dy = 9000
map_proj = 'mercator'
ref_lat = 28.597
ref_lon = 77.018
truelat1 = 27.866
pole_lat = 90
pole_lon = 0
geog_data_path = 'geog'
opt_geogrid_tbl_path = './geogrid/'
/

&ungrib
out_format = 'WPS'
prefix = 'FILE'
/

&metgrid
fg_name = 'FILE'
io_form_metgrid = 2
opt_metgrid_tbl_path = './metgrid'
/

i make in 45km y axis and 48km on x axis on the third domain to get all the area that you use, for the geog data res, that depands on resolution that you need in high resolution or low resolution on static geographical data also the geographical data that you need to calculate (you can check that on WPS_GEOG), also on the namelist.wps theres 4 section, you can learn that from wps manual book, usualy just the first and second section that need to edit, on first on the time and interval data, and second on the geog data that will be use.

here some information that i can give to you about creating domain based on my experience as beginner on wrf
Click to expand...


William.Hatheway

Thread 'WRF Configuration Studio is a browser-based configuration environment for the Weather Research and Forecasting Model'

WRF Configuration Studio v1.0.0 is now available for public testing.


Website: WRF Configuration Studio v1.0.0

GitHub: GitHub - HathewayWill/WRFConfigurationStudio: WRF Config Studio is a browser-based configuration tool for designing WRF domains, editing namelist.wps and namelist.input, exporting OBSPROC namelists, and reviewing WRF, WRFDA, OBSPROC, and Registry metadata.


The Weather Research and Forecasting Model is incredibly flexible, but that flexibility comes with a cost: many configuration choices have to be correct before...
  • Like
 
You must log in or register to reply here.
Back
Top