about parent_id

[kinguEnt]

I run geogrid.exe, ungrib.exe and metgrid.exe with a parent_id, 1, 1, 2, 3. when I run real.exe, an error related to boundary condition occurred. Which parent_id is correct for four domains; 1, 1, 2, 3, or 0, 1, 2, 3?

 

[kwerner]

Hi,
The setting of = 1, 1, 2, 3 should be correct. If that is what you are using, can you send the error log with the error message? If you have multiple error logs (e.g., rsl.error.*), can you package those into a single *.tar file and attach that, along with your full namelist.input file? Thanks.

 

[kinguEnt]

Sorry for my late reply. I attached below the associated files.
Thanks.

 

[kwerner]

Thanks for sending that. The error message is

 *** Error in boundary condition specification
  boundary conditions at xs            0
  boundary conditions at xe            0
  boundary conditions at ys            0
  boundary conditions at ye            0
  boundary conditions logicals are
  periodic_x    F
  periodic_y    F
  symmetric_xs  F
  symmetric_xe  F
  symmetric_ys  F
  symmetric_ye  F
  open_xs       F
  open_xe       F
  open_ys       F
  open_ye       F
  polar         F
  nested        F
  specified     F
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE:  <stdin>  LINE:     165
 *** Error in boundary condition specification
-------------------------------------------

This indicates there is something wrong with the &bdy_control section of your namelist. When I look at your namelist.input file, it just stops after the &dynamics section, with no &bdy_control section present. Additionally, the &dynamics section does not have a closing "/". Can you add that forward slash after the dynamics section (see other sections to see how they are done), and then add this below it. Then save the modified namelist.input file and try again.

 &bdy_control
 spec_bdy_width                      = 5,
 specified                           = .true.
 /
 
 &grib2
 /
 
 &namelist_quilt                     
 nio_tasks_per_group = 0,           
 nio_groups = 1,
 /

 

[kinguEnt]

Thank you kwerner.

 

[kinguEnt]

When I move forward, the following errors happened during real.exe. It creates only wrfinput_d01 and wrfinput_d02 with wrfbdy_d01 but, wrfinput_d03 and wrfinput_d04 are not created. For further, I attached additional files. Anyone suggest me how to fix?


starting wrf task 0 of 1

===================================================================================
= BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
= PID 627814 RUNNING AT negusu-OptiPlex-3060
= EXIT CODE: 9
= CLEANING UP REMAINING PROCESSES
= YOU CAN IGNORE THE BELOW CLEANUP MESSAGES
===================================================================================
YOUR APPLICATION TERMINATED WITH THE EXIT STRING: Killed (signal 9)
This typically refers to a problem with your application.
Please see the FAQ page for debugging suggestions

 

[Liangcheng Qiu]

Have you resolved the issue you encountered? I'm facing the same problem. Thank you.

Thanks for sending that. The error message is

 *** Error in boundary condition specification
  boundary conditions at xs            0
  boundary conditions at xe            0
  boundary conditions at ys            0
  boundary conditions at ye            0
  boundary conditions logicals are
  periodic_x    F
  periodic_y    F
  symmetric_xs  F
  symmetric_xe  F
  symmetric_ys  F
  symmetric_ye  F
  open_xs       F
  open_xe       F
  open_ys       F
  open_ye       F
  polar         F
  nested        F
  specified     F
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE:  <stdin>  LINE:     165
 *** Error in boundary condition specification
-------------------------------------------

This indicates there is something wrong with the &bdy_control section of your namelist. When I look at your namelist.input file, it just stops after the &dynamics section, with no &bdy_control section present. Additionally, the &dynamics section does not have a closing "/". Can you add that forward slash after the dynamics section (see other sections to see how they are done), and then add this below it. Then save the modified namelist.input file and try again.

 &bdy_control
 spec_bdy_width                      = 5,
 specified                           = .true.
 /
 
 &grib2
 /
 
 &namelist_quilt                    
 nio_tasks_per_group = 0,          
 nio_groups = 1,
 /

Have you resolved the issue you encountered? I'm facing the same problem. Thank you.

 

[kinguEnt]

Have you resolved the issue you encountered? I'm facing the same problem. Thank you.

Have you resolved the issue you encountered? I'm facing the same problem. Thank you.

Hi Liangcheng Qiu,
Have you tried what Kwerner has suggested here in this post?

 

[Liangcheng Qiu]

&bdy_control
spec_bdy_width = 5,
spec_zone = 1,
relax_zone = 4,
specified = .false.,
nested = .false.,
polar = .true.,
periodic_x = .true.,

&dynamics
fft_filter_lat = 45.,

thanks for your response. I followed the modifications to the relevant variables as suggested in your forum post, but the issue still persisted. However, after making changes based on another post, I was able to run WRF successfully. Here is the link for your reference: https://forum.mmm.ucar.edu/threads/error-in-boundary-condition-specification.16522/post-48149

 

[kinguEnt]

thanks for your response. I followed the modifications to the relevant variables as suggested in your forum post, but the issue still persisted. However, after making changes based on another post, I was able to run WRF successfully. Here is the link for your reference: https://forum.mmm.ucar.edu/threads/error-in-boundary-condition-specification.16522/post-48149

Thank you for sharing.