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

namelist.input and input data mismatch

This post was from a previous version of the WRF&MPAS-A Support Forum. New replies have been disabled and if you have follow up questions related to this post, then please start a new thread from the forum home page.

Shihao Zeng

New member
I have the trouble with inconsistence of data input from namelist.input and input data. BUT when I changed my namelist.input, it still gets the same error. Then I did an experiment that I deleted the dx and dy value in my namelist.input, it still gets the same bad results. I wonder if this bug is connected with my previous run?
For desciption of this run, it's a LES run, I want to run ndown.exe with a coarser domain(dx=1350) and d01(dx=450) in this namelist...
 

Attachments

  • namelist.input
    3.8 KB · Views: 120
  • rsl.error.0000.txt
    2 KB · Views: 68
Is this a nesting run with three domains? Please send me your namelist.wps to take a look. Also, please let me know what data you used to drive the model. Specifically, please save the output of the command ncdump -h met_em.d01 and send it to me. Thanks.
 
Hi thanks for your reply. This run contains 6 domains with nested condition. And I have run real.exe and wrf.exe the first 3 domains already, then I wish to run the d04-d06 as what I wrote in namelist.input as d01-d03 for real.exe, and do one-way ndown.exe and wrf.exe for each domain.
Someone says it may help by use ./clean but I don't really know if it has some risks on it.
 

Attachments

  • met.log
    16.8 KB · Views: 65
  • namelist.wps
    1 KB · Views: 77
Ming Chen said:
Is this a nesting run with three domains? Please send me your namelist.wps to take a look. Also, please let me know what data you used to drive the model. Specifically, please save the output of the command ncdump -h met_em.d01 and send it to me. Thanks.
By changing all the variable I can imagine in &domain, I found that when I change time_step from 10/9 to 1, it successfully runs. So then maybe there's something wrong with the 10/9 itself... And if I try 1.11111 or 1.1, it goes wrong, and the rsl.error are like the same. That's strange. I still want to know how can I do a time_step like 10/9 there.
 
I don't think the settings are correct in your case.
(1) namelist.wps indicates you run a 6-domain nesting case, but namelist.input shows this is a 3-domain nesting run
(2) in namelist,wps, you have the grid numbers
e_we = 91, 91, 91, 91, 91, 100,
e_sn = 82, 82, 82, 82, 82, 100,
but in namelist.input, your grid numbers are
e_we = 91, 91, 100,
e_sn = 82, 82, 100,
Note that grid numbers in D03 are wrong.
(3) time step should be six times of the grid interval of the outermost domain. In your case, it should be 72.
 
Top