Difference between revisions of "Tips and Tricks"

Line 2: Line 2:
 
[[Category:WRF]]
 
[[Category:WRF]]
  
1. If you notice that the WRF model has become unstable, you should consider to make the following changes in the namelis.input file:
+
== Unstable WRF simulation ==
 +
If you notice that the WRF model has become unstable, you should consider making the following changes in the namelist.input file:
  
 
(a) reduce the time-step; and/or
 
(a) reduce the time-step; and/or
Line 10: Line 11:
 
(c) set epssm (0.1 by default) to a higher value (e.g. 0.3)
 
(c) set epssm (0.1 by default) to a higher value (e.g. 0.3)
  
The changes above indeed improves the stabilities in our case.
+
The changes above indeed improved the stabilities in our case.
  
2. If there is segmentation error in runtime, you can add following line to your PBS job batch script and see if this works:
+
== Runtime segmentation error ==
 +
WRF will always crash with a segmentation error when compiled without debugging information.
  
limit stacksize unlimited (for TCSH)
+
But you should make sure, you always run WRF with an unlimited stacksize. This should be set in your run script.
or
+
:For TCSH
 +
<code>
 +
limit stacksize unlimited
 +
</code>
 +
:For BASH
 +
<code>
 
ulimit -s unlimited (for BASH)
 
ulimit -s unlimited (for BASH)
 +
</code>
  
**If you have some tricks that can help WRF users in our community and hope that they could be included on this page, please email climate_help@nf.nci.org.au.'''
+
'''If you have some tricks that can help WRF users in our community and hope that they could be included on this page, please email cws_help@nci.org.au.'''

Revision as of 22:27, 11 December 2019

Template:Stub This is a stub page and needs expansion

Unstable WRF simulation

If you notice that the WRF model has become unstable, you should consider making the following changes in the namelist.input file:

(a) reduce the time-step; and/or

(b) set w_damping to 1; and/or

(c) set epssm (0.1 by default) to a higher value (e.g. 0.3)

The changes above indeed improved the stabilities in our case.

Runtime segmentation error

WRF will always crash with a segmentation error when compiled without debugging information.

But you should make sure, you always run WRF with an unlimited stacksize. This should be set in your run script.

For TCSH

limit stacksize unlimited

For BASH

ulimit -s unlimited (for BASH)

If you have some tricks that can help WRF users in our community and hope that they could be included on this page, please email cws_help@nci.org.au.