Changeset 242 for trunk/SRC/Documentation/idldoc_assistant_output
- Timestamp:
- 04/06/07 10:35:17 (17 years ago)
- Location:
- trunk/SRC/Documentation/idldoc_assistant_output
- Files:
-
- 160 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/SRC/Documentation/idldoc_assistant_output/Calendar/caldat.html
r234 r242 236 236 237 237 <h4>Version</h4> 238 $Id: caldat.pro 231 2007-03-19 17:15:51Z pinsard $ 238 $Id: caldat.pro 238 2007-03-27 13:43:18Z pinsard $ 239 239 240 <h4>History</h4> 240 241 Translated from "Numerical Recipies in C", by William H. Press, … … 268 269 269 270 270 <h4>Uses routines</h4> cm_4cal 271 <h4>Uses routines</h4> 272 cm_4cal 271 273 272 274 -
trunk/SRC/Documentation/idldoc_assistant_output/Calendar/date2jul.html
r234 r242 61 61 </dl> 62 62 63 63 64 64 gives Julian day equivalent of a date in yyyymmdd format 65 65 … … 79 79 80 80 81 <h3>Return value</h3> 81 <h3>Return value</h3> 82 82 date in Julian day 83 83 … … 139 139 140 140 <h4>Version</h4> 141 $Id: date2jul.pro 23 1 2007-03-19 17:15:51Z pinsard $141 $Id: date2jul.pro 238 2007-03-27 13:43:18Z pinsard $ 142 142 143 <h4>History</h4> 143 <h4>History</h4> 144 144 Sebastien Masson (smasson@lodyc.jussieu.fr) June 2005 145 145 -
trunk/SRC/Documentation/idldoc_assistant_output/Calendar/date2string.html
r234 r242 138 138 139 139 <h4>Version</h4> 140 $Id: date2string.pro 23 1 2007-03-19 17:15:51Z pinsard $140 $Id: date2string.pro 238 2007-03-27 13:43:18Z pinsard $ 141 141 142 <h4>History</h4> Sebastien Masson (smasson@lodyc.jussieu.fr) 142 <h4>History</h4> 143 Sebastien Masson (smasson@lodyc.jussieu.fr) 143 144 Creation ??? 144 145 update/review June 2005 Sebastien Masson. -
trunk/SRC/Documentation/idldoc_assistant_output/Calendar/daysinmonth.html
r234 r242 70 70 <a name="#_daysinmonth"></a> 71 71 72 <h2>daysinmonth <font size="-1" color="#006633"> 72 <h2>daysinmonth <font size="-1" color="#006633"> 73 73 Calendar 74 74 </font></h2> … … 79 79 80 80 81 <h3>Return value</h3> 81 <h3>Return value</h3> 82 82 number of days in a month or -1 in case of error 83 83 … … 131 131 </pre><h3>Version history</h3> 132 132 133 <h4>Version</h4> 134 $Id: daysinmonth.pro 23 1 2007-03-19 17:15:51Z pinsard $133 <h4>Version</h4> 134 $Id: daysinmonth.pro 238 2007-03-27 13:43:18Z pinsard $ 135 135 136 <h4>History</h4> 136 <h4>History</h4> 137 137 Sebastien Masson (smasson@lodyc.jussieu.fr) 138 138 2/7/98 … … 150 150 151 151 152 <h4>Uses routines</h4> 153 cm_4cal, updatenew 152 <h4>Uses routines</h4> 153 cm_4cal 154 updatenew 154 155 155 156 -
trunk/SRC/Documentation/idldoc_assistant_output/Calendar/leapyr.html
r234 r242 72 72 <a name="#_leapyr"></a> 73 73 74 <h2>leapyr <font size="-1" color="#006633"> 74 <h2>leapyr <font size="-1" color="#006633"> 75 75 Calendar 76 76 </font></h2> … … 81 81 82 82 83 <h3>Return value</h3> 83 <h3>Return value</h3> 84 84 0 then not a leap year, 1 then year is a leap year 85 85 with the same number of elements than year. … … 116 116 117 117 <h4>Version</h4> 118 $Id: leapyr.pro 23 1 2007-03-19 17:15:51Z pinsard $118 $Id: leapyr.pro 238 2007-03-27 13:43:18Z pinsard $ 119 119 120 120 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/Colors/color24.html
r234 r242 64 64 The purpose of this function is to convert a RGB color triple 65 65 into the equivalent 24-big long integer. 66 This routine was written to be used with routines like COLORS or 66 This routine was written to be used with routines like 67 COLORS <!--++ COLORS is not a routine--> or 67 68 <a href=".//GETCOLOR.html">GETCOLOR</a>. 68 69 … … 126 127 127 128 <h4>Version</h4> 128 $Id: color24.pro 23 1 2007-03-19 17:15:51Z pinsard $129 $Id: color24.pro 237 2007-03-26 15:37:03Z pinsard $ 129 130 130 131 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/Colors/lct.html
r234 r242 182 182 183 183 <h4>Version</h4> 184 $Id: lct.pro 23 2 2007-03-20 16:59:36Z pinsard$184 $Id: lct.pro 239 2007-03-28 06:50:03Z smasson $ 185 185 186 186 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/Colors/newpalette.html
r234 r242 163 163 164 164 <h4>Version</h4> 165 $Id: newpalette.pro 23 2 2007-03-20 16:59:36Z pinsard$165 $Id: newpalette.pro 239 2007-03-28 06:50:03Z smasson $ 166 166 167 <h4>History</h4> 167 <h4>History</h4> 168 168 Guillaume Roulet (gr@lodyc.jussieu.fr) 169 169 30/3/1999 s.masson, add _extra, research of the full name, OVER -
trunk/SRC/Documentation/idldoc_assistant_output/Colors/xlct.html
r234 r242 62 62 63 63 64 Like xloadct but fastest to write and call by default the palette65 palette.tbl which can be in any directory64 Like <proidl>xloadct<proidl> but fastest to write and call by default 65 the palette palette.tbl which can be in any directory 66 66 67 67 … … 78 78 79 79 80 80 81 81 82 … … 279 280 280 281 <h4>Version</h4> 281 $Id: xlct.pro 23 1 2007-03-19 17:15:51Z pinsard$282 $Id: xlct.pro 239 2007-03-28 06:50:03Z smasson $ 282 283 283 284 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/Colors/xpal.html
r234 r242 66 66 67 67 68 like xpalette but shorter to write and, moreover, 69 possess a hotkey save which (thanks to the newpalette routine) 68 Re-draw the RGB plots. 69 70 71 Change current color. 72 73 74 Like <proidl>xpalette</proidl> but shorter to write and, moreover, 75 possess a hotkey save which (thanks to the <a href=".//newpalette.html">newpalette</a> routine) 70 76 allows to save the routine that we have just done. Comment: when we 71 press the predefined hotkey, it calls xlct instead of xloadct 77 press the predefined hotkey, it calls <a href=".//xlct.html">xlct</a> instead of 78 <proidl>xloadct</proidl> 72 79 No explicit inputs. The current color table is used as a starting point. 73 80 … … 255 262 256 263 <h4>Version</h4> 257 $Id: xpal.pro 23 3 2007-03-20 17:04:40Z pinsard $264 $Id: xpal.pro 238 2007-03-27 13:43:18Z pinsard $ 258 265 259 266 <h4>History</h4> … … 292 299 293 300 294 <h4>Uses routines</h4> XP_COM: Private to this module. 301 <h4>Uses routines</h4> 302 XP_COM Private to this module. 295 303 296 304 -
trunk/SRC/Documentation/idldoc_assistant_output/Computation/curl.html
r234 r242 79 79 80 80 81 <h3>Return value</h3> RES81 <h3>Return value</h3> 82 82 the vertical component of the curl of the input data (with the same size) 83 83 … … 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 a 2D (xy), 3D (xyz or yt) array (4 dcase is not coded yet).105 note that the dimension of the array must suit the domain dimension.104 a 2D (xy), 3D (xyz or yt) array (4D case is not coded yet). 105 Note that the dimension of the array must suit the domain dimension. 106 106 107 107 … … 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 a 2D (xy), 3D (xyz or yt) array (4 dcase is not coded yet).125 note that the dimension of the array must suit the domain dimension.124 a 2D (xy), 3D (xyz or yt) array (4D case is not coded yet). 125 Note that the dimension of the array must suit the domain dimension. 126 126 127 127 … … 145 145 146 146 147 Use if you want to call moyenne or grossemoyenne after the div computation 147 Use if you want to call <a href="..//ToBeReviewed/CALCULS/moyenne.html">moyenne</a> or 148 <a href="..//ToBeReviewed/CALCULS/grossemoyenne.html">grossemoyenne</a> after the div computation 148 149 with a mean done in the DIREC direction 149 150 … … 158 159 159 160 <h4>Version</h4> 160 $Id: curl.pro 23 1 2007-03-19 17:15:51Z pinsard $161 $Id: curl.pro 238 2007-03-27 13:43:18Z pinsard $ 161 162 162 163 <h4>History</h4> … … 172 173 173 174 <h4>Todo items</h4> 174 code the 4d case 175 code the 4D case 176 175 177 <h4>Restrictions</h4> 176 178 177 179 - Works only for Arakawa C-grid. 178 180 - UU must be on U grid, VV must be on V grid 179 - 4 dcase is not coded yet181 - 4D case is not coded yet 180 182 - the common variable jpt is used to differ xyz (jpt=1) and xyt (jpt=1) cases. 181 183 - U and V arrays are cut in the same geographic domain. Because of the shift between … … 183 185 size and refer to different indexes. In this case, arrays are re-cut on 184 186 common indexes. To avoid these re-cuts, use the keyword /memeindice in 185 <a href=". //../../ToBeReviewed/GRILLE/domdef.html">domdef</a>187 <a href="..//ToBeReviewed/GRILLE/domdef.html">domdef</a> 186 188 - When computing the divergence, we update, vargrid, varname, varunits and the 187 189 grid position parameters (firstxf, lastxf, nxf, firstyf, lastyf, nyf). … … 193 195 194 196 <h4>Uses routines</h4> 195 cm_4cal, cm_4data, cm_4mmesh 197 cm_4cal 198 cm_4data 199 cm_4mmesh 196 200 197 201 -
trunk/SRC/Documentation/idldoc_assistant_output/Computation/div.html
r234 r242 79 79 80 80 81 <h3>Return value</h3> RES81 <h3>Return value</h3> 82 82 the divergence of the input data (with the same size) 83 83 … … 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 a 2D (xy), 3D (xyz or yt) array (4 dcase is not coded yet).104 a 2D (xy), 3D (xyz or yt) array (4D case is not coded yet). 105 105 note that the dimension of the array must suit the domain dimension. 106 106 … … 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 a 2D (xy), 3D (xyz or yt) array (4 dcase is not coded yet).124 a 2D (xy), 3D (xyz or yt) array (4D case is not coded yet). 125 125 note that the dimension of the array must suit the domain dimension. 126 126 … … 145 145 146 146 147 Use if you want to call moyenne or grossemoyenne after the div computation 147 Use if you want to call <a href="..//ToBeReviewed/CALCULS/moyenne.html">moyenne</a> or 148 <a href="..//ToBeReviewed/CALCULS/grossemoyenne.html">grossemoyenne</a> after the div computation 148 149 (stupid ?) with a mean done in the DIREC direction 149 150 … … 158 159 159 160 <h4>Version</h4> 160 $Id: div.pro 23 1 2007-03-19 17:15:51Z pinsard $161 $Id: div.pro 238 2007-03-27 13:43:18Z pinsard $ 161 162 162 163 <h4>History</h4> … … 171 172 172 173 <h4>Todo items</h4> 173 code the 4d case 174 code the 4D case 175 174 176 <h4>Restrictions</h4> 175 177 176 178 - Works only for Arakawa C-grid. 177 179 - UU must be on U grid, VV must be on V grid 178 - 4 dcase is not coded yet180 - 4D case is not coded yet 179 181 - the common variable jpt is used to differ xyz (jpt=1) and xyt (jpt=1) cases. 180 182 - U and V arrays are cut in the same geographic domain. Because of the shift between 181 183 T, U, V and F grids, it is possible that these two arrays do not have the same 182 184 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>185 common indexes. To avoid these re-cuts, use the keyword /memeindice in 186 <a href="..//ToBeReviewed/GRILLE/domdef.html">domdef</a> 185 187 - When computing the divergence, we update, vargrid, varname, varunits and the 186 188 grid position parameters (firstxt, lastxt, nxt, firstyt, lastyt, nyt). … … 192 194 193 195 <h4>Uses routines</h4> 194 cm_4cal, cm_4data, cm_4mmesh 196 cm_4cal 197 cm_4data 198 cm_4mmesh 195 199 196 200 -
trunk/SRC/Documentation/idldoc_assistant_output/Computation/grad.html
r234 r242 79 79 80 80 81 <h3>Return value</h3> RES {type=2D, 3D or 4D array}82 the gradient of the input data (with the same size)81 <h3>Return value</h3> 82 the gradient of the input data with the same size 2D, 3D or 4D array 83 83 84 84 … … 100 100 101 101 102 The field for which we want to compute the gradient. A 2D (xy), 103 3D (xyz or yt) or 4D (xyzt) array or a structure readable by litchamp 102 The field for which we want to compute the gradient. A 2D (xy), 103 3D (xyz or yt) or 4D (xyzt) array or a structure readable by 104 <proidl>litchamp</proidl> 104 105 and containing a 2D (xy), 3D (xyz or yt) or 4D (xyzt) array. 105 note that the dimension of the array must suit the domain dimension.106 Note that the dimension of the array must suit the domain dimension. 106 107 107 108 … … 135 136 136 137 <h4>Version</h4> 137 $Id: grad.pro 23 2 2007-03-20 16:59:36Z pinsard $138 $Id: grad.pro 238 2007-03-27 13:43:18Z pinsard $ 138 139 139 140 <h4>History</h4> … … 160 161 161 162 <h4>Uses routines</h4> 162 cm_4cal, cm_4data, cm_4mmesh 163 cm_4cal 164 cm_4data 165 cm_4mmesh 163 166 164 167 -
trunk/SRC/Documentation/idldoc_assistant_output/ForOldVersion/keep_compatibility.html
r234 r242 73 73 <a name="#_keep_compatibility"></a> 74 74 75 <h2>keep_compatibility <font size="-1" color="#006633"> 75 <h2>keep_compatibility <font size="-1" color="#006633"> 76 76 Compatibility 77 77 </font></h2> … … 100 100 </h4> 101 101 102 1 or 0 to keep or forget the compatibility 102 103 1 or 0 to keep or forget the compatibility 103 104 104 105 … … 112 113 </pre><h3>Version history</h3> 113 114 114 <h4>Version</h4> $Id: keep_compatibility.pro 232 2007-03-20 16:59:36Z pinsard $ 115 <h4>Version</h4> 116 $Id: keep_compatibility.pro 239 2007-03-28 06:50:03Z smasson $ 115 117 116 <h4>History</h4> Sebastien Masson (smasson@lodyc.jussieu.fr) 118 <h4>History</h4> 119 Sebastien Masson (smasson@lodyc.jussieu.fr) 117 120 June 2005 118 121 … … 131 134 132 135 133 <h4>Uses routines</h4> cm_general 136 <h4>Uses routines</h4> 137 cm_general 134 138 135 139 -
trunk/SRC/Documentation/idldoc_assistant_output/Grid/changemsk.html
r234 r242 80 80 81 81 <h3>Return value</h3> 82 newmskthe new 2D land-sea mask82 the new 2D land-sea mask 83 83 84 84 … … 136 136 137 137 <h4>Version</h4> 138 $Id: changemsk.pro 23 2 2007-03-20 16:59:36Z pinsard $138 $Id: changemsk.pro 238 2007-03-27 13:43:18Z pinsard $ 139 139 140 140 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/Grid/checkperio.html
r234 r242 148 148 149 149 <h4>Version</h4> 150 $Id: checkperio.pro 23 2 2007-03-20 16:59:36Z pinsard $150 $Id: checkperio.pro 238 2007-03-27 13:43:18Z pinsard $ 151 151 <h4>History</h4> 152 152 October 2006: Sebastien Masson (smasson@locean-ipsl.upmc.fr) -
trunk/SRC/Documentation/idldoc_assistant_output/Grid/computegrid.html
r234 r242 273 273 Specify latitudes in this case starty, stepy and ny are not used but 274 274 starty and stepy could be necessary if the x axis is not defined with 275 xaxis. It must be sorted in the increasing or dec easing order (along each column if 2d array).275 xaxis. It must be sorted in the increasing or decreasing order (along each column if 2d array). 276 276 277 277 … … 289 289 290 290 291 Specify the vertical axis. Must be sorted in the increasing or dec easing order291 Specify the vertical axis. Must be sorted in the increasing or decreasing order 292 292 293 293 … … 647 647 648 648 a string containing the calling command used to 649 call computegrid (this is used by <a href=". //../../ToBeReviewed/WIDGET/xxx.html">xxx</a>)649 call computegrid (this is used by <a href="..//ToBeReviewed/WIDGET/xxx.html">xxx</a>) 650 650 651 651 … … 690 690 691 691 692 (not used in the present case...)692 not used in the present case ... 693 693 694 694 … … 699 699 700 700 <h4>Version</h4> 701 $Id: computegrid.pro 2 32 2007-03-20 16:59:36Z pinsard $701 $Id: computegrid.pro 240 2007-03-28 12:17:24Z pinsard $ 702 702 703 703 <h4>History</h4> … … 713 713 714 714 715 <h4>Restrictions</h4> if the grid has x/y periodicity overlap and/or if 716 the mask has 0 everywhere at the border (like a close sea) and 715 <h4>Restrictions</h4> 716 if the grid has x/y periodicity overlap and/or if 717 the mask has 0 everywhere at the border (like a closed sea) and 717 718 if (we did not activate /plain and xminmesh, xmaxmesh, yminmesh, 718 719 ymaxmesh keywords are defined to their default values), we redefine 719 720 xminmesh, xmaxmesh, yminmesh, ymaxmesh in order to reove the 720 overlapping part and/or to open the domain (avoid tibe forced721 overlapping part and/or to open the domain (avoid it be forced 721 722 to use cell_fill = 1). 722 723 … … 727 728 728 729 729 <h4>Uses routines</h4> cm_4mesh cm_4data cm_4cal 730 <h4>Uses routines</h4> 731 cm_4mesh 732 cm_4data 733 cm_4cal 730 734 731 735 -
trunk/SRC/Documentation/idldoc_assistant_output/Grid/micromeshmask.html
r234 r242 114 114 115 115 116 116 117 117 118 … … 129 130 130 131 132 131 133 132 134 … … 144 146 145 147 148 146 149 147 150 … … 169 172 170 173 <h4>Version</h4> 171 $Id: micromeshmask.pro 2 31 2007-03-19 17:15:51Z pinsard $174 $Id: micromeshmask.pro 240 2007-03-28 12:17:24Z pinsard $ 172 175 173 176 <h4>History</h4> … … 239 242 240 243 241 242 243 </h4> 244 245 the name of the uniq reduced meshmask file.246 default definition is micromeshmask.nc244 <font size="-1" color="#006633">default:</font> <font size="-1" color="#006633"><i>'micromeshmask.nc'</i></font> 245 246 </h4> 247 248 249 the name of the uniq reduced meshmask file. 247 250 248 251 … … 265 268 </h4> 266 269 267 to define the files path. 270 271 to define the files path. 268 272 269 273 -
trunk/SRC/Documentation/idldoc_assistant_output/Grid/n128gaussian.html
r234 r242 80 80 81 81 82 <h3>Return value</h3> a 1d array 82 <h3>Return value</h3> 83 a 1d array 83 84 84 85 … … 93 94 94 95 <h4>Version</h4> 95 $Id: n128gaussian.pro 23 1 2007-03-19 17:15:51Z pinsard $96 $Id: n128gaussian.pro 238 2007-03-27 13:43:18Z pinsard $ 96 97 97 98 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/Grid/n160gaussian.html
r234 r242 80 80 81 81 82 <h3>Return value</h3> a 1d array 82 <h3>Return value</h3> 83 a 1d array 83 84 84 85 … … 88 89 89 90 <h3>Examples</h3><pre> 90 IDL> lat=n160gaussian()91 IDL> lat=n160gaussian() 91 92 92 93 </pre><h3>Version history</h3> 93 94 94 95 <h4>Version</h4> 95 $Id: n160gaussian.pro 23 1 2007-03-19 17:15:51Z pinsard $96 $Id: n160gaussian.pro 238 2007-03-27 13:43:18Z pinsard $ 96 97 97 98 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/Grid/n256gaussian.html
r234 r242 80 80 81 81 82 <h3>Return value</h3> a 1d array 82 <h3>Return value</h3> 83 a 1d array 83 84 84 85 … … 93 94 94 95 <h4>Version</h4> 95 $Id: n256gaussian.pro 23 1 2007-03-19 17:15:51Z pinsard $96 $Id: n256gaussian.pro 238 2007-03-27 13:43:18Z pinsard $ 96 97 97 98 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/Grid/n48gaussian.html
r234 r242 80 80 81 81 82 <h3>Return value</h3> a 1d array 82 <h3>Return value</h3> 83 a 1d array 83 84 84 85 … … 93 94 94 95 <h4>Version</h4> 95 $Id: n48gaussian.pro 23 1 2007-03-19 17:15:51Z pinsard $96 $Id: n48gaussian.pro 238 2007-03-27 13:43:18Z pinsard $ 96 97 97 98 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/Grid/n80gaussian.html
r234 r242 61 61 </dl> 62 62 63 63 64 64 compute the latitudes of the n80 gaussian grid. See: 65 65 <a href="http://www.ecmwf.int/products/data/technical/gaussian/n80FIS.html">Gaussian 80</a> … … 80 80 81 81 82 <h3>Return value</h3> a 1d array 82 <h3>Return value</h3> 83 a 1d array 83 84 84 85 … … 93 94 94 95 <h4>Version</h4> 95 $Id: n80gaussian.pro 23 2 2007-03-20 16:59:36Z pinsard $96 $Id: n80gaussian.pro 238 2007-03-27 13:43:18Z pinsard $ 96 97 97 98 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/Grid/ncdf_meshread.html
r234 r242 251 251 252 252 253 the calling command used to call computegrid (this is used by <a href=". //../../ToBeReviewed/WIDGET/xxx.html">xxx</a>)253 the calling command used to call computegrid (this is used by <a href="..//ToBeReviewed/WIDGET/xxx.html">xxx</a>) 254 254 255 255 … … 267 267 268 268 269 Used to pass keywords to <a href=". //../../Utilities/isafile.html">isafile</a>269 Used to pass keywords to <a href="..//Utilities/isafile.html">isafile</a> 270 270 271 271 … … 278 278 279 279 <h4>Version</h4> 280 $Id: ncdf_meshread.pro 2 32 2007-03-20 16:59:36Z pinsard $280 $Id: ncdf_meshread.pro 240 2007-03-28 12:17:24Z pinsard $ 281 281 282 282 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/Grid/ncdf_meshroms.html
r234 r242 267 267 268 268 269 Used to pass keywords to <a href=". //../../Utilities/isafile.html">isafile</a>269 Used to pass keywords to <a href="..//Utilities/isafile.html">isafile</a> 270 270 271 271 … … 278 278 279 279 <h4>Version</h4> 280 $Id: ncdf_meshroms.pro 2 31 2007-03-19 17:15:51Z pinsard $280 $Id: ncdf_meshroms.pro 240 2007-03-28 12:17:24Z pinsard $ 281 281 282 282 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/Grid/numbisland.html
r234 r242 66 66 67 67 68 given a 2D land-se mask, give a number to each islands68 given a 2D land-sea mask, give a number to each island 69 69 70 70 … … 81 81 82 82 83 83 84 84 85 <h3>Return value</h3> … … 116 117 117 118 <h4>Version</h4> 118 $Id: numbisland.pro 231 2007-03-19 17:15:51Z pinsard $ 119 $Id: numbisland.pro 240 2007-03-28 12:17:24Z pinsard $ 120 119 121 <h4>History</h4> 120 122 Jan 2006: sebastien masson (smasson@locean-ipsl.upmc.fr) -
trunk/SRC/Documentation/idldoc_assistant_output/Grid/restoreboxparam.html
r234 r242 62 62 63 63 64 restore all the zoom parameters (defined by calling <a href=". //../../ToBeReviewed/GRILLE/domdef.html">domdef</a>)64 restore all the zoom parameters (defined by calling <a href="..//ToBeReviewed/GRILLE/domdef.html">domdef</a>) 65 65 previously defined by <a href=".//saveboxparam.html">saveboxparam</a> 66 66 … … 91 91 <font size="-1" color="#006633">required</font> 92 92 93 93 <font size="-1" color="#006633">type:</font> <font size="-1" color="#006633"><i> scalar string</i></font> 94 94 95 95 … … 97 97 98 98 99 a scalar string definingthe file name99 the file name 100 100 101 101 … … 110 110 111 111 <h4>Version</h4> 112 $Id: restoreboxparam.pro 23 1 2007-03-19 17:15:51Z pinsard $112 $Id: restoreboxparam.pro 238 2007-03-27 13:43:18Z pinsard $ 113 113 114 114 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/Grid/romsdepth.html
r234 r242 92 92 93 93 <h4>Version</h4> 94 $Id: romsdepth.pro 231 2007-03-19 17:15:51Z pinsard $ 94 $Id: romsdepth.pro 238 2007-03-27 13:43:18Z pinsard $ 95 95 96 <h4>History</h4> 96 97 Sept 2006 Sebastien Masson (smasson@lodyc.jussieu.fr) … … 110 111 111 112 <h4>Uses routines</h4> 112 cm_4mesh cm_4data 113 cm_4mesh 114 cm_4data 113 115 114 116 -
trunk/SRC/Documentation/idldoc_assistant_output/Grid/saveboxparam.html
r234 r242 62 62 63 63 64 save all the zoom parameters (defined by calling <a href=". //../../ToBeReviewed/GRILLE/domdef.html">domdef</a>)64 save all the zoom parameters (defined by calling <a href="..//ToBeReviewed/GRILLE/domdef.html">domdef</a>) 65 65 in a file (using save command) located in myuniquetmpdir 66 66 (common variable defined by def_myuniquetmpdir) … … 92 92 <font size="-1" color="#006633">required</font> 93 93 94 94 <font size="-1" color="#006633">type:</font> <font size="-1" color="#006633"><i>scalar string</i></font> 95 95 96 96 … … 98 98 99 99 100 a scalar string definingthe file name100 the file name 101 101 102 102 … … 111 111 112 112 <h4>Version</h4> 113 $Id: saveboxparam.pro 23 1 2007-03-19 17:15:51Z pinsard $113 $Id: saveboxparam.pro 238 2007-03-27 13:43:18Z pinsard $ 114 114 115 115 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/Grid/smallmeshmask.html
r234 r242 76 76 77 77 <dt><a href="#_smallmeshmask">smallmeshmask<i>, ncfilein[, ncfileout]</i>, IODIR=<i>IODIR</i></a><dt> 78 <dd><font size="-1"> </font></dd>78 <dd><font size="-1"> </font></dd> 79 79 80 80 </dl> … … 114 114 115 115 116 116 117 117 118 … … 129 130 130 131 132 131 133 132 134 … … 144 146 145 147 148 146 149 147 150 … … 169 172 170 173 <h4>Version</h4> 171 $Id: smallmeshmask.pro 2 31 2007-03-19 17:15:51Z pinsard $174 $Id: smallmeshmask.pro 240 2007-03-28 12:17:24Z pinsard $ 172 175 173 176 <h4>History</h4> … … 203 206 204 207 208 205 209 206 210 … … 266 270 </h4> 267 271 268 to define the files path. 272 273 to define the files path. 274 269 275 270 276 … … 277 283 278 284 <h4>Version</h4> 279 $Id: smallmeshmask.pro 2 31 2007-03-19 17:15:51Z pinsard $285 $Id: smallmeshmask.pro 240 2007-03-28 12:17:24Z pinsard $ 280 286 281 287 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/Interpolation/angle.html
r234 r242 64 64 north stereographic polar projection 65 65 66 66 67 Compute angles between grid lines and direction of the North pole 67 68 (fom angle.F,v 2.2 in OPA8.2) … … 80 81 81 82 83 82 84 83 85 … … 252 254 253 255 <h4>Version</h4> 254 $Id: angle.pro 232 2007-03-20 16:59:36Z pinsard $ 256 $Id: angle.pro 238 2007-03-27 13:43:18Z pinsard $ 257 255 258 <h4>History</h4> 256 259 Original : 96-07 (O. Marti) -
trunk/SRC/Documentation/idldoc_assistant_output/Interpolation/clickincell.html
r234 r242 105 105 106 106 107 = 'T', 'W', 'U', 'V' or 'F' This this the type of point 107 = 'T', 'W', 'U', 'V' or 'F' 108 the type of point 108 109 that is located in the center of the cell which the click is 109 110 located. default is T type of cell (with corner defined by F … … 174 175 175 176 176 see outputs177 see returns 177 178 178 179 … … 190 191 191 192 192 Used to pass extra keywords to <a href=".//inquad.html">inquad</a> and 193 Used to pass extra keywords to <a href=".//inquad.html">inquad</a> and 193 194 <proidl>plot</proidl> 194 195 (when /drawcell) … … 209 210 210 211 <h4>Version</h4> 211 $Id: clickincell.pro 23 2 2007-03-20 16:59:36Z pinsard $212 $Id: clickincell.pro 238 2007-03-27 13:43:18Z pinsard $ 212 213 213 214 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/Interpolation/compute_fromirr_bilinear_weigaddr.html
r234 r242 235 235 236 236 <h4>Version</h4> 237 $Id: compute_fromirr_bilinear_weigaddr.pro 23 2 2007-03-20 16:59:36Z pinsard $237 $Id: compute_fromirr_bilinear_weigaddr.pro 238 2007-03-27 13:43:18Z pinsard $ 238 238 239 239 <h4>History</h4> … … 257 257 and the weight is redistributed on the remaining "water" corners 258 258 - points located out of the southern and northern boundaries or in cells 259 containing only land points are set the thesame value as their closest neighbor259 containing only land points are set the same value as their closest neighbor 260 260 261 261 -
trunk/SRC/Documentation/idldoc_assistant_output/Interpolation/compute_fromreg_bilinear_weigaddr.html
r234 r242 236 236 237 237 <h4>Version</h4> 238 $Id: compute_fromreg_bilinear_weigaddr.pro 23 2 2007-03-20 16:59:36Z pinsard $238 $Id: compute_fromreg_bilinear_weigaddr.pro 238 2007-03-27 13:43:18Z pinsard $ 239 239 240 240 <h4>History</h4> … … 249 249 <h4>Restrictions</h4> 250 250 - the input grid must be a "regular grid", defined as a grid for which each 251 longitude s lines have the same latitude and each latitudescolumns have the251 longitude lines have the same latitude and each latitude columns have the 252 252 same longitude. 253 253 - We supposed the data are located on a sphere, with a periodicity along -
trunk/SRC/Documentation/idldoc_assistant_output/Interpolation/compute_fromreg_imoms3_weigaddr.html
r234 r242 236 236 237 237 <h4>Version</h4> 238 $Id: compute_fromreg_imoms3_weigaddr.pro 23 1 2007-03-19 17:15:51Z pinsard $238 $Id: compute_fromreg_imoms3_weigaddr.pro 238 2007-03-27 13:43:18Z pinsard $ 239 239 240 240 <h4>History</h4> … … 250 250 <h4>Restrictions</h4> 251 251 - the input grid must be a "regular/rectangular grid", defined as a grid for 252 which each longitude s lines have the same latitude and each latitudescolumns252 which each longitude lines have the same latitude and each latitude columns 253 253 have the same longitude. 254 254 - We supposed the data are located on a sphere, with a periodicity along -
trunk/SRC/Documentation/idldoc_assistant_output/Interpolation/cutpar.html
r234 r242 209 209 210 210 1d arrays of p elements, giving the edge positions. 211 The edges must be given as in plot to draw the parallelogram. (see example). 211 The edges must be given as in <proidl>plot</proidl> to draw the 212 parallelogram. (see example). 212 213 213 214 … … 248 249 249 250 250 see outputs251 see returns 251 252 252 253 … … 265 266 266 267 to specify that the points are located on a 267 sphere. In this case, x and y correspond sto longitude and268 sphere. In this case, x and y correspond to longitude and 268 269 latitude in degrees. 269 270 -
trunk/SRC/Documentation/idldoc_assistant_output/Interpolation/cutsegment.html
r234 r242 187 187 188 188 189 see outputs189 see returns 190 190 191 191 … … 204 204 205 205 to specify that the points are located on a sphere. 206 In this case, x and y correspond sto longitude and latitude in degrees.206 In this case, x and y correspond to longitude and latitude in degrees. 207 207 208 208 … … 210 210 211 211 <h3>Examples</h3><pre> 212 213 212 IDL> x0=[2,5] 214 213 IDL> y0=[5,1] -
trunk/SRC/Documentation/idldoc_assistant_output/Interpolation/extrapolate.html
r234 r242 62 62 63 63 64 extrapolate data (zinput) where maskinput eq 0 by filling step by64 extrapolate data (zinput) where maskinput equal 0 by filling step by 65 65 step the coastline points with the mean value of the 8 neighbourgs 66 66 (weighted by their mask value). … … 81 81 82 82 83 <h3>Return value</h3> {type=2d array}84 the extrapolated array83 <h3>Return value</h3> 84 the extrapolated 2d array 85 85 86 86 … … 137 137 138 138 139 Maximum number if iterations done in the extrapolation process. If there139 Maximum number of iterations done in the extrapolation process. If there 140 140 is no more masked values we exit extrapolate before reaching nb_iteration 141 141 (to be sure to fill everything, you can use a very large value) … … 225 225 226 226 <h4>Version</h4> 227 $Id: extrapolate.pro 23 2 2007-03-20 16:59:36Z pinsard $227 $Id: extrapolate.pro 238 2007-03-27 13:43:18Z pinsard $ 228 228 229 229 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/Interpolation/extrapsmooth.html
r234 r242 62 62 63 63 64 similar to extrapolate but could to the job in a better way because the 65 extrapolated values are smoothed... takes more time than extrapolate. 66 extrapolate data where mskin eq 0 by filling 64 similar to <a href=".//extrapolate.html">extrapolate</a> but could to the job in a better way 65 because the extrapolated values are smoothed... 66 takes more time than <a href=".//extrapolate.html">extrapolate</a>. 67 extrapolate data where mskin is equal 0 by filling 67 68 step by step the coastline points with the mean value of the 8 neighbourgs. 68 69 … … 204 205 205 206 <h4>Version</h4> 206 $Id: extrapsmooth.pro 23 2 2007-03-20 16:59:36Z pinsard $207 $Id: extrapsmooth.pro 238 2007-03-27 13:43:18Z pinsard $ 207 208 <h4>History</h4> 208 209 January 2007: Sebastien Masson (smasson@lodyc.jussieu.fr) -
trunk/SRC/Documentation/idldoc_assistant_output/Interpolation/fromirr.html
r234 r242 101 101 102 102 103 a string definingthe interpolation method. must be 'bilinear'103 the interpolation method. must be 'bilinear' 104 104 105 105 … … 118 118 119 119 120 a 2D arraythe input data to interpolate120 the input data to interpolate 121 121 122 122 … … 135 135 136 136 137 a 2D array definingthe longitude of the input data137 the longitude of the input data 138 138 139 139 … … 152 152 153 153 154 a 2D array definingthe latitude of the input data.154 the latitude of the input data. 155 155 156 156 … … 187 187 188 188 189 1D or 2D array definingthe longitude of the output data.189 the longitude of the output data. 190 190 191 191 … … 204 204 205 205 206 1D or 2D array definingthe latitude of the output data.206 the latitude of the output data. 207 207 208 208 … … 289 289 IDL> help, a, b 290 290 291 2) use a and b that are now defined to bypass the computation of the weights and addresses292 and speed-up the computation!291 2) use a and b that are now defined to bypass the computation of the weights 292 and addresses and speed-up the computation! 293 293 294 294 IDL> t2ncep = fromirr('bilinear', topa, WEIG = a, ADDR = b) … … 297 297 298 298 <h4>Version</h4> 299 $Id: fromirr.pro 23 1 2007-03-19 17:15:51Z pinsard $299 $Id: fromirr.pro 238 2007-03-27 13:43:18Z pinsard $ 300 300 301 301 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/Interpolation/fromreg.html
r234 r242 64 64 interpolate data from a "regular/rectangular grid" to any grid. 65 65 2 methods available: bilinear and imoms3 66 A "regular/rectangular grid" is defined as a grid for which each longitudes lines have 67 the same latitude and each latitudes columns have the same longitude. 66 A "regular/rectangular grid" is defined as a grid for which 67 each longitude lines have the same latitude and each latitude columns 68 have the same longitude. 68 69 69 70 … … 103 104 104 105 105 a string definingthe interpolation method.106 the interpolation method. 106 107 must be 'bilinear' or 'imoms3' 107 108 … … 121 122 122 123 123 a 2D arraythe input data to interpolate124 the input data to interpolate 124 125 125 126 … … 138 139 139 140 140 1D or 2D array definingthe longitude of the input data141 the longitude of the input data 141 142 142 143 … … 155 156 156 157 157 1D or 2D array definingthe latitude of the input data158 the latitude of the input data 158 159 159 160 … … 172 173 173 174 174 1D or 2D array definingthe longitude of the output data175 the longitude of the output data 175 176 176 177 … … 189 190 190 191 191 1D or 2D array definingthe latitude of the output data192 the latitude of the output data 192 193 193 194 … … 284 285 285 286 1) get back the weights and addresses in variables a and b 286 (that must be undefined or equal to 0 before calling fromreg )287 (that must be undefined or equal to 0 before calling fromreg 287 288 288 289 IDL> t1opa = fromreg('bilinear', t1ncep, xncep, yncep, glamt, gphit, WEIG = a, ADDR = b) … … 297 298 298 299 <h4>Version</h4> 299 $Id: fromreg.pro 23 1 2007-03-19 17:15:51Z pinsard $300 $Id: fromreg.pro 238 2007-03-27 13:43:18Z pinsard $ 300 301 301 302 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/Interpolation/get_gridparams.html
r234 r242 66 66 67 67 or 68 2) given longitude and latitude arrays get their dimensions and make68 2) given longitude and latitude arrays, get their dimensions and make 69 69 sure they are 1D or 2D arrays 70 70 … … 104 104 105 105 Case 1: the name of the netcdf file 106 Case 2: 1d or 2 Darrays defining longitudes and latitudes.106 Case 2: 1d or 2d arrays defining longitudes and latitudes. 107 107 Out: the variable that will contain the longitudes 108 108 … … 123 123 124 124 Case 1: the name of the variable that contains the longitude in the NetCDF file 125 Case 2: 1d or 2 Darrays defining longitudes and latitudes.125 Case 2: 1d or 2d arrays defining longitudes and latitudes. 126 126 Note that these arrays are also outputs and can therefore be modified. 127 127 Out: the variable that will contain the latitudes … … 181 181 Case 2: 1 or 2 to specify if lon and lat should be 1D (jpi or jpj) 182 182 arrays or 2D arrays (jpi,jpj). Note that of n_dimensions = 1, then the 183 grid must be regular (each longitude smust be the same for all latitudes184 and each latitude sshould be the same for all longitudes).183 grid must be regular (each longitude must be the same for all latitudes 184 and each latitude should be the same for all longitudes). 185 185 186 186 … … 270 270 IDL> get_gridparams, lon, lat, jpi, jpj, n_dimensions 271 271 272 1)273 272 274 273 … … 281 280 282 281 <h4>Version</h4> 283 $Id: get_gridparams.pro 23 1 2007-03-19 17:15:51Z pinsard $282 $Id: get_gridparams.pro 238 2007-03-27 13:43:18Z pinsard $ 284 283 285 284 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/Interpolation/imoms3.html
r234 r242 75 75 76 76 77 78 77 79 78 -
trunk/SRC/Documentation/idldoc_assistant_output/Interpolation/inquad.html
r234 r242 80 80 81 81 <h3>Return value</h3> 82 a n element vector. Where n is the number of elements of82 a n elements vector where n is the number of elements of 83 83 x. res[i]=j means that the point number i is located in the 84 84 quadrilateral number j with (0 <= j <= n_elements(x0)-1) … … 300 300 301 301 the zoom (circle centered on the (x,y) with a radius of 302 zoomradius degree where we look for the thequadrilateral which302 zoomradius degree where we look for the quadrilateral which 303 303 contains the (x,y) point) used for the satellite projection 304 304 when /ONSPHERE is activated. … … 363 363 364 364 <h4>Version</h4> 365 $Id: inquad.pro 2 32 2007-03-20 16:59:36Z pinsard $365 $Id: inquad.pro 240 2007-03-28 12:17:24Z pinsard $ 366 366 367 367 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/Interpolation/inrecgrid.html
r234 r242 72 72 <a name="#_inrecgrid"></a> 73 73 74 <h2>inrecgrid <font size="-1" color="#006633"> 74 <h2>inrecgrid <font size="-1" color="#006633"> 75 75 Without loop 76 76 </font></h2> … … 215 215 216 216 <h4>Version</h4> 217 $Id: inrecgrid.pro 23 1 2007-03-19 17:15:51Z pinsard $217 $Id: inrecgrid.pro 238 2007-03-27 13:43:18Z pinsard $ 218 218 219 219 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/Interpolation/ll_narcs_distances.html
r234 r242 64 64 This function returns the longitude and latitude [lon, lat] of 65 65 a point a given arc distance (-pi <= Arc_Dist <= pi), and azimuth (Az), 66 from a specified location Lon0, lat0.67 Same as LL_ARC_DISTANCEbut for n points without do loop.66 from a specified location Lon0, Lat0. 67 Same as <proidl>LL_ARC_DISTANCE</proidl> but for n points without do loop. 68 68 69 69 Formula from Map Projections - a working manual. USGS paper … … 76 76 <a name="#_ll_narcs_distances"></a> 77 77 78 <h2>ll_narcs_distances <font size="-1" color="#006633"> 78 <h2>ll_narcs_distances <font size="-1" color="#006633"> 79 79 Mapping, geography 80 80 </font></h2> … … 86 86 87 87 <h3>Return value</h3> 88 a (2, 88 a (2,n) array containing the longitude/latitude of the resulting points. 89 89 Values are in radians unless the keyword DEGREES is set. 90 90 … … 215 215 216 216 <h4>Version</h4> 217 $Id: ll_narcs_distances.pro 23 1 2007-03-19 17:15:51Z pinsard $217 $Id: ll_narcs_distances.pro 238 2007-03-27 13:43:18Z pinsard $ 218 218 219 219 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/Interpolation/map_npoints.html
r234 r242 66 66 returns the distances between number n of P0 points and number 67 67 n of P1 points (in that case, np0 and np1 must be equal). 68 Same as map_2points with the meter parameter but for n points69 without do loop.68 Same as <proidl>map_2points</proidl> with the meter parameter but for n 69 points without do loop. 70 70 71 71 … … 88 88 points P0 and np1 points P1. Element (i,j) of the output is the 89 89 distance between element P0[i] and P1[j]. 90 If keyword /TWO_BY_TWO is given then Map_nPointsreturns91 an np-element vector giving the distance in meter between P0[i]90 If keyword /TWO_BY_TWO is given then <a href=".//map_npoints.html">map_npoints</a> returns 91 an np-elements vector giving the distance in meter between P0[i] 92 92 and P1[i] (in that case, we have np0 = np1 = np) ; if /MIDDLE see this keyword. 93 93 … … 245 245 246 246 247 If given, then Map_nPoints returns the distances between number n of248 P0 points and number n of P1 points247 If given, then <a href=".//map_npoints.html">map_npoints</a> returns the distances between 248 number n of P0 points and number n of P1 pointsi. 249 249 In that case, np0 and np1 must be equal. 250 250 … … 301 301 302 302 <h4>Version</h4> 303 $Id: map_npoints.pro 23 1 2007-03-19 17:15:51Z pinsard $303 $Id: map_npoints.pro 238 2007-03-27 13:43:18Z pinsard $ 304 304 305 305 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/Interpolation/neighbor.html
r234 r242 62 62 63 63 64 find the close test point of (P0) within a list of np1 points65 P1 Which can be on a sphere64 find the closest point of (P0) within a list of np1 points 65 P1 which can be on a sphere 66 66 67 67 … … 75 75 </font></h2> 76 76 77 <p><font face="Courier"><i>result = </i>neighbor(<i><a href="#_neighbor_keyword_p0lon">p0lon</a>, <a href="#_neighbor_keyword_p0lat">p0lat</a>[, <a href="#_neighbor_keyword_neighlon">neighlon</a>][, <a href="#_neighbor_keyword_neighlat">neighlat</a>]</i>, <a href="#_neighbor_keyword_ sphere">sphere</a>=<i>sphere</i>, <a href="#_neighbor_keyword_distance">distance</a>=<i>distance</i>, <a href="#_neighbor_keyword_radians">radians</a>=<i>radians</i>)</font></p>77 <p><font face="Courier"><i>result = </i>neighbor(<i><a href="#_neighbor_keyword_p0lon">p0lon</a>, <a href="#_neighbor_keyword_p0lat">p0lat</a>[, <a href="#_neighbor_keyword_neighlon">neighlon</a>][, <a href="#_neighbor_keyword_neighlat">neighlat</a>]</i>, <a href="#_neighbor_keyword_SPHERE">SPHERE</a>=<i>SPHERE</i>, <a href="#_neighbor_keyword_DISTANCE">DISTANCE</a>=<i>DISTANCE</i>, <a href="#_neighbor_keyword_RADIANS">RADIANS</a>=<i>RADIANS</i>)</font></p> 78 78 79 79 … … 95 95 <font size="-1" color="#006633">required</font> 96 96 97 98 99 100 </h4> 101 102 103 scalar.longitudes of point P0.97 <font size="-1" color="#006633">type:</font> <font size="-1" color="#006633"><i>scalar</i></font> 98 99 100 </h4> 101 102 103 longitudes of point P0. 104 104 105 105 … … 112 112 <font size="-1" color="#006633">required</font> 113 113 114 115 116 117 </h4> 118 119 120 scalar.latitudes of point P0.114 <font size="-1" color="#006633">type:</font> <font size="-1" color="#006633"><i>scalar</i></font> 115 116 117 </h4> 118 119 120 latitudes of point P0. 121 121 122 122 … … 159 159 160 160 161 <a name="#_neighbor_keyword_sphere"></a> 162 <h4>sphere 163 164 165 166 167 168 169 170 171 </h4> 172 173 to activate if points are located on a sphere. 174 175 176 <a name="#_neighbor_keyword_distance"></a> 177 <h4>distance 161 <a name="#_neighbor_keyword_SPHERE"></a> 162 <h4>SPHERE 163 164 165 166 167 168 169 170 171 </h4> 172 173 174 to activate if points are located on a sphere. 175 176 177 <a name="#_neighbor_keyword_DISTANCE"></a> 178 <h4>DISTANCE 178 179 179 180 … … 191 192 192 193 193 <a name="#_neighbor_keyword_ radians"></a>194 <h4> radians 194 <a name="#_neighbor_keyword_RADIANS"></a> 195 <h4>RADIANS 195 196 196 197 … … 219 220 220 221 <h4>Version</h4> 221 $Id: neighbor.pro 23 1 2007-03-19 17:15:51Z pinsard $222 $Id: neighbor.pro 238 2007-03-27 13:43:18Z pinsard $ 222 223 223 224 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/Interpolation/quadrilateral2square.html
r234 r242 90 90 91 91 <h3>Return value</h3> 92 93 (2,n) array: the new coordinates (xout, yout) of the (xin,yin) point(s) after 92 (2,n) array: the new coordinates (xout,yout) of the (xin,yin) point(s) after 94 93 mapping. 95 94 If xin is a scalar, then n is equal to the number of elements of x0. 96 If xin is an array 95 If xin is an array, then n is equal to the number of elements of xin. 97 96 98 97 … … 299 298 300 299 <h4>Version</h4> 301 $Id: quadrilateral2square.pro 23 1 2007-03-19 17:15:51Z pinsard $300 $Id: quadrilateral2square.pro 238 2007-03-27 13:43:18Z pinsard $ 302 301 303 302 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/Interpolation/spl_fstdrv.html
r234 r242 62 62 63 63 64 SPL_FSTDRVreturns the values of the first derivative of64 returns the values of the first derivative of 65 65 the interpolating function at the points X2i. It is a double 66 66 precision array. 67 67 68 68 Given the arrays X and Y, which tabulate a function (with the X[i] 69 ANDY[i] in ascending order), and given an input value X2, the70 SPL_INCR function returns an interpolated value for the given values71 of X2. The interpolation method is based on cubic spline, corrected72 in a way that interpolated value are also in ascending order 69 and Y[i] in ascending order), and given an input value X2, the 70 <a href=".//spl_incr.html">spl_incr</a> function returns an interpolated value for the given 71 values of X2. The interpolation method is based on cubic spline, corrected 72 in a way that interpolated value are also in ascending order. 73 73 74 74 … … 106 106 107 107 108 An n-element (at least 2) input vector that specifies the108 An n-elements (at least 2) input vector that specifies the 109 109 tabulate points in ascending order. 110 110 … … 124 124 125 125 126 f(x) = y. An n-element input vector that specifies the values126 f(x) = y. An n-elements input vector that specifies the values 127 127 of the tabulated function F(Xi) corresponding to Xi. 128 128 … … 142 142 143 143 144 The output from SPL_INITfor the specified X and Y.144 The output from <proidl>SPL_INIT</pro> for the specified X and Y. 145 145 146 146 … … 153 153 <font size="-1" color="#006633">required</font> 154 154 155 155 <font size="-1" color="#006633">type:</font> <font size="-1" color="#006633"><i> scalar or array</i></font> 156 156 157 157 … … 160 160 161 161 The input values for which the first derivative values are desired. 162 X can be scalar or an array of values.163 162 164 163 … … 173 172 174 173 <h4>Version</h4> 175 $Id: spl_fstdrv.pro 23 1 2007-03-19 17:15:51Z pinsard $174 $Id: spl_fstdrv.pro 238 2007-03-27 13:43:18Z pinsard $ 176 175 177 176 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/Interpolation/spl_incr.html
r234 r242 62 62 63 63 64 65 64 Given the arrays X and Y, which tabulate a function (with the X[i] 66 65 AND Y[i] in ascending order), and given an input value X2, the 67 SPL_INCRfunction returns an interpolated value for the given values66 spl_incr function returns an interpolated value for the given values 68 67 of X2. The interpolation method is based on cubic spline, corrected 69 68 in a way that interpolated values are also monotonically increasing. … … 79 78 80 79 <dt><a href="#_pure_convex"><i>result = </i>pure_convex(<i>x1, x2, y1, y2, der2, x</i>)</a><dt> 81 <dd><font size="-1"> </font></dd>80 <dd><font size="-1"> </font></dd> 82 81 83 82 <dt><a href="#_spl_incr"><i>result = </i>spl_incr(<i>x, y, x2</i>, YP0=<i>YP0</i>, YPN_1=<i>YPN_1</i>)</a><dt> 84 <dd><font size="-1"> </font></dd>83 <dd><font size="-1"> </font></dd> 85 84 86 85 </dl> … … 100 99 101 100 <h3>Return value</h3> 102 103 y2: f(x2) = y2. Double precision array 101 y2: f(x2) = y2. Double precision array 104 102 105 103 … … 121 119 122 120 123 An n-element (at least 2) input vector that specifies the tabulate points in121 An n-elements (at least 2) input vector that specifies the tabulate points in 124 122 a strict ascending order. 125 123 … … 157 155 158 156 159 f(x) = y. An n-element input vector that specifies the values157 f(x) = y. An n-elements input vector that specifies the values 160 158 of the tabulated function F(Xi) corresponding to Xi. As f is 161 159 supposed to be monotonically increasing, y values must be … … 215 213 216 214 <h3>Examples</h3><pre> 217 218 215 IDL> n = 100L 219 216 IDL> x = (dindgen(n))^2 … … 238 235 239 236 <h4>Version</h4> 240 $Id: spl_incr.pro 23 1 2007-03-19 17:15:51Z pinsard $237 $Id: spl_incr.pro 238 2007-03-27 13:43:18Z pinsard $ 241 238 242 239 <h4>History</h4> … … 273 270 274 271 272 275 273 276 274 … … 292 290 293 291 294 An n-element (at least 2) input vector that specifies the tabulate points in292 An n-elements (at least 2) input vector that specifies the tabulate points in 295 293 a strict ascending order. 296 294 … … 328 326 329 327 330 f(x) = y. An n-element input vector that specifies the values328 f(x) = y. An n-elements input vector that specifies the values 331 329 of the tabulated function F(Xi) corresponding to Xi. As f is 332 330 supposed to be monotonically increasing, y values must be … … 363 361 364 362 363 365 364 366 365 … … 416 415 417 416 417 418 418 419 419 … … 484 484 </h4> 485 485 486 The first derivative of the interpolating function at the 486 487 The first derivative of the interpolating function at the 487 488 point X0. If YP0 is omitted, the second derivative at the 488 489 boundary is set to zero, resulting in a "natural spline." 490 489 491 490 492 <a name="#_spl_incr_keyword_YPN_1"></a> … … 500 502 </h4> 501 503 502 The first derivative of the interpolating function at the 504 505 The first derivative of the interpolating function at the 503 506 point Xn-1. If YPN_1 is omitted, the second derivative at the 504 507 boundary is set to zero, resulting in a "natural spline." -
trunk/SRC/Documentation/idldoc_assistant_output/Interpolation/spl_keep_mean.html
r234 r242 62 62 63 63 64 65 64 Given the arrays X and Y, which tabulate a function (with the X[i] 66 65 AND Y[i] in ascending order), and given an input value X2, the 67 SPL_INCRfunction returns an interpolated value for the given values66 <a href=".//spl_incr.html">spl_incr</a> function returns an interpolated value for the given values 68 67 of X2. The interpolation method is based on cubic spline, corrected 69 68 in a way that integral of the interpolated values is the same as the … … 107 106 108 107 109 An n-element (at least 2) input vector that specifies the tabulate points in108 An n-elements (at least 2) input vector that specifies the tabulate points in 110 109 a strict ascending order. 111 110 … … 233 232 234 233 <h4>Version</h4> 235 $Id: spl_keep_mean.pro 23 2 2007-03-20 16:59:36Z pinsard $234 $Id: spl_keep_mean.pro 238 2007-03-27 13:43:18Z pinsard $ 236 235 237 236 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/Interpolation/square2quadrilateral.html
r234 r242 88 88 89 89 <h3>Return value</h3> 90 (2,n) array: the new coordinates (xout, 90 (2,n) array: the new coordinates (xout,yout) of the (xin,yin) 91 91 point(s) after mapping. 92 92 If xin is a scalar, then n is equal to the number of elements of 93 93 x0. If xin is an array , then n is equal to the number of 94 94 elements of xin. 95 If xin and yin are omited, square2quadrilateralreturns the95 If xin and yin are omited, <a href=".//square2quadrilateral.html">square2quadrilateral</a> returns the 96 96 matrix A which is used for the inverse transformation. 97 97 … … 223 223 Can be scalar or array. 224 224 (x0,y0), (x1,y1), (x2,y2) and (x3,y3) are given in the anticlockwise order. 225 226 225 227 226 … … 274 273 275 274 <h4>Version</h4> 276 $Id: square2quadrilateral.pro 23 1 2007-03-19 17:15:51Z pinsard $275 $Id: square2quadrilateral.pro 238 2007-03-27 13:43:18Z pinsard $ 277 276 278 277 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/Matrix/cmapply.html
r234 r242 110 110 111 111 It's worth noting however, that the implementation of user-defined 112 functions is not particularly optimized for speed. 112 functions is not particularly optimized for speed. Users are 113 113 encouraged to implement their own array if the number of output 114 114 elements is large. … … 124 124 125 125 <dt><a href="#_cmapply_redim">cmapply_redim<i>, newarr, dimapply, dimkeep, nkeep, totcol, totkeep</i></a><dt> 126 <dd><font size="-1"> </font></dd>126 <dd><font size="-1"> </font></dd> 127 127 128 128 <dt><a href="#_cmapply"><i>result = </i>cmapply(<i>op, array[, dimapply]</i>, double=<i>double</i>, type=<i>type</i>, functargs=<i>functargs</i>, nocatch=<i>nocatch</i>)</a><dt> … … 164 164 165 165 166 167 166 168 167 … … 173 172 </pre><h3>Version history</h3> 174 173 175 <h4>Version</h4> $Id: cmapply.pro 232 2007-03-20 16:59:36Z pinsard $ 174 <h4>Version</h4> 175 $Id: cmapply.pro 238 2007-03-27 13:43:18Z pinsard $ 176 176 177 177 … … 203 203 204 204 205 205 206 206 207 … … 223 224 224 225 225 226 226 227 227 … … 240 240 241 241 242 243 242 244 243 … … 257 256 258 257 259 260 258 261 259 … … 274 272 275 273 276 277 274 278 275 … … 291 288 292 289 293 294 290 295 291 … … 308 304 309 305 310 311 306 312 307 … … 325 320 326 321 <h4>Todo items</h4> seb 322 327 323 328 324 … … 340 336 <a name="#_cmapply"></a> 341 337 342 <h2>cmapply <font size="-1" color="#006633"> 338 <h2>cmapply <font size="-1" color="#006633"> 343 339 Array 344 340 </font></h2> … … 393 389 </h4> 394 390 395 391 396 392 An array of values to be operated on. 397 393 Must not be of type STRING (7) or STRUCTURE (8). … … 413 409 414 410 An array of dimensions that are to be "collapsed", where 415 the thefirst dimension starts with 1 (ie, same convention411 the first dimension starts with 1 (ie, same convention 416 412 as IDL function TOTAL). Whereas TOTAL only allows one 417 413 dimension to be added, you can specify multiple dimensions … … 460 456 461 457 Set this to the IDL code of the desired output type (refer 462 to documentation of SIZE()). Internal results will be458 to documentation of <proidl>SIZE</proidl>()). Internal results will be 463 459 rounded to the nearest integer if the output type is an 464 460 integer type. … … 545 541 </pre><h3>Version history</h3> 546 542 547 <h4>Version</h4> 548 $Id: cmapply.pro 23 2 2007-03-20 16:59:36Z pinsard $549 550 <h4>History</h4> 543 <h4>Version</h4> 544 $Id: cmapply.pro 238 2007-03-27 13:43:18Z pinsard $ 545 546 <h4>History</h4> 551 547 Mar 1998, Written, CM 552 548 Changed usage message to not bomb, 24 Mar 2000, CM -
trunk/SRC/Documentation/idldoc_assistant_output/Matrix/cmset_op.html
r234 r242 114 114 <a name="#_cmset_op"></a> 115 115 116 <h2>cmset_op <font size="-1" color="#006633"> 116 <h2>cmset_op <font size="-1" color="#006633"> 117 117 Array 118 118 </font></h2> … … 359 359 </pre><h3>Version history</h3> 360 360 361 <h4>Version</h4> $Id: cmset_op.pro 163 2006-08-29 12:59:46Z navarro $ 362 363 <h4>History</h4> Written, CM, 23 Feb 2000 361 <h4>Version</h4> 362 $Id: cmset_op.pro 238 2007-03-27 13:43:18Z pinsard $ 363 364 <h4>History</h4> 365 Written, CM, 23 Feb 2000 364 366 Added empty set capability, CM, 25 Feb 2000 365 367 Documentation clarification, CM 02 Mar 2000 -
trunk/SRC/Documentation/idldoc_assistant_output/Matrix/extrac2.html
r234 r242 95 95 <a name="#_extrac2"></a> 96 96 97 <h2>extrac2 <font size="-1" color="#006633"> 97 <h2>extrac2 <font size="-1" color="#006633"> 98 98 Utilities 99 99 </font></h2> … … 206 206 I have a dim 2 matrix named A. I want extract a small intersection 207 207 matrix 2d of the line 2,3 and 7 and of the column 0 and 1: 208 208 209 209 IDL> res=extrac2(A,[2,3,7],[0,1]) 210 210 … … 220 220 </pre><h3>Version history</h3> 221 221 222 <h4>Version</h4> $Id: extrac2.pro 231 2007-03-19 17:15:51Z pinsard $ 223 224 <h4>History</h4> Sebastien Masson (smasson@lodyc.jussieu.fr) 222 <h4>Version</h4> 223 $Id: extrac2.pro 238 2007-03-27 13:43:18Z pinsard $ 224 225 <h4>History</h4> 226 Sebastien Masson (smasson@lodyc.jussieu.fr) 225 227 12/1/1999 226 228 29/4/1999: correction of a bug and complement of the heading -
trunk/SRC/Documentation/idldoc_assistant_output/Matrix/inter.html
r234 r242 79 79 80 80 81 <h3>Return value</h3> tableau 81 <h3>Return value</h3> 82 tableau 82 83 83 84 … … 98 99 </h4> 99 100 100 arrays of positive integers, which need not to be 101 102 arrays of positive integers, which need not to be 101 103 sorted. Duplicate elements are ignored, as they have no effect on the 102 104 result … … 116 118 </h4> 117 119 118 see a 120 121 see a 119 122 120 123 … … 131 134 132 135 <h4>Version</h4> 133 $Id: inter.pro 23 2 2007-03-20 16:59:36Z pinsard $136 $Id: inter.pro 237 2007-03-26 15:37:03Z pinsard $ 134 137 135 138 <h4>History</h4> … … 142 145 143 146 144 <h4>Restrictions</h4> The empty set is denoted by an array with the first element equal to 147 <h4>Restrictions</h4> 148 The empty set is denoted by an array with the first element equal to 145 149 -1. 146 150 151 147 152 These functions will not be efficient on sparse sets with wide 148 ranges, as they trade memory for efficiency. The HISTOGRAM function 153 ranges, as they trade memory for efficiency. 154 The <proidl>HISTOGRAM</proidl> function 149 155 is used, which creates arrays of size equal to the range of the 150 156 resulting set. -
trunk/SRC/Documentation/idldoc_assistant_output/Matrix/union.html
r234 r242 118 118 </h4> 119 119 120 see a 120 121 see a 121 122 122 123 … … 133 134 134 135 <h4>Version</h4> 135 $Id: union.pro 23 2 2007-03-20 16:59:36Z pinsard $136 $Id: union.pro 237 2007-03-26 15:37:03Z pinsard $ 136 137 137 138 <h4>History</h4> … … 147 148 The empty set is denoted by an array with the first element equal to -1. 148 149 150 149 151 These functions will not be efficient on sparse sets with wide 150 ranges, as they trade memory for efficiency. The HISTOGRAM function 152 ranges, as they trade memory for efficiency. 153 The <proidl>HISTOGRAM</proidl> function 151 154 is used, which creates arrays of size equal to the range of the 152 155 resulting set. -
trunk/SRC/Documentation/idldoc_assistant_output/Matrix/zero_one.html
r234 r242 61 61 </dl> 62 62 63 63 64 64 Send back a vector or a matrix constituted of 0 and 1 in alternation 65 65 … … 70 70 <a name="#_zero_one"></a> 71 71 72 <h2>zero_one <font size="-1" color="#006633"> 72 <h2>zero_one <font size="-1" color="#006633"> 73 73 Function, Matrix 74 74 </font></h2> … … 78 78 79 79 80 <h3>Return value</h3> result 81 80 <h3>Return value</h3> 81 result 82 82 83 83 84 … … 97 98 </h4> 98 99 99 number of elements in the first dimension 100 101 number of elements in the first dimension 102 100 103 101 104 … … 112 115 </h4> 113 116 114 number of elements in the second dimension 117 118 number of elements in the second dimension 115 119 116 120 … … 122 126 </pre><h3>Version history</h3> 123 127 124 <h4>Version</h4> $Id: zero_one.pro 231 2007-03-19 17:15:51Z pinsard $ 128 <h4>Version</h4> 129 $Id: zero_one.pro 237 2007-03-26 15:37:03Z pinsard $ 125 130 126 <h4>History</h4> Sebastien Masson (smasson@lodyc.jussieu.fr) 131 <h4>History</h4> 132 Sebastien Masson (smasson@lodyc.jussieu.fr) 127 133 1/12/98 128 134 -
trunk/SRC/Documentation/idldoc_assistant_output/Obsolete/congridseb.html
r234 r242 163 163 </pre><h3>Version history</h3> 164 164 165 <h4>Version</h4> $Id: congridseb.pro 232 2007-03-20 16:59:36Z pinsard $ 165 <h4>Version</h4> 166 $Id: congridseb.pro 238 2007-03-27 13:43:18Z pinsard $ 166 167 167 <h4>History</h4> Sebastien Masson (smasson@lodyc.jussieu.fr) 168 <h4>History</h4> 169 Sebastien Masson (smasson@lodyc.jussieu.fr) 168 170 20/3/98 169 171 18/6/1999 supression d''une horrible boucle -
trunk/SRC/Documentation/idldoc_assistant_output/Obsolete/extrait.html
r234 r242 223 223 </pre><h3>Version history</h3> 224 224 225 <h4>Version</h4> $Id: extrait.pro 231 2007-03-19 17:15:51Z pinsard $ 226 227 <h4>History</h4> Sebastien Masson (smasson@lodyc.jussieu.fr) 225 <h4>Version</h4> 226 $Id: extrait.pro 238 2007-03-27 13:43:18Z pinsard $ 227 228 <h4>History</h4> 229 Sebastien Masson (smasson@lodyc.jussieu.fr) 228 230 12/1/1999 229 231 29/4/1999: correction of a bug and complement of the heading -
trunk/SRC/Documentation/idldoc_assistant_output/Obsolete/fictype.html
r234 r242 125 125 </pre><h3>Version history</h3> 126 126 127 <h4>Version</h4> 128 $Id: fictype.pro 23 2 2007-03-20 16:59:36Z pinsard $127 <h4>Version</h4> 128 $Id: fictype.pro 238 2007-03-27 13:43:18Z pinsard $ 129 129 130 <h4>History</h4> 130 <h4>History</h4> 131 131 Jerome Vialard (jv@lodyc.jussieu.fr) 132 132 2/7/98 -
trunk/SRC/Documentation/idldoc_assistant_output/Obsolete/jourdsmois.html
r236 r242 62 62 63 63 64 use d <a href="../Calendar/daysinmonth.html">daysinmonth</a> instead64 use <a href="..//Calendar/daysinmonth.html">daysinmonth</a> instead 65 65 66 66 … … 122 122 123 123 <h4>Version</h4> 124 $Id: jourdsmois.pro 23 2 2007-03-20 16:59:36Z pinsard $124 $Id: jourdsmois.pro 237 2007-03-26 15:37:03Z pinsard $ 125 125 126 126 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/Obsolete/ncdf_meshlec.html
r234 r242 62 62 63 63 64 use <a href=". //../../Grid/ncdf_meshread.html">ncdf_meshread</a> instead64 use <a href="..//Grid/ncdf_meshread.html">ncdf_meshread</a> instead 65 65 66 66 -
trunk/SRC/Documentation/idldoc_assistant_output/Obsolete/nlecan.html
r234 r242 71 71 <a name="#_nlecan"></a> 72 72 73 <h2>nlecan <font size="-1" color="#FF6633">obsolete</font> <font size="-1" color="#006633"> 73 <h2>nlecan <font size="-1" color="#FF6633">obsolete</font> <font size="-1" color="#006633"> 74 74 Reading 75 75 </font></h2> … … 80 80 81 81 82 <h3>Return value</h3> 82 <h3>Return value</h3> 83 83 tableau 2d (qd la serie ne fait que 1 pas de temps) ou 84 84 3d (valable ds 1 premier tps que pour les tableaux 2d) … … 101 101 </h4> 102 102 103 103 104 104 nom du tableau contenant le champ que l'on veut (le 105 105 trouver avec ncdflec,fichier,/var … … 119 119 </h4> 120 120 121 121 122 122 le numero du pas de temps que l'on veut sortir du 123 123 fichier (compte a partir de 1) a partir de 79 … … 137 137 </h4> 138 138 139 139 140 140 nombre de pas de temps a extraire 141 141 … … 159 159 </h4> 160 160 161 161 162 162 boite sur laquelle integrer (par defaut tt le domaine) 163 163 … … 175 175 </h4> 176 176 177 177 178 178 impose la grille a laquelle est rapporte le champ. rq permet 179 179 d'aller plus vite ds la lecture … … 192 192 </h4> 193 193 194 194 195 195 oblige a lire le tableau entier en non pas celui reduit a domdef 196 196 … … 208 208 </h4> 209 209 210 210 211 211 Used to pass keywords 212 212 … … 219 219 </pre><h3>Version history</h3> 220 220 221 <h4>Version</h4> 222 $Id: nlecan.pro 23 2 2007-03-20 16:59:36Z pinsard $223 224 <h4>History</h4> 221 <h4>Version</h4> 222 $Id: nlecan.pro 238 2007-03-27 13:43:18Z pinsard $ 223 224 <h4>History</h4> 225 225 Sebastien Masson (smasson@lodyc.jussieu.fr) 226 226 … … 231 231 232 232 233 <h4>Restrictions</h4> 233 <h4>Restrictions</h4> 234 234 appele par <a href=".//nlec.html">nlec</a> 235 235 … … 238 238 239 239 240 <h4>Uses routines</h4> 240 <h4>Uses routines</h4> 241 241 common.pro 242 242 -
trunk/SRC/Documentation/idldoc_assistant_output/Obsolete/strrepl.html
r234 r242 63 63 64 64 replace one (or more) character(s)/string(s) in a string 65 --- OBSOLETE --- you should better use <a href=". //../../ToBeReviewed/STRING/strsed.html">strsed</a>65 --- OBSOLETE --- you should better use <a href="..//ToBeReviewed/STRING/strsed.html">strsed</a> 66 66 67 67 -
trunk/SRC/Documentation/idldoc_assistant_output/Obsolete/vairdate.html
r234 r242 65 65 sets month, day and year to the corresp values 66 66 67 you better use <a href=". //../../Calendar/jul2date.html">jul2date</a>67 you better use <a href="..//Calendar/jul2date.html">jul2date</a> 68 68 69 69 -
trunk/SRC/Documentation/idldoc_assistant_output/Obsolete/zeroun.html
r234 r242 64 64 Send back a vector or a matrix constituate of 0 and 1 in alternation 65 65 66 you better use <a href=". //../../Matrix/zero_one.html">zero_one</a>66 you better use <a href="..//Matrix/zero_one.html">zero_one</a> 67 67 68 68 -
trunk/SRC/Documentation/idldoc_assistant_output/Picture/imdisp.html
r234 r242 63 63 64 64 Display an image on the current graphics device. 65 IMDISP is an advanced replacement for TV and TVSCL. 65 IMDISP is an advanced replacement for <prodil>TV</proidl> and 66 <proidl>TVSCL</proidl>. 66 67 67 68 - Supports WIN, MAC, X, CGM, PCL, PRINTER, PS, and Z graphics devices, … … 614 615 615 616 <h4>Version</h4> 616 $Id: imdisp.pro 23 2 2007-03-20 16:59:36Z pinsard $617 $Id: imdisp.pro 236 2007-03-21 17:18:44Z pinsard $ 617 618 618 619 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/Postscript/closeps.html
r234 r242 113 113 114 114 <h4>Version</h4> 115 $Id: closeps.pro 23 2 2007-03-20 16:59:36Z pinsard $115 $Id: closeps.pro 238 2007-03-27 13:43:18Z pinsard $ 116 116 117 117 <h4>History</h4> … … 131 131 132 132 133 <h4>Uses routines</h4> 133 <h4>Uses routines</h4> 134 134 cm_4ps 135 135 -
trunk/SRC/Documentation/idldoc_assistant_output/Postscript/openps.html
r234 r242 246 246 247 247 <h4>Version</h4> 248 $Id: openps.pro 232 2007-03-20 16:59:36Z pinsard $ 249 250 <h4>History</h4> Sebastien Masson (smasson@lodyc.jussieu.fr) 248 $Id: openps.pro 238 2007-03-27 13:43:18Z pinsard $ 249 250 <h4>History</h4> 251 Sebastien Masson (smasson@lodyc.jussieu.fr) 251 252 21/12/98 252 253 1/2/98: ajout de nameps en input … … 265 266 266 267 267 <h4>Uses routines</h4> 268 <h4>Uses routines</h4> 268 269 cm_4ps 269 270 -
trunk/SRC/Documentation/idldoc_assistant_output/ReadWrite/ncdf_timeget.html
r234 r242 71 71 <a name="#_ncdf_timeget"></a> 72 72 73 <h2>ncdf_timeget <font size="-1" color="#006633"> 73 <h2>ncdf_timeget <font size="-1" color="#006633"> 74 74 Reading 75 75 </font></h2> … … 165 165 </pre><h3>Version history</h3> 166 166 167 <h4>Version</h4> $Id: ncdf_timeget.pro 232 2007-03-20 16:59:36Z pinsard $ 168 <h4>History</h4> Sebastien Masson (smasson@lodyc.jussieu.fr) 167 <h4>Version</h4> 168 $Id: ncdf_timeget.pro 238 2007-03-27 13:43:18Z pinsard $ 169 <h4>History</h4> 170 Sebastien Masson (smasson@lodyc.jussieu.fr) 169 171 June 2001 170 172 -
trunk/SRC/Documentation/idldoc_assistant_output/ReadWrite/read_oasis.html
r234 r242 79 79 80 80 81 <h3>Return value</h3> a 2d array 81 <h3>Return value</h3> 82 a 2d array 82 83 83 84 … … 98 99 </h4> 99 100 100 101 101 102 the filename 102 103 … … 115 116 </h4> 116 117 117 118 118 119 the name of the variable to be read 119 120 … … 226 227 </pre><h3>Version history</h3> 227 228 228 <h4>Version</h4> $Id: read_oasis.pro 232 2007-03-20 16:59:36Z pinsard $ 229 <h4>History</h4> Sebastien Masson (smasson@lodyc.jussieu.fr) 229 <h4>Version</h4> 230 $Id: read_oasis.pro 238 2007-03-27 13:43:18Z pinsard $ 231 232 <h4>History</h4> 233 Sebastien Masson (smasson@lodyc.jussieu.fr) 230 234 July 01, 2002 231 235 -
trunk/SRC/Documentation/idldoc_assistant_output/ReadWrite/readbat.html
r234 r242 79 79 80 80 81 <h3>Return value</h3> a 2d array 81 <h3>Return value</h3> 82 a 2d array 82 83 83 84 … … 128 129 </pre><h3>Version history</h3> 129 130 130 <h4>Version</h4> $Id: readbat.pro 232 2007-03-20 16:59:36Z pinsard $ 131 <h4>Version</h4> 132 $Id: readbat.pro 238 2007-03-27 13:43:18Z pinsard $ 131 133 132 <h4>History</h4> Sebastien Masson (smasson@lodyc.jussieu.fr) 134 <h4>History</h4> 135 Sebastien Masson (smasson@lodyc.jussieu.fr) 133 136 May 31, 2002 134 137 based on batlec2.pro, written by Maurice Imbard, March 17, 1998 -
trunk/SRC/Documentation/idldoc_assistant_output/ReadWrite/readoldopadistcoast.html
r234 r242 69 69 70 70 71 72 71 73 72 <h2>Routine summary</h2> … … 79 78 80 79 <dt><a href="#_readoldopadistcoast"><i>result = </i>readoldopadistcoast(<i>filename, jpiglo, jpjglo, jpk</i>, IBLOC=<i>IBLOC</i>, JPBYT=<i>JPBYT</i>, NUMREC=<i>NUMREC</i>)</a><dt> 81 <dd><font size="-1"> </font></dd>80 <dd><font size="-1"> </font></dd> 82 81 83 82 </dl> … … 89 88 <a name="#_read3fromopa"></a> 90 89 91 <h2>read3fromopa <font size="-1" color="#006633"> 90 <h2>read3fromopa <font size="-1" color="#006633"> 92 91 For OPA 93 92 </font></h2> … … 98 97 99 98 100 <h3>Return value</h3> 99 <h3>Return value</h3> 101 100 a structure that contains two elements: tdistcoast (the 102 101 distance for the t-points) and fdiscoast (the distance for the … … 122 121 123 122 124 125 123 126 124 … … 138 136 139 137 140 141 138 142 139 143 140 … … 155 152 156 153 157 158 154 159 155 … … 165 161 </pre><h3>Version history</h3> 166 162 167 <h4>Version</h4> $Id: readoldopadistcoast.pro 232 2007-03-20 16:59:36Z pinsard $ 168 <h4>History</h4> Sebastien Masson (smasson@lodyc.jussieu.fr) 163 <h4>Version</h4> 164 $Id: readoldopadistcoast.pro 240 2007-03-28 12:17:24Z pinsard $ 165 166 <h4>History</h4> 167 Sebastien Masson (smasson@lodyc.jussieu.fr) 169 168 June, 2002 170 169 … … 197 196 198 197 198 199 199 200 200 … … 234 234 235 235 236 237 236 238 237 … … 251 250 252 251 253 254 252 255 253 … … 290 288 291 289 Ibloc size 292 290 293 291 294 292 <a name="#_readoldopadistcoast_keyword_JPBYT"></a> … … 306 304 307 305 Jpbyt size 308 306 309 307 310 308 <a name="#_readoldopadistcoast_keyword_NUMREC"></a> … … 330 328 331 329 <h4>Version</h4> 332 $Id: readoldopadistcoast.pro 232 2007-03-20 16:59:36Z pinsard $ 330 $Id: readoldopadistcoast.pro 240 2007-03-28 12:17:24Z pinsard $ 331 333 332 <h4>History</h4> 334 333 Sebastien Masson (smasson@lodyc.jussieu.fr) -
trunk/SRC/Documentation/idldoc_assistant_output/ReadWrite/readoldoparestart.html
r234 r242 159 159 160 160 <h4>Version</h4> 161 $Id: readoldoparestart.pro 2 31 2007-03-19 17:15:51Z pinsard $161 $Id: readoldoparestart.pro 240 2007-03-28 12:17:24Z pinsard $ 162 162 <h4>History</h4> 163 163 Sebastien Masson (smasson@lodyc.jussieu.fr) … … 725 725 726 726 <h4>Version</h4> 727 $Id: readoldoparestart.pro 2 31 2007-03-19 17:15:51Z pinsard $727 $Id: readoldoparestart.pro 240 2007-03-28 12:17:24Z pinsard $ 728 728 <h4>History</h4> 729 729 Sebastien Masson (smasson@lodyc.jussieu.fr) -
trunk/SRC/Documentation/idldoc_assistant_output/ReadWrite/scanctl.html
r234 r242 296 296 </h4> 297 297 298 298 299 299 300 300 … … 319 319 </pre><h3>Version history</h3> 320 320 321 <h4>Version</h4> 322 $Id: scanctl.pro 2 32 2007-03-20 16:59:36Z pinsard $321 <h4>Version</h4> 322 $Id: scanctl.pro 240 2007-03-28 12:17:24Z pinsard $ 323 323 324 324 -
trunk/SRC/Documentation/idldoc_assistant_output/ReadWrite/scanoasis.html
r234 r242 96 96 </h4> 97 97 98 98 99 99 The file name 100 100 … … 109 109 </pre><h3>Version history</h3> 110 110 111 <h4>Version</h4> $Id: scanoasis.pro 232 2007-03-20 16:59:36Z pinsard $ 112 <h4>History</h4> Sebastien Masson (smasson@lodyc.jussieu.fr) 111 <h4>Version</h4> 112 $Id: scanoasis.pro 238 2007-03-27 13:43:18Z pinsard $ 113 114 <h4>History</h4> 115 Sebastien Masson (smasson@lodyc.jussieu.fr) 113 116 July 01, 2002 114 117 … … 118 121 119 122 120 <h4>Restrictions</h4> 123 <h4>Restrictions</h4> 121 124 List the variable names included in a Oasis file 122 125 -
trunk/SRC/Documentation/idldoc_assistant_output/ReadWrite/write_oasis.html
r234 r242 95 95 </h4> 96 96 97 97 98 98 the filename 99 99 … … 112 112 </h4> 113 113 114 114 115 115 the name of the variable to be written 116 116 … … 129 129 </h4> 130 130 131 131 132 132 the variable (2D array) to be written 133 133 … … 209 209 </h4> 210 210 211 212 to open the file with the file pointer at the end of the file, ready for 211 212 to open the file with the file pointer at the end of the file, ready for 213 213 data to be appended. 214 214 … … 219 219 </pre><h3>Version history</h3> 220 220 221 <h4>Version</h4> $Id: write_oasis.pro 231 2007-03-19 17:15:51Z pinsard $ 222 <h4>History</h4> Sebastien Masson (smasson@lodyc.jussieu.fr) 221 <h4>Version</h4> 222 $Id: write_oasis.pro 238 2007-03-27 13:43:18Z pinsard $ 223 224 <h4>History</h4> 225 Sebastien Masson (smasson@lodyc.jussieu.fr) 223 226 July 01, 2002 224 227 … … 228 231 229 232 230 <h4>Restrictions</h4> 233 <h4>Restrictions</h4> 231 234 varname is automatically written as a "character*8" 232 235 by default z2d is written as an R8 array -
trunk/SRC/Documentation/idldoc_assistant_output/ReadWrite/writebat.html
r234 r242 70 70 <a name="#_writebat"></a> 71 71 72 <h2>writebat <font size="-1" color="#006633"> 72 <h2>writebat <font size="-1" color="#006633"> 73 73 For OPA 74 74 </font></h2> … … 97 97 </h4> 98 98 99 99 100 100 the bathymetry, a 2d array 101 101 … … 125 125 </pre><h3>Version history</h3> 126 126 127 <h4>Version</h4> $Id: writebat.pro 231 2007-03-19 17:15:51Z pinsard $ 128 <h4>History</h4> Sebastien Masson (smasson@lodyc.jussieu.fr) 127 <h4>Version</h4> 128 $Id: writebat.pro 238 2007-03-27 13:43:18Z pinsard $ 129 130 <h4>History</h4> 131 Sebastien Masson (smasson@lodyc.jussieu.fr) 129 132 Sept 30, 2003 130 133 based on batsav2.pro, written by Maurice Imbard, March 17, 1998 -
trunk/SRC/Documentation/idldoc_assistant_output/Tests/TestsOld/tst_basic_old.html
r234 r242 77 77 78 78 79 79 80 80 81 … … 86 87 </pre><h3>Version history</h3> 87 88 88 <h4>Version</h4> $Id: tst_basic_old.pro 189 2006-09-21 13:55:54Z pinsard $ 89 <h4>Version</h4> 90 $Id: tst_basic_old.pro 237 2007-03-26 15:37:03Z pinsard $ 91 89 92 <h4>History</h4> 90 93 Sebastien Masson may 2005 -
trunk/SRC/Documentation/idldoc_assistant_output/Tests/TestsOld/tst_plt_old.html
r234 r242 64 64 65 65 66 67 66 68 67 … … 71 70 72 71 <h2>tst_plt_old <font size="-1" color="#006633"> 73 74 </font></h2> 72 </font></h2> 75 73 76 74 <p><font face="Courier">tst_plt_old, <a href="#_tst_plt_old_keyword_IMAGE">IMAGE</a>=<i>IMAGE</i></font></p> 77 75 78 76 77 79 78 80 79 … … 106 105 </pre><h3>Version history</h3> 107 106 108 <h4>Version</h4> 109 $Id: tst_plt_old.pro 189 2006-09-21 13:55:54Z pinsard $ 107 <h4>Version</h4> 108 $Id: tst_plt_old.pro 238 2007-03-27 13:43:18Z pinsard $ 109 110 110 <h4>History</h4> 111 111 Sebastien Masson -
trunk/SRC/Documentation/idldoc_assistant_output/Tests/TestsOld/tst_pltt_old.html
r234 r242 64 64 65 65 66 67 66 68 67 … … 71 70 72 71 <h2>tst_pltt_old <font size="-1" color="#006633"> 73 74 72 </font></h2> 75 73 … … 77 75 78 76 77 79 78 80 79 … … 107 106 108 107 <h4>Version</h4> 109 $Id: tst_pltt_old.pro 189 2006-09-21 13:55:54Z pinsard $ 108 $Id: tst_pltt_old.pro 237 2007-03-26 15:37:03Z pinsard $ 109 110 110 <h4>History</h4> 111 111 Sebastien Masson -
trunk/SRC/Documentation/idldoc_assistant_output/Tests/TestsOld/tst_pltz_old.html
r234 r242 64 64 65 65 66 67 66 68 67 … … 71 70 72 71 <h2>tst_pltz_old <font size="-1" color="#006633"> 73 74 72 </font></h2> 75 73 … … 77 75 78 76 77 79 78 80 79 … … 107 106 108 107 <h4>Version</h4> 109 $Id: tst_pltz_old.pro 189 2006-09-21 13:55:54Z pinsard $ 108 $Id: tst_pltz_old.pro 237 2007-03-26 15:37:03Z pinsard $ 109 110 110 <h4>History</h4> 111 111 Sebastien Masson -
trunk/SRC/Documentation/idldoc_assistant_output/Tests/tst_basic.html
r234 r242 87 87 </pre><h3>Version history</h3> 88 88 89 <h4>Version</h4> $Id: tst_basic.pro 232 2007-03-20 16:59:36Z pinsard $ 89 <h4>Version</h4> 90 $Id: tst_basic.pro 237 2007-03-26 15:37:03Z pinsard $ 91 90 92 <h4>History</h4> 91 93 Sebastien Masson may 2005 -
trunk/SRC/Documentation/idldoc_assistant_output/Tests/tst_plt.html
r234 r242 70 70 71 71 <h2>tst_plt <font size="-1" color="#006633"> 72 72 </font></h2> 73 73 74 74 <p><font face="Courier">tst_plt, <a href="#_tst_plt_keyword_IMAGE">IMAGE</a>=<i>IMAGE</i></font></p> … … 105 105 </pre><h3>Version history</h3> 106 106 107 <h4>Version</h4> 108 $Id: tst_plt.pro 232 2007-03-20 16:59:36Z pinsard $ 107 <h4>Version</h4> 108 $Id: tst_plt.pro 237 2007-03-26 15:37:03Z pinsard $ 109 109 110 <h4>History</h4> 110 111 Sebastien Masson -
trunk/SRC/Documentation/idldoc_assistant_output/Tests/tst_pltt.html
r234 r242 106 106 107 107 <h4>Version</h4> 108 $Id: tst_pltt.pro 232 2007-03-20 16:59:36Z pinsard $ 108 $Id: tst_pltt.pro 237 2007-03-26 15:37:03Z pinsard $ 109 109 110 <h4>History</h4> 110 111 Sebastien Masson -
trunk/SRC/Documentation/idldoc_assistant_output/Tests/tst_pltz.html
r234 r242 106 106 107 107 <h4>Version</h4> 108 $Id: tst_pltz.pro 232 2007-03-20 16:59:36Z pinsard $ 108 $Id: tst_pltz.pro 237 2007-03-26 15:37:03Z pinsard $ 109 109 110 <h4>History</h4> 110 111 Sebastien Masson -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/CALCULS/grossemoyenne.html
r234 r242 198 198 199 199 200 We activate it if we do not want to pass in domdef even if the keyword 201 boxzoom is present (like when grossemoyenne is called via checkfield) 200 We activate it if we do not want to pass in <a href="../..//ToBeReviewed/GRILLE/domdef.html">domdef</a> even if the 201 keyword boxzoom is present (like when <a href=".//grossemoyenne.html">grossemoyenne</a> is called via 202 <a href="../..//ToBeReviewed/PLOTS/DIVERS/checkfield.html">checkfield</a>) 202 203 203 204 … … 279 280 280 281 <h4>Version</h4> 281 $Id: grossemoyenne.pro 2 32 2007-03-20 16:59:36Z pinsard $282 $Id: grossemoyenne.pro 240 2007-03-28 12:17:24Z pinsard $ 282 283 <h4>History</h4> 283 284 Jerome Vialard (jv@lodyc.jussieu.fr) -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/CALCULS/hdyn.html
r234 r242 179 179 Give a depth to this keyword which will be considered as the reference depth 180 180 (in this case, LEVEL has not any effect). the calculation will be effectuated 181 until this depth effecting an interpolation between the thelast W level above181 until this depth effecting an interpolation between the last W level above 182 182 PROFREF and PROFREF. 183 183 … … 241 241 242 242 <h4>Version</h4> 243 $Id: hdyn.pro 23 1 2007-03-19 17:15:51Z pinsard $243 $Id: hdyn.pro 238 2007-03-27 13:43:18Z pinsard $ 244 244 245 245 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/CALCULS/moyenne.html
r234 r242 198 198 199 199 200 We activate it if we do not want to pass in domdef even if the keyword boxzoom 201 is present (like when grossemoyenne is called via checkfield) 200 We activate it if we do not want to pass in <a href="../..//ToBeReviewed/GRILLE/domdef.html">domdef</a> even if the 201 keyword boxzoom is present (like when <a href=".//grossemoyenne.html">grossemoyenne</a> is called 202 via <a href="../..//ToBeReviewed/PLOTS/DIVERS/checkfield.html">checkfield</a>) 202 203 203 204 … … 239 240 240 241 <h4>Version</h4> 241 $Id: moyenne.pro 23 2 2007-03-20 16:59:36Z pinsard $242 $Id: moyenne.pro 237 2007-03-26 15:37:03Z pinsard $ 242 243 243 244 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/CALCULS/remplit.html
r234 r242 232 232 233 233 <h4>Version</h4> 234 $Id: remplit.pro 23 2 2007-03-20 16:59:36Z pinsard $234 $Id: remplit.pro 238 2007-03-27 13:43:18Z pinsard $ 235 235 236 236 ; -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/GRILLE/decoupeterre.html
r234 r242 191 191 is passed in the variable we have equate at TRI. 192 192 For example: grille,...,tri=triangulation_reduite. 193 This keyword is used in <a href=". //../../../ToBeReviewed/PLOTS/DESSINE/plt.html">plt</a>.193 This keyword is used in <a href="../..//ToBeReviewed/PLOTS/DESSINE/plt.html">plt</a>. 194 194 195 195 -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/GRILLE/domdef.html
r234 r242 377 377 378 378 <h4>Version</h4> 379 $Id: domdef.pro 2 32 2007-03-20 16:59:36Z pinsard $379 $Id: domdef.pro 240 2007-03-28 12:17:24Z pinsard $ 380 380 381 381 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/GRILLE/grille.html
r234 r242 384 384 is passed in the variable we have equate at TRI. 385 385 For example: grille,...,tri=triangulation_reduite. 386 This keyword is used in <a href=". //../../../ToBeReviewed/PLOTS/DESSINE/plt.html">plt</a>.386 This keyword is used in <a href="../..//ToBeReviewed/PLOTS/DESSINE/plt.html">plt</a>. 387 387 388 388 … … 433 433 434 434 435 In <a href=". //../../../ToBeReviewed/PLOTS/DESSINE/plt.html">plt</a>, we want that land points,435 In <a href="../..//ToBeReviewed/PLOTS/DESSINE/plt.html">plt</a>, we want that land points, 436 436 glam and gphi, be equal to glamt and 437 437 gphit regardless of the grid. -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/HOPE/findlineandpointtype.html
r234 r242 156 156 157 157 <h4>Version</h4> 158 $Id: findlineandpointtype.pro 2 31 2007-03-19 17:15:51Z pinsard $158 $Id: findlineandpointtype.pro 240 2007-03-28 12:17:24Z pinsard $ 159 159 160 160 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/HOPE/read_hope.html
r234 r242 164 164 version) 165 165 166 A structure which but be read by <a href=". //../../../ToBeReviewed/LECTURE/litchamp.html">litchamp</a> and is166 A structure which but be read by <a href="../..//ToBeReviewed/LECTURE/litchamp.html">litchamp</a> and is 167 167 necessary to complete the grid associated to the data (see 168 168 the example). -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/IMAGE/animgif.html
r234 r242 61 61 </dl> 62 62 63 63 64 64 Build a gif animation 65 65 … … 70 70 <a name="#_animgif"></a> 71 71 72 <h2>animgif <font size="-1" color="#006633"> 72 <h2>animgif <font size="-1" color="#006633"> 73 73 Animated drawings. 74 74 </font></h2> … … 97 97 </h4> 98 98 99 99 100 100 It is the name of the gif file containing the animation. 101 101 Comment: this file is placed in the directory defined by iodir. … … 109 109 </pre><h3>Version history</h3> 110 110 111 <h4>Version</h4> 112 $Id: animgif.pro 157 2006-08-21 09:01:50Z navarro$111 <h4>Version</h4> 112 $Id: animgif.pro 238 2007-03-27 13:43:18Z pinsard $ 113 113 114 <h4>History</h4> 114 <h4>History</h4> 115 115 Guillaume Roullet (grlod@ipsl.jussieu.fr) 116 116 Sebastien Masson (smasson@lodyc.jussieu.fr) … … 123 123 124 124 125 <h4>Restrictions</h4> 125 <h4>Restrictions</h4> 126 126 We use the Z buffer to go faster!. 127 127 So, if it failed in animgif, you have to do: … … 130 130 IDL> retall 131 131 132 132 133 133 If we want to delete the @common, 134 we have to define manually the picture's size 134 we have to define manually the picture's size 135 135 (variables xsize and ysize) just as iodir. 136 136 … … 139 139 140 140 141 <h4>Uses routines</h4> 141 <h4>Uses routines</h4> 142 142 common.pro 143 143 -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/INIT/initncdf.html
r234 r242 265 265 266 266 267 Used to pass keywords to <a href=". //../../../Grid/computegrid.html">computegrid</a> and268 <a href=". //../../../ReadWrite/ncdf_getaxis.html">ncdf_getaxis</a>267 Used to pass keywords to <a href="../..//Grid/computegrid.html">computegrid</a> and 268 <a href="../..//ReadWrite/ncdf_getaxis.html">ncdf_getaxis</a> 269 269 270 270 … … 277 277 278 278 <h4>Version</h4> 279 $Id: initncdf.pro 23 2 2007-03-20 16:59:36Z pinsard $279 $Id: initncdf.pro 238 2007-03-27 13:43:18Z pinsard $ 280 280 281 281 <h4>History</h4> … … 290 290 291 291 <h4>Restrictions</h4> 292 Change the grid parameters (see <a href=". //../../../Grid/computegrid.html">computegrid</a>)292 Change the grid parameters (see <a href="../..//Grid/computegrid.html">computegrid</a>) 293 293 294 294 -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/LECTURE/GRIB/read_grib.html
r234 r242 161 161 162 162 <h4>Version</h4> 163 $Id: read_grib.pro 23 2 2007-03-20 16:59:36Z pinsard $163 $Id: read_grib.pro 236 2007-03-21 17:18:44Z pinsard $ 164 164 165 165 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/LECTURE/ncdf_lec.html
r234 r242 199 199 200 200 <h4>Version</h4> 201 $Id: ncdf_lec.pro 2 32 2007-03-20 16:59:36Z pinsard $201 $Id: ncdf_lec.pro 240 2007-03-28 12:17:24Z pinsard $ 202 202 203 203 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/LECTURE/read_ncdf.html
r234 r242 367 367 368 368 369 For ROMS outputs. The filename of the file where zeta v riable should be read369 For ROMS outputs. The filename of the file where zeta variable should be read 370 370 371 371 … … 408 408 409 409 <h4>Version</h4> 410 $Id: read_ncdf.pro 2 31 2007-03-19 17:15:51Z pinsard $410 $Id: read_ncdf.pro 240 2007-03-28 12:17:24Z pinsard $ 411 411 <h4>History</h4> 412 412 Sebastien Masson (smasson@lodyc.jussieu.fr) -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/MATRICE/colle.html
r234 r242 61 61 </dl> 62 62 63 64 This concatenation function exist in IDL so long 65 as we do not try to stick with a dimension superior or equal at 4. 63 64 This concatenation function exist in IDL so long 65 as we do not try to stick with a dimension superior or equal at 4. 66 66 67 67 … … 71 71 <a name="#_colle"></a> 72 72 73 <h2>colle <font size="-1" color="#006633"> 73 <h2>colle <font size="-1" color="#006633"> 74 74 Utilities 75 75 </font></h2> … … 79 79 80 80 81 <h3>Return value</h3> res=matrice resultat 81 <h3>Return value</h3> 82 matrice resultat 82 83 83 84 … … 445 446 446 447 447 <h3>Examples</h3><pre> IDL> print, colle(replicate(1,2,2,2),indgen(2,2,2),2) 448 <h3>Examples</h3><pre> 449 IDL> print, colle(replicate(1,2,2,2),indgen(2,2,2),2) 448 450 1 1 449 451 1 1 … … 458 460 </pre><h3>Version history</h3> 459 461 460 <h4>Version</h4> $Id: colle.pro 163 2006-08-29 12:59:46Z navarro $ 461 462 <h4>History</h4> Sebastien Masson (smasson@lodyc.jussieu.fr) 462 <h4>Version</h4> 463 $Id: colle.pro 238 2007-03-27 13:43:18Z pinsard $ 464 465 <h4>History</h4> 466 Sebastien Masson (smasson@lodyc.jussieu.fr) 463 467 13/1/98 464 468 -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/PLOTS/DESSINE/bar_plot.html
r234 r242 417 417 418 418 <h4>Version</h4> 419 $Id: bar_plot.pro 2 32 2007-03-20 16:59:36Z pinsard $419 $Id: bar_plot.pro 240 2007-03-28 12:17:24Z pinsard $ 420 420 421 421 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/PLOTS/DESSINE/plt.html
r234 r242 102 102 will be automatically performed. 103 103 2) a structure respecting all criterions specified by 104 <a href=". //../../../../ToBeReviewed/LECTURE/litchamp.html">litchamp</a> cf. IDL> xhelp,'litchamp'104 <a href="../../..//ToBeReviewed/LECTURE/litchamp.html">litchamp</a> cf. IDL> xhelp,'litchamp' 105 105 106 106 … … 313 313 314 314 It is an integer n. If n different of 0, it choose the label's type 315 corresponding to cases n. cf <a href=". //../../../../ToBeReviewed/PLOTS/LABEL/label.html">label</a>315 corresponding to cases n. cf <a href="../../..//ToBeReviewed/PLOTS/LABEL/label.html">label</a> 316 316 Comment: When CONTOUR is activated, it only specify the label's type for colored isolines. 317 317 For these one traced by a trait, use CONTLABEL. -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/PLOTS/DESSINE/plt1d.html
r234 r242 104 104 * 1d:Nevertheless, the type must be specified in order to we know which trace 105 105 it is about. To have a correct caption, respecify the extraction zone via BOXZOOM. 106 2) a structure respecting all criterions specified by <a href=". //../../../../ToBeReviewed/LECTURE/litchamp.html">litchamp</a>106 2) a structure respecting all criterions specified by <a href="../../..//ToBeReviewed/LECTURE/litchamp.html">litchamp</a> 107 107 See IDL> xhelp,'litchamp'. The array contained in the structure 108 108 respecting criterions of case 1) -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/PLOTS/DESSINE/pltt.html
r234 r242 108 108 to we know of which trace it is about. 109 109 To have a correct caption, respecify the extraction zone via BOXZOOM. 110 2) a structure respecting all criterions specified by <a href=". //../../../../ToBeReviewed/LECTURE/litchamp.html">litchamp</a>110 2) a structure respecting all criterions specified by <a href="../../..//ToBeReviewed/LECTURE/litchamp.html">litchamp</a> 111 111 See IDL> xhelp,'litchamp'. The array contained in the structure 112 112 respecting criterions of case 1) … … 340 340 341 341 If n different of 0, it choose the label's type 342 corresponding to cases n. cf <a href=". //../../../../ToBeReviewed/PLOTS/LABEL/label.html">label</a>342 corresponding to cases n. cf <a href="../../..//ToBeReviewed/PLOTS/LABEL/label.html">label</a> 343 343 Comment: When CONTOUR is activated, it only specify the label's type for colored isolines. 344 344 For these one traced by a trait, use CONTLABEL. … … 738 738 739 739 <h4>Version</h4> 740 $Id: pltt.pro 2 32 2007-03-20 16:59:36Z pinsard $740 $Id: pltt.pro 240 2007-03-28 12:17:24Z pinsard $ 741 741 742 742 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/PLOTS/DESSINE/pltv.html
r234 r242 103 103 (as it is done in plt). 104 104 2) a structure respecting all criterions specified by 105 <a href=". //../../../../ToBeReviewed/LECTURE/litchamp.html">litchamp</a> cf. IDL> xhelp,'litchamp'105 <a href="../../..//ToBeReviewed/LECTURE/litchamp.html">litchamp</a> cf. IDL> xhelp,'litchamp' 106 106 107 107 … … 310 310 311 311 312 Used to pass keywords to <a href=". //../../../../ToBeReviewed/PLOTS/DIVERS/PLACEDESSIN</pro>, <pro>TV</pro>, <pro>AXE</pro>, <pro>LEGENDE</pro>, <pro>BARRECOULEUR</pro>, <pro>TERMINEDESSIN.html">PLACEDESSIN</pro>, <pro>TV</pro>, <pro>AXE</pro>, <pro>LEGENDE</pro>, <pro>BARRECOULEUR</pro>, <pro>TERMINEDESSIN</a>312 Used to pass keywords to <a href="../../..//ToBeReviewed/PLOTS/DIVERS/PLACEDESSIN</pro>, <pro>TV</pro>, <pro>AXE</pro>, <pro>LEGENDE</pro>, <pro>BARRECOULEUR</pro>, <pro>TERMINEDESSIN.html">PLACEDESSIN</pro>, <pro>TV</pro>, <pro>AXE</pro>, <pro>LEGENDE</pro>, <pro>BARRECOULEUR</pro>, <pro>TERMINEDESSIN</a> 313 313 314 314 -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/PLOTS/DESSINE/pltz.html
r234 r242 102 102 If the field is 2d, indicate, with the keyword BOXZOOM, geographic delineations of the boxzoom. 103 103 If the field is 3d, we extract the section on we average possibly before to do the plot. 104 2) a structure respecting all criterions specified by <a href=". //../../../../ToBeReviewed/LECTURE/litchamp.html">litchamp</a>.104 2) a structure respecting all criterions specified by <a href="../../..//ToBeReviewed/LECTURE/litchamp.html">litchamp</a>. 105 105 See IDL> xhelp,'litchamp'. The array contained in the structure must be 2 or 3d (See case 1) 106 106 … … 312 312 313 313 314 It choose the label's type corresponding to cases in <a href=". //../../../../ToBeReviewed/PLOTS/LABEL/label.html">label</a>314 It choose the label's type corresponding to cases in <a href="../../..//ToBeReviewed/PLOTS/LABEL/label.html">label</a> 315 315 Comment: When CONTOUR is activated, it only specify the label's type for colored isolines. 316 316 For these one traced by a trait, use CONTLABEL. -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/PLOTS/DESSINE/sbar_plot.html
r234 r242 163 163 164 164 <h3>Examples</h3><pre> 165 166 167 165 IDL> sbar_plot, indgen(10),small = [2,2,2],/rempli 166 IDL> sbar_plot, indgen(10),small = [2,2,3],/noerase 167 IDL> @ps 168 168 169 169 </pre><h3>Version history</h3> 170 170 171 171 <h4>Version</h4> 172 $Id: sbar_plot.pro 23 2 2007-03-20 16:59:36Z pinsard $172 $Id: sbar_plot.pro 237 2007-03-26 15:37:03Z pinsard $ 173 173 174 174 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/PLOTS/DESSINE/scontour.html
r234 r242 171 171 172 172 <h3>Examples</h3><pre> 173 174 175 173 IDL> z = dist(100) 174 IDL> scontour, z, nlevels=10,small=[1,2,1],xstyle=1,ystyle=1 175 IDL> @ps 176 176 177 177 </pre><h3>Version history</h3> 178 178 179 179 <h4>Version</h4> 180 $Id: scontour.pro 23 1 2007-03-19 17:15:51Z pinsard $180 $Id: scontour.pro 237 2007-03-26 15:37:03Z pinsard $ 181 181 182 182 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/PLOTS/DESSINE/splot.html
r234 r242 156 156 157 157 <h3>Examples</h3><pre> 158 159 160 158 IDL> splot, indgen(10),ystyle=1,small=[1,2,1],/portrait 159 IDL> splot, -indgen(10),ystyle=1,small=[1,2,2],/noerase 160 IDL> @ps 161 161 162 162 </pre><h3>Version history</h3> 163 163 164 164 <h4>Version</h4> 165 $Id: splot.pro 23 1 2007-03-19 17:15:51Z pinsard $165 $Id: splot.pro 237 2007-03-26 15:37:03Z pinsard $ 166 166 167 167 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/PLOTS/DESSINE/tvplus.html
r234 r242 62 62 63 63 64 Enhanced version of tvscl64 Enhanced version of <proidl>tvscl</proidl> 65 65 66 66 … … 328 328 329 329 330 Used to pass keywords to <proidl>TV</proidl>, 331 <proidl>PLOT</proidl>, 332 <a href=". //../../../../Colors/COLORBAR.html">COLORBAR</a>330 Used to pass keywords to <proidl>TV</proidl>, 331 <proidl>PLOT</proidl>, 332 <a href="../../..//Colors/COLORBAR.html">COLORBAR</a> 333 333 334 334 … … 341 341 342 342 <h4>Version</h4> 343 $Id: tvplus.pro 23 2 2007-03-20 16:59:36Z pinsard $343 $Id: tvplus.pro 236 2007-03-21 17:18:44Z pinsard $ 344 344 345 345 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/PLOTS/DIVERS/addaxe.html
r234 r242 62 62 63 63 64 Add an axis when we do an oblique section in pltz, pltt 65 or plt1d 64 Add an axis when we do an oblique section in <a href="../../..//ToBeReviewed/PLOTS/DESSINE/pltz.html">pltz</a>, 65 <a href="../../..//ToBeReviewed/PLOTS/DESSINE/pltt.html">pltt</a> 66 or <a href="../../..//ToBeReviewed/PLOTS/DESSINE/plt1d.html">plt1d</a> 66 67 67 68 … … 163 164 164 165 <h4>Version</h4> 165 $Id: addaxe.pro 23 1 2007-03-19 17:15:51Z pinsard $166 $Id: addaxe.pro 237 2007-03-26 15:37:03Z pinsard $ 166 167 167 168 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/PLOTS/DIVERS/autoscale.html
r234 r242 93 93 <font size="-1" color="#006633">required</font> 94 94 95 95 <font size="-1" color="#006633">type:</font> <font size="-1" color="#006633"><i>float</i></font> 96 96 97 97 … … 99 99 100 100 101 A reel number specifyingabove what value we want to trace a contour101 above what value we want to trace a contour 102 102 103 103 … … 110 110 <font size="-1" color="#006633">required</font> 111 111 112 112 <font size="-1" color="#006633">type:</font> <font size="-1" color="#006633"><i>float</i></font> 113 113 114 114 … … 116 116 117 117 118 A reel number specifyingbelow what value we want to trace a contour118 below what value we want to trace a contour 119 119 120 120 … … 133 133 134 134 135 It is a reel number giving the contour interval. Use it in CONTOUR with the keyword LEVEL. 135 the contour interval. Use it in <proidl>CONTOUR</proidl> with the 136 keyword LEVEL. 136 137 137 138 … … 144 145 145 146 <h4>Version</h4> 146 $Id: autoscale.pro 23 1 2007-03-19 17:15:51Z pinsard $147 $Id: autoscale.pro 237 2007-03-26 15:37:03Z pinsard $ 147 148 148 149 <h4>History</h4> … … 157 158 <h4>Restrictions</h4> 158 159 CI is a multiple of the unity in unity log of 10. 159 It force the number of contour to be even.160 It force the number of contours to be even. 160 161 161 162 -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/PLOTS/DIVERS/axis4pltz.html
r234 r242 111 111 112 112 113 113 3d mask 114 114 115 115 … … 184 184 185 185 186 to get the xaxis we need to use in pltbase186 to get the xaxis we need to use in <a href="../../..//ToBeReviewed/PLOTS/DESSINE/pltbase.html">pltbase</a> 187 187 188 188 … … 200 200 201 201 202 to get the yaxis we need to use in pltbase202 to get the yaxis we need to use in <a href="../../..//ToBeReviewed/PLOTS/DESSINE/pltbase.html">pltbase</a> 203 203 204 204 … … 294 294 Used to pass keywords 295 295 296 Others: see pltz 297 296 Others: see pltz 298 297 299 298 … … 304 303 305 304 <h4>Version</h4> 306 $Id: axis4pltz.pro 23 2 2007-03-20 16:59:36Z pinsard $305 $Id: axis4pltz.pro 237 2007-03-26 15:37:03Z pinsard $ 307 306 308 307 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/PLOTS/DIVERS/barrecouleur.html
r234 r242 99 99 100 100 101 102 101 103 102 … … 116 115 117 116 118 119 117 120 118 … … 133 131 134 132 135 136 133 137 134 … … 150 147 151 148 152 153 149 154 150 … … 172 168 173 169 174 175 170 176 171 <a name="#_barrecouleur_keyword_CB_TITLE"></a> … … 188 183 189 184 190 191 185 192 186 <a name="#_barrecouleur_keyword_NOFILL"></a> … … 204 198 205 199 206 207 200 208 201 <a name="#_barrecouleur_keyword_COLOR_c"></a> … … 220 213 221 214 222 223 215 224 216 <a name="#_barrecouleur_keyword_MIN"></a> … … 268 260 269 261 270 271 262 272 263 <a name="#_barrecouleur_keyword_CB_SUBTITLE"></a> … … 284 275 285 276 286 287 277 288 278 <a name="#_barrecouleur_keyword_POST"></a> … … 300 290 301 291 302 303 292 304 293 <a name="#_barrecouleur_keyword__EXTRA"></a> … … 324 313 325 314 <h4>Version</h4> 326 $Id: barrecouleur.pro 23 2 2007-03-20 16:59:36Z pinsard $315 $Id: barrecouleur.pro 237 2007-03-26 15:37:03Z pinsard $ 327 316 328 317 <h4>History</h4> … … 337 326 <h4>Todo items</h4> 338 327 seb: mettre les keyword et les param 328 339 329 <h4>Restrictions</h4> 340 330 pass all arguments we want thanks to _EXTRA -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/PLOTS/DIVERS/checkfield.html
r234 r242 88 88 <dd><font size="-1"> </font></dd> 89 89 90 <dt><a href="#_checkfield"><i>result = </i>checkfield(<i>field, procedure</i>, TYPE=<i>TYPE</i>, BOXZOOM=<i>vector</i>, DIREC=<i>DIREC</i>, NOQUESTION=<i>NOQUESTION</i>, VECTEUR=<i>ve tcor</i>, WDEPTH=<i>WDEPTH</i>, _EXTRA=<i>_EXTRA</i>)</a><dt>90 <dt><a href="#_checkfield"><i>result = </i>checkfield(<i>field, procedure</i>, TYPE=<i>TYPE</i>, BOXZOOM=<i>vector</i>, DIREC=<i>DIREC</i>, NOQUESTION=<i>NOQUESTION</i>, VECTEUR=<i>vector</i>, WDEPTH=<i>WDEPTH</i>, _EXTRA=<i>_EXTRA</i>)</a><dt> 91 91 <dd><font size="-1"> </font></dd> 92 92 … … 192 192 193 193 <h4>Version</h4> 194 $Id: checkfield.pro 232 2007-03-20 16:59:36Z pinsard $ 194 $Id: checkfield.pro 238 2007-03-27 13:43:18Z pinsard $ 195 195 196 <h4>History</h4> 196 197 … … 257 258 258 259 259 <font size="-1" color="#006633">default:</font> <font size="-1" color="#006633"><i>defined by <a href=". //../../../../ToBeReviewed/GRILLE/grille.html">grille</a></i></font>260 <font size="-1" color="#006633">default:</font> <font size="-1" color="#006633"><i>defined by <a href="../../..//ToBeReviewed/GRILLE/grille.html">grille</a></i></font> 260 261 261 262 </h4> … … 273 274 274 275 275 <font size="-1" color="#006633">default:</font> <font size="-1" color="#006633"><i>defined by <a href=". //../../../../ToBeReviewed/GRILLE/grille.html">grille</a></i></font>276 <font size="-1" color="#006633">default:</font> <font size="-1" color="#006633"><i>defined by <a href="../../..//ToBeReviewed/GRILLE/grille.html">grille</a></i></font> 276 277 277 278 </h4> … … 289 290 290 291 291 <font size="-1" color="#006633">default:</font> <font size="-1" color="#006633"><i>defined by <a href=". //../../../../ToBeReviewed/GRILLE/grille.html">grille</a></i></font>292 <font size="-1" color="#006633">default:</font> <font size="-1" color="#006633"><i>defined by <a href="../../..//ToBeReviewed/GRILLE/grille.html">grille</a></i></font> 292 293 293 294 </h4> … … 321 322 322 323 <h4>Version</h4> 323 $Id: checkfield.pro 232 2007-03-20 16:59:36Z pinsard $ 324 $Id: checkfield.pro 238 2007-03-27 13:43:18Z pinsard $ 325 324 326 <h4>History</h4> 325 327 … … 386 388 387 389 388 <font size="-1" color="#006633">default:</font> <font size="-1" color="#006633"><i>defined by <a href=". //../../../../ToBeReviewed/GRILLE/grille.html">grille</a></i></font>390 <font size="-1" color="#006633">default:</font> <font size="-1" color="#006633"><i>defined by <a href="../../..//ToBeReviewed/GRILLE/grille.html">grille</a></i></font> 389 391 390 392 </h4> … … 402 404 403 405 404 <font size="-1" color="#006633">default:</font> <font size="-1" color="#006633"><i>defined by <a href=". //../../../../ToBeReviewed/GRILLE/grille.html">grille</a></i></font>406 <font size="-1" color="#006633">default:</font> <font size="-1" color="#006633"><i>defined by <a href="../../..//ToBeReviewed/GRILLE/grille.html">grille</a></i></font> 405 407 406 408 </h4> … … 418 420 419 421 420 <font size="-1" color="#006633">default:</font> <font size="-1" color="#006633"><i>defined by <a href=". //../../../../ToBeReviewed/GRILLE/grille.html">grille</a></i></font>422 <font size="-1" color="#006633">default:</font> <font size="-1" color="#006633"><i>defined by <a href="../../..//ToBeReviewed/GRILLE/grille.html">grille</a></i></font> 421 423 422 424 </h4> … … 450 452 451 453 <h4>Version</h4> 452 $Id: checkfield.pro 23 2 2007-03-20 16:59:36Z pinsard $454 $Id: checkfield.pro 238 2007-03-27 13:43:18Z pinsard $ 453 455 454 456 <h4>History</h4> … … 480 482 </font></h2> 481 483 482 <p><font face="Courier"><i>result = </i>checkfield(<i><a href="#_checkfield_keyword_field">field</a>, <a href="#_checkfield_keyword_procedure">procedure</a></i>, <a href="#_checkfield_keyword_TYPE">TYPE</a>=<i>TYPE</i>, <a href="#_checkfield_keyword_BOXZOOM">BOXZOOM</a>=<i>vector</i>, <a href="#_checkfield_keyword_DIREC">DIREC</a>=<i>DIREC</i>, <a href="#_checkfield_keyword_NOQUESTION">NOQUESTION</a>=<i>NOQUESTION</i>, <a href="#_checkfield_keyword_VECTEUR">VECTEUR</a>=<i>ve tcor</i>, <a href="#_checkfield_keyword_WDEPTH">WDEPTH</a>=<i>WDEPTH</i>, <a href="#_checkfield_keyword__EXTRA">_EXTRA</a>=<i>_EXTRA</i>)</font></p>484 <p><font face="Courier"><i>result = </i>checkfield(<i><a href="#_checkfield_keyword_field">field</a>, <a href="#_checkfield_keyword_procedure">procedure</a></i>, <a href="#_checkfield_keyword_TYPE">TYPE</a>=<i>TYPE</i>, <a href="#_checkfield_keyword_BOXZOOM">BOXZOOM</a>=<i>vector</i>, <a href="#_checkfield_keyword_DIREC">DIREC</a>=<i>DIREC</i>, <a href="#_checkfield_keyword_NOQUESTION">NOQUESTION</a>=<i>NOQUESTION</i>, <a href="#_checkfield_keyword_VECTEUR">VECTEUR</a>=<i>vector</i>, <a href="#_checkfield_keyword_WDEPTH">WDEPTH</a>=<i>WDEPTH</i>, <a href="#_checkfield_keyword__EXTRA">_EXTRA</a>=<i>_EXTRA</i>)</font></p> 483 485 484 486 … … 504 506 505 507 506 It respect <a href=". //../../../../ToBeReviewed/LECTURE/litchamp.html">litchamp</a>'s criterions. See IDL>xhelp,'litchamp'508 It respect <a href="../../..//ToBeReviewed/LECTURE/litchamp.html">litchamp</a>'s criterions. See IDL>xhelp,'litchamp' 507 509 508 510 … … 565 567 6 elements: The extraction is made on Boxzoom 566 568 567 Where lon1, lon2,lat1,lat2 are global variables defined at the last domdef! 569 Where lon1, lon2,lat1,lat2 are global variables defined at the last 570 <a href="../../..//ToBeReviewed/GRILLE/domdef.html">domdef</a> ! 568 571 569 572 … … 605 608 606 609 607 <font size="-1" color="#006633">type:</font> <font size="-1" color="#006633"><i>ve tcor</i></font>610 <font size="-1" color="#006633">type:</font> <font size="-1" color="#006633"><i>vector</i></font> 608 611 609 612 … … 652 655 653 656 <h4>Version</h4> 654 $Id: checkfield.pro 23 2 2007-03-20 16:59:36Z pinsard $657 $Id: checkfield.pro 238 2007-03-27 13:43:18Z pinsard $ 655 658 656 659 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/PLOTS/DIVERS/placecolor.html
r234 r242 63 63 64 64 allows to trace the independently from a graph 65 By default, trace a color bar of the same type than the one present in plt 66 and pltz. If max, min and divisions are not stipulated, then max=sup,min=inf 65 By default, trace a color bar of the same type than the one present in 66 <a href="../../..//ToBeReviewed/PLOTS/DESSINE/plt.html">plt</a> 67 and <a href="../../..//ToBeReviewed/PLOTS/DESSINE/pltz.html">pltz</a>. 68 If max, min and divisions are not stipulated, then max=sup,min=inf 67 69 and divisions=div. 68 70 … … 133 135 134 136 <h4>Version</h4> 135 $Id: placecolor.pro 23 2 2007-03-20 16:59:36Z pinsard $137 $Id: placecolor.pro 237 2007-03-26 15:37:03Z pinsard $ 136 138 137 139 <h4>History</h4> … … 144 146 145 147 146 148 <h4>Todo items</h4> 149 reference to plein2dessin in restriction not understable : 150 plein2dessin does'nt exist. 151 147 152 <h4>Restrictions</h4> 148 153 Only usable for Postscripts effectuated with plein2dessin -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/PLOTS/DIVERS/placedessin.html
r234 r242 98 98 99 99 100 It specify what procedure is called by PLACEDESSIN: 'plt', 'pltz' or 'pltt' 100 It specify what procedure is called by <a href=".//PLACEDESSIN.html">PLACEDESSIN</a> : 101 'plt', 'pltz' or 'pltt' 101 102 102 103 … … 223 224 If we want to trace contours of a different field than the one 224 225 whose we have the colored drawing (by example E-P in color and QSR in contours). 225 It must be a field respecting same characteristics than the argument number one of plt. 226 It must be a field respecting same characteristics than the argument number 227 one of <a href="../../..//ToBeReviewed/PLOTS/DESSINE/plt.html">plt</a>. 226 228 227 229 … … 290 292 If there is 4 elements: 291 293 then is constituted of coordinates (expressed in cm located from the up and 292 left corner of the page or the window (in portrait like in landscape) )of the bottom294 left corner of the page or the window (in portrait like in landscape) of the bottom 293 295 and left corner and of the up and right corner of the drawing zone. 294 296 If there is 3 elements: … … 332 334 /MAP: In this case, map is automatically calculated have the value: 333 335 map = [0, (lon1+lon2)/2., 0] 334 Comment : A good way to choose the type of the projection we want to do is to have a look at IDL demo:336 Comment 1: A good way to choose the type of the projection we want to do is to have a look at IDL demo: 335 337 IDL> demo 336 338 Then choose earth sciences and mapping. 337 Comment 2: By default it is a cylindrical projection which is effectuated (with or without the keyword map).339 Comment 2: By default it is a cylindrical projection which is effectuated (with or without the keyword map). 338 340 If we want an other projection, MAP must be activated and we have to add the keyword: /nom_projection. 339 341 For example, for a polar projection centered on the south pole: … … 372 374 373 375 Make a postscript. Only works if we made one drawing on the page. 374 If we make several drawing, use @ ps.376 If we make several drawing, use @<a href="../../..//ToBeReviewed/POSTSCRIPT/ps.html">ps</a>. 375 377 376 378 … … 525 527 526 528 <h4>Version</h4> 527 $Id: placedessin.pro 23 2 2007-03-20 16:59:36Z pinsard $529 $Id: placedessin.pro 237 2007-03-26 15:37:03Z pinsard $ 528 530 529 531 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/PLOTS/DIVERS/restoreatt.html
r234 r242 99 99 100 100 101 a structure like the one who read litchamp.101 a structure like the one who read <a href="../../..//ToBeReviewed/LECTURE/litchamp.html">litchamp</a>. 102 102 See IDL> xhelp,'litchamp' 103 103 … … 111 111 112 112 <h4>Version</h4> 113 $Id: restoreatt.pro 23 1 2007-03-19 17:15:51Z pinsard $113 $Id: restoreatt.pro 237 2007-03-26 15:37:03Z pinsard $ 114 114 115 115 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/PLOTS/DIVERS/terminedessin.html
r234 r242 101 101 102 102 Make a postscript. Only works if we made one drawing on the page. 103 If we make several drawing, use @ ps.103 If we make several drawing, use @<a href="../../..//ToBeReviewed/POSTSCRIPT/ps.html">ps</a>. 104 104 105 105 … … 153 153 154 154 <h4>Version</h4> 155 $Id: terminedessin.pro 23 2 2007-03-20 16:59:36Z pinsard $155 $Id: terminedessin.pro 237 2007-03-26 15:37:03Z pinsard $ 156 156 157 157 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/PLOTS/LABEL/label_gmt.html
r234 r242 208 208 209 209 <h4>Version</h4> 210 $Id: label_gmt.pro 2 31 2007-03-19 17:15:51Z pinsard $210 $Id: label_gmt.pro 240 2007-03-28 12:17:24Z pinsard $ 211 211 <h4>History</h4> 212 212 -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/PLOTS/VECTEUR/ajoutvect.html
r234 r242 196 196 197 197 <h4>Version</h4> 198 $Id: ajoutvect.pro 2 31 2007-03-19 17:15:51Z pinsard$198 $Id: ajoutvect.pro 241 2007-04-03 19:23:34Z smasson $ 199 199 200 200 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/PLOTS/VECTEUR/velovect.html
r234 r242 119 119 120 120 121 The Y component of the two dimensional field. 122 the same dimensions as X. 121 The Y component of the two dimensional field. Y must have 122 the same dimensions as X. The vector at point [i,j] has a 123 123 magnitude of: 124 124 … … 144 144 145 145 146 Optional abscissa values. 146 Optional abscissa values. X must be a vector with a length 147 147 equal to the first dimension of U and V. 148 148 … … 162 162 163 163 164 Optional ordinate values. 164 Optional ordinate values. Y must be a vector with a length 165 165 equal to the first dimension of U and V. 166 166 … … 185 185 186 186 187 Missing data value. 187 Missing data value. Vectors with a LENGTH greater 188 188 than MISSING are ignored. 189 189 … … 202 202 203 203 204 Length factor. 204 Length factor. The default of 1.0 makes the longest (U,V) 205 205 vector the length of a cell. 206 206 … … 221 221 Set this keyword to 1 to place a dot at each missing point. 222 222 Set this keyword to 0 or omit it to draw nothing for missing 223 points. 223 points. Has effect only if MISSING is specified. 224 224 225 225 … … 283 283 284 284 285 Set this keyword to make VELOVECT "overplot". 285 Set this keyword to make VELOVECT "overplot". That is, the 286 286 current graphics screen is not erased, no axes are drawn, and 287 287 the previously established scaling remains in effect. … … 310 310 311 311 <h4>Version</h4> 312 $Id: velovect.pro 23 1 2007-03-19 17:15:51Z pinsard $312 $Id: velovect.pro 238 2007-03-27 13:43:18Z pinsard $ 313 313 314 314 <h4>History</h4> … … 317 317 Added TITLE, Oct, 1990. 318 318 Added POSITION, NOERASE, COLOR, Feb 91, RES. 319 August, 1993. 319 August, 1993. Vince Patrick, Adv. Visualization Lab, U. of Maryland, 320 320 fixed errors in math. 321 321 August, 1993. DMS, Added _EXTRA keyword inheritance. … … 326 326 OPLOT to PLOTS. 327 327 September, 1996, GGS. Changed denominator of x_step and y_step vars. 328 February, 1998, DLD. 329 June, 1998, DLD. 330 331 Copyright (c) 1983-1998, Research Systems, Inc. 328 February, 1998, DLD. Add support for CLIP and NO_CLIP keywords. 329 June, 1998, DLD. Add support for OVERPLOT keyword. 330 331 Copyright (c) 1983-1998, Research Systems, Inc. All rights reserved. 332 332 Unauthorized reproduction prohibited. 333 333 … … 339 339 340 340 <h4>Restrictions</h4> 341 Plotting on the selected device is performed. 341 Plotting on the selected device is performed. System 342 342 variables concerning plotting are changed. 343 343 Note: All other keywords are passed directly to the PLOT procedure -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/POSTSCRIPT/chcolps.html
r234 r242 130 130 131 131 <h4>Version</h4> 132 $Id: chcolps.pro 2 31 2007-03-19 17:15:51Z pinsard $132 $Id: chcolps.pro 240 2007-03-28 12:17:24Z pinsard $ 133 133 134 134 <h4>History</h4> … … 195 195 196 196 <h4>Version</h4> 197 $Id: chcolps.pro 2 31 2007-03-19 17:15:51Z pinsard $197 $Id: chcolps.pro 240 2007-03-28 12:17:24Z pinsard $ 198 198 199 199 <h4>History</h4> … … 330 330 331 331 <h4>Version</h4> 332 $Id: chcolps.pro 2 31 2007-03-19 17:15:51Z pinsard $332 $Id: chcolps.pro 240 2007-03-28 12:17:24Z pinsard $ 333 333 334 334 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/STATISTICS/a_correlate2d.html
r234 r242 75 75 <dl> 76 76 77 <dt><a href="#_auto_cov2d"><i>result = </i>auto_cov2d(<i>X, Lag</i>, D ouble=<i>Double</i>, zero2nan=<i>zero2nan</i>)</a><dt>77 <dt><a href="#_auto_cov2d"><i>result = </i>auto_cov2d(<i>X, Lag</i>, DOUBLE=<i>DOUBLE</i>, ZERO2NAN=<i>ZERO2NAN</i>)</a><dt> 78 78 <dd><font size="-1"> </font></dd> 79 79 … … 93 93 </font></h2> 94 94 95 <p><font face="Courier"><i>result = </i>auto_cov2d(<i><a href="#_auto_cov2d_keyword_X">X</a>, <a href="#_auto_cov2d_keyword_Lag">Lag</a></i>, <a href="#_auto_cov2d_keyword_D ouble">Double</a>=<i>Double</i>, <a href="#_auto_cov2d_keyword_zero2nan">zero2nan</a>=<i>zero2nan</i>)</font></p>95 <p><font face="Courier"><i>result = </i>auto_cov2d(<i><a href="#_auto_cov2d_keyword_X">X</a>, <a href="#_auto_cov2d_keyword_Lag">Lag</a></i>, <a href="#_auto_cov2d_keyword_DOUBLE">DOUBLE</a>=<i>DOUBLE</i>, <a href="#_auto_cov2d_keyword_ZERO2NAN">ZERO2NAN</a>=<i>ZERO2NAN</i>)</font></p> 96 96 97 97 … … 145 145 146 146 147 <a name="#_auto_cov2d_keyword_D ouble"></a>148 <h4>D ouble 147 <a name="#_auto_cov2d_keyword_DOUBLE"></a> 148 <h4>DOUBLE 149 149 150 150 … … 161 161 162 162 163 <a name="#_auto_cov2d_keyword_ zero2nan"></a>164 <h4> zero2nan 163 <a name="#_auto_cov2d_keyword_ZERO2NAN"></a> 164 <h4>ZERO2NAN 165 165 166 166 -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/STATISTICS/a_timecorrelate.html
r234 r242 62 62 63 63 64 65 64 66 65 … … 83 82 84 83 <dt><a href="#_a_timecorrelate"><i>result = </i>a_timecorrelate(<i>X, Lag</i>, COVARIANCE=<i>COVARIANCE</i>, DOUBLE=<i>DOUBLE</i>)</a><dt> 85 <dd><font size="-1"> </font></dd>84 <dd><font size="-1"> </font></dd> 86 85 87 86 </dl> … … 121 120 122 121 123 An Array which last dimension is the time dimension so122 An array which last dimension is the time dimension so 124 123 size n. 125 124 … … 140 139 141 140 142 143 141 144 142 … … 157 155 158 156 159 160 157 161 158 … … 196 193 197 194 198 199 195 200 196 201 197 202 198 <h3>Examples</h3><pre> 203 204 199 205 200 </pre><h3>Version history</h3> … … 209 204 210 205 <h4>History</h4> 211 212 206 213 207 … … 240 234 241 235 236 242 237 243 238 … … 259 254 260 255 261 An Array which last dimension is the time dimension so256 An array which last dimension is the time dimension so 262 257 size n. 263 258 … … 277 272 278 273 279 A scalar or n-element vector, in the interval [-(n-2),(n-2)],280 of type integer that specifies the absolute distance(s) between 274 A scalar or n-elements vector, in the interval [-(n-2),(n-2)], 275 of type integer that specifies the absolute distance(s) between 281 276 indexed elements of X. 282 277 … … 325 320 326 321 <h3>Examples</h3><pre> 327 Define an n-elementsample population.328 329 330 331 332 333 334 335 322 Define an n-elements sample population. 323 IDL> x = [3.73, 3.67, 3.77, 3.83, 4.67, 5.87, 6.70, 6.97, 6.40, 5.57] 324 325 Compute the autocorrelation of X for LAG = -3, 0, 1, 3, 4, 8 326 IDL> lag = [-3, 0, 1, 3, 4, 8] 327 IDL> result = a_correlate(x, lag) 328 329 The result should be: 330 [0.0146185, 1.00000, 0.810879, 0.0146185, -0.325279, -0.151684] 336 331 337 332 </pre><h3>Version history</h3> -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/STATISTICS/c_timecorrelate.html
r234 r242 79 79 80 80 <dt><a href="#_c_timecorrelate"><i>result = </i>c_timecorrelate(<i>X, Y, Lag</i>, Covariance=<i>Covariance</i>, Double=<i>Double</i>)</a><dt> 81 <dd><font size="-1"> </font></dd>81 <dd><font size="-1"> </font></dd> 82 82 83 83 </dl> … … 118 118 119 119 120 121 120 122 121 … … 135 134 136 135 137 138 136 139 137 … … 152 150 153 151 154 155 152 156 153 … … 169 166 170 167 171 172 168 173 169 … … 186 182 187 183 188 189 184 190 185 … … 225 220 226 221 227 228 222 229 223 230 224 231 225 <h3>Examples</h3><pre> 232 233 226 234 227 </pre><h3>Version history</h3> … … 238 231 239 232 <h4>History</h4> 240 241 233 242 234 … … 269 261 270 262 263 271 264 272 265 … … 288 281 289 282 290 An Array which last dimension is the time dimension of283 An array which last dimension is the time dimension of 291 284 size n, float or double. 292 285 … … 306 299 307 300 308 An Array which last dimension is the time dimension of301 An array which last dimension is the time dimension of 309 302 size n, float or double. 310 303 … … 324 317 325 318 326 A scalar or n-element vector, in the interval [-(n-2),(n-2)],319 A scalar or n-elements vector, in the interval [-(n-2),(n-2)], 327 320 of type integer that specifies the absolute distance(s) between 328 321 indexed elements of X. … … 373 366 <h3>Examples</h3><pre> 374 367 375 Define two n-elementsample populations.376 377 378 379 380 381 382 383 384 368 Define two n-elements sample populations. 369 IDL> x = [3.73, 3.67, 3.77, 3.83, 4.67, 5.87, 6.70, 6.97, 6.40, 5.57] 370 IDL> y = [2.31, 2.76, 3.02, 3.13, 3.72, 3.88, 3.97, 4.39, 4.34, 3.95] 371 372 Compute the cross correlation of X and Y for LAG = -5, 0, 1, 5, 6, 7 373 IDL> lag = [-5, 0, 1, 5, 6, 7] 374 IDL> result = c_timecorrelate(x, y, lag) 375 376 The result should be: 377 [-0.428246, 0.914755, 0.674547, -0.405140, -0.403100, -0.339685] 385 378 386 379 </pre><h3>Version history</h3> -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/STRING/chkeywd.html
r234 r242 62 62 63 63 64 In a string containing an order to execute with EXECUTE by example. 64 In a string containing an order to execute with EXECUTE by example. 65 65 We change the value of one of keywords. 66 66 More generally, in a string, we look for the character chain: ', keywdname= ..., … … 75 75 <h2>chkeywd <font size="-1" color="#006633"> 76 76 String, keywords 77 78 </font></h2> 77 </font></h2> 79 78 80 79 <p><font face="Courier"><i>result = </i>chkeywd(<i><a href="#_chkeywd_keyword_stringin">stringin</a>, <a href="#_chkeywd_keyword_keywdname">keywdname</a>, <a href="#_chkeywd_keyword_keywdvalue">keywdvalue</a></i>, <a href="#_chkeywd_keyword_SEPARATOR">SEPARATOR</a>=<i>SEPARATOR</i>, <a href="#_chkeywd_keyword_AFTER">AFTER</a>=<i>AFTER</i>)</font></p> … … 83 82 84 83 85 <h3>Return value</h3> 84 <h3>Return value</h3> 86 85 stringout=stringin modified if keywdname has been found in stringin 87 86 … … 137 136 </h4> 138 137 139 138 140 139 The new value of the keyword to considerate in STRINGIN 141 140 … … 160 159 161 160 162 To look for the keyword, we look for the first sign = which follow 163 the position of keywdname. By default, we substitute the string 164 before the comma. With the keyword SEPARATOR,we can modify the cut 165 of the string. SEPARATOR give a Character before the one we have to 161 To look for the keyword, we look for the first sign = which follow 162 the position of keywdname. By default, we substitute the string 163 before the comma. With the keyword SEPARATOR,we can modify the cut 164 of the string. SEPARATOR give a Character before the one we have to 166 165 look for the comma which delimit the keyword in the string. 167 166 (see examples) … … 181 180 182 181 183 To look for the keyword, we look for the first sign = which follow 184 the position of keywdname. By default, we substitute the string 185 before the comma. With the keyword AFTER,we can modify the cut 186 of the string. AFTER give a Character after the one we have to 182 To look for the keyword, we look for the first sign = which follow 183 the position of keywdname. By default, we substitute the string 184 before the comma. With the keyword AFTER,we can modify the cut 185 of the string. AFTER give a Character after the one we have to 187 186 look for the comma which delimit the keyword in the string. 188 187 (see examples) … … 209 208 210 209 <h4>Version</h4> 211 $Id: chkeywd.pro 23 2 2007-03-20 16:59:36Z pinsard $210 $Id: chkeywd.pro 238 2007-03-27 13:43:18Z pinsard $ 212 211 213 212 <h4>History</h4> … … 215 214 18/10/1999 216 215 24/11/1999: adaptation for keywords starting by / 217 216 218 217 219 218 … … 226 225 227 226 228 Beware, this function has loops, ifs ad cases everywhere. So it can 229 not be used by big keywords (with a lot of elements which are big 230 arrays). The input keyword must not contain Complex floatings, structure, 231 Double-precision complex, Pointer, Object reference, Unsigned Integer, 227 Beware, this function has loops, ifs ad cases everywhere. So it can 228 not be used by big keywords (with a lot of elements which are big 229 arrays). The input keyword must not contain Complex floatings, structure, 230 Double-precision complex, Pointer, Object reference, Unsigned Integer, 232 231 Unsigned Longword Integer, 64-bit Integer or Unsigned 64-bit Integer. 233 232 234 233 235 234 … … 237 236 238 237 239 <h4>Uses routines</h4> 238 <h4>Uses routines</h4> 240 239 common.pro 241 240 -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/STRING/delchr.html
r234 r242 146 146 147 147 <h4>Version</h4> 148 $Id: delchr.pro 2 32 2007-03-20 16:59:36Z pinsard $148 $Id: delchr.pro 240 2007-03-28 12:17:24Z pinsard $ 149 149 150 150 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/STRING/getfile.html
r234 r242 195 195 196 196 <h4>Version</h4> 197 $Id: getfile.pro 2 32 2007-03-20 16:59:36Z pinsard $197 $Id: getfile.pro 240 2007-03-28 12:17:24Z pinsard $ 198 198 199 199 <h4>History</h4> … … 207 207 208 208 S. Masson (smasson@lodyc.jussieu.fr) 4 Feb 2002 209 search te file in the all !path directories (use find.pro) 210 when using /find keyword. Use spawn, 'cat...' for unix os. 209 search the file in the all !path directories (use <a href="../..//Utilities/find.html">find</a>) 210 when using /find keyword. Use <proidl>spawn</proidl>, 'cat...' for 211 unix os. 211 212 212 213 Copyright (C) 1990, Johns Hopkins University/Applied Physics Laboratory -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/STRING/strwhere.html
r234 r242 79 79 80 80 81 <h3>Return value</h3> COUNT {out}{optional}82 The number of matches that were found 81 <h3>Return value</h3> 82 The number of matches that were found 83 83 84 The function returns an index array similar to the 84 The function returns an index array similar to the 85 85 result of the where function 86 86 … … 143 143 144 144 <h3>Examples</h3><pre> 145 146 147 ; returns[ 0, 3, 6 ]145 IDL> ind = strwhere('abcabcabc','a') 146 IDL> print, ind 147 [ 0, 3, 6 ] 148 148 149 149 </pre><h3>Version history</h3> 150 150 151 151 <h4>Version</h4> 152 $Id: strwhere.pro 23 2 2007-03-20 16:59:36Z pinsard $152 $Id: strwhere.pro 238 2007-03-27 13:43:18Z pinsard $ 153 153 154 154 <h4>History</h4> 155 155 mgs, 02 Jun 1998: VERSION 1.00 156 bmy, 30 Jun 1998: - now returns COUNT, the number 156 bmy, 30 Jun 1998: - now returns COUNT, the number 157 157 of matches that are found (this is 158 158 analogous to the WHERE command) -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/STRUCTURE/struct2string.html
r234 r242 183 183 184 184 <h4>Restrictions</h4> 185 Use <a href=". //../../../ToBeReviewed/STRING/tostr.html">tostr</a>, cf this function header!185 Use <a href="../..//ToBeReviewed/STRING/tostr.html">tostr</a>, cf this function header! 186 186 187 187 -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/TRIANGULATION/section.html
r234 r242 281 281 282 282 <h4>Version</h4> 283 $Id: section.pro 23 2 2007-03-20 16:59:36Z pinsard $283 $Id: section.pro 237 2007-03-26 15:37:03Z pinsard $ 284 284 285 285 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/WIDGET/AUTOUR_de_XXX/inserthistory.html
r234 r242 156 156 157 157 <h4>Version</h4> 158 $Id: inserthistory.pro 2 31 2007-03-19 17:15:51Z pinsard $158 $Id: inserthistory.pro 240 2007-03-28 12:17:24Z pinsard $ 159 159 160 160 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/WIDGET/AUTOUR_de_XXX/scanfile.html
r234 r242 134 134 135 135 136 Used to pass keywords to <a href=". //../../../../Utilities/isafile.html">isafile</a>137 and <a href=". //../../../../ReadWrite/ncdf_getaxis.html">ncdf_getaxis</a>136 Used to pass keywords to <a href="../../..//Utilities/isafile.html">isafile</a> 137 and <a href="../../..//ReadWrite/ncdf_getaxis.html">ncdf_getaxis</a> 138 138 139 139 … … 145 145 146 146 <h4>Version</h4> 147 $Id: scanfile.pro 23 2 2007-03-20 16:59:36Z pinsard $147 $Id: scanfile.pro 238 2007-03-27 13:43:18Z pinsard $ 148 148 149 149 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/WIDGET/COMPOUND_WIDGET/cw_combobox_pm.html
r234 r242 62 62 63 63 64 65 64 66 65 -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/WIDGET/COMPOUND_WIDGET/cw_slide_slice.html
r234 r242 69 69 70 70 71 72 71 73 72 <h2>Routine summary</h2> … … 149 148 150 149 <h4>Version</h4> 151 $Id: cw_slide_slice.pro 23 2 2007-03-20 16:59:36Z pinsard $150 $Id: cw_slide_slice.pro 238 2007-03-27 13:43:18Z pinsard $ 152 151 <h4>History</h4> 153 152 … … 215 214 216 215 <h4>Version</h4> 217 $Id: cw_slide_slice.pro 23 2 2007-03-20 16:59:36Z pinsard $216 $Id: cw_slide_slice.pro 238 2007-03-27 13:43:18Z pinsard $ 218 217 <h4>History</h4> 219 218 … … 407 406 408 407 <h4>Version</h4> 409 $Id: cw_slide_slice.pro 23 2 2007-03-20 16:59:36Z pinsard $408 $Id: cw_slide_slice.pro 238 2007-03-27 13:43:18Z pinsard $ 410 409 411 410 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/WIDGET/slec.html
r234 r242 189 189 5 elements: The extraction is made on [Boxzoom[0:3], 0, Boxzoom[4]] 190 190 6 elements: The extraction is made on Boxzoom 191 Where lon1,lon2,lat1,lat2 are global variables defined at the last domdef!191 where lon1,lon2,lat1,lat2 are global variables defined at the last domdef! 192 192 193 193 … … 215 215 216 216 <h4>Version</h4> 217 $Id: slec.pro 23 1 2007-03-19 17:15:51Z pinsard $217 $Id: slec.pro 238 2007-03-27 13:43:18Z pinsard $ 218 218 219 219 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/ToBeReviewed/WIDGET/xquestion.html
r234 r242 65 65 66 66 A small widget who ask a question and give an answer. 67 WARNING: For a binary question with yes/no answer use68 DIALOG_MESSAGE.67 WARNING: For a binary question with yes/no, answer use 68 <proidl>DIALOG_MESSAGE</proidl>. 69 69 70 70 … … 177 177 178 178 179 180 181 182 </h4> 183 184 185 A scalar string or a array of string. If this 186 argument is set to : 187 + an array of strings: each array element is 179 <font size="-1" color="#006633">type:</font> <font size="-1" color="#006633"><i>A scalar string or a array of string</i></font> 180 181 182 </h4> 183 184 185 If this argument is set to : 186 - an array of strings: each array element is 188 187 displayed as a separate line of text. 189 +a scalar string: we are looking for the "separate line188 - a scalar string: we are looking for the "separate line 190 189 character" '!C' 191 190 … … 205 204 206 205 207 A stringproposing a answer206 proposing a answer 208 207 209 208 … … 227 226 228 227 229 Active this keyword if you want that xquestion230 check if managed widget are present. If not, xquestiondo not228 Active this keyword if you want that <a href=".//xquestion.html">xquestion</a> 229 check if managed widget are present. If not, <a href=".//xquestion.html">xquestion</a> do not 231 230 open a widget but print the question in the IDL window. 232 231 -
trunk/SRC/Documentation/idldoc_assistant_output/Utilities/createfunc.html
r234 r242 73 73 <h2>createfunc </h2> 74 74 75 <p><font face="Courier"><i>result = </i>createfunc(<i><a href="#_createfunc_keyword_command">command</a></i>, <a href="#_createfunc_keyword_FILENAMEIN">FILENAMEIN</a>=<i>FILENAMEIN</i>, <a href="#_createfunc_keyword_KWDLIST">KWDLIST</a>=<i> KWDLIST</i>, <a href="#_createfunc_keyword__EXTRA">_EXTRA</a>=<i>_EXTRA</i>)</font></p>75 <p><font face="Courier"><i>result = </i>createfunc(<i><a href="#_createfunc_keyword_command">command</a></i>, <a href="#_createfunc_keyword_FILENAMEIN">FILENAMEIN</a>=<i>FILENAMEIN</i>, <a href="#_createfunc_keyword_KWDLIST">KWDLIST</a>=<i>vector string</i>, <a href="#_createfunc_keyword__EXTRA">_EXTRA</a>=<i>_EXTRA</i>)</font></p> 76 76 77 77 … … 91 91 <font size="-1" color="#006633">required</font> 92 92 93 94 95 96 </h4> 97 98 99 a scalar stringdefining the result to be given back by the function.93 <font size="-1" color="#006633">type:</font> <font size="-1" color="#006633"><i>scalar string</i></font> 94 95 96 </h4> 97 98 99 defining the result to be given back by the function. 100 100 (see examples) 101 101 … … 130 130 131 131 132 132 <font size="-1" color="#006633">type:</font> <font size="-1" color="#006633"><i>vector string</i></font> 133 133 134 134 … … 136 136 137 137 138 a vector string.to specify a list of keywords that must be included in the138 to specify a list of keywords that must be included in the 139 139 function definition. 140 140 Warning: the string must start with a ',' … … 168 168 169 169 <h4>Version</h4> 170 $Id: createfunc.pro 23 1 2007-03-19 17:15:51Z pinsard$170 $Id: createfunc.pro 239 2007-03-28 06:50:03Z smasson $ 171 171 172 172 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/Utilities/createpro.html
r234 r242 72 72 <h2>createpro </h2> 73 73 74 <p><font face="Courier">createpro<i>, <a href="#_createpro_keyword_command">command</a></i>, <a href="#_createpro_keyword_FILENAMEIN">FILENAMEIN</a>=<i>FILENAMEIN</i>, <a href="#_createpro_keyword_KWDLIST">KWDLIST</a>=<i> KWDLIST</i>, <a href="#_createpro_keyword_KWDUSED">KWDUSED</a>=<i>KWDUSED</i>, <a href="#_createpro_keyword__EXTRA">_EXTRA</a>=<i>_EXTRA</i></font></p>74 <p><font face="Courier">createpro<i>, <a href="#_createpro_keyword_command">command</a></i>, <a href="#_createpro_keyword_FILENAMEIN">FILENAMEIN</a>=<i>FILENAMEIN</i>, <a href="#_createpro_keyword_KWDLIST">KWDLIST</a>=<i>vector string</i>, <a href="#_createpro_keyword_KWDUSED">KWDUSED</a>=<i>KWDUSED</i>, <a href="#_createpro_keyword__EXTRA">_EXTRA</a>=<i>_EXTRA</i></font></p> 75 75 76 76 … … 96 96 97 97 98 a string array defining the procedure to be created.98 array defining the procedure to be created. 99 99 each element will be a line of the created procedure. 100 100 … … 129 129 130 130 131 132 133 134 </h4> 135 136 137 a vector string. 131 <font size="-1" color="#006633">type:</font> <font size="-1" color="#006633"><i>vector string</i></font> 132 133 134 </h4> 135 136 138 137 to specify a list of keywords that must be included in the procedure 139 138 definition. … … 186 185 187 186 <h4>Version</h4> 188 $Id: createpro.pro 232 2007-03-20 16:59:36Z pinsard $ 187 $Id: createpro.pro 239 2007-03-28 06:50:03Z smasson $ 188 189 189 <h4>History</h4> 190 190 Sebastien Masson (smasson@lodyc.jussieu.fr) … … 199 199 200 200 <h4>Restrictions</h4> 201 - is not working with functions, use createfuncinstead.201 - is not working with functions, use <a href=".//createfunc.html">createfunc</a> instead. 202 202 - arguments can be given only through keywords. 203 203 - ends the procedure name with '.pro' if needed. -
trunk/SRC/Documentation/idldoc_assistant_output/Utilities/def_myuniquetmpdir.html
r234 r242 92 92 93 93 <h4>Version</h4> 94 $Id: def_myuniquetmpdir.pro 23 1 2007-03-19 17:15:51Z pinsard$94 $Id: def_myuniquetmpdir.pro 239 2007-03-28 06:50:03Z smasson $ 95 95 96 96 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/Utilities/find.html
r234 r242 67 67 By default look for files included in !path 68 68 69 all file_searchkeywords can be used.69 all <proidl>file_search</proidl> keywords can be used. 70 70 71 71 … … 75 75 <a name="#_find"></a> 76 76 77 <h2>find <font size="-1" color="#006633"> 77 <h2>find <font size="-1" color="#006633"> 78 78 find a file 79 79 </font></h2> 80 80 81 <p><font face="Courier"><i>result = </i>find(<i><a href="#_find_keyword_filein">filein</a></i>, <a href="#_find_keyword_IODIRECTORY">IODIRECTORY</a>=<i> IODIRECTORY</i>, <a href="#_find_keyword_RECURSIVE">RECURSIVE</a>=<i>RECURSIVE</i>, <a href="#_find_keyword_REPERTOIRE">REPERTOIRE</a>=<i>REPERTOIRE</i>, <a href="#_find_keyword_NOPRO">NOPRO</a>=<i>NOPRO</i>, <a href="#_find_keyword_ONLYPRO">ONLYPRO</a>=<i>ONLYPRO</i>, <a href="#_find_keyword_ONLYNC">ONLYNC</a>=<i>ONLYNC</i>, <a href="#_find_keyword_UNIQUE">UNIQUE</a>=<i>UNIQUE</i>, <a href="#_find_keyword_FIRSTFOUND">FIRSTFOUND</a>=<i>FIRSTFOUND</i>, <a href="#_find_keyword_LOOKALLDIR">LOOKALLDIR</a>=<i>LOOKALLDIR</i>, <a href="#_find_keyword_TRYFIND">TRYFIND</a>=<i>TRYFIND</i>, <a href="#_find_keyword__EXTRA">_EXTRA</a>=<i>_EXTRA</i>)</font></p>82 83 84 85 86 <h3>Return value</h3> 81 <p><font face="Courier"><i>result = </i>find(<i><a href="#_find_keyword_filein">filein</a></i>, <a href="#_find_keyword_IODIRECTORY">IODIRECTORY</a>=<i>scalar string or array of strings</i>, <a href="#_find_keyword_RECURSIVE">RECURSIVE</a>=<i>RECURSIVE</i>, <a href="#_find_keyword_REPERTOIRE">REPERTOIRE</a>=<i>REPERTOIRE</i>, <a href="#_find_keyword_NOPRO">NOPRO</a>=<i>NOPRO</i>, <a href="#_find_keyword_ONLYPRO">ONLYPRO</a>=<i>ONLYPRO</i>, <a href="#_find_keyword_ONLYNC">ONLYNC</a>=<i>ONLYNC</i>, <a href="#_find_keyword_UNIQUE">UNIQUE</a>=<i>UNIQUE</i>, <a href="#_find_keyword_FIRSTFOUND">FIRSTFOUND</a>=<i>FIRSTFOUND</i>, <a href="#_find_keyword_LOOKALLDIR">LOOKALLDIR</a>=<i>LOOKALLDIR</i>, <a href="#_find_keyword_TRYFIND">TRYFIND</a>=<i>TRYFIND</i>, <a href="#_find_keyword__EXTRA">_EXTRA</a>=<i>_EXTRA</i>)</font></p> 82 83 84 85 86 <h3>Return value</h3> 87 87 A scalar or array variable of string type, containing the 88 88 name (with the full path of the matching files. If no files 89 exist with names matching the input arguments, findreturns89 exist with names matching the input arguments, <a href=".//find.html">find</a> returns 90 90 the scalar string : 'NOT FOUND' 91 91 … … 102 102 <font size="-1" color="#006633">required</font> 103 103 104 105 106 107 </h4> 108 109 110 A scalar or array variable of string type, containing 111 file names to match. Input names specifications may contain 104 <font size="-1" color="#006633">type:</font> <font size="-1" color="#006633"><i>scalar string or array of strings</i></font> 105 106 107 </h4> 108 109 110 File name[s] to match. Input names specifications may contain 112 111 wildcard characters, enabling them to match multiple files 113 (see file_searchfor more informations). By default and if114 necessary, findis looking for filename and also for filename112 (see <proidl>file_search</proidl> for more informations). By default and if 113 necessary, <a href=".//find.html">find</a> is looking for filename and also for filename 115 114 completed with '.pro' 116 115 … … 129 128 130 129 131 130 <font size="-1" color="#006633">type:</font> <font size="-1" color="#006633"><i>scalar string or array of strings</i></font> 132 131 <font size="-1" color="#006633">default:</font> <font size="-1" color="#006633"><i>['.',!path]</i></font> 133 132 134 133 </h4> 135 134 136 137 A scalar or array variable of string type, containing 138 directories names where we are looking for the file. 135 136 Directories names where we are looking for the file. 139 137 Different directories can be separated by 140 138 path_sep(/search_path) (':' on unix type machine) as it is done … … 156 154 </h4> 157 155 158 156 159 157 performs recursive searching of directory hierarchies. 160 In a recursive search, findlooks recursively for any and all158 In a recursive search, <a href=".//find.html">find</a> looks recursively for any and all 161 159 subdirectories in the file hierarchy rooted at the IODIRECTORY argument. 162 160 … … 174 172 </h4> 175 173 176 177 obsolete. keep for compatibility, use directorykeyword174 175 obsolete. keep for compatibility, use IODIRECTORY keyword 178 176 179 177 … … 190 188 </h4> 191 189 192 190 193 191 activate to avoid the automatic search of filename completed with '.pro' 194 192 … … 206 204 </h4> 207 205 208 206 209 207 force to look only at file ending with .pro 210 208 … … 222 220 </h4> 223 221 224 222 225 223 force to look only at file ending with .nc 226 224 … … 238 236 </h4> 239 237 240 238 241 239 activate to make sure that each element of the output vector is unique. 242 240 … … 254 252 </h4> 255 253 256 254 257 255 activate this keyword to stop looking for the file as soon as we found one. 258 256 … … 270 268 </h4> 271 269 272 270 273 271 activate to look for the file (with a recursive search if needed) 274 272 in . iodir, homedir, !path + the DATA:TestsData directory if it exists. … … 287 285 </h4> 288 286 289 290 if the file was not found and this keyword is activated, find will call 287 288 if the file was not found and this keyword is activated, <a href=".//find.html">find</a> 289 will call 291 290 itself with the keywords /LOOKALLDIR and /FIRSTFOUND to try to find 292 291 the file we are looking for. Note that if the file was found at the 293 first try this keyword as no effect (which is not the case with LOOKALLDIR) 292 first try this keyword as no effect (which is not the case with LOOKALLDIR) 294 293 295 294 … … 306 305 </h4> 307 306 308 307 309 308 Used to pass keywords 310 309 … … 313 312 314 313 <h3>Examples</h3><pre> 315 316 314 IDL> print, find('*loadct') 317 315 /usr/local/rsi/idl_6.0/lib/utilities/xloadct.pro … … 342 340 343 341 <h4>Version</h4> 344 $Id: find.pro 232 2007-03-20 16:59:36Z pinsard $ 342 $Id: find.pro 239 2007-03-28 06:50:03Z smasson $ 343 345 344 <h4>History</h4> 346 345 Sebastien Masson (smasson@lodyc.jussieu.fr) -
trunk/SRC/Documentation/idldoc_assistant_output/Utilities/fitintobox.html
r234 r242 104 104 105 105 an array or a structure that can be read by the function 106 <a href=". //../../ToBeReviewed/LECTURE/litchamp.html">litchamp</a>106 <a href="..//ToBeReviewed/LECTURE/litchamp.html">litchamp</a> 107 107 108 108 … … 116 116 117 117 118 <font size="-1" color="#006633">default:</font> <font size="-1" color="#006633"><i>define by <a href=". //../../ToBeReviewed/GRILLE/grille.html">grille</a></i></font>118 <font size="-1" color="#006633">default:</font> <font size="-1" color="#006633"><i>define by <a href="..//ToBeReviewed/GRILLE/grille.html">grille</a></i></font> 119 119 120 120 </h4> … … 132 132 133 133 134 <font size="-1" color="#006633">default:</font> <font size="-1" color="#006633"><i>define by <a href=". //../../ToBeReviewed/GRILLE/grille.html">grille</a></i></font>134 <font size="-1" color="#006633">default:</font> <font size="-1" color="#006633"><i>define by <a href="..//ToBeReviewed/GRILLE/grille.html">grille</a></i></font> 135 135 136 136 </h4> … … 148 148 149 149 150 <font size="-1" color="#006633">default:</font> <font size="-1" color="#006633"><i>define by <a href=". //../../ToBeReviewed/GRILLE/grille.html">grille</a></i></font>150 <font size="-1" color="#006633">default:</font> <font size="-1" color="#006633"><i>define by <a href="..//ToBeReviewed/GRILLE/grille.html">grille</a></i></font> 151 151 152 152 </h4> … … 164 164 165 165 166 <font size="-1" color="#006633">default:</font> <font size="-1" color="#006633"><i>define by <a href=". //../../ToBeReviewed/GRILLE/grille.html">grille</a></i></font>166 <font size="-1" color="#006633">default:</font> <font size="-1" color="#006633"><i>define by <a href="..//ToBeReviewed/GRILLE/grille.html">grille</a></i></font> 167 167 168 168 </h4> … … 180 180 181 181 182 <font size="-1" color="#006633">default:</font> <font size="-1" color="#006633"><i>define by <a href=". //../../ToBeReviewed/GRILLE/grille.html">grille</a></i></font>182 <font size="-1" color="#006633">default:</font> <font size="-1" color="#006633"><i>define by <a href="..//ToBeReviewed/GRILLE/grille.html">grille</a></i></font> 183 183 184 184 </h4> … … 196 196 197 197 198 <font size="-1" color="#006633">default:</font> <font size="-1" color="#006633"><i>define by <a href=". //../../ToBeReviewed/GRILLE/grille.html">grille</a></i></font>198 <font size="-1" color="#006633">default:</font> <font size="-1" color="#006633"><i>define by <a href="..//ToBeReviewed/GRILLE/grille.html">grille</a></i></font> 199 199 200 200 </h4> … … 212 212 213 213 214 <font size="-1" color="#006633">default:</font> <font size="-1" color="#006633"><i>define by <a href=". //../../ToBeReviewed/GRILLE/grille.html">grille</a></i></font>214 <font size="-1" color="#006633">default:</font> <font size="-1" color="#006633"><i>define by <a href="..//ToBeReviewed/GRILLE/grille.html">grille</a></i></font> 215 215 216 216 </h4> … … 228 228 229 229 230 <font size="-1" color="#006633">default:</font> <font size="-1" color="#006633"><i>define by <a href=". //../../ToBeReviewed/GRILLE/grille.html">grille</a></i></font>230 <font size="-1" color="#006633">default:</font> <font size="-1" color="#006633"><i>define by <a href="..//ToBeReviewed/GRILLE/grille.html">grille</a></i></font> 231 231 232 232 </h4> … … 244 244 245 245 246 <font size="-1" color="#006633">default:</font> <font size="-1" color="#006633"><i>define by <a href=". //../../ToBeReviewed/GRILLE/grille.html">grille</a></i></font>246 <font size="-1" color="#006633">default:</font> <font size="-1" color="#006633"><i>define by <a href="..//ToBeReviewed/GRILLE/grille.html">grille</a></i></font> 247 247 248 248 </h4> … … 281 281 Error: 282 282 the array dimensions [180,148,78] are incompatible 283 with the thedomain dimensions283 with the domain dimensions 284 284 [jpi/nx, jpj/ny, jpk/nz, jpt] = [180/41, 148/3, 31/31, 1] 285 285 <Expression> INT = -1 … … 288 288 289 289 <h4>Version</h4> 290 $Id: fitintobox.pro 231 2007-03-19 17:15:51Z pinsard $ 290 $Id: fitintobox.pro 238 2007-03-27 13:43:18Z pinsard $ 291 291 292 <h4>History</h4> 292 293 Sebastien Masson (smasson@lodyc.jussieu.fr) … … 305 306 306 307 307 <h4>Uses routines</h4> 308 <h4>Uses routines</h4> 308 309 cm_4mesh 309 310 cm_4cal -
trunk/SRC/Documentation/idldoc_assistant_output/Utilities/isadirectory.html
r234 r242 103 103 a proposed directory. If neither dirname 104 104 input parameter of IODIRECTORY keyword are defined, 105 the ask the user to choose a directory.105 we ask the user to choose a directory. 106 106 107 107 … … 157 157 158 158 159 Used to pass keywords 160 161 all dialog_pickfile keywords (like filter) can be used. 159 Used to pass keywords to <proidl>dialog_pickfile</proidl> 162 160 163 161 … … 175 173 176 174 <h4>Version</h4> 177 $Id: isadirectory.pro 232 2007-03-20 16:59:36Z pinsard $ 175 $Id: isadirectory.pro 237 2007-03-26 15:37:03Z pinsard $ 176 178 177 <h4>History</h4> 179 178 Sebastien Masson (smasson@lodyc.jussieu.fr) -
trunk/SRC/Documentation/idldoc_assistant_output/Utilities/isafile.html
r234 r242 63 63 64 64 same as <a href=".//find.html">find</a> except that as long as the file is 'NOT FOUND', 65 isafile calls dialog_pickfile, to ask the user to select a file. 65 <a href=".//isafile.html">isafile</a> calls 66 <proidl>dialog_pickfile</proidl>, to ask the user to select a file. 66 67 67 68 … … 71 72 <a name="#_isafile"></a> 72 73 73 <h2>isafile <font size="-1" color="#006633"> 74 <h2>isafile <font size="-1" color="#006633"> 74 75 io 75 76 </font></h2> … … 102 103 103 104 a proposed name. If neither filein input parameter of filename keyword are 104 defined, the ask the user to choose a file.105 defined, we ask the user to choose a file. 105 106 106 107 … … 176 177 177 178 performs recursive searching of directory hierarchies. 178 In a recursive search, findlooks recursively for any and all179 In a recursive search, <a href=".//find.html">find</a> looks recursively for any and all 179 180 subdirectories in the file hierarchy rooted at the IODIRECTORY argument. 180 181 … … 225 226 226 227 227 Used to pass keywords 228 229 all find, file_search and dialog_pickfile keywords (like title) can be used228 Used to pass keywords to <a href=".//find.html">find</a>, 229 <proidl>file_search</proidl> and 230 <proidl>dialog_pickfile</proidl> 230 231 231 232 … … 233 234 234 235 <h3>Examples</h3><pre> 235 236 236 IDL> print, isafile('/Users/sebastie/SAXO_RD/Commons/cm_4mesh.pro') 237 237 /Users/sebastie/SAXO_RD/Commons/cm_4mesh.pro … … 249 249 250 250 <h4>Version</h4> 251 $Id: isafile.pro 232 2007-03-20 16:59:36Z pinsard $ 251 $Id: isafile.pro 237 2007-03-26 15:37:03Z pinsard $ 252 252 253 <h4>History</h4> 253 254 Sebastien Masson (smasson@lodyc.jussieu.fr) -
trunk/SRC/Documentation/idldoc_assistant_output/Utilities/linearequation.html
r234 r242 104 104 105 105 106 This is the first point of (the) straight line(s) whose we want to calculate106 This is the first point of (the) straight line(s) whose we want to calculate 107 107 equation(s) 108 108 … … 122 122 123 123 124 This is the second point of (the) straight line(s) whose we want to calculate124 This is the second point of (the) straight line(s) whose we want to calculate 125 125 equation(s) 126 126 -
trunk/SRC/Documentation/idldoc_assistant_output/Utilities/lineintersection.html
r234 r242 84 84 1) by default: it is a vector of complex whose each element is the coordinates 85 85 of the intersection point of a pair of straight lines. 86 2) if FLOAT is activated, it is a array of re els of dimension 2,86 2) if FLOAT is activated, it is a array of reals of dimension 2, 87 87 number_of_pairs_of_straight_lines whose each row is the coordinates 88 88 of the intersection point of a pair of straight line. … … 107 107 108 108 is the first array of dimension 3, number_of_pairs_of_straight_lines, 109 whose each line contain the 3 parameters a, b and c of the first linear109 whose each line contain the 3 parameters a, b and c of the first linear 110 110 equation of the type ax+by+c=0 111 111 … … 126 126 127 127 is second array of dimension 3, number_of_pairs_of_straight_lines, 128 whose each line contain the 3 parameters a, b and c of the second linear128 whose each line contain the 3 parameters a, b and c of the second linear 129 129 equation of the type ax+by+c=0 130 130 … … 179 179 180 180 <h4>Restrictions</h4> 181 If the 2 straight line are parallel, we return coordinates181 If the 2 straight lines are parallel, we return coordinates 182 182 (!values.f_nan,!values.f_nan) 183 183 -
trunk/SRC/Documentation/idldoc_assistant_output/Utilities/mergeonline_help.html
r234 r242 89 89 90 90 <h4>Version</h4> 91 $Id: mergeonline_help.pro 231 2007-03-19 17:15:51Z pinsard $ 91 $Id: mergeonline_help.pro 239 2007-03-28 06:50:03Z smasson $ 92 92 93 <h4>History</h4> 93 94 Sept 2006: Sebastien Masson (smasson@lodyc.jussieu.fr) -
trunk/SRC/Documentation/idldoc_assistant_output/Utilities/protype.html
r234 r242 125 125 <h4>Version</h4> 126 126 $Id: protype.pro 231 2007-03-19 17:15:51Z pinsard $ 127 127 128 <h4>History</h4> 128 129 Sebastien Masson (smasson@lodyc.jussieu.fr) -
trunk/SRC/Documentation/idldoc_assistant_output/Utilities/report.html
r234 r242 64 64 Like <proidl>dialog_message</proidl> if there is already some widget 65 65 active or like <proidl>message</proidl> if there is not any widget active. 66 To ask a question whose answer is not yes/no, use xquestion.66 To ask a question whose answer is not yes/no, use xquestion. 67 67 68 68 … … 95 95 <font size="-1" color="#006633">required</font> 96 96 97 98 99 100 </h4> 101 102 103 one string or one vector of string. Si le string ne97 <font size="-1" color="#006633">type:</font> <font size="-1" color="#006633"><i>scalar string or arrays of string</i></font> 98 99 100 </h4> 101 102 103 If TEXT is a scalar string, we look for the line feed characters "!C" 104 104 comporte qu''un element, on cherche les eventuels caracteres de 105 105 retour a la ligne: '!C'. If text is set to an array of strings, each … … 176 176 177 177 activate to print only the message without the name 178 and the line of the routine (defined by calling routine_name) 179 180 178 and the line of the routine (defined by calling <a href=".//routine_name.html">routine_name</a>) 179 or++ 181 180 Activate to print the error message without printing the routine name with 182 181 its full path. … … 221 220 222 221 <h4>Version</h4> 223 $Id: report.pro 23 2 2007-03-20 16:59:36Z pinsard$222 $Id: report.pro 239 2007-03-28 06:50:03Z smasson $ 224 223 225 224 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/Utilities/routine_name.html
r234 r242 137 137 138 138 <h4>Restrictions</h4> 139 This function use the keyword OUTPUT in help.pro and it is specified 139 This function use the keyword OUTPUT in <proidl>help</proidl> and 140 it is specified 140 141 in the on-line help that the return syntax of this word can change in 141 142 function of the version of the code. This version works with IDL 5.2. -
trunk/SRC/Documentation/idldoc_assistant_output/Utilities/testvar.html
r234 r242 62 62 63 63 64 A kind of keyword_set but when the value exist, it send it back. 64 A kind of <proidl>keyword_set</proidl> but when the value exist, it 65 send it back. 65 66 66 67 -
trunk/SRC/Documentation/idldoc_assistant_output/Utilities/text_box.html
r234 r242 63 63 64 64 This procedure writes a short text message within a box-shaped 65 area in a graphic s window.The message may be split at word65 area in a graphic window. The message may be split at word 66 66 boundaries into several lines, and the character size and 67 67 orientation may be adjusted for the text to fit within the box. … … 93 93 <font size="-1" color="#006633">required</font> 94 94 95 96 97 98 </h4> 99 100 101 ASCII text string containing the message.95 <font size="-1" color="#006633">type:</font> <font size="-1" color="#006633"><i>string</i></font> 96 97 98 </h4> 99 100 101 message in ASCII. 102 102 103 103 … … 121 121 122 122 123 4 element vector specifying the box position and size124 pos[0],pos[1] specify the lower left corner coordinate 125 pos[2],pos[3] specify the upper right corner coordinate 126 data window normalized coordinates are use 123 4 elements vector specifying the box position and size 124 pos[0],pos[1] specify the lower left corner coordinate, 125 pos[2],pos[3] specify the upper right corner coordinate, 126 data window normalized coordinates are used. 127 127 128 128 … … 208 208 209 209 210 activate to show the box on graphic swindow.210 activate to show the box on graphic window. 211 211 212 212 -
trunk/SRC/Documentation/idldoc_assistant_output/Utilities/undefine.html
r234 r242 63 63 64 64 erase a variable 65 same thing that delvarbut usable in a program and usable65 same thing like <proidl>delvar</proidl> but usable in a program and usable 66 66 for one variable simultaneously 67 67 … … 123 123 <a href="http://www.dfanning.com"/> : 124 124 QUESTION: How do I make an IDL variable have a type "undefined"? 125 ANSWER: At the main IDL level you can use the IDL procedure DELVARto125 ANSWER: At the main IDL level you can use the IDL procedure <proidl>DELVAR</proidl> to 126 126 delete an IDL variable and make it undefined. Inside of procedures 127 and functions, I use this little program named UNDEFINEthat I got127 and functions, I use this little program named <a href=".//UNDEFINE.html">UNDEFINE</a> that I got 128 128 from Andrew Cool at the DSTO High Frequency Radar Division in 129 129 Adelaide, Australia. -
trunk/SRC/Documentation/idldoc_assistant_output/Utilities/xfile.html
r234 r242 62 62 63 63 64 display in a widget an ASCII file.65 It is the same thing that xdisplayfilebut here, we use it66 to display the content of a procedure or of a function ,67 even if it is not in the current directory (thanks to the path).64 display an ASCII file in a widget. 65 It is the same thing that <proidl>xdisplayfile<proidl> but here, we use it 66 to display the content of a procedure or of a function located in the !path 67 ".pro" suffix will be appended if needed. 68 68 69 69 … … 124 124 125 125 126 Used to pass keywords 126 Used to pass keywords to <proidl>xdisplayfile</proidl> 127 127 128 128 … … 135 135 136 136 <h4>Version</h4> 137 $Id: xfile.pro 23 2 2007-03-20 16:59:36Z pinsard$137 $Id: xfile.pro 239 2007-03-28 06:50:03Z smasson $ 138 138 139 139 <h4>History</h4> -
trunk/SRC/Documentation/idldoc_assistant_output/Utilities/xhelp.html
r234 r242 92 92 <font size="-1" color="#006633">required</font> 93 93 94 94 <font size="-1" color="#006633">type:</font> <font size="-1" color="#006633"><i>scalar string</i></font> 95 95 96 96 … … 98 98 99 99 100 A scalar string that contains the filename of the file to display. 101 If FILENAME does not include a complete path specification, xhelp will 102 search for the file in the current working directory and then each of the 103 directories listed in !PATH environment variable. The 104 ".pro" file suffix will be appended if it is not supplied. 100 the name of the file to display. 101 FILENAME should be located in !path. 102 ".pro" suffix will be appended if needed. 105 103 106 104 … … 124 122 125 123 126 Used to pass keywords 124 Used to pass keywords to <proidl>xdisplayfile</proidl> 127 125 128 126 … … 135 133 136 134 <h4>Version</h4> 137 $Id: xhelp.pro 23 2 2007-03-20 16:59:36Z pinsard$135 $Id: xhelp.pro 239 2007-03-28 06:50:03Z smasson $ 138 136 139 137 <h4>History</h4> … … 155 153 156 154 <h4>Restrictions</h4> 157 Triggers the XMANAGERif it is not already in use.155 Triggers the <proidl>XMANAGER</proidl> if it is not already in use. 158 156 159 157 -
trunk/SRC/Documentation/idldoc_assistant_output/buildinit.html
r234 r242 82 82 <dl> 83 83 84 <dt><a href="#_cw_field2"><i>result = </i>cw_field2(<i> Parent</i>, COLUMN=<i>COLUMN</i>, ROW=<i>ROW</i>, EVENT_FUNC=<i>EVENT_FUNC</i>, FLOATING=<i>FLOATING</i>, INTEGER=<i>INTEGER</i>, LONG=<i>LONG</i>, STRING=<i>STRING</i>, FONT=<i>FONT</i>, FRAME=<i>FRAME</i>, TITLE=<i>TITLE</i>, UVALUE=<i>UVALUE</i>, VALUE=<i>VALUE</i>, RETURN_EVENTS=<i>RETURN_EVENTS</i>, ALL_EVENTS=<i>ALL_EVENTS</i>, FIELDFONT=<i>FIELDFONT</i>, NOEDIT=<i>NOEDIT</i>, TEXT_FRAME=<i>TEXT_FRAME</i>, XSIZE=<i>XSIZE</i>, YSIZE=<i>YSIZE</i>, UNAME=<i>UNAME</i>)</a><dt>84 <dt><a href="#_cw_field2"><i>result = </i>cw_field2(<i>parent</i>, COLUMN=<i>COLUMN</i>, ROW=<i>ROW</i>, EVENT_FUNC=<i>EVENT_FUNC</i>, FLOATING=<i>FLOATING</i>, INTEGER=<i>INTEGER</i>, LONG=<i>LONG</i>, STRING=<i>STRING</i>, FONT=<i>FONT</i>, FRAME=<i>FRAME</i>, TITLE=<i>TITLE</i>, UVALUE=<i>UVALUE</i>, VALUE=<i>VALUE</i>, RETURN_EVENTS=<i>RETURN_EVENTS</i>, ALL_EVENTS=<i>ALL_EVENTS</i>, FIELDFONT=<i>FIELDFONT</i>, NOEDIT=<i>NOEDIT</i>, TEXT_FRAME=<i>TEXT_FRAME</i>, XSIZE=<i>XSIZE</i>, YSIZE=<i>YSIZE</i>, UNAME=<i>UNAME</i>)</a><dt> 85 85 <dd><font size="-1"> </font></dd> 86 86 … … 114 114 </font></h2> 115 115 116 <p><font face="Courier"><i>result = </i>cw_field2(<i><a href="#_cw_field2_keyword_ Parent">Parent</a></i>, <a href="#_cw_field2_keyword_COLUMN">COLUMN</a>=<i>COLUMN</i>, <a href="#_cw_field2_keyword_ROW">ROW</a>=<i>ROW</i>, <a href="#_cw_field2_keyword_EVENT_FUNC">EVENT_FUNC</a>=<i>EVENT_FUNC</i>, <a href="#_cw_field2_keyword_FLOATING">FLOATING</a>=<i>FLOATING</i>, <a href="#_cw_field2_keyword_INTEGER">INTEGER</a>=<i>INTEGER</i>, <a href="#_cw_field2_keyword_LONG">LONG</a>=<i>LONG</i>, <a href="#_cw_field2_keyword_STRING">STRING</a>=<i>STRING</i>, <a href="#_cw_field2_keyword_FONT">FONT</a>=<i>FONT</i>, <a href="#_cw_field2_keyword_FRAME">FRAME</a>=<i>FRAME</i>, <a href="#_cw_field2_keyword_TITLE">TITLE</a>=<i>TITLE</i>, <a href="#_cw_field2_keyword_UVALUE">UVALUE</a>=<i>UVALUE</i>, <a href="#_cw_field2_keyword_VALUE">VALUE</a>=<i>VALUE</i>, <a href="#_cw_field2_keyword_RETURN_EVENTS">RETURN_EVENTS</a>=<i>RETURN_EVENTS</i>, <a href="#_cw_field2_keyword_ALL_EVENTS">ALL_EVENTS</a>=<i>ALL_EVENTS</i>, <a href="#_cw_field2_keyword_FIELDFONT">FIELDFONT</a>=<i>FIELDFONT</i>, <a href="#_cw_field2_keyword_NOEDIT">NOEDIT</a>=<i>NOEDIT</i>, <a href="#_cw_field2_keyword_TEXT_FRAME">TEXT_FRAME</a>=<i>TEXT_FRAME</i>, <a href="#_cw_field2_keyword_XSIZE">XSIZE</a>=<i>XSIZE</i>, <a href="#_cw_field2_keyword_YSIZE">YSIZE</a>=<i>YSIZE</i>, <a href="#_cw_field2_keyword_UNAME">UNAME</a>=<i>UNAME</i>)</font></p>116 <p><font face="Courier"><i>result = </i>cw_field2(<i><a href="#_cw_field2_keyword_parent">parent</a></i>, <a href="#_cw_field2_keyword_COLUMN">COLUMN</a>=<i>COLUMN</i>, <a href="#_cw_field2_keyword_ROW">ROW</a>=<i>ROW</i>, <a href="#_cw_field2_keyword_EVENT_FUNC">EVENT_FUNC</a>=<i>EVENT_FUNC</i>, <a href="#_cw_field2_keyword_FLOATING">FLOATING</a>=<i>FLOATING</i>, <a href="#_cw_field2_keyword_INTEGER">INTEGER</a>=<i>INTEGER</i>, <a href="#_cw_field2_keyword_LONG">LONG</a>=<i>LONG</i>, <a href="#_cw_field2_keyword_STRING">STRING</a>=<i>STRING</i>, <a href="#_cw_field2_keyword_FONT">FONT</a>=<i>FONT</i>, <a href="#_cw_field2_keyword_FRAME">FRAME</a>=<i>FRAME</i>, <a href="#_cw_field2_keyword_TITLE">TITLE</a>=<i>TITLE</i>, <a href="#_cw_field2_keyword_UVALUE">UVALUE</a>=<i>UVALUE</i>, <a href="#_cw_field2_keyword_VALUE">VALUE</a>=<i>VALUE</i>, <a href="#_cw_field2_keyword_RETURN_EVENTS">RETURN_EVENTS</a>=<i>RETURN_EVENTS</i>, <a href="#_cw_field2_keyword_ALL_EVENTS">ALL_EVENTS</a>=<i>ALL_EVENTS</i>, <a href="#_cw_field2_keyword_FIELDFONT">FIELDFONT</a>=<i>FIELDFONT</i>, <a href="#_cw_field2_keyword_NOEDIT">NOEDIT</a>=<i>NOEDIT</i>, <a href="#_cw_field2_keyword_TEXT_FRAME">TEXT_FRAME</a>=<i>TEXT_FRAME</i>, <a href="#_cw_field2_keyword_XSIZE">XSIZE</a>=<i>XSIZE</i>, <a href="#_cw_field2_keyword_YSIZE">YSIZE</a>=<i>YSIZE</i>, <a href="#_cw_field2_keyword_UNAME">UNAME</a>=<i>UNAME</i>)</font></p> 117 117 118 118 … … 126 126 127 127 128 <a name="#_cw_field2_keyword_ Parent"></a>129 <h4> Parent 128 <a name="#_cw_field2_keyword_parent"></a> 129 <h4>parent 130 130 <font size="-1" color="#006633">in</font> 131 131 … … 468 468 469 469 <h4>Version</h4> 470 $Id: buildinit.pro 23 2 2007-03-20 16:59:36Z pinsard $470 $Id: buildinit.pro 237 2007-03-26 15:37:03Z pinsard $ 471 471 <h4>History</h4> 472 472 … … 534 534 535 535 <h4>Version</h4> 536 $Id: buildinit.pro 23 2 2007-03-20 16:59:36Z pinsard $536 $Id: buildinit.pro 237 2007-03-26 15:37:03Z pinsard $ 537 537 <h4>History</h4> 538 538 … … 599 599 600 600 <h4>Version</h4> 601 $Id: buildinit.pro 23 2 2007-03-20 16:59:36Z pinsard $601 $Id: buildinit.pro 237 2007-03-26 15:37:03Z pinsard $ 602 602 <h4>History</h4> 603 603 … … 663 663 664 664 <h4>Version</h4> 665 $Id: buildinit.pro 23 2 2007-03-20 16:59:36Z pinsard $665 $Id: buildinit.pro 237 2007-03-26 15:37:03Z pinsard $ 666 666 <h4>History</h4> 667 667 … … 729 729 730 730 <h4>Version</h4> 731 $Id: buildinit.pro 23 2 2007-03-20 16:59:36Z pinsard $731 $Id: buildinit.pro 237 2007-03-26 15:37:03Z pinsard $ 732 732 <h4>History</h4> 733 733 … … 825 825 826 826 <h4>Version</h4> 827 $Id: buildinit.pro 23 2 2007-03-20 16:59:36Z pinsard $827 $Id: buildinit.pro 237 2007-03-26 15:37:03Z pinsard $ 828 828 <h4>History</h4> 829 829 … … 871 871 872 872 <h4>Version</h4> 873 $Id: buildinit.pro 23 2 2007-03-20 16:59:36Z pinsard $873 $Id: buildinit.pro 237 2007-03-26 15:37:03Z pinsard $ 874 874 <h4>History</h4> 875 875
Note: See TracChangeset
for help on using the changeset viewer.