Changeset 356 for trunk/SRC/Documentation
- Timestamp:
- 04/23/08 11:07:27 (16 years ago)
- Location:
- trunk/SRC/Documentation/xmldoc
- Files:
-
- 9 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/SRC/Documentation/xmldoc/makefile
r354 r356 325 325 awk 'sub(/ @star@ $$/,""){printf(" * %s", $$0);next};1' | \ 326 326 sed -e "s+@star@+*+" \ 327 -e "s+=== idl\>+=== idl\>+" \ 328 -e "s+---\>+---\>+" \ 327 329 > $@ 328 330 -
trunk/SRC/Documentation/xmldoc/mini_notice.html
r351 r356 52 52 </p><div class="figure"><a name="fig_xxx_0101" id="fig_xxx_0101"></a><p class="title"><b>Figure 1. Window xxx 1</b></p><div class="figure-contents"> 53 53 54 <div class="mediaobject"><img border="0" usemap="id2572 796" src="figpng/xxx_0101.png" alt="Window xxx 1" /><map name="id2572796" id="id2572796"><area shape="rect" coords="27,298,504,249" /><area shape="rect" coords="81,242,450,183" /><area shape="rect" coords="3,175,538,36" /></map><div class="calloutlist"><table border="0" summary="Callout list"><tr><td width="5%" valign="top" align="left"><img src="images/callouts/1.png" alt="1" border="0" /></td><td valign="top" align="left">54 <div class="mediaobject"><img border="0" usemap="id2572841" src="figpng/xxx_0101.png" alt="Window xxx 1" /><map name="id2572841" id="id2572841"><area shape="rect" coords="27,298,504,249" /><area shape="rect" coords="81,242,450,183" /><area shape="rect" coords="3,175,538,36" /></map><div class="calloutlist"><table border="0" summary="Callout list"><tr><td width="5%" valign="top" align="left"><img src="images/callouts/1.png" alt="1" border="0" /></td><td valign="top" align="left"> 55 55 <p>Data file name</p> 56 56 </td></tr><tr><td width="5%" valign="top" align="left"><img src="images/callouts/2.png" alt="2" border="0" /></td><td valign="top" align="left"> … … 69 69 <div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="initmethodtxt" id="initmethodtxt"></a>1.1.2. Grid initialization method</h4></div></div></div> 70 70 <p> 71 For visualising grilled data, you need to <a href="./firststeps.html#load_grid" target="_top">define the grid</a> on which are located the data. By default, "automatic grid construction with initncdf.pro" is checked. This means that the grid will be defined by using the informations contained in the data file (through the IDL prodecure <span><strong class="command">initncdf</strong></span>) without needing any other auxiliary file. If you checked "grid construction with other IDL batch or procedure", this means that you don't want to use the default <span><strong class="command">initncdf</strong></span> procedure to define the grid and you will provide your own IDL procedure or the so-called IDL batch file (a file which is called by using @, see IDL documentation).71 For visualising grilled data, you need to <a href="./firststeps.html#load_grid" target="_top">define the grid</a> on which are located the data. By default, <span class="guibutton">automatic grid construction with initncdf.pro</span> is checked. This means that the grid will be defined by using the informations contained in the data file (through the IDL prodecure <span><strong class="command">initncdf</strong></span>) without needing any other auxiliary file. If you checked <span class="guibutton">grid construction with other IDL batch or procedure</span>, this means that you don't want to use the default <span><strong class="command">initncdf</strong></span> procedure to define the grid and you will provide your own IDL procedure or the so-called IDL batch file (a file which is called by using @, see IDL documentation). 72 72 </p> 73 73 </div> … … 75 75 <p> 76 76 This third part allows you to specify the name, the argument and the keywords of the routine you want to use to initialize the grid. 77 By default the name of the procedure is <span><strong class="command">initncdf</strong></span>, its argument will be automatically defined so you cannot change them. If you If you checked "grid construction with other IDL batch or procedure", you have to select the name of the IDL procedure or batch file and its suitable arguments and keywords. Note that if you select an IDL batch file you cannot give any parameter or keyword.77 By default the name of the procedure is <span><strong class="command">initncdf</strong></span>, its argument will be automatically defined so you cannot change them. If you checked <span class="guibutton">grid construction with other IDL batch or procedure</span>, you have to select the name of the IDL procedure or batch file and its suitable arguments and keywords. Note that if you select an IDL batch file you cannot give any parameter or keyword. 78 78 </p><div class="figure"><a name="fig_xxx_0102" id="fig_xxx_0102"></a><p class="title"><b>Figure 2. Window xxx 1</b></p><div class="figure-contents"> 79 79 … … 84 84 Once these two lines have been completed, click on <span class="guibutton">let's go</span>. 85 85 </p> 86 <p>For example, we choose the IDL batch file "tst_initlev". Compare the result with "automatic grid construction with initncdf.pro"checked. Cf <a href="#fig_xxx_0404" title="Figure 18. temperature of the ocean at depth 125 meters without proper land/sea mask">Figure 18, âtemperature of the ocean at depth 125 meters without proper land/sea maskâ</a>86 <p>For example, we choose the IDL batch file <code class="filename">tst_initlev</code>. Compare the result with <span class="guibutton">automatic grid construction with initncdf.pro</span> checked. Cf <a href="#fig_xxx_0404" title="Figure 18. temperature of the ocean at depth 125 meters without proper land/sea mask">Figure 18, âtemperature of the ocean at depth 125 meters without proper land/sea maskâ</a> 87 87 </p> 88 88 <p> … … 97 97 <div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="launch_xxx_2" id="launch_xxx_2"></a>1.2. <code class="prompt">idl></code> <strong class="userinput"><code><span><strong class="command">xxx</strong></span>, <em class="parameter"><code>/separate</code></em></code></strong></h3></div></div></div> 98 98 <p> 99 This is the same as the simple <a href="#launch_xxx_1" title="1.1. idl> xxx"> <code class="prompt">idl></code> <strong class="userinput"><code><span><strong class="command">xxx</strong></span></code></strong></a> except that once the xxx window open, you will have 2 separate windows (command and plotting window) instead of one.99 This is the same as the simple <a href="#launch_xxx_1" title="1.1. idl> xxx">Section 1.1, â<code class="prompt">idl></code> <strong class="userinput"><code><span><strong class="command">xxx</strong></span></code></strong>â</a> except that once the xxx window open, you will have 2 separate windows (command and plotting window) instead of one. 100 100 </p> 101 101 </div> … … 103 103 <div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="launch_xxx_3" id="launch_xxx_3"></a>1.3. <code class="prompt">idl></code> <strong class="userinput"><code><span><strong class="command">xxx</strong></span>, <em class="parameter"><code>restore = 'file.dat'</code></em></code></strong></h3></div></div></div> 104 104 <p> 105 In that case xxx window will open directly in the same state as it was when the file "file.dat" was created. see <a href="#restore">+++++++</a>105 In that case xxx window will open directly in the same state as it was when the file <code class="filename">file.dat</code> was created. see <a href="#restore">???</a>. 106 106 </p> 107 107 </div> … … 109 109 <div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="launch_xxx_4" id="launch_xxx_4"></a>1.4. <code class="prompt">idl></code> <strong class="userinput"><code><span><strong class="command">xxx</strong></span>, <em class="parameter"><code>'file.nc'</code></em></code></strong></h3></div></div></div> 110 110 <p> 111 In this case, the xxx window directly open the data file 'file.nc'and build the grid automatically with the IDL procedure <span><strong class="command">initncdf</strong></span>. For example:111 In this case, the xxx window directly open the data file <code class="filename">file.nc</code> and build the grid automatically with the IDL procedure <span><strong class="command">initncdf</strong></span>. For example: 112 112 </p><pre class="screen"> 113 113 <code class="prompt">idl></code> <strong class="userinput"><code><span><strong class="command">xxx</strong></span>, <em class="parameter"><code>'Levitus98_1m_01_12_Temperature_Pot_1x1.nc'</code></em></code></strong> … … 118 118 <div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="launch_xxx_5" id="launch_xxx_5"></a>1.5. <code class="prompt">idl></code> <strong class="userinput"><code><span><strong class="command">xxx</strong></span>, <em class="parameter"><code>'file.nc'</code></em>, <em class="parameter"><code>keywd1 = âŠ</code></em>, <em class="parameter"><code>keywd2 = âŠ</code></em></code></strong></h3></div></div></div> 119 119 <p> 120 In this case, the xxx window directly open the data file 'file.nc', build the grid automatically with the IDL procedure <span><strong class="command">initncdf</strong></span> and use the keywords <strong class="userinput"><code><em class="parameter"><code>keywd1 = âŠ</code></em>, <em class="parameter"><code>keywd2 = âŠ</code></em></code></strong> in the call of <span><strong class="command">initncdf</strong></span>. For example:120 In this case, the xxx window directly open the data file <code class="filename">file.nc</code>, build the grid automatically with the IDL procedure <span><strong class="command">initncdf</strong></span> and use the keywords <strong class="userinput"><code><em class="parameter"><code>keywd1 = âŠ</code></em>, <em class="parameter"><code>keywd2 = âŠ</code></em></code></strong> in the call of <span><strong class="command">initncdf</strong></span>. For example: 121 121 </p><pre class="screen"> 122 122 <code class="prompt">idl></code> <strong class="userinput"><code><span><strong class="command">xxx</strong></span>, <em class="parameter"><code>'Levitus98_1m_01_12_Temperature_Pot_1x1.nc'</code></em>, <em class="parameter"><code>useasmask = 'votemper'</code></em>, <em class="parameter"><code>missing_value = 31.0720</code></em></code></strong> … … 127 127 <div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="launch_xxx_6" id="launch_xxx_6"></a>1.6. <code class="prompt">idl></code> <strong class="userinput"><code><span><strong class="command">xxx</strong></span>, <em class="parameter"><code>'file.nc'</code></em>, <em class="parameter"><code>'initgrid'</code></em></code></strong></h3></div></div></div> 128 128 <p> 129 In this case, the xxx window directly open the data file 'file.nc'and build the grid directly with the IDL procedure or batch file <span><strong class="command">initgrid</strong></span>129 In this case, the xxx window directly open the data file <code class="filename">file.nc</code> and build the grid directly with the IDL procedure or batch file <span><strong class="command">initgrid</strong></span> 130 130 </p><pre class="screen"> 131 131 <code class="prompt">idl></code> <strong class="userinput"><code><span><strong class="command">xxx</strong></span>, <em class="parameter"><code>'Levitus98_1m_01_12_Temperature_Pot_ORCA2.nc'</code></em>, <em class="parameter"><code>'tst_initorca2'</code></em></code></strong> … … 136 136 <div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="launch_xxx_7" id="launch_xxx_7"></a>1.7. <code class="prompt">idl></code> <strong class="userinput"><code><span><strong class="command">xxx</strong></span>, <em class="parameter"><code>'file.nc'</code></em>, <em class="parameter"><code>'initgrid'</code></em>, <em class="parameter"><code>keywd1 = âŠ</code></em>, <em class="parameter"><code>keywd2 = âŠ</code></em></code></strong></h3></div></div></div> 137 137 <p> 138 In this case, the xxx window directly open the data file 'file.nc', build the grid directly with the IDL procedure <span><strong class="command">initgrid</strong></span> and use the keywords <strong class="userinput"><code><em class="parameter"><code>keywd1 = âŠ</code></em>, <em class="parameter"><code>keywd2 = âŠ</code></em></code></strong> in the call of <span><strong class="command">initgrid</strong></span>.138 In this case, the xxx window directly open the data file <code class="filename">file.nc</code>, build the grid directly with the IDL procedure <span><strong class="command">initgrid</strong></span> and use the keywords <strong class="userinput"><code><em class="parameter"><code>keywd1 = âŠ</code></em>, <em class="parameter"><code>keywd2 = âŠ</code></em></code></strong> in the call of <span><strong class="command">initgrid</strong></span>. 139 139 </p> 140 140 </div> … … 142 142 <div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="launch_xxx_8" id="launch_xxx_8"></a>1.8. <code class="prompt">idl></code> <strong class="userinput"><code><span><strong class="command">xxx</strong></span>, <em class="parameter"><code>'file.nc'</code></em>, <em class="parameter"><code>'initgrid'</code></em>, <em class="parameter"><code>'arg1, arg2, âŠ'</code></em></code></strong></h3></div></div></div> 143 143 <p> 144 In this case, the xxx window directly open the data file 'file.nc', build the grid directly with the IDL procedure <span><strong class="command">initgrid</strong></span> and use the string <strong class="userinput"><code><em class="parameter"><code>'arg1, arg2, âŠ'</code></em></code></strong> to specify the input arguments in the call of <span><strong class="command">initgrid</strong></span>.144 In this case, the xxx window directly open the data file <code class="filename">file.nc</code>, build the grid directly with the IDL procedure <span><strong class="command">initgrid</strong></span> and use the string <strong class="userinput"><code><em class="parameter"><code>'arg1, arg2, âŠ'</code></em></code></strong> to specify the input arguments in the call of <span><strong class="command">initgrid</strong></span>. 145 145 </p> 146 146 </div> … … 154 154 </p><div class="figure"><a name="fig_xxx_0201" id="fig_xxx_0201"></a><p class="title"><b>Figure 4. Window xxx 2</b></p><div class="figure-contents"> 155 155 156 <div class="mediaobject"><img border="0" usemap="id2573 385" src="figpng/xxx_0201.png" alt="Window xxx 2" /><map name="id2573385" id="id2573385"><area shape="rect" coords="4,346,122,331" /><area shape="rect" coords="136,346,409,330" /><area shape="rect" coords="6,326,55,311" /><area shape="rect" coords="88,326,243,311" /><area shape="rect" coords="263,326,407,311" /><area shape="rect" coords="2,306,433,293" /><area shape="rect" coords="2,288,436,269" /><area shape="rect" coords="2,263,267,237" /><area shape="rect" coords="20,230,388,105" /><area shape="rect" coords="1,98,434,29" /></map><div class="calloutlist"><table border="0" summary="Callout list"><tr><td width="5%" valign="top" align="left"><img src="images/callouts/1.png" alt="1" border="0" /></td><td valign="top" align="left">156 <div class="mediaobject"><img border="0" usemap="id2573460" src="figpng/xxx_0201.png" alt="Window xxx 2" /><map name="id2573460" id="id2573460"><area shape="rect" coords="4,346,122,331" /><area shape="rect" coords="136,346,409,330" /><area shape="rect" coords="6,326,55,311" /><area shape="rect" coords="88,326,243,311" /><area shape="rect" coords="263,326,407,311" /><area shape="rect" coords="2,306,433,293" /><area shape="rect" coords="2,288,436,269" /><area shape="rect" coords="2,263,267,237" /><area shape="rect" coords="20,230,388,105" /><area shape="rect" coords="1,98,434,29" /></map><div class="calloutlist"><table border="0" summary="Callout list"><tr><td width="5%" valign="top" align="left"><img src="images/callouts/1.png" alt="1" border="0" /></td><td valign="top" align="left"> 157 157 <p>Plot type</p> 158 158 </td></tr><tr><td width="5%" valign="top" align="left"><img src="images/callouts/2.png" alt="2" border="0" /></td><td valign="top" align="left"> … … 202 202 </p> 203 203 <p> 204 </p><div class="itemizedlist"><ul type="disc"><li><p><span class="guisubmenu">Open:</span> to open a new file. Same procedure as during the <a href="#launch_xxx_1" title="1.1. idl> xxx"> launch of XXX</a>.204 </p><div class="itemizedlist"><ul type="disc"><li><p><span class="guisubmenu">Open:</span> to open a new file. Same procedure as during the <a href="#launch_xxx_1" title="1.1. idl> xxx">Section 1.1, â<code class="prompt">idl></code> <strong class="userinput"><code><span><strong class="command">xxx</strong></span></code></strong>â</a>. 205 205 The new file can be on a different grid, with different variables, with a different time base ⊠206 206 </p></li><li><p><span class="guisubmenu">New XXX:</span> to open a second XXX window identical to the first one.</p></li><li><p><span class="guisubmenu">Quit:</span> to close the XXX window.</p></li></ul></div><p> … … 232 232 </pre><p> 233 233 will then create a Postscript file of the figure. 234 </p></li><li><p><a name="restore" id="restore"></a><span class="guisubmenu">RESTORE kwd of xxx:</span> to save the xxx widget (all buttons and parameters stored in memory âŠ) in a binary file in order to quit xxx and relaunch it later with <a href="#launch_xxx_3" title="1.3. idl> xxx, restore = 'file.dat'"><code class="prompt">idl></code> <strong class="userinput"><code><span><strong class="command">xxx</strong></span>, <em class="parameter"><code>restore = 'file.dat'</code></em></code></strong></a> and get exactly the same configuration.</p></li><li><p><span class="guisubmenu">Print to prompt:</span> lists in the IDL window the command history that created the last plot. Useful primarily for debuggingâŠ</p></li></ul></div><p> 234 </p></li><li> 235 <p><a name="restore" id="restore"></a><span class="guisubmenu">RESTORE kwd of xxx:</span> to save the xxx widget (all buttons and parameters stored in memory âŠ) in a binary file in order to quit xxx and relaunch it later like in <a href="#launch_xxx_3" title="1.3. idl> xxx, restore = 'file.dat'">Section 1.3, â<code class="prompt">idl></code> <strong class="userinput"><code><span><strong class="command">xxx</strong></span>, <em class="parameter"><code>restore = 'file.dat'</code></em></code></strong>â</a> and get exactly the same configuration. 236 </p> 237 </li><li> 238 <p> 239 <span class="guisubmenu">Print to prompt:</span> lists in the IDL window the command history that created the last plot. Useful primarily for debugging⊠240 </p> 241 </li></ul></div><p> 235 242 </p> 236 243 </div> 237 244 <div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="flagsubmenu" id="flagsubmenu"></a>2.2.3. <span class="guisubmenu">Flag options</span> sub-menu</h4></div></div></div> 238 245 <p> 239 </p><div class="figure"><a name="fig_xxx_0205" id="fig_xxx_0205"></a><p class="title"><b>Figure 8. The Flag Option menu</b></p><div class="figure-contents"> 240 241 <div class="mediaobject"><img src="figpng/xxx_0205.png" alt="The Flag Option menu" /></div> 242 </div></div><p><br class="figure-break" /> 243 </p> 244 <p> 245 </p><div class="itemizedlist"><ul type="disc"><li><p><span class="guisubmenu">Portrait/Landscape:</span> changes the configuration of the plot.</p></li><li><p><span class="guisubmenu">Overlay:</span> to plot contours of a different field on top the 246 one represented as color-filled contours. It is necessary to relaunch the entire plot to make this work!</p></li><li><p><span class="guisubmenu">Vecteur:</span> to plot a vector field on top of contours. Only 247 works on horizontal plots (<code class="filename">plt.pro</code>). 246 </p><div class="figure"><a name="fig_xxx_0205" id="fig_xxx_0205"></a><p class="title"><b>Figure 8. The <span class="guisubmenu">Flag option</span> menu</b></p><div class="figure-contents"> 247 248 <div class="mediaobject"><img src="figpng/xxx_0205.png" alt="The Flag option menu" /></div> 249 </div></div><p><br class="figure-break" /> 250 </p> 251 <p> 252 </p><div class="itemizedlist"><ul type="disc"><li><p><span class="guisubmenu">Portrait/Landscape:</span> changes the configuration of the plot.</p></li><li><p><span class="guisubmenu">Overlay:</span> to plot contours of a different field on top the one represented as color-filled contours. It is necessary to relaunch the entire plot to make this work!</p></li><li><p><span class="guisubmenu">Vecteur:</span> to plot a vector field on top of contours. Only works on horizontal plots (<code class="filename">plt.pro</code>). 248 253 As for Overlay, a relaunch of the entire plot is necessary.</p></li><li><p><span class="guisubmenu">Longitude / x index:</span> switches longitude labeling of the plot sub-domain from degrees to indexes following i.</p></li><li><p><span class="guisubmenu">Latitude / y index:</span> switches latitude labeling of the plot sub-domain from degrees to indexes following j.</p></li></ul></div><p> 249 254 </p> … … 275 280 <p>You can choose the variable to work on.</p> 276 281 <p> 277 </p><div class="figure"><a name="fig_xxx_0207" id="fig_xxx_0207"></a><p class="title"><b>Figure 11. Example of different Variables available</b></p><div class="figure-contents">278 279 <div class="mediaobject"><img src="figpng/xxx_0207.png" alt="Example of different Variables available" /></div>282 </p><div class="figure"><a name="fig_xxx_0207" id="fig_xxx_0207"></a><p class="title"><b>Figure 11. Example of different variables available</b></p><div class="figure-contents"> 283 284 <div class="mediaobject"><img src="figpng/xxx_0207.png" alt="Example of different variables available" /></div> 280 285 </div></div><p><br class="figure-break" /> 281 286 </p> … … 299 304 <div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="commandtext_linear" id="commandtext_linear"></a>2.7.1. Linear calculation</h4></div></div></div> 300 305 <p> 301 If you want to make basic linear computation (like difference between fields, add/multiply by a constant âŠ) . you can simply put the following commands: </p><pre class="screen">a - b</pre><pre class="screen">numb1*a</pre><pre class="screen">a + numb</pre><p> or any command with the following format </p><pre class="screen">numb1*a + numb2*b + numb3*c ⊠+ numb</pre><p> where numb1, numb2, ⊠correspond to numbers and a, b, c ⊠will be the data to read.306 If you want to make basic linear computation (like difference between fields, add/multiply by a constant âŠ), you can simply put the following commands: <code class="literal">a - b</code><code class="literal">numb1*a</code><code class="literal">a + numb</code> or any command with the following format <code class="literal">numb1*a + numb2*b + numb3*c ⊠+ numb</code> where numb1, numb2, ⊠correspond to numbers and a, b, c ⊠will be the data to read. 302 307 </p> 303 308 </div> 304 309 <div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="commandtext_anykind" id="commandtext_anykind"></a>2.7.2. Any kind of computation</h4></div></div></div> 305 310 <p> 306 If you want to make a computation more complicated than a basic linear you must putdesignate the data you want to read between <span><strong class="keycap">"</strong></span><span><strong class="keycap">"</strong></span> (with anything in between the "). For example: </p><pre class="screen">"a"^2</pre><pre class="screen">"a" - abs("b")</pre><pre class="screen">grad("a", 'x')</pre><p> âŠ311 If you want to make a computation more complicated than a basic linear you must designate the data you want to read between <span><strong class="keycap">"</strong></span><span><strong class="keycap">"</strong></span> (with anything in between the "). For example: </p><pre class="screen">"a"^2</pre><pre class="screen">"a" - abs("b")</pre><pre class="screen">grad("a", 'x')</pre><p> ⊠307 312 </p> 308 313 </div> … … 497 502 </p> 498 503 <p> 499 </p><div class="figure"><a name="fig_xxx_0801" id="fig_xxx_0801"></a><p class="title"><b>Figure 33. The referenceframe is selected</b></p><div class="figure-contents">504 </p><div class="figure"><a name="fig_xxx_0801" id="fig_xxx_0801"></a><p class="title"><b>Figure 33. The â<span class="quote">reference</span>â frame is selected</b></p><div class="figure-contents"> 500 505 501 506 <div class="mediaobject"><img src="figpng/xxx_0801.png" alt="The reference frame is selected" /></div> … … 511 516 </p> 512 517 <p> 513 </p><div class="figure"><a name="fig_xxx_0802" id="fig_xxx_0802"></a><p class="title"><b>Figure 35. The targetframe is selected</b></p><div class="figure-contents">518 </p><div class="figure"><a name="fig_xxx_0802" id="fig_xxx_0802"></a><p class="title"><b>Figure 35. The â<span class="quote">target</span>â frame is selected</b></p><div class="figure-contents"> 514 519 515 520 <div class="mediaobject"><img src="figpng/xxx_0802.png" alt="The target frame is selected" /></div> … … 528 533 <div class="procedure"><ol type="1"><li> 529 534 <p> 530 load xxx with the command:535 Load xxx with the command: 531 536 </p><pre class="screen"> 532 537 <code class="prompt">idl></code> <strong class="userinput"><code><span><strong class="command">xxx</strong></span>, <em class="parameter"><code>'Levitus98_1m_01_12_Temperature_Pot_ORCA05.nc'</code></em>, <em class="parameter"><code>'tst_initorca05'</code></em></code></strong> … … 543 548 </li><li> 544 549 <p> 545 <abbr class="abbrev">DCM</abbr> in frame 2, <abbr class="abbrev">LCL</abbr> on the plot in frame 1, to create a horizontal 546 zoom in frame 2.</p> 547 <p> 548 <abbr class="abbrev">DCM</abbr> in frame 3, <abbr class="abbrev">LCM</abbr> on the plot in frame 1, to create a vertical cut 549 in frame 3.</p> 550 <p> 551 <abbr class="abbrev">DCM</abbr> in frame 4, <abbr class="abbrev">LCR</abbr> on the plot in frame 1, to create a hovmoeller in frame 4. 550 <abbr class="abbrev">DCM</abbr> in frame 2, <abbr class="abbrev">LCL</abbr> on the plot in frame 1 to create a horizontal zoom in frame 2.</p> 551 <p> 552 <abbr class="abbrev">DCM</abbr> in frame 3, <abbr class="abbrev">LCM</abbr> on the plot in frame 1 to create a vertical cut in frame 3.</p> 553 <p> 554 <abbr class="abbrev">DCM</abbr> in frame 4, <abbr class="abbrev">LCR</abbr> on the plot in frame 1 to create a hovmoeller in frame 4. 552 555 </p> 553 556 <p> … … 577 580 </li><li> 578 581 <p> 579 click <span class="guibutton">OK</span>, and the plot is redone.582 Click <span class="guibutton">OK</span>, and the plot is redone. 580 583 </p> 581 584 <p> … … 587 590 </li></ol></div> 588 591 <div class="procedure"><p> 589 in frame 5, let's create the same plot as in frame 2 except we use pltv instead of plt592 In frame 5, let's create the same plot as in frame 2 except we use pltv instead of plt 590 593 </p><ol type="1"><li> 591 594 <p> … … 598 601 </li><li> 599 602 <p> 600 change plt for pltv603 Change plt for pltv 601 604 </p> 602 605 </li><li> … … 624 627 </p></li><li> 625 628 <p> 626 in the IDL window, type627 628 <code class="prompt">idl></code> <strong class="userinput"><code>domdef</code></strong>629 In the IDL window, type 630 </p><pre class="screen"> 631 <code class="prompt">idl></code> <strong class="userinput"><code>domdef</code></strong> 629 632 </pre><p> 630 633 </p></li><li> 631 634 <p><abbr class="abbrev">DCR</abbr> to erase the problem frame. 632 635 </p> 633 </li><li><p>change the orientation of the plot by pressing Flag options -> Portrait/Landscape. Cf <a href="#flagsubmenu" title="2.2.3. Flag options sub-menu">Section 2.2.3, â<span class="guisubmenu">Flag options</span> sub-menuâ</a> 634 </p></li><li><p>quit XXX cleanly using <span class="guisubmenu">quit</span> from the <span class="guibutton">File</span> menu. Cf <a href="#filesubmenu" title="2.2.1. File sub-menu">Section 2.2.1, â<span class="guibutton">File</span> sub-menuâ</a> 635 </p></li></ol></div><p> 636 </li><li> 637 <p>change the orientation of the plot by pressing <span class="guisubmenu">Flag options</span> â <span class="guimenuitem">Portrait/Landscape</span>. Cf <a href="#flagsubmenu" title="2.2.3. Flag options sub-menu">Section 2.2.3, â<span class="guisubmenu">Flag options</span> sub-menuâ</a> 638 </p> 639 </li><li> 640 <p>quit XXX cleanly using <span class="guisubmenu">quit</span> from the <span class="guibutton">File</span> menu. Cf <a href="#filesubmenu" title="2.2.1. File sub-menu">Section 2.2.1, â<span class="guibutton">File</span> sub-menuâ</a> 641 </p> 642 </li></ol></div><p> 636 643 </p> 637 644 <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3> … … 643 650 overflow. 644 651 To clean up this memory: 645 646 <code class="prompt">idl></code> <strong class="userinput"><code>ptr_free, ptr_valid()</code></strong>652 </p><pre class="screen"> 653 <code class="prompt">idl></code> <strong class="userinput"><code>ptr_free, ptr_valid()</code></strong> 647 654 </pre><p> 648 655 </p> -
trunk/SRC/Documentation/xmldoc/mini_notice.xml
r351 r356 141 141 <sect3 xml:id="initmethodtxt"><title>Grid initialization method</title> 142 142 <para> 143 For visualising grilled data, you need to <link xl:href="./firststeps.html#load_grid">define the grid</link> on which are located the data. By default, "automatic grid construction with initncdf.pro" is checked. This means that the grid will be defined by using the informations contained in the data file (through the IDL prodecure <command>initncdf</command>) without needing any other auxiliary file. If you checked "grid construction with other IDL batch or procedure", this means that you don't want to use the default <command>initncdf</command> procedure to define the grid and you will provide your own IDL procedure or the so-called IDL batch file (a file which is called by using @, see IDL documentation).143 For visualising grilled data, you need to <link xl:href="./firststeps.html#load_grid">define the grid</link> on which are located the data. By default, <guibutton>automatic grid construction with initncdf.pro</guibutton> is checked. This means that the grid will be defined by using the informations contained in the data file (through the IDL prodecure <command>initncdf</command>) without needing any other auxiliary file. If you checked <guibutton>grid construction with other IDL batch or procedure</guibutton>, this means that you don't want to use the default <command>initncdf</command> procedure to define the grid and you will provide your own IDL procedure or the so-called IDL batch file (a file which is called by using @, see IDL documentation). 144 144 </para> 145 145 </sect3> … … 147 147 <para> 148 148 This third part allows you to specify the name, the argument and the keywords of the routine you want to use to initialize the grid. 149 By default the name of the procedure is <command>initncdf</command>, its argument will be automatically defined so you cannot change them. If you If you checked "grid construction with other IDL batch or procedure", you have to select the name of the IDL procedure or batch file and its suitable arguments and keywords. Note that if you select an IDL batch file you cannot give any parameter or keyword.149 By default the name of the procedure is <command>initncdf</command>, its argument will be automatically defined so you cannot change them. If you checked <guibutton>grid construction with other IDL batch or procedure</guibutton>, you have to select the name of the IDL procedure or batch file and its suitable arguments and keywords. Note that if you select an IDL batch file you cannot give any parameter or keyword. 150 150 <figure xml:id="fig_xxx_0102"> 151 151 <title>Window xxx 1</title> … … 160 160 Once these two lines have been completed, click on <guibutton>let's go</guibutton>. 161 161 </para> 162 <para>For example, we choose the IDL batch file "tst_initlev". Compare the result with "automatic grid construction with initncdf.pro"checked. Cf <xref linkend="fig_xxx_0404"/>162 <para>For example, we choose the IDL batch file <filename>tst_initlev</filename>. Compare the result with <guibutton>automatic grid construction with initncdf.pro</guibutton> checked. Cf <xref linkend="fig_xxx_0404"/> 163 163 </para> 164 164 <para> … … 177 177 <sect2 xml:id="launch_xxx_2"><title><prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>/separate</parameter></userinput></title> 178 178 <para> 179 This is the same as the simple < link linkend="launch_xxx_1"><prompt>&promptidl;</prompt> <userinput><command>xxx</command></userinput></link> except that once the xxx window open, you will have 2 separate windows (command and plotting window) instead of one.179 This is the same as the simple <xref linkend="launch_xxx_1"/> except that once the xxx window open, you will have 2 separate windows (command and plotting window) instead of one. 180 180 </para> 181 181 </sect2> … … 183 183 <sect2 xml:id="launch_xxx_3"><title><prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>restore = 'file.dat'</parameter></userinput></title> 184 184 <para> 185 In that case xxx window will open directly in the same state as it was when the file "file.dat" was created. see <link linkend="restore">+++++++</link>185 In that case xxx window will open directly in the same state as it was when the file <filename>file.dat</filename> was created. see <xref linkend="restore"/>. 186 186 </para> 187 187 </sect2> … … 189 189 <sect2 xml:id="launch_xxx_4"><title><prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>'file.nc'</parameter></userinput></title> 190 190 <para> 191 In this case, the xxx window directly open the data file 'file.nc'and build the grid automatically with the IDL procedure <command>initncdf</command>. For example:191 In this case, the xxx window directly open the data file <filename>file.nc</filename> and build the grid automatically with the IDL procedure <command>initncdf</command>. For example: 192 192 <screen> 193 193 <prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>'Levitus98_1m_01_12_Temperature_Pot_1x1.nc'</parameter></userinput> … … 198 198 <sect2 xml:id="launch_xxx_5"><title><prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>'file.nc'</parameter>, <parameter>keywd1 = …</parameter>, <parameter>keywd2 = …</parameter></userinput></title> 199 199 <para> 200 In this case, the xxx window directly open the data file 'file.nc', build the grid automatically with the IDL procedure <command>initncdf</command> and use the keywords <userinput><parameter>keywd1 = …</parameter>, <parameter>keywd2 = …</parameter></userinput> in the call of <command>initncdf</command>. For example:200 In this case, the xxx window directly open the data file <filename>file.nc</filename>, build the grid automatically with the IDL procedure <command>initncdf</command> and use the keywords <userinput><parameter>keywd1 = …</parameter>, <parameter>keywd2 = …</parameter></userinput> in the call of <command>initncdf</command>. For example: 201 201 <screen> 202 202 <prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>'Levitus98_1m_01_12_Temperature_Pot_1x1.nc'</parameter>, <parameter>useasmask = 'votemper'</parameter>, <parameter>missing_value = 31.0720</parameter></userinput> … … 207 207 <sect2 xml:id="launch_xxx_6"><title><prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>'file.nc'</parameter>, <parameter>'initgrid'</parameter></userinput></title> 208 208 <para> 209 In this case, the xxx window directly open the data file 'file.nc'and build the grid directly with the IDL procedure or batch file <command>initgrid</command>209 In this case, the xxx window directly open the data file <filename>file.nc</filename> and build the grid directly with the IDL procedure or batch file <command>initgrid</command> 210 210 <screen> 211 211 <prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>'Levitus98_1m_01_12_Temperature_Pot_ORCA2.nc'</parameter>, <parameter>'tst_initorca2'</parameter></userinput> … … 216 216 <sect2 xml:id="launch_xxx_7"><title><prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>'file.nc'</parameter>, <parameter>'initgrid'</parameter>, <parameter>keywd1 = …</parameter>, <parameter>keywd2 = …</parameter></userinput></title> 217 217 <para> 218 In this case, the xxx window directly open the data file 'file.nc', build the grid directly with the IDL procedure <command>initgrid</command> and use the keywords <userinput><parameter>keywd1 = …</parameter>, <parameter>keywd2 = …</parameter></userinput> in the call of <command>initgrid</command>.218 In this case, the xxx window directly open the data file <filename>file.nc</filename>, build the grid directly with the IDL procedure <command>initgrid</command> and use the keywords <userinput><parameter>keywd1 = …</parameter>, <parameter>keywd2 = …</parameter></userinput> in the call of <command>initgrid</command>. 219 219 </para> 220 220 </sect2> … … 222 222 <sect2 xml:id="launch_xxx_8"><title><prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>'file.nc'</parameter>, <parameter>'initgrid'</parameter>, <parameter>'arg1, arg2, …'</parameter></userinput></title> 223 223 <para> 224 In this case, the xxx window directly open the data file 'file.nc', build the grid directly with the IDL procedure <command>initgrid</command> and use the string <userinput><parameter>'arg1, arg2, …'</parameter></userinput> to specify the input arguments in the call of <command>initgrid</command>.224 In this case, the xxx window directly open the data file <filename>file.nc</filename>, build the grid directly with the IDL procedure <command>initgrid</command> and use the string <userinput><parameter>'arg1, arg2, …'</parameter></userinput> to specify the input arguments in the call of <command>initgrid</command>. 225 225 </para> 226 226 </sect2> … … 330 330 <para> 331 331 <itemizedlist> 332 <listitem><para><menuchoice><guisubmenu>Open:</guisubmenu></menuchoice> to open a new file. Same procedure as during the < link linkend="launch_xxx_1">launch of XXX</link>.332 <listitem><para><menuchoice><guisubmenu>Open:</guisubmenu></menuchoice> to open a new file. Same procedure as during the <xref linkend="launch_xxx_1"/>. 333 333 The new file can be on a different grid, with different variables, with a different time base … 334 334 </para></listitem> … … 372 372 will then create a Postscript file of the figure. 373 373 </para></listitem> 374 <listitem><para xml:id='restore'><menuchoice><guisubmenu>RESTORE kwd of xxx:</guisubmenu></menuchoice> to save the xxx widget (all buttons and parameters stored in memory …) in a binary file in order to quit xxx and relaunch it later with <link linkend="launch_xxx_3"><prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>restore = 'file.dat'</parameter></userinput></link> and get exactly the same configuration.</para></listitem> 375 <listitem><para><menuchoice><guisubmenu>Print to prompt:</guisubmenu></menuchoice> lists in the IDL window the command history that created the last plot. Useful primarily for debugging…</para></listitem> 374 <listitem> 375 <para xml:id="restore"><menuchoice><guisubmenu>RESTORE kwd of xxx:</guisubmenu></menuchoice> to save the xxx widget (all buttons and parameters stored in memory …) in a binary file in order to quit xxx and relaunch it later like in <xref linkend="launch_xxx_3"/> and get exactly the same configuration. 376 </para> 377 </listitem> 378 <listitem> 379 <para> 380 <menuchoice><guisubmenu>Print to prompt:</guisubmenu></menuchoice> lists in the IDL window the command history that created the last plot. Useful primarily for debugging… 381 </para> 382 </listitem> 376 383 </itemizedlist> 377 384 </para> … … 380 387 <para> 381 388 <figure xml:id="fig_xxx_0205"> 382 <title>The Flag Optionmenu</title>389 <title>The <guisubmenu>Flag option</guisubmenu> menu</title> 383 390 <mediaobject> 384 391 <imageobject> … … 391 398 <itemizedlist> 392 399 <listitem><para><guisubmenu>Portrait/Landscape:</guisubmenu> changes the configuration of the plot.</para></listitem> 393 <listitem><para><guisubmenu>Overlay:</guisubmenu> to plot contours of a different field on top the 394 one represented as color-filled contours. It is necessary to relaunch the entire plot to make this work!</para></listitem> 395 <listitem><para><guisubmenu>Vecteur:</guisubmenu> to plot a vector field on top of contours. Only 396 works on horizontal plots (<filename>plt.pro</filename>). 400 <listitem><para><guisubmenu>Overlay:</guisubmenu> to plot contours of a different field on top the one represented as color-filled contours. It is necessary to relaunch the entire plot to make this work!</para></listitem> 401 <listitem><para><guisubmenu>Vecteur:</guisubmenu> to plot a vector field on top of contours. Only works on horizontal plots (<filename>plt.pro</filename>). 397 402 As for Overlay, a relaunch of the entire plot is necessary.</para></listitem> 398 403 <listitem><para><guisubmenu>Longitude / x index:</guisubmenu> switches longitude labeling of the plot sub-domain from degrees to indexes following i.</para></listitem> … … 436 441 <para> 437 442 <figure xml:id="fig_xxx_0207"> 438 <title>Example of different Variables available</title>443 <title>Example of different variables available</title> 439 444 <mediaobject> 440 445 <imageobject> … … 467 472 <sect3 xml:id="commandtext_linear"><title>Linear calculation</title> 468 473 <para> 469 If you want to make basic linear computation (like difference between fields, add/multiply by a constant …) . you can simply put the following commands: <screen>a - b</screen><screen>numb1*a</screen><screen>a + numb</screen> or any command with the following format <screen>numb1*a + numb2*b + numb3*c … + numb</screen> where numb1, numb2, … correspond to numbers and a, b, c … will be the data to read.474 If you want to make basic linear computation (like difference between fields, add/multiply by a constant …), you can simply put the following commands: <literal>a - b</literal><literal>numb1*a</literal><literal>a + numb</literal> or any command with the following format <literal>numb1*a + numb2*b + numb3*c … + numb</literal> where numb1, numb2, … correspond to numbers and a, b, c … will be the data to read. 470 475 </para> 471 476 </sect3> 472 477 <sect3 xml:id="commandtext_anykind"><title>Any kind of computation</title> 473 478 <para> 474 If you want to make a computation more complicated than a basic linear you must putdesignate the data you want to read between <keycap>"</keycap><keycap>"</keycap> (with anything in between the "). For example: <screen>"a"^2</screen><screen>"a" - abs("b")</screen><screen>grad("a", 'x')</screen> …479 If you want to make a computation more complicated than a basic linear you must designate the data you want to read between <keycap>"</keycap><keycap>"</keycap> (with anything in between the "). For example: <screen>"a"^2</screen><screen>"a" - abs("b")</screen><screen>grad("a", 'x')</screen> … 475 480 </para> 476 481 </sect3> … … 755 760 <para> 756 761 <figure xml:id="fig_xxx_0801"> 757 <title>The referenceframe is selected</title>762 <title>The <quote>reference</quote> frame is selected</title> 758 763 <mediaobject> 759 764 <imageobject> … … 778 783 <para> 779 784 <figure xml:id="fig_xxx_0802"> 780 <title>The targetframe is selected</title>785 <title>The <quote>target</quote> frame is selected</title> 781 786 <mediaobject> 782 787 <imageobject> … … 805 810 <step> 806 811 <para> 807 load xxx with the command:812 Load xxx with the command: 808 813 <screen> 809 814 <prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>'Levitus98_1m_01_12_Temperature_Pot_ORCA05.nc'</parameter>, <parameter>'tst_initorca05'</parameter></userinput> … … 824 829 <step> 825 830 <para> 826 <abbrev>DCM</abbrev> in frame 2, <abbrev>LCL</abbrev> on the plot in frame 1, to create a horizontal 827 zoom in frame 2.</para> 828 <para> 829 <abbrev>DCM</abbrev> in frame 3, <abbrev>LCM</abbrev> on the plot in frame 1, to create a vertical cut 830 in frame 3.</para> 831 <para> 832 <abbrev>DCM</abbrev> in frame 4, <abbrev>LCR</abbrev> on the plot in frame 1, to create a hovmoeller in frame 4. 831 <abbrev>DCM</abbrev> in frame 2, <abbrev>LCL</abbrev> on the plot in frame 1 to create a horizontal zoom in frame 2.</para> 832 <para> 833 <abbrev>DCM</abbrev> in frame 3, <abbrev>LCM</abbrev> on the plot in frame 1 to create a vertical cut in frame 3.</para> 834 <para> 835 <abbrev>DCM</abbrev> in frame 4, <abbrev>LCR</abbrev> on the plot in frame 1 to create a hovmoeller in frame 4. 833 836 </para> 834 837 <para> … … 871 874 <step> 872 875 <para> 873 click <guibutton>OK</guibutton>, and the plot is redone.876 Click <guibutton>OK</guibutton>, and the plot is redone. 874 877 </para> 875 878 <para> … … 887 890 <procedure> 888 891 <para> 889 in frame 5, let's create the same plot as in frame 2 except we use pltv instead of plt892 In frame 5, let's create the same plot as in frame 2 except we use pltv instead of plt 890 893 </para> 891 894 <step> … … 901 904 <step> 902 905 <para> 903 change plt for pltv906 Change plt for pltv 904 907 </para> 905 908 </step> … … 935 938 <listitem> 936 939 <para> 937 in the IDL window, type938 939 <prompt>&promptidl;</prompt> <userinput>domdef</userinput>940 In the IDL window, type 941 <screen> 942 <prompt>&promptidl;</prompt> <userinput>domdef</userinput> 940 943 </screen> 941 944 </para></listitem> … … 944 947 </para> 945 948 </listitem> 946 <listitem><para>change the orientation of the plot by pressing Flag options -> Portrait/Landscape. Cf <xref linkend="flagsubmenu"/> 947 </para></listitem> 948 <listitem><para>quit XXX cleanly using <guisubmenu>quit</guisubmenu> from the <guibutton>File</guibutton> menu. Cf <xref linkend="filesubmenu"/> 949 </para></listitem> 949 <listitem> 950 <para>change the orientation of the plot by pressing <menuchoice><guisubmenu>Flag options</guisubmenu> <guimenuitem>Portrait/Landscape</guimenuitem></menuchoice>. Cf <xref linkend="flagsubmenu"/> 951 </para> 952 </listitem> 953 <listitem> 954 <para>quit XXX cleanly using <guisubmenu>quit</guisubmenu> from the <guibutton>File</guibutton> menu. Cf <xref linkend="filesubmenu"/> 955 </para> 956 </listitem> 950 957 </orderedlist> 951 958 </para> … … 958 965 overflow. 959 966 To clean up this memory: 960 961 <prompt>&promptidl;</prompt> <userinput>ptr_free, ptr_valid()</userinput>967 <screen> 968 <prompt>&promptidl;</prompt> <userinput>ptr_free, ptr_valid()</userinput> 962 969 </screen> 963 970 </para> -
trunk/SRC/Documentation/xmldoc/saxo_tracwiki.xsl
r355 r356 64 64 <xsl:template match="d:sect2/d:title"> 65 65 <xsl:text>
</xsl:text> 66 <xsl:text>=== </xsl:text><xsl:value-of select="normalize-space(.)"/><xsl:text> ===</xsl:text> 66 <xsl:variable name="newtitle"> 67 <xsl:call-template name="replace-string"> 68 <xsl:with-param name="text" select="normalize-space(.)"/> 69 <xsl:with-param name="replace" select="'>'"/> 70 <!-- do not how to write > instead of > ++. need sed features --> 71 <xsl:with-param name="with" select="'>'"/> 72 </xsl:call-template> 73 </xsl:variable> 74 <xsl:text>=== </xsl:text><xsl:value-of select="$newtitle"/><xsl:text> ===</xsl:text> 67 75 <xsl:text>
</xsl:text> 68 76 </xsl:template> … … 118 126 <xsl:text>{{{</xsl:text><xsl:apply-templates/><xsl:text>}}}</xsl:text> 119 127 </xsl:template> 128 <xsl:template match="d:literal"> 129 <xsl:text>{{{</xsl:text><xsl:apply-templates/><xsl:text>}}}</xsl:text> 130 </xsl:template> 120 131 121 132 <xsl:template match="d:screen"> 122 133 <!-- 123 we open an HTML block because it is not possible to have font effect (bold, italic) 124 using TracWiki 134 we open an HTML block because it is not possible to have font effect (bold, italic) using TracWiki 125 135 --> 126 136 <xsl:text>
</xsl:text> … … 238 248 <xsl:text>wiki:WikiStart</xsl:text> 239 249 </xsl:when> 240 <xsl:when test="contains(@xl:href,'../../ Tests/')">241 <xsl:text>source:/trunk/SRC/ Tests/</xsl:text><xsl:value-of select="substring-after(@xl:href,'../../Tests/')"/>250 <xsl:when test="contains(@xl:href,'../../')"> 251 <xsl:text>source:/trunk/SRC/</xsl:text><xsl:value-of select="substring-after(@xl:href,'../../')"/> 242 252 </xsl:when> 243 253 <xsl:when test="contains(@xl:href,'idldoc_html_output')"> … … 278 288 </xsl:template> 279 289 290 <xsl:template match="d:caution"> 291 <xsl:text>
</xsl:text> 292 <xsl:text>
</xsl:text> 293 <xsl:text>'''Caution'''</xsl:text> 294 <xsl:text>
</xsl:text> 295 <xsl:text>
</xsl:text> 296 <xsl:apply-templates/> 297 </xsl:template> 298 299 <xsl:template match="d:note"> 300 <xsl:text>
</xsl:text> 301 <xsl:text>
</xsl:text> 302 <xsl:text>'''Note'''</xsl:text> 303 <xsl:text>
</xsl:text> 304 <xsl:text>
</xsl:text> 305 <xsl:apply-templates/> 306 </xsl:template> 280 307 281 308 <xsl:template match="d:replaceable"> … … 327 354 </xsl:template> 328 355 356 <xsl:template match="d:link[@linkend]"> 357 <xsl:variable name="target" select="key('id',@linkend)[1]"/> 358 <xsl:text>[#</xsl:text><xsl:value-of select="translate(normalize-space(//*[normalize-space(@xml:id='$target')]/d:title),' ','')"/><xsl:text>]</xsl:text> 359 </xsl:template> 360 329 361 <xsl:template match="d:xref"> 330 362 <xsl:variable name="target" select="key('id',@linkend)[1]"/> 331 363 <xsl:text>[#</xsl:text><xsl:value-of select="translate(normalize-space(//d:sect1[normalize-space(@xml:id='$target')]/d:title),' ','')"/><xsl:text> </xsl:text> <xsl:value-of select="normalize-space(//d:sect1[normalize-space(@xml:id='$target')]/d:title)"/><xsl:text>]</xsl:text> 332 364 </xsl:template> 365 366 <xsl:template match="d:callout"> 367 <xsl:text>[[Image(source:/trunk/SRC/Documentation/xmldoc/images/callouts/</xsl:text><xsl:value-of select="position() div 2"/><xsl:text>.png)]]</xsl:text><xsl:apply-templates/> 368 </xsl:template> 369 370 <xsl:template name="replace-string"> 371 <!-- from http://www.dpawson.co.uk/xsl/sect2/replace.html --> 372 <xsl:param name="text"/> 373 <xsl:param name="replace"/> 374 <xsl:param name="with"/> 375 <xsl:choose> 376 <xsl:when test="contains($text,$replace)"> 377 <xsl:value-of select="substring-before($text,$replace)"/> 378 <xsl:value-of select="$with"/> 379 <xsl:call-template name="replace-string"> 380 <xsl:with-param name="text" 381 select="substring-after($text,$replace)"/> 382 <xsl:with-param name="replace" select="$replace"/> 383 <xsl:with-param name="with" select="$with"/> 384 </xsl:call-template> 385 </xsl:when> 386 <xsl:otherwise> 387 <xsl:value-of select="$text"/> 388 </xsl:otherwise> 389 </xsl:choose> 390 </xsl:template> 333 391 334 392 <!-- do not reproduce the followings elements --> -
trunk/SRC/Documentation/xmldoc/wiki/FaqSaxo
r355 r356 182 182 Yes, there are some : 183 183 184 * \in {{{*.pro}}} are not written184 * {{{\}}} in {{{*.pro}}} are not written 185 185 in {{{*.html}}}. 186 They must be escaped by an other \or you can choose an other character.187 188 * Search doesn't handle characters like -189 and |.186 They must be escaped by an other {{{\}}} or you can choose an other character. 187 188 * Search doesn't handle characters like {{{-}}} 189 and {{{|}}}. 190 190 191 191 * Paragraphs of {{{*.pro}}} headers are shown with a proportional 192 font in the HTMLrelease.192 font in the {{{HTML}}} release. 193 193 194 194 If you need to draw some small figure like grid cell, you can encapsulate 195 195 the block to be shown in constant font 196 196 between 197 ; <fixe>and198 ; </fixe> 197 {{{; <fixe>}}} and 198 {{{; </fixe>}}} 199 199 200 200 Unfortunately, these troubles may not be fixed because the author does not -
trunk/SRC/Documentation/xmldoc/wiki/FirstSteps
r355 r356 95 95 96 96 97 97 [[Image(source:/trunk/SRC/Documentation/xmldoc/images/callouts/1.png)]] 98 98 {{{findgen}}} stands for '''f'''loat '''ind'''ex '''gen'''erator. 99 99 … … 151 151 152 152 153 153 [[Image(source:/trunk/SRC/Documentation/xmldoc/images/callouts/1.png)]] 154 154 155 155 If needed, the name of the postscript will automatically be completed with .ps. Just hit return, if you want to use the default postscript name: {{{idl.ps}}}. … … 231 231 232 232 233 233 [[Image(source:/trunk/SRC/Documentation/xmldoc/images/callouts/1.png)]] 234 234 235 235 the small keyword is a 3 elements vector which defines how we divide the page and in which case we should make the plot: [number of columns, number of rows, case number]. The case numbering is starting at 1, from top to bottom and left to right. 236 236 237 237 238 238 [[Image(source:/trunk/SRC/Documentation/xmldoc/images/callouts/2.png)]] 239 239 240 240 you must put /noerase otherwise the second plot will be done in a new window. … … 257 257 </pre> 258 258 }}} 259 {{{scontour}}} accepts the same keywords as {{{contour}}} (C_ANNOTATION=vector_of_strings, C_CHARSIZE=value, C_CHARTHICK=integer, C_COLORS=vector, C_LABELS=vector{each element 0 or 1}, C_LINESTYLE=vector, { /FILL | /CELL_FILL | C_ORIENTATION=degrees}, C_SPACING=value, C_THICK=vector, /CLOSED, /DOWNHILL, /FOLLOW, /IRREGULAR, /ISOTROPIC, LEVELS=vector, NLEVELS=integer{1 to 60}, MAX_VALUE=value, MIN_VALUE=value, /OVERPLOT, {/PATH_DATA_COORDS, PATH_FILENAME=string, PATH_INFO=variable, PATH_XY=variable}, TRIANGULATION=variable, /PATH_DOUBLE, /XLOG, /YLOG, ZAXIS={0 | 1 | 2 | 3 | 4}), including the graphics keywords(except LINESTYLE, PSYM, SYMSIZE).259 {{{scontour}}} accepts the same keywords as {{{contour}}} (C_ANNOTATION=vector_of_strings, C_CHARSIZE=value, C_CHARTHICK=integer, C_COLORS=vector, C_LABELS=vector{each element 0 or 1}, C_LINESTYLE=vector, { /FILL | /CELL_FILL | C_ORIENTATION=degrees}, C_SPACING=value, C_THICK=vector, /CLOSED, /DOWNHILL, /FOLLOW, /IRREGULAR, /ISOTROPIC, LEVELS=vector, NLEVELS=integer{1 to 60}, MAX_VALUE=value, MIN_VALUE=value, /OVERPLOT, {/PATH_DATA_COORDS, PATH_FILENAME=string, PATH_INFO=variable, PATH_XY=variable}, TRIANGULATION=variable, /PATH_DOUBLE, /XLOG, /YLOG, ZAXIS={0 | 1 | 2 | 3 | 4}), including the [#FirststepswithSAXO] (except LINESTYLE, PSYM, SYMSIZE). 260 260 It can therefore be customized ''as much as you want''. See these short examples: 261 261 {{{ … … 284 284 285 285 286 286 [[Image(source:/trunk/SRC/Documentation/xmldoc/images/callouts/1.png)]] 287 287 {{{rebin}}} is used to build an array containing an alternation of 1 and 0 in order to label one contour every two contours. 288 288 … … 340 340 </pre> 341 341 }}} 342 343 344 '''Note''' 345 342 346 New Feature 343 347 … … 353 357 354 358 ==== Formal quick look at 2D arrays: pltv ==== 355 {{{pltv}}} is a mix between tvplus and pltand allow you to have formal quick look of 2D arrays.359 {{{pltv}}} is a mix between [#FirststepswithSAXO] and [#FirststepswithSAXO] and allow you to have formal quick look of 2D arrays. 356 360 357 361 {{{ … … 451 455 ==== Load the grid from OPA meshmask file ==== 452 456 453 When the grid is really irregular (its abscissa and ordinate cannot be descried by a vector), loading the grid directly from the data forces us to make an approximation when computing the grid corners position and the cells size. In that case, it can be preferable to load the grid from the meshmask file created by OPA. As OPA use a Arakawa-C discretization, loading the grid from the meshmask will also define all parameters related to the U, V and F grids (glam[uv],gphi[uv], e[12][uvf]). Note that, when using a simple grid definition from the data itself(with {{{initncdf}}} or {{{computegrid}}}), adding the keyword /FULLCGRID leads also to the definition of all U, V and F grids parameters. There is the examples to load ORCA grids from OPA meshmask.457 When the grid is really irregular (its abscissa and ordinate cannot be descried by a vector), loading the grid directly from the data forces us to make an approximation when computing the grid corners position and the cells size. In that case, it can be preferable to load the grid from the meshmask file created by OPA. As OPA use a Arakawa-C discretization, loading the grid from the meshmask will also define all parameters related to the U, V and F grids (glam[uv],gphi[uv], e[12][uvf]). Note that, when using a simple [#FirststepswithSAXO] (with {{{initncdf}}} or {{{computegrid}}}), adding the keyword /FULLCGRID leads also to the definition of all U, V and F grids parameters. There is the examples to load ORCA grids from OPA meshmask. 454 458 455 459 * [source:/trunk/SRC/Tests/tst_initorca2.pro @tst_initorca2] : ORCA2 … … 463 467 === Horizontal plots and maps === 464 468 465 A quick presentation of horizontal plots and maps is shown in [source:/trunk/SRC/Tests/tst_plt.pro tst_plt]. After loading any of the grid (for example with one of the above examples). Just try:469 A quick presentation of horizontal plots and maps is shown in [source:/trunk/SRC/Tests/tst_plt.pro tst_plt]. After loading any of the grid (for example with one of the [#FirststepswithSAXO]). Just try: 466 470 467 471 {{{ … … 482 486 === Vertical sections === 483 487 484 A quick presentation of vertical sections is shown in [source:/trunk/SRC/Tests/tst_pltz.pro tst_pltz]. After loading any of the grid (for example with one of the above examples). Just try:488 A quick presentation of vertical sections is shown in [source:/trunk/SRC/Tests/tst_pltz.pro tst_pltz]. After loading any of the grid (for example with one of the [#FirststepswithSAXO]). Just try: 485 489 486 490 {{{ … … 501 505 === Hovmoellers and time series === 502 506 503 A quick presentation of hovmoellers and time series is shown in [source:/trunk/SRC/Tests/tst_pltt.pro tst_pltt]. After loading any of the grid (for example with one of the above examples). Just try:507 A quick presentation of hovmoellers and time series is shown in [source:/trunk/SRC/Tests/tst_pltt.pro tst_pltt]. After loading any of the grid (for example with one of the [#FirststepswithSAXO]). Just try: 504 508 505 509 {{{ -
trunk/SRC/Documentation/xmldoc/wiki/MiniNotice
r355 r356 25 25 }}} 26 26 27 === idl >xxx ===27 === idl> xxx === 28 28 29 29 A window will open with 3 parts to consider. … … 41 41 42 42 43 43 [[Image(source:/trunk/SRC/Documentation/xmldoc/images/callouts/1.png)]] 44 44 Data file name 45 45 46 46 [[Image(source:/trunk/SRC/Documentation/xmldoc/images/callouts/2.png)]] 47 47 Grid initialization method 48 48 49 49 [[Image(source:/trunk/SRC/Documentation/xmldoc/images/callouts/3.png)]] 50 50 Grid initialization parameters 51 51 … … 61 61 ==== Grid initialization method ==== 62 62 63 For visualising grilled data, you need to [wiki:FirstSteps define the grid] on which are located the data. By default, "automatic grid construction with initncdf.pro" is checked. This means that the grid will be defined by using the informations contained in the data file (through the IDL prodecure {{{initncdf}}}) without needing any other auxiliary file. If you checked "grid construction with other IDL batch or procedure", this means that you don't want to use the default {{{initncdf}}} procedure to define the grid and you will provide your own IDL procedure or the so-called IDL batch file (a file which is called by using @, see IDL documentation).63 For visualising grilled data, you need to [wiki:FirstSteps define the grid] on which are located the data. By default, automatic grid construction with initncdf.pro is checked. This means that the grid will be defined by using the informations contained in the data file (through the IDL prodecure {{{initncdf}}}) without needing any other auxiliary file. If you checked grid construction with other IDL batch or procedure, this means that you don't want to use the default {{{initncdf}}} procedure to define the grid and you will provide your own IDL procedure or the so-called IDL batch file (a file which is called by using @, see IDL documentation). 64 64 65 65 ==== Grid initialization parameters ==== 66 66 67 67 This third part allows you to specify the name, the argument and the keywords of the routine you want to use to initialize the grid. 68 By default the name of the procedure is {{{initncdf}}}, its argument will be automatically defined so you cannot change them. If you If you checked "grid construction with other IDL batch or procedure", you have to select the name of the IDL procedure or batch file and its suitable arguments and keywords. Note that if you select an IDL batch file you cannot give any parameter or keyword.68 By default the name of the procedure is {{{initncdf}}}, its argument will be automatically defined so you cannot change them. If you checked grid construction with other IDL batch or procedure, you have to select the name of the IDL procedure or batch file and its suitable arguments and keywords. Note that if you select an IDL batch file you cannot give any parameter or keyword. 69 69 70 70 Window xxx 1 … … 76 76 77 77 Once these two lines have been completed, click on let's go. 78 For example, we choose the IDL batch file "tst_initlev". Compare the result with "automatic grid construction with initncdf.pro"checked. Cf [#LaunchingXXX Launching XXX]78 For example, we choose the IDL batch file {{{tst_initlev}}}. Compare the result with automatic grid construction with initncdf.pro checked. Cf [#LaunchingXXX Launching XXX] 79 79 Oceania at 125 meters of depth with proper grid initialization 80 80 … … 84 84 85 85 86 === idl> xxx, /separate === 87 88 This is the same as the simple idl> xxx except that once the xxx window open, you will have 2 separate windows (command and plotting window) instead of one. 89 90 === idl> xxx, restore = 'file.dat' === 91 92 In that case xxx window will open directly in the same state as it was when the file "file.dat" was created. see +++++++ 93 === idl> xxx, 'file.nc' === 94 95 In this case, the xxx window directly open the data file 'file.nc' and build the grid automatically with the IDL procedure {{{initncdf}}}. For example: 86 === idl> xxx, /separate === 87 88 This is the same as the simple [#LaunchingXXX Launching XXX] except that once the xxx window open, you will have 2 separate windows (command and plotting window) instead of one. 89 90 === idl> xxx, restore = 'file.dat' === 91 92 In that case xxx window will open directly in the same state as it was when the file {{{file.dat}}} was created. see [#LaunchingXXX Launching XXX]. 93 94 === idl> xxx, 'file.nc' === 95 96 In this case, the xxx window directly open the data file {{{file.nc}}} and build the grid automatically with the IDL procedure {{{initncdf}}}. For example: 96 97 97 98 {{{ … … 102 103 }}} 103 104 104 === idl >xxx, 'file.nc', keywd1 = âŠ, keywd2 = ⊠===105 106 In this case, the xxx window directly open the data file 'file.nc', build the grid automatically with the IDL procedure {{{initncdf}}} and use the keywords keywd1 = âŠ, keywd2 = ⊠in the call of {{{initncdf}}}. For example:105 === idl> xxx, 'file.nc', keywd1 = âŠ, keywd2 = ⊠=== 106 107 In this case, the xxx window directly open the data file {{{file.nc}}}, build the grid automatically with the IDL procedure {{{initncdf}}} and use the keywords keywd1 = âŠ, keywd2 = ⊠in the call of {{{initncdf}}}. For example: 107 108 108 109 {{{ … … 113 114 }}} 114 115 115 === idl >xxx, 'file.nc', 'initgrid' ===116 117 In this case, the xxx window directly open the data file 'file.nc'and build the grid directly with the IDL procedure or batch file {{{initgrid}}}116 === idl> xxx, 'file.nc', 'initgrid' === 117 118 In this case, the xxx window directly open the data file {{{file.nc}}} and build the grid directly with the IDL procedure or batch file {{{initgrid}}} 118 119 {{{ 119 120 #!html … … 123 124 }}} 124 125 125 === idl >xxx, 'file.nc', 'initgrid', keywd1 = âŠ, keywd2 = ⊠===126 127 In this case, the xxx window directly open the data file 'file.nc', build the grid directly with the IDL procedure {{{initgrid}}} and use the keywords keywd1 = âŠ, keywd2 = ⊠in the call of {{{initgrid}}}.128 129 === idl >xxx, 'file.nc', 'initgrid', 'arg1, arg2, âŠ' ===130 131 In this case, the xxx window directly open the data file 'file.nc', build the grid directly with the IDL procedure {{{initgrid}}} and use the string 'arg1, arg2, âŠ' to specify the input arguments in the call of {{{initgrid}}}.126 === idl> xxx, 'file.nc', 'initgrid', keywd1 = âŠ, keywd2 = ⊠=== 127 128 In this case, the xxx window directly open the data file {{{file.nc}}}, build the grid directly with the IDL procedure {{{initgrid}}} and use the keywords keywd1 = âŠ, keywd2 = ⊠in the call of {{{initgrid}}}. 129 130 === idl> xxx, 'file.nc', 'initgrid', 'arg1, arg2, âŠ' === 131 132 In this case, the xxx window directly open the data file {{{file.nc}}}, build the grid directly with the IDL procedure {{{initgrid}}} and use the string 'arg1, arg2, âŠ' to specify the input arguments in the call of {{{initgrid}}}. 132 133 133 134 == Description of XXX window == … … 152 153 153 154 154 155 [[Image(source:/trunk/SRC/Documentation/xmldoc/images/callouts/1.png)]] 155 156 Plot type 156 157 157 158 [[Image(source:/trunk/SRC/Documentation/xmldoc/images/callouts/2.png)]] 158 159 Menu 159 160 160 161 [[Image(source:/trunk/SRC/Documentation/xmldoc/images/callouts/3.png)]] 161 162 OK 162 163 163 164 [[Image(source:/trunk/SRC/Documentation/xmldoc/images/callouts/4.png)]] 164 165 Page layout 165 166 166 167 [[Image(source:/trunk/SRC/Documentation/xmldoc/images/callouts/5.png)]] 167 168 Variables list 168 169 169 170 [[Image(source:/trunk/SRC/Documentation/xmldoc/images/callouts/6.png)]] 170 171 Files list 171 172 172 173 [[Image(source:/trunk/SRC/Documentation/xmldoc/images/callouts/7.png)]] 173 174 Command text 174 175 175 176 [[Image(source:/trunk/SRC/Documentation/xmldoc/images/callouts/8.png)]] 176 177 Calendar 177 178 178 179 [[Image(source:/trunk/SRC/Documentation/xmldoc/images/callouts/9.png)]] 179 180 Domdef 180 181 181 182 [[Image(source:/trunk/SRC/Documentation/xmldoc/images/callouts/10.png)]] 182 183 Spefications 183 184 … … 197 198 198 199 200 '''Note''' 201 202 203 199 204 If the type plt is selected, the selection of plot type 200 205 is made by mouse. Cf [#LaunchingXXX Launching XXX] … … 211 216 212 217 213 * Open: to open a new file. Same procedure as during the launch of XXX.218 * Open: to open a new file. Same procedure as during the [#LaunchingXXX Launching XXX]. 214 219 The new file can be on a different grid, with different variables, with a different time base ⊠215 220 … … 227 232 * Postscript: to save the plotting window in Postscript format 228 233 * Animated gif: to create an animation of the plotting window. 229 The creation of an animation is only possible if none of the plots have a time axis, and if the plots are all on the same time base (calendar). On the other hand, animations of horizontal and vertical plots, with different color palettes (for those not on an X-terminal), are possible.The creation of animations has a tendency to saturate the video memory of X-terminals, crashing the entire program ⊠234 235 236 '''Note''' 237 238 The creation of an animation is only possible if none of the plots have a time axis, and if the plots are all on the same time base (calendar). On the other hand, animations of horizontal and vertical plots, with different color palettes (for those not on an X-terminal), are possible. 239 240 '''Note''' 241 242 The creation of animations has a tendency to saturate the video memory of X-terminals, crashing the entire program ⊠230 243 * Gif: to save a gif of the plotting window. 231 244 * IDL procedure: to save the command history that has created the plot in an IDL procedure that can be re-executed later. For example if I save the commands in {{{xxx_figure.pro}}} file, when ever I want, I can then launch a new IDL session and type: … … 259 272 will then create a Postscript file of the figure. 260 273 261 * RESTORE kwd of xxx: to save the xxx widget (all buttons and parameters stored in memory âŠ) in a binary file in order to quit xxx and relaunch it later with idl> xxx, restore = 'file.dat' and get exactly the same configuration. 274 * RESTORE kwd of xxx: to save the xxx widget (all buttons and parameters stored in memory âŠ) in a binary file in order to quit xxx and relaunch it later like in [#LaunchingXXX Launching XXX] and get exactly the same configuration. 275 262 276 * Print to prompt: lists in the IDL window the command history that created the last plot. Useful primarily for debugging⊠277 263 278 ==== Flag options sub-menu ==== 264 279 265 The Flag Option menu280 The Flag option menu 266 281 267 282 … … 271 286 272 287 * Portrait/Landscape: changes the configuration of the plot. 273 * Overlay: to plot contours of a different field on top the 274 one represented as color-filled contours. It is necessary to relaunch the entire plot to make this work! 275 * Vecteur: to plot a vector field on top of contours. Only 276 works on horizontal plots ({{{plt.pro}}}). 288 * Overlay: to plot contours of a different field on top the one represented as color-filled contours. It is necessary to relaunch the entire plot to make this work! 289 * Vecteur: to plot a vector field on top of contours. Only works on horizontal plots ({{{plt.pro}}}). 277 290 As for Overlay, a relaunch of the entire plot is necessary. 278 291 * Longitude / x index: switches longitude labeling of the plot sub-domain from degrees to indexes following i. 279 * Latitude / y index: switches latitude labeling of the plot sub-domain from degrees to indexes following j.Careful, a selected option remains selected until it is re-clicked. 292 * Latitude / y index: switches latitude labeling of the plot sub-domain from degrees to indexes following j. 293 294 '''Caution''' 295 296 Careful, a selected option remains selected until it is re-clicked. 280 297 === OK button === 281 298 Click on this OK button is required to make a new plot appear … … 298 315 === List of variables === 299 316 You can choose the variable to work on. 300 Example of different Variables available317 Example of different variables available 301 318 302 319 … … 317 334 318 335 To specify in the widget part number 7 the computation you want to do on the data 336 337 338 '''Note''' 339 319 340 In all cases bellow, the name given to a field (a, b, c, âŠ) is of no importance. 320 341 ==== Linear calculation ==== 321 342 322 If you want to make basic linear computation (like difference between fields, add/multiply by a constant âŠ). you can simply put the following commands: 323 {{{ 324 #!html 325 <pre xmlns:xl="http://www.w3.org/1999/xlink" class="screen">a - b</pre> 326 }}} 327 328 {{{ 329 #!html 330 <pre xmlns:xl="http://www.w3.org/1999/xlink" class="screen">numb1*a</pre> 331 }}} 332 333 {{{ 334 #!html 335 <pre xmlns:xl="http://www.w3.org/1999/xlink" class="screen">a + numb</pre> 336 }}} 337 or any command with the following format 338 {{{ 339 #!html 340 <pre xmlns:xl="http://www.w3.org/1999/xlink" class="screen">numb1*a + numb2*b + numb3*c ⊠+ numb</pre> 341 }}} 342 where numb1, numb2, ⊠correspond to numbers and a, b, c ⊠will be the data to read. 343 If you want to make basic linear computation (like difference between fields, add/multiply by a constant âŠ), you can simply put the following commands: {{{a - b}}}{{{numb1*a}}}{{{a + numb}}} or any command with the following format {{{numb1*a + numb2*b + numb3*c ⊠+ numb}}} where numb1, numb2, ⊠correspond to numbers and a, b, c ⊠will be the data to read. 343 344 344 345 ==== Any kind of computation ==== 345 346 346 If you want to make a computation more complicated than a basic linear you must putdesignate the data you want to read between "" (with anything in between the "). For example:347 If you want to make a computation more complicated than a basic linear you must designate the data you want to read between "" (with anything in between the "). For example: 347 348 {{{ 348 349 #!html … … 423 424 424 425 You can restore configuration by default by pressing the Default button. 425 The path of the file [../../ToBeReviewed/WIDGET/AUTOUR_de_XXX/definedefaultextra.pro definedefaultextra.pro] that defines the default values for each variable names is displayed when the cursor hovers over the button Default. This file contains a case statement based on the name of the variable and defining the min, max, contour interval and other keywords that should be used as default for the specified variable. You can copy this file in your own {{{${HOME}/My_IDL/}}} directory and easily modify it to suit your favorite default values. 426 427 428 '''Note''' 429 430 The path of the file [source:/trunk/SRC/ToBeReviewed/WIDGET/AUTOUR_de_XXX/definedefaultextra.pro definedefaultextra.pro] that defines the default values for each variable names is displayed when the cursor hovers over the button Default. This file contains a case statement based on the name of the variable and defining the min, max, contour interval and other keywords that should be used as default for the specified variable. You can copy this file in your own {{{${HOME}/My_IDL/}}} directory and easily modify it to suit your favorite default values. 426 431 ==== Specify the palette to be used ==== 427 432 For the color palette, you can either specify the name or go search for one among the palettes available. … … 465 470 466 471 467 Graphic with /realcont, map=[90,0,0], /ortho, cell_fill=2keywords472 Graphic with {{{/realcont, map=[90,0,0], /ortho, cell_fill=2}}} keywords 468 473 469 474 … … 491 496 * the middle mouse button to create vertical plots (pltz) 492 497 * the right mouse button to create common hovmoellers for xt and yt cuts (pltt)In summary: 493 * LCL--- >plt498 * LCL--->plt 494 499 495 500 … … 505 510 506 511 507 * LCM--- >pltz512 * LCM--->pltz 508 513 509 514 … … 519 524 520 525 521 * LCR--- >pltt526 * LCR--->pltt 522 527 523 528 … … 532 537 533 538 534 If the plot selector is on something other than plt the indicated plot type is made. 539 540 541 '''Note''' 542 543 If the plot selector is on something other than plt the indicated plot type is made. 535 544 === Create multiple plots on the same sheet and make them interact === 536 545 … … 549 558 A double-click with the right button in the second frame will erase the 550 559 plot.In summary: 551 * DCL--- >"reference" frame560 * DCL--->"reference" frame 552 561 553 562 … … 556 565 557 566 558 The referenceframe is selected567 The "reference" frame is selected 559 568 560 569 … … 563 572 564 573 565 * DCM--- >"target" frame574 * DCM--->"target" frame 566 575 567 576 … … 570 579 571 580 572 The targetframe is selected581 The "target" frame is selected 573 582 574 583 … … 577 586 578 587 579 * DCR--- >erase the frame588 * DCR--->erase the frame 580 589 581 590 … … 586 595 587 596 588 load xxx with the command:597 Load xxx with the command: 589 598 590 599 {{{ … … 608 617 609 618 610 DCM in frame 2, LCL on the plot in frame 1, to create a horizontal 611 zoom in frame 2. 612 DCM in frame 3, LCM on the plot in frame 1, to create a vertical cut 613 in frame 3. 614 DCM in frame 4, LCR on the plot in frame 1, to create a hovmoeller in frame 4. 619 DCM in frame 2, LCL on the plot in frame 1 to create a horizontal zoom in frame 2. 620 DCM in frame 3, LCM on the plot in frame 1 to create a vertical cut in frame 3. 621 DCM in frame 4, LCR on the plot in frame 1 to create a hovmoeller in frame 4. 615 622 616 623 … … 645 652 646 653 647 click OK, and the plot is redone.654 Click OK, and the plot is redone. 648 655 649 656 … … 658 665 659 666 660 in frame 5, let's create the same plot as in frame 2 except we use pltv instead of plt667 In frame 5, let's create the same plot as in frame 2 except we use pltv instead of plt 661 668 662 669 … … 670 677 671 678 672 change plt for pltv679 Change plt for pltv 673 680 674 681 … … 699 706 700 707 701 in the IDL window, type702 703 {{{ 704 #!html 705 <pre xmlns:xl="http://www.w3.org/1999/xlink" class="screen"> 706 <code class="prompt">idl></code> <strong class="userinput"><code>domdef</code></strong>708 In the IDL window, type 709 710 {{{ 711 #!html 712 <pre xmlns:xl="http://www.w3.org/1999/xlink" class="screen"> 713 <code class="prompt">idl></code> <strong class="userinput"><code>domdef</code></strong> 707 714 </pre> 708 715 }}} … … 710 717 DCR to erase the problem frame. 711 718 712 change the orientation of the plot by pressing Flag options ->Portrait/Landscape. Cf [#LaunchingXXX Launching XXX]719 change the orientation of the plot by pressing Flag options Portrait/Landscape. Cf [#LaunchingXXX Launching XXX] 713 720 quit XXX cleanly using quit from the File menu. Cf [#LaunchingXXX Launching XXX] 721 722 723 '''Note''' 724 714 725 715 726 … … 720 731 overflow. 721 732 To clean up this memory: 722 723 {{{ 724 #!html 725 <pre xmlns:xl="http://www.w3.org/1999/xlink" class="screen"> 726 <code class="prompt">idl></code> <strong class="userinput"><code>ptr_free, ptr_valid()</code></strong>733 734 {{{ 735 #!html 736 <pre xmlns:xl="http://www.w3.org/1999/xlink" class="screen"> 737 <code class="prompt">idl></code> <strong class="userinput"><code>ptr_free, ptr_valid()</code></strong> 727 738 </pre> 728 739 }}} -
trunk/SRC/Documentation/xmldoc/wiki/WhatisSaxo
r355 r356 18 18 SAXO needs at least [http://www.ittvis.com/idl/ IDL] 6.0. 19 19 20 21 '''Note''' 22 23 20 24 SAXO can be used with the 7 minutes demo-mode (within the limitations of this mode: impossible to save data and create a file). 21 25 -
trunk/SRC/Documentation/xmldoc/wiki/WhatsNew
r355 r356 33 33 == Changeset 152 (2006-08-10) == 34 34 35 This revision includes new [ ../../ToBeReviewed/PLOTS/DESSINE/pltv.pro pltv] (a mix between {{{plt}}} and {{{tvplus}}}) plotting procedure.35 This revision includes new [source:/trunk/SRC/ToBeReviewed/PLOTS/DESSINE/pltv.pro pltv] (a mix between {{{plt}}} and {{{tvplus}}}) plotting procedure. 36 36 37 37 Details can be seen in [http://forge.ipsl.jussieu.fr/saxo/changeset/152 Changeset 152].
Note: See TracChangeset
for help on using the changeset viewer.