Scheduled Downtime
On Friday 21 April 2023 @ 5pm MT, this website will be down for maintenance and expected to return online the morning of 24 April 2023 at the latest

Vortex following issue

L

ltt

New member
Hi all, I am running a simulation with two domains (d01 is static, d02 is moving). Different corral_dist settings were tried to make the inner grid move, however, no success was found. It appeared in the following situations:

1. With the corral_dist (e.g., 70) smaller than the current closet distance between d01 and d02 boundaries (i.e. 80 d01 grid points), the model crashed with the following error message (as shown in rsl.error.0000_1):
forrtl: severe (408): fort: (2): Subscript #1 of the array I_START has value 2 which is greater than the upper bound of 1
Click to expand...
2. With the corral_dist (e.g., 190) larger than all distances between d01 and d02 boundaries, the model ran throughout the simulation, but d02 was prevented to move (as shown in rsl.error.0000_2).
MOAD can not move. Cancelling nest move in X.
MOAD can not move. Cancelling nest move in Y
Click to expand...
If the corral_dist is in range of (80,180), the nest could not move in Y direction and the error as in #1 also occurred.

I would appreciate any suggestions to make the vortex following work with this two-domain configuration. Warm regards
 

Attachments

  • namelist.input
    5.7 KB · Views: 17
  • rsl.error.0000_1.txt
    5.6 KB · Views: 6
  • rsl.error.0000_2.txt
    12.3 KB · Views: 1
There are a few issues in your namelist.input:

(1) end_year = 2017, 2017, 2017,
end_month = 03, 03, 03,
end_day = 25, 26, 26,
end_hour = 06, 00, 00,

Note that D01 end time cannot be earlier than that of D2. please change the option.
(2) for dx = 5000, 1000, time step = 1 is too small. Please change it to 30
(3) diff_opt and km_opt should be specified for all domains.
(4) corral_dist = 70 for D02 is too large. Can you try with the number of 8 or 12?

By the way, how did you compile this case?
 
Hi Ming,

Thank you for pointing out the issues in the namelist file! I have revised it following your suggestions, but unfortunately, the model still crashed with the same error as below.

Input data is acceptable to use:
WRF NUMBER OF TILES FROM OMP_GET_MAX_THREADS = 1
Tile Strategy is not specified. Assuming 1D-Y
WRF TILE 1 IS 418 IE 501 JS 1 JE 63
WRF NUMBER OF TILES = 1
WRF NUMBER OF TILES FROM OMP_GET_MAX_THREADS = 1
Tile Strategy is not specified. Assuming 1D-Y
WRF TILE 1 IS 418 IE 501 JS 1 JE 63
WRF NUMBER OF TILES = 1
forrtl: severe (408): fort: (2): Subscript #1 of the array I_START has value 2 which is greater than the upper bound of 1

Image PC Routine Line Source
wrf.exe 00000000025440CC module_tiles_mp_s 185 module_tiles.f90
wrf.exe 0000000002443EE8 solve_em_ 437 solve_em.f90
wrf.exe 000000000214FE87 solve_interface_ 122 solve_interface.f90
wrf.exe 000000000059BC8F module_integrate_ 339 module_integrate.f90
wrf.exe 000000000059D036 module_integrate_ 376 module_integrate.f90
wrf.exe 00000000004177A4 module_wrf_top_mp 325 module_wrf_top.f90
wrf.exe 0000000000417748 MAIN__ 30 wrf.f90
wrf.exe 000000000041769D Unknown Unknown Unknown
Click to expand...

About the compilation process, I used the following options:
Compiler choice: (dm+sm) INTEL (ifort/icc): CL/SL less opt
Nesting option: 3

I am using version 4.0.3, have you heard of any problems with this version? I also tried with the idealized simulation and found the same issue.

With thanks,
 
Please recompile WRF in dmpar mode and with the vortex-following option. Then rerun this case.
Please keep me updated about the output. Thanks.
 
Hi Ming, I am sorry for the delayed response as I wanted to test with different versions of WRF (4.0.3 & 4.1.1). The compilations with the dm option did solve the problem in both versions. The nests are now able to follow the vortex. Thank you very much for your help!
 
All the options in namelist.input are same as that without moving nest, except that you should include the following options in &domains:

vortex_interval = 15, 15, 15,
max_vortex_speed = 40, 40, 40,
corral_dist = 8, 12, 12,
track_level = 70000,
time_to_move = 0,

Note that the above are just examples, and you need to set these options based on your case.
 
Sir , at the initial step don't we have to define the inital nested domain positions?
And sir , please tell me the output varibales in the wrfoutput file corresponding to the vortex followinf WRF run?
 
Last edited:
Please take a look at the document here, which describes in detail how to run vortex-following.

Please clarify what variables you intend to look. I am not quite sure what are "output varibales in the wrfoutput file corresponding to the vortex following".
 
I am attaching the namelist file below. My run is blowing off showing , 'horizontal interp error - lake ( 258, 606), using average -0.0113' . Kindly resolve this .
 

Attachments

  • namelist.input
    4.2 KB · Views: 5
A few options in your namelist.input look unreasonable. Specifically,

Code: 
i_parent_start           = 1,        48,      387,
j_parent_start           = 1,        41,      164,
corral_dist              = 0,        70,       70,

Your D02 starts at grid (48, 41) of D01. However, you set corral_dist = 70, which is the distance in the number of coarse grid cells that the moving nest is allowed to get near the mother domain boundary. It is inconsistent with setttings of i_parent_start and j_parent_start .

Please read carefully the document how to employ moving nest and set correct options.
 
You must log in or register to reply here.
Top