Idealized Case em_seabreeze2d_x

[Claudio.Iturra]

Dear Community,

I am currently working on generating wind velocity simulations based on changes in radiation, specifically for simulating sea-breeze phenomena. Through a Google search, I discovered that the idealized case em_seabreeze2d_x in WRF can assist me in achieving this simulation.

Following the installation process (thanks youtube!), I executed the ./compile em_seabreeze2d_x command, resulting in the generation of two files, namely ideal.exe and wrf.exe. Additionally, the file wrfout_d01_2007-06-01_05:00:00 was generated. Upon checking the variables using MATLAB ncdisp and ncread, everything seems to be in order.

Now, I am aiming to generate a 5-day output at an hourly resolution for my desired longitude and latitude near the coastal area of Concepción. As I begin editing the namelist.input, I am uncertain about where to find information about all the variables in that file and what modifications I need to make to the code (also interested in learning the physics used for that simulation).

I would greatly appreciate any suggestions or guidance on learning about the variables in the namelist.input file and understanding the necessary modifications. Thank you to all.

Best regards,

 

[Ming Chen]

Hi,
The ideal case is not designed to run over a specific region. It is a more general approach to simulate sea-breeze, which can be anywhere on the earth surface. To run this ideal case, you can go to WRF/test/em_seabreeze2d_x, then run ./ideal.exe and ./wrf.exe using the default namelist.input.
This will give you some idea how this case works.

 

[Claudio.Iturra]

Hello Ming, thanks for your reply. I already run the em_seabreeze2d_x with the default namelist.input. ,that just covers a couples of hours (can I extend that period for 2 days?). In the README.seabreeze file located in WRF/test/em_seabreeze2d_x the following description is found :

Note that since the longitude is set to zero, start_hour in the namelist
is the local time as well as the UTC time (5Z in the namelist).
For other longitudes the start_hour refers to UTC time.

So, following that description, can I change the longitude/latitude? of the namelist.imput file?, I'm apologize if this is a really basic question, I'm a 2 days new user to WRF.

Thanks Ming

namelist.input>>

&time_control
run_days = 0,
run_hours = 12,
run_minutes = 0,
run_seconds = 0,
start_year = 2007, % 2005
start_month = 06, % 1
start_day = 1, % 1
start_hour = 5, % 0
start_minute = 00,
start_second = 00,
end_year = 2007, % 2005
end_month = 06, % 1
end_day = 2, % 2
end_hour = 5, % 23
end_minute = 00,
end_second = 00,
history_interval = 30,
frames_per_outfile = 1000,
restart = .false.,
restart_interval = 360,
io_form_history = 2
io_form_restart = 2
io_form_input = 2
io_form_boundary = 2
/

&domains
time_step = 15,
time_step_fract_num = 0,
time_step_fract_den = 1,
max_dom = 1,
s_we = 1,
e_we = 202,
s_sn = 1,
e_sn = 3,
s_vert = 1,
e_vert = 35,
dx = 2000,
dy = 2000,
ztop = 20000.,
eta_levels = 1.000, 0.993, 0.983, 0.970, 0.954,
0.934, 0.909, 0.880, 0.845, 0.807,
0.765, 0.719, 0.672, 0.622, 0.571,
0.520, 0.468, 0.420, 0.376, 0.335,
0.298, 0.263, 0.231, 0.202, 0.175,
0.150, 0.127, 0.106, 0.088, 0.070,
0.055, 0.040, 0.026, 0.013, 0.000

 

[Ming Chen]

Hello Ming, thanks for your reply. I already run the em_seabreeze2d_x with the default namelist.input. ,that just covers a couples of hours (can I extend that period for 2 days?). In the README.seabreeze file located in WRF/test/em_seabreeze2d_x the following description is found :

Yes you can extend the integration time to 2 days.

Note that since the longitude is set to zero, start_hour in the namelist
is the local time as well as the UTC time (5Z in the namelist).
For other longitudes the start_hour refers to UTC time.

So, following that description, can I change the longitude/latitude? of the namelist.imput file?, I'm apologize if this is a really basic question, I'm a 2 days new user to WRF.

lat/lon are not namelis options. please take a look at the code module_initialize_ideal.F, in which you can find the following piece of code:
CASE(seabreeze2d_x)



mminlu2 = ' '

mminlu2(1:4) = 'USGS'

CALL nl_set_mminlu(1, mminlu2)

! CALL nl_set_mminlu(1, 'USGS')

CALL nl_set_iswater(1,16)

CALL nl_set_isice(1,3)

CALL nl_set_cen_lat(1,20.)


CALL nl_set_cen_lon(1, 0.)

You can change lat/lon here.

Thanks Ming

namelist.input>>

&time_control
run_days = 0,
run_hours = 12,
run_minutes = 0,
run_seconds = 0,
start_year = 2007, % 2005
start_month = 06, % 1
start_day = 1, % 1
start_hour = 5, % 0
start_minute = 00,
start_second = 00,
end_year = 2007, % 2005
end_month = 06, % 1
end_day = 2, % 2
end_hour = 5, % 23
end_minute = 00,
end_second = 00,
history_interval = 30,
frames_per_outfile = 1000,
restart = .false.,
restart_interval = 360,
io_form_history = 2
io_form_restart = 2
io_form_input = 2
io_form_boundary = 2
/

&domains
time_step = 15,
time_step_fract_num = 0,
time_step_fract_den = 1,
max_dom = 1,
s_we = 1,
e_we = 202,
s_sn = 1,
e_sn = 3,
s_vert = 1,
e_vert = 35,
dx = 2000,
dy = 2000,
ztop = 20000.,
eta_levels = 1.000, 0.993, 0.983, 0.970, 0.954,
0.934, 0.909, 0.880, 0.845, 0.807,
0.765, 0.719, 0.672, 0.622, 0.571,
0.520, 0.468, 0.420, 0.376, 0.335,
0.298, 0.263, 0.231, 0.202, 0.175,
0.150, 0.127, 0.106, 0.088, 0.070,
0.055, 0.040, 0.026, 0.013, 0.000