Changeset 138 for trunk/SRC/Documentation/idldoc_html_output/Grid/computegrid.html

Timestamp:

07/12/06 11:52:09 (18 years ago)

Author:

smasson

Message:

update documentation and .idlwave_catalog

File:

• trunk/SRC/Documentation/idldoc_html_output/Grid/computegrid.html (modified) (20 diffs)

trunk/SRC/Documentation/idldoc_html_output/Grid/computegrid.html

@@ -328 +328 @@
 table.variables td.image { width: 64px; }
 
-div#file_comments { 
+div#file_comments { white-space: pre; 
   margin: 2em;
   font-size: 80%;
@@ -703 +703 @@
        or a suitable mix...
 
- glamt 
- glamf 
- gphit 
- gphif 
- e1t 
- e2t 
+ glamt
+ glamf
+ gphit
+ gphit
+ e1t
+ e2t
  horizontal parameters
 
@@ -722 +722 @@
  e2f {in}
  horizontal parameters if FULLCGRID keyword is defined
-      
- gdept 
- gdepw 
- e3t 
- e3w 
+
+ gdept
+ gdepw
+ e3t
+ e3w
  verticals parameters
 
- tmask 
+ tmask
  masks
 
@@ -737 +737 @@
  fmaskredy {in}
  masks if FULLCGRID keyword is defined
- 
+
  triangles_list
  triangulation
@@ -821 +821 @@
             </h4>
         
-          <div class="comments"> scalar or vector: y direction step, 
+          <div class="comments"> scalar or vector: y direction step,
              could be > 0 (south to north) or < 0 (north to south)
              if vector ny is not used</div>
@@ -836 +836 @@
             </h4>
         
-          <div class="comments"> scalar, number of points in x direction </div>
+          <div class="comments"> scalar, number of points in x direction</div>
             
             <h4 id="_computegrid_param_nyin">nyin&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
@@ -870 +870 @@
             </h4>
         
-            <div class="comments"> to specify longitude1 with a 1 or 2 dimension array, in 
+            <div class="comments"> to specify longitude1 with a 1 or 2 dimension array, in
        this case startx, stepx and nx are not used but could be
        necessary if the y axis is not defined with yaxis. It must be
@@ -888 +888 @@
             </h4>
         
-            <div class="comments"> to specify latitudes with a 1 or 2 dimension array, in 
+            <div class="comments"> to specify latitudes with a 1 or 2 dimension array, in
        this case starty, stepy and ny are not used but starty and
        stepy could be necessary if the x axis is not defined with xaxis.
@@ -939 +939 @@
        we must have lon2 > lon1 and lon2 - lon1 le 360
        key_shift will be defined automaticaly computed according to
-       glamboundary by using the FIRST LINE of glamt but 
-       key_shift will /= 0 only if key_periodic = 1 
+       glamboundary by using the FIRST LINE of glamt but
+       key_shift will /= 0 only if key_periodic = 1
 </div>
             
@@ -980 +980 @@
             </h4>
         
-            <div class="comments"> </div>
+            <div class="comments"></div>
             
             <h4 id="_computegrid_keyword_YMAXMESH">YMAXMESH&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
@@ -1006 +1006 @@
             </h4>
         
-            <div class="comments"> 
+            <div class="comments">
        to define the common variables i[xyz]minmesh
        used to define the grid only in a zoomed part of the original
@@ -1026 +1026 @@
        to define the common variables i[xyz]maxmesh
        used to define the grid only in a zoomed part of the original
-       grid. max value is jp[ijk]glo-1. 
-       if [XYZ]MAXMESH is negative, then we define i[xyz]maxmesh as 
+       grid. max value is jp[ijk]glo-1.
+       if [XYZ]MAXMESH is negative, then we define i[xyz]maxmesh as
        jp[ijk]glo - 1 + [XYZ]MAXMESH instead of [XYZ]MAXMESH    
 </div>
@@ -1045 +1045 @@
        key_onearth (to specify if the data are on earth -> use longitude
        /latitude etc...). By default, key_onearth = 1.
-       note that ONEARTH = 0 forces PERIODIC = 0, SHIFT = 0, 
+       note that ONEARTH = 0 forces PERIODIC = 0, SHIFT = 0,
        and is cancelling GLAMBOUNDARY
 </div>
@@ -1062 +1062 @@
             <div class="comments"> = 0 or 1 to force the manual definition of
        key_periodic. By default, key_periodic is automaticaly
-       computed by using the first line of glamt. 
+       computed by using the first line of glamt.
 </div>
             
@@ -1077 +1077 @@
         
             <div class="comments"> force PERIODIC = 0, SHIFT = 0, STRIDE = [1, 1, 1] and
-       suppress the automatic redefinition of the domain in case of 
+       suppress the automatic redefinition of the domain in case of
        x periodicity overlap, y periodicity overlap (ORCA type only)
        and mask border to 0.
@@ -1096 +1096 @@
        default, key_shift is automaticaly computed according to
        glamboundary (when defined) by using the FIRST LINE of glamt. if
-       key_periodic=0 then in any case key_shift = 0. 
+       key_periodic=0 then in any case key_shift = 0.
 </div>
             
@@ -1143 +1143 @@
             </h4>
         
-            <div class="comments"> activate to specify that the horizontal grid should 
+            <div class="comments"> activate to specify that the horizontal grid should
        be simply defined by using the index of the points
           (xaxis = findgen(nx) and yaxis = findgen(ny))
@@ -1199 +1199 @@
           <h3>Version history</h3>
           
-          <h4>Version</h4><div class="value"> $Id: computegrid.pro 118 2006-06-27 15:47:06Z pinsard $
-</div>
-          <h4>History</h4><div class="value"> Sebastien Masson (smasson@lodyc.jussieu.fr)
+          <h4>Version</h4><div class="preformat"> $Id: computegrid.pro 134 2006-07-07 10:19:08Z navarro $
+</div>
+          <h4>History</h4><div class="preformat"> Sebastien Masson (smasson@lodyc.jussieu.fr)
                       2000-04-20
   Sept 2004, several bug fixs to suit C grid type...
@@ -1212 +1212 @@
           
           
-          <h4>Restrictions</h4><div class="value"> if the grid has x/y periodicity orverlap and/or if
+          <h4>Restrictions</h4><div class="preformat"> if the grid has x/y periodicity orverlap and/or if
     the mask has 0 everywhere at the border (like a close sea) and
     if (we did not activate /plain and xminmesh, xmaxmesh, yminmesh,
@@ -1226 +1226 @@
           
           
-          <h4>Uses routines</h4><div class="value"> cm_4mesh cm_4data cm_4cal
+          <h4>Uses routines</h4><div class="preformat"> cm_4mesh cm_4data cm_4cal
 </div>