- Timestamp:
- 03/21/07 10:14:37 (17 years ago)
- Location:
- trunk/SRC/Documentation/idldoc_assistant_output/Computation
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/SRC/Documentation/idldoc_assistant_output/Computation/curl.html
r200 r234 72 72 <h2>curl <font size="-1" color="#006633"> 73 73 Calculation 74 74 </font></h2> 75 75 76 76 <p><font face="Courier"><i>result = </i>curl(<i><a href="#_curl_keyword_uu">uu</a>, <a href="#_curl_keyword_vv">vv</a></i>, <a href="#_curl_keyword_DIREC">DIREC</a>=<i>scalar string</i>)</font></p> … … 103 103 A 2D (xy), 3D (xyz or yt) or a structure readable by litchamp and containing 104 104 a 2D (xy), 3D (xyz or yt) array (4d case is not coded yet). 105 note that the dimension of the arr y must suit the domain dimension.105 note that the dimension of the array must suit the domain dimension. 106 106 107 107 … … 119 119 </h4> 120 120 121 121 122 122 Matrix representing the meridional coordinates (V point) of a field of vectors 123 123 A 2D (xy), 3D (xyz or yt) or a structure readable by litchamp and containing 124 124 a 2D (xy), 3D (xyz or yt) array (4d case is not coded yet). 125 note that the dimension of the arr y must suit the domain dimension.125 note that the dimension of the array must suit the domain dimension. 126 126 127 127 … … 151 151 152 152 153 <h3>Examples</h3> 153 <h3>Examples</h3><pre> 154 154 IDL> @tst_initorca2 155 155 IDL> plt, curl(dist(jpi,jpj), dist(jpi,jpj)) 156 156 157 < h3>Version history</h3>157 </pre><h3>Version history</h3> 158 158 159 159 <h4>Version</h4> 160 $Id: curl.pro 168 2006-09-06 10:46:29Z pinsard $161 162 <h4>History</h4> 160 $Id: curl.pro 231 2007-03-19 17:15:51Z pinsard $ 161 162 <h4>History</h4> 163 163 Guillaume Roullet (grlod@ipsl.jussieu.fr) 164 164 Sebastien Masson (smasson@lodyc.jussieu.fr) 165 165 adaptation to work with a reduce domain 166 166 21/5/1999: missing values at !values.f_nan 167 167 168 168 169 169 … … 171 171 172 172 173 <h4>Todo items</h4> 173 <h4>Todo items</h4> 174 174 code the 4d case 175 175 <h4>Restrictions</h4> 176 176 177 - Works only for Arakawa C-grid. 177 - Works only for Arakawa C-grid. 178 178 - UU must be on U grid, VV must be on V grid 179 179 - 4d case is not coded yet 180 180 - the common variable jpt is used to differ xyz (jpt=1) and xyt (jpt=1) cases. 181 - U and V arrays are cut in the same geographic domain. Because of the shift between 182 T, U, V and F grids, it is possible that these two arrays do not have the same 183 size and refer to different indexes. In this case, arrays are re-cut on 184 common indexes. To avoid these re-cuts, use the keyword /memeindice in domdef.pro 181 - U and V arrays are cut in the same geographic domain. Because of the shift between 182 T, U, V and F grids, it is possible that these two arrays do not have the same 183 size and refer to different indexes. In this case, arrays are re-cut on 184 common indexes. To avoid these re-cuts, use the keyword /memeindice in 185 <a href=".//../../ToBeReviewed/GRILLE/domdef.html">domdef</a> 185 186 - When computing the divergence, we update, vargrid, varname, varunits and the 186 187 grid position parameters (firstxf, lastxf, nxf, firstyf, lastyf, nyf). 187 - points that cannot be computed (domain bo ndaries, coastline) are set to NaN188 - points that cannot be computed (domain boundaries, coastline) are set to NaN 188 189 189 190 … … 192 193 193 194 <h4>Uses routines</h4> 194 cm_4cal, cm_4data, cm_4mmesh 195 cm_4cal, cm_4data, cm_4mmesh 195 196 196 197 -
trunk/SRC/Documentation/idldoc_assistant_output/Computation/div.html
r200 r234 99 99 </h4> 100 100 101 101 102 102 Matrix representing the zonal coordinates (U point) of a field of vectors 103 103 A 2D (xy), 3D (xyz or yt) or a structure readable by litchamp and containing 104 104 a 2D (xy), 3D (xyz or yt) array (4d case is not coded yet). 105 note that the dimension of the arr y must suit the domain dimension.105 note that the dimension of the array must suit the domain dimension. 106 106 107 107 … … 119 119 </h4> 120 120 121 121 122 122 Matrix representing the meridional coordinates (V point) of a field of vectors 123 123 A 2D (xy), 3D (xyz or yt) or a structure readable by litchamp and containing 124 124 a 2D (xy), 3D (xyz or yt) array (4d case is not coded yet). 125 note that the dimension of the arr y must suit the domain dimension.125 note that the dimension of the array must suit the domain dimension. 126 126 127 127 … … 151 151 152 152 153 <h3>Examples</h3> 153 <h3>Examples</h3><pre> 154 154 IDL> @tst_initorca2 155 155 IDL> plt, div(dist(jpi,jpj), dist(jpi,jpj)) 156 156 157 < h3>Version history</h3>157 </pre><h3>Version history</h3> 158 158 159 159 <h4>Version</h4> 160 $Id: div.pro 168 2006-09-06 10:46:29Z pinsard $160 $Id: div.pro 231 2007-03-19 17:15:51Z pinsard $ 161 161 162 162 <h4>History</h4> … … 170 170 171 171 172 <h4>Todo items</h4> 172 <h4>Todo items</h4> 173 173 code the 4d case 174 174 <h4>Restrictions</h4> 175 175 176 - Works only for Arakawa C-grid. 176 - Works only for Arakawa C-grid. 177 177 - UU must be on U grid, VV must be on V grid 178 178 - 4d case is not coded yet 179 179 - the common variable jpt is used to differ xyz (jpt=1) and xyt (jpt=1) cases. 180 - U and V arrays are cut in the same geographic domain. Because of the shift between 181 T, U, V and F grids, it is possible that these two arrays do not have the same 182 size and refer to different indexes. In this case, arrays are re-cut on 183 common indexes. To avoid these re-cuts, use the keyword /memeindice in domdef.pro 180 - U and V arrays are cut in the same geographic domain. Because of the shift between 181 T, U, V and F grids, it is possible that these two arrays do not have the same 182 size and refer to different indexes. In this case, arrays are re-cut on 183 common indexes. To avoid these re-cuts, use the keyword /memeindice in 184 <a href=".//../../ToBeReviewed/GRILLE/domdef.html">domdef</a> 184 185 - When computing the divergence, we update, vargrid, varname, varunits and the 185 186 grid position parameters (firstxt, lastxt, nxt, firstyt, lastyt, nyt). 186 - points that cannot be computed (domain bo ndaries, coastline) are set to NaN187 - points that cannot be computed (domain boundaries, coastline) are set to NaN 187 188 188 189 … … 191 192 192 193 <h4>Uses routines</h4> 193 cm_4cal, cm_4data, cm_4mmesh 194 cm_4cal, cm_4data, cm_4mmesh 194 195 195 196 -
trunk/SRC/Documentation/idldoc_assistant_output/Computation/grad.html
r200 r234 78 78 79 79 80 80 81 <h3>Return value</h3> RES {type=2D, 3D or 4D array} 81 82 the gradient of the input data (with the same size) … … 102 103 3D (xyz or yt) or 4D (xyzt) array or a structure readable by litchamp 103 104 and containing a 2D (xy), 3D (xyz or yt) or 4D (xyzt) array. 104 note that the dimension of the arr y must suit the domain dimension.105 note that the dimension of the array must suit the domain dimension. 105 106 106 107 … … 126 127 127 128 128 <h3>Examples</h3> 129 <h3>Examples</h3><pre> 129 130 IDL> @tst_initorca2 130 131 IDL> plt, grad({arr:gphit,g:'T'}, 'x') 131 132 IDL> plt, grad({arr:gphit,g:'T'}, 'y') 132 133 133 < h3>Version history</h3>134 </pre><h3>Version history</h3> 134 135 135 136 <h4>Version</h4> 136 $Id: grad.pro 168 2006-09-06 10:46:29Z pinsard $137 $Id: grad.pro 232 2007-03-20 16:59:36Z pinsard $ 137 138 138 139 <h4>History</h4> … … 146 147 147 148 <h4>Restrictions</h4> 148 - Works only for Arakawa C-grid. 149 - Works only for Arakawa C-grid. 149 150 - When computing the gradient, the result is not on the same grid point 150 151 than the input data. In consequence, we update, vargrid and the grid position 151 152 parameters (firstx[tuvf], lastx[tuvf], nx[tuvf], firsty[tuvf], lasty[tuvf], 152 153 ny[tuvf], firstz[tw], lastz[tw], nz[tw]). 153 - points that cannot be computed (domain bo ndaries, coastline) are set to NaN154 - points that cannot be computed (domain boundaries, coastline) are set to NaN 154 155 - the common variable jpt is used to differ xyz (jpt=1) and xyt (jpt=1) cases. 155 156 … … 159 160 160 161 <h4>Uses routines</h4> 161 cm_4cal, cm_4data, cm_4mmesh 162 cm_4cal, cm_4data, cm_4mmesh 162 163 163 164
Note: See TracChangeset
for help on using the changeset viewer.