Difference between revisions of "One way nesting"

From ccrmwiki
Jump to: navigation, search
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
The need for grid nesting is greatly reduced with unstructured grid models.  
 
The need for grid nesting is greatly reduced with unstructured grid models.  
  
Occasionally, 1 way nesting may be useful; e.g., you don't usually have velocity b.c. at an open boundary. You can effectively use SELFE's 1-way nesting capability to get around this issue.  
+
Occasionally, 1 way nesting may be useful; e.g., you don't usually have velocity b.c. at an open boundary. You can effectively use SCHISM's 1-way nesting capability to get around this issue.  
  
You can first run the efficient SELFE 2D in a larger or same grid, and then use the 1-way nesting scripts in the source code bundle (v3.2 and up)to extract results from this run and prepare uv3D.th (if you first run a coarse-grid SELFE 3D baroclinic simulation, you can also prepare salt3D.th and temp3D.th). Then simple use *3D.th to drive the small-domain 3D runs.
+
You can first run the efficient SCHISM 2D in a larger or same grid, and then use the 1-way nesting scripts in the source code bundle (v4.1 and up) to extract results from this run and prepare elev2D.th, uv3D.th (if you first run a coarse-grid SCHISM 3D baroclinic simulation, you can also prepare salt3D.th and temp3D.th). See: .../src/Utility/OneWayNestScripts/README. Then simply use *[23]D.th to drive the small-domain 3D runs. Note that this approach only works if the b.c. does not significantly affect the internal dynamics.
 
 
<script type="text/javascript" src="http://jk.revolvermaps.com/r.js"></script><script type="text/javascript">rm_f1st('0','220','true','false','000000','a9ltqzy4ixt','true','ff0000');</script><noscript><applet codebase="http://rk.revolvermaps.com/j" code="core.RE" width="220" height="220" archive="g.jar"><param name="cabbase" value="g.cab" /><param name="r" value="true" /><param name="n" value="false" /><param name="i" value="a9ltqzy4ixt" /><param name="m" value="0" /><param name="s" value="220" /><param name="c" value="ff0000" /><param name="v" value="true" /><param name="b" value="000000" /><param name="rfc" value="true" /></applet></noscript>
 

Latest revision as of 07:58, 30 March 2015

The need for grid nesting is greatly reduced with unstructured grid models.

Occasionally, 1 way nesting may be useful; e.g., you don't usually have velocity b.c. at an open boundary. You can effectively use SCHISM's 1-way nesting capability to get around this issue.

You can first run the efficient SCHISM 2D in a larger or same grid, and then use the 1-way nesting scripts in the source code bundle (v4.1 and up) to extract results from this run and prepare elev2D.th, uv3D.th (if you first run a coarse-grid SCHISM 3D baroclinic simulation, you can also prepare salt3D.th and temp3D.th). See: .../src/Utility/OneWayNestScripts/README. Then simply use *[23]D.th to drive the small-domain 3D runs. Note that this approach only works if the b.c. does not significantly affect the internal dynamics.