[Dart-dev] DART/branches Revision: 10983

dart at ucar.edu dart at ucar.edu
Wed Feb 1 16:43:24 MST 2017


raeder at ucar.edu
2017-02-01 16:43:23 -0700 (Wed, 01 Feb 2017)
57
THIS has the CAM-SE code description taken out (mostly).



Modified: DART/branches/rma_trunk/models/cam-fv/model_mod.html
===================================================================
--- DART/branches/rma_trunk/models/cam-fv/model_mod.html	2017-02-01 23:43:10 UTC (rev 10982)
+++ DART/branches/rma_trunk/models/cam-fv/model_mod.html	2017-02-01 23:43:23 UTC (rev 10983)
@@ -266,8 +266,6 @@
    output_state_vector = .false.,
    model_config_file   = 'caminput.nc',
    cam_phis            = 'cam_phis.nc',
-   cs_grid_file        = 'SEMapping_cs_grid.nc'
-   homme_map_file      = 'SEMapping.nc'
    state_num_0d        = 0,
    state_num_1d        = 0,
    state_num_2d        = 1,
@@ -829,7 +827,6 @@
 model_mod namelist parameters, sets the calendar type (the GREGORIAN
 calendar is used with the CAM model), and determines the dart vector
 length, among other things.  This subroutine requires that caminput.nc,
-and SEMapping.nc or SEMapping_cs_grid.nc for CAM-SE,
 (or the names in namelist variable model_config_file) be present in the working
 directory to retrieve model information (grid dimensions and spacing
 including the vertical hybrid coordinate coefficients, time step, and
@@ -1143,91 +1140,6 @@
 <!--================================================================-->
 <!--=================== DESCRIPTION OF SUBROUTINE ====================-->
 
-<A NAME="interp_cubed_sphere"></A>
-<div class=routine>
-<em class=call> call interp_cubed_sphere(st_vec, obs_loc, obs_kind, interp_val, istatus)</em>
-<pre>
-real(r8), dimension(:),   intent(in)  :: <em class=code> st_vec </em>
-type(location_type),      intent(in)  :: <em class=code> obs_loc </em>
-integer,                  intent(in)  :: <em class=code> obs_kind </em>
-real(r8),                 intent(out) :: <em class=code> interp_val </em>
-integer,                  intent(out) :: <em class=code> istatus </em>
-</pre></div>
-
-<div class=indent1>
-<P>
-Find the cubed-sphere grid cell which encloses (horizontally) an observation at 'obs_loc'.
-Interpolate the values of field 'obs_kind', from the cell's 4 corners 
-on the bounding vertical levels, to that location.
-</P>
-<br>
-</div>
-
-<!--================================================================-->
-<!--=================== DESCRIPTION OF SUBROUTINE ====================-->
-
-<A NAME="unit_square_location"></A>
-<div class=routine>
-<em class=call> call unit_square_location(cell, closest, location, lon_o, lat_o, found_cell, origin, l,m)</em>
-<pre>
-integer,             intent(in)    :: <em class=code>cell</em>
-integer,             intent(in)    :: <em class=code>closest</em>
-type(location_type), intent(in)    :: <em class=code>location</em>
-real(r8),            intent(in)    :: <em class=code>lon_o, lat_o</em>
-integer,             intent(inout) :: <em class=code>found_cell</em>
-integer,             intent(out)   :: <em class=code>origin</em>
-real(r8),            intent(out)   :: <em class=code>l</em>
-real(r8),            intent(out)   :: <em class=code>m</em>
-</pre></div>
-
-<div class=indent1>
-<P>
-Uses a pre-derived mapping, from the cubed-sphere cell "closest" to a location (observation)
-onto the unit square (l,m), to map the "location" onto that square.
-This is a bilinear interpolation,
-<pre>
-  x = a0 + a1*l*m + a2*m + a3*l
-  y = b0 + b1*l*m + b2*m + b3*l
-</pre>
-so does not take into account the curvature of the quadrilateral.
-That has been handled by the intermediate mapping from (lon,lat) to (x,y).
-If the location is in the cell, the routine passes back the interpolation weights (l,m).
-Otherwise, it signals the calling routine to send it another candidate cell.
-Based on http://www.particleincell.com/2012/quad-interpolation/.
-</P>
-<TABLE width=100% border=0 summary="" cellpadding=3>
-
-<TR><TD valign=top><em class=code>cell&nbsp;&nbsp;</em></TD>
-    <TD>Candidate cubed sphere cell, which may contain <em class=code>location</em>. </TD></TR>
-
-<TR><TD valign=top><em class=code>closest &nbsp;&nbsp;</em></TD>
-    <TD>The node (cell corner) closest to the observation. </TD></TR>
-
-<TR><TD valign=top><em class=code>location &nbsp;&nbsp;</em></TD>
-    <TD>The location of the observation, used in <em class=sub>get_dist</em>. </TD></TR>
-
-<TR><TD valign=top><em class=code>lon_o,lat_o &nbsp;&nbsp;</em></TD>
-    <TD>Longitude and latitude of the observation. </TD></TR>
-
-<TR><TD valign=top><em class=code>l,m &nbsp;&nbsp;</em></TD>
-    <TD>Location of the observation in the unit square space of this cell.  
-        Used to determine whether the cell contains the observation and,
-        if so, as interpolation weights. </TD></TR>
-
-<TR><TD valign=top><em class=code>found_cell &nbsp;&nbsp;</em></TD>
-    <TD>Flag to tell calling routine that the observation is in this cell. </TD></TR>
-
-<TR><TD valign=top><em class=code>origin &nbsp;&nbsp;</em></TD>
-    <TD>The node number of the cell corner which is used as the origin


More information about the Dart-dev mailing list