likeyou511
New member
When I run wrf.exe, it always stops after 3h12min and there is no error.
Why is this?
Why is this?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Some problems about the ./wrf.exe
- Thread starter likeyou511
- Start date
likeyou511
New member
I have some concerns of your namelist options:
(1) dx and dy are required for all domains. Please set
(2) please turn on w_damping
w_damping = 1
(3) The options below are required for all the domains. please set
Please change these options and rerun your case. let me know if you still have issues.
(1) dx and dy are required for all domains. Please set
Code:
dx = 9000, 3000, 1000
dy = 9000, 3000, 1000(2) please turn on w_damping
w_damping = 1
(3) The options below are required for all the domains. please set
Code:
diff_opt = 2, 2, 2
km_opt = 4, 4, 4
zdamp = 5000, 5000, 5000
dampcoef = 0.2, 0.2, 0.2Please change these options and rerun your case. let me know if you still have issues.
likeyou511
New member
It stopped at 3h12min again, the same as last time.I have some concerns of your namelist options:
(1) dx and dy are required for all domains. Please set
Code:dx = 9000, 3000, 1000 dy = 9000, 3000, 1000
(2) please turn on w_damping
w_damping = 1
(3) The options below are required for all the domains. please set
Code:diff_opt = 2, 2, 2 km_opt = 4, 4, 4 zdamp = 5000, 5000, 5000 dampcoef = 0.2, 0.2, 0.2
Please change these options and rerun your case. let me know if you still have issues.
Please look at all your rsl files and see whether you can find any error messages. Note that the error message doesn't necessarily occur in rsl.error.0000. They can be in any of your RSL files. if the case crashed, there must be something wrong in the physics/dynamics and we hope to see error messages that may give us hints what is wrong.
Your namelist.input looks fine with the above changes. Where is your model domain located? What is the foricng data for this case?
Your namelist.input looks fine with the above changes. Where is your model domain located? What is the foricng data for this case?
likeyou511
New member
I don't know where is the error.Please look at all your rsl files and see whether you can find any error messages. Note that the error message doesn't necessarily occur in rsl.error.0000. They can be in any of your RSL files. if the case crashed, there must be something wrong in the physics/dynamics and we hope to see error messages that may give us hints what is wrong.
Your namelist.input looks fine with the above changes. Where is your model domain located? What is the foricng data for this case?
And I am using fnl driver data.
Attachments
There are a few issues here:
(1) The namelist.input you uploaded on September 24 doesn't include the changes suggested in my answer on September 20. Can you double check whether you use the modified namelist.input and the case still failed?
(2) what variable is displayed in the small area of the figure (domain.pdf)? Your case is a triply-nested case, but your figure tells me no information where the domains are located and how they nested.
(3) If you cannot find any error messages, I would suggest you recompile WRF in debug mode, i.e., ./configure -D, then rerun the case. When and where the model crashes first will show in your log file when the code is compiled in this mode. This will give you some hints what is wrong.
(1) The namelist.input you uploaded on September 24 doesn't include the changes suggested in my answer on September 20. Can you double check whether you use the modified namelist.input and the case still failed?
(2) what variable is displayed in the small area of the figure (domain.pdf)? Your case is a triply-nested case, but your figure tells me no information where the domains are located and how they nested.
(3) If you cannot find any error messages, I would suggest you recompile WRF in debug mode, i.e., ./configure -D, then rerun the case. When and where the model crashes first will show in your log file when the code is compiled in this mode. This will give you some hints what is wrong.