Ignore:
Timestamp:
06/29/06 12:30:03 (18 years ago)
Author:
pinsard
Message:

correction of xmldoc/*.xml using aspell

File:
1 edited

Legend:

Unmodified
Added
Removed

  • trunk/SRC/Documentation/xmldoc/getsaxo.html

    r119 r120  
    55  </title><link rel="stylesheet" href="saxo.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.70.1"><meta name="keywords" content="idl, SAXO"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="article" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="d0e2"></a> 
    66    Get <span class="application">SAXO</span> 
    7   </h2></div><div><div class="authorgroup"><div class="author"><h3 class="author"><span class="firstname">S&eacute;bastien</span> <span class="surname">Masson</span></h3><code class="email">&lt;<a href="mailto:smasson_at_lodyc.jussieu.fr">smasson_at_lodyc.jussieu.fr</a>&gt;</code></div><div class="author"><h3 class="author"><span class="firstname">Fran&ccedil;oise</span> <span class="surname">Pinsard</span></h3><code class="email">&lt;<a href="mailto:fplod_at_lodyc.jussieu.fr">fplod_at_lodyc.jussieu.fr</a>&gt;</code></div></div></div><div><div class="revhistory"><table border="1" width="100%" summary="Revision history"><tr><th align="left" valign="top" colspan="2"><b>Revision History</b></th></tr><tr><td align="left">Revision 0.0</td><td align="left">May 2006</td></tr><tr><td align="left" colspan="2">First draft</td></tr></table></div></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#create_saxo_env">1.  
     7  </h2></div><div><div class="authorgroup"><div class="author"><h3 class="author"><span class="firstname">S&eacute;bastien</span> <span class="surname">Masson</span></h3><code class="email">&lt;<a href="mailto:smasson_at_locean-ipsl.upmc.fr">smasson_at_locean-ipsl.upmc.fr</a>&gt;</code></div><div class="author"><h3 class="author"><span class="firstname">Fran&ccedil;oise</span> <span class="surname">Pinsard</span></h3><code class="email">&lt;<a href="mailto:fplod_at_locean-ipsl.upmc.fr">fplod_at_locean-ipsl.upmc.fr</a>&gt;</code></div></div></div><div><div class="revhistory"><table border="1" width="100%" summary="Revision history"><tr><th align="left" valign="top" colspan="2"><b>Revision History</b></th></tr><tr><td align="left">Revision 0.0</td><td align="left">May 2006</td></tr><tr><td align="left" colspan="2">First draft</td></tr></table></div></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#create_saxo_env">1.  
    88      Create <span class="application">SAXO</span> environment 
    99    </a></span></dt><dt><span class="sect1"><a href="#get_saxo_files">2.  
    … …  
    3535        <span class="application">SAXO</span> is already installed at 
    3636        </p><div class="itemizedlist"><ul type="disc"><li>IDRIS, on rhodes: <code class="filename">/home/rech/eee/reee217/SAXO_DIR</code></li><li>IPSL: <code class="filename">/home/smlod/SAXO_DIR</code></li><li>LOCEAN: <code class="filename">/usr/home/smasson/SAXO_DIR</code></li></ul></div><p> 
    37         If you can access one of theses directories, there is no need to re-install <span class="application">SAXO</span> again! In that case, you only have to link <code class="filename"><code class="envar">${HOME}</code>/SAXO_DIR</code> to the appropiate directory: 
     37        If you can access one of theses directories, there is no need to re-install <span class="application">SAXO</span> again! In that case, you only have to link <code class="filename"><code class="envar">${HOME}</code>/SAXO_DIR</code> to the appropriate directory: 
    3838        </p><div class="variablelist"><dl><dt><span class="term"><span><strong class="command">IDRIS</strong></span></span></dt><dd><pre class="screen"> 
    3939  <code class="prompt">$</code> <strong class="userinput"><code><span><strong class="command">ln</strong></span> <code class="option">-s</code> <em class="parameter"><code>/home/rech/eee/reee217/SAXO_DIR</code></em> <em class="parameter"><code><code class="envar">${HOME}</code>/SAXO_DIR</code></em></code></strong> 
    … …  
    5353        </pre><p> 
    5454      </p><p> 
    55         The latest revision of the <span><strong class="command">source files</strong></span> (49 Mb) can be checked out with the following command: 
     55        The latest revision of the <span><strong class="command">source files</strong></span> (50 Mb) can be checked out with the following command: 
    5656        </p><pre class="screen"> 
    5757  <code class="prompt">$</code> <strong class="userinput"><code><span><strong class="command">svn</strong></span> <code class="option">checkout</code> <em class="parameter"><code>http://forge.ipsl.jussieu.fr/saxo/svn/trunk/SRC</code></em> <em class="parameter"><code>SAXO_DIR/SRC</code></em></code></strong> 
    5858        </pre><p> 
    5959      </p><p> 
    60         The latest revision of the <span><strong class="command">NetCDF data files</strong></span> (727 Mb) used by the test programs can be checked out with the following command: 
     60        The latest revision of the <span><strong class="command">NetCDF data files</strong></span> (728 Mb) used by the test programs can be checked out with the following command: 
    6161        </p><pre class="screen"> 
    6262  <code class="prompt">$</code> <strong class="userinput"><code><span><strong class="command">svn</strong></span> <code class="option">checkout</code> <em class="parameter"><code>http://forge.ipsl.jussieu.fr/saxo/svn/trunk/DATA</code></em> <em class="parameter"><code>SAXO_DIR/DATA</code></em></code></strong> 
    … …  
    9696        </h4></div></div></div><p> 
    9797        If you want to use the tests programs, you need to download the data tests files (<code class="filename">SAXO_DATA_20060602.tar.gz</code>), You may download theses files in  
    98         </p><div class="itemizedlist"><ul type="disc"><li><code class="filename"><code class="envar">${HOME}</code>/My_IDL</code>. This is the easiest solution but it could be unconvenient if your <code class="envar">${HOME}</code> disk space is limited.</li><li>any other Directory of your choice. In that case, when using IDL, you will need to define the variable <code class="varname">iodir</code> to the Directory you choose in order to let IDL find the data tests files. This can be done either through the init.pro file (see <a href="#generate_init" title="3.&nbsp;&#xA;Generate your init.pro file&#xA;      "><a href="#generate_init" title="3.&nbsp;&#xA;Generate your init.pro file&#xA;      ">Section&nbsp;3, &#8220; 
     98        </p><div class="itemizedlist"><ul type="disc"><li><code class="filename"><code class="envar">${HOME}</code>/My_IDL</code>. This is the easiest solution but it could be inconvenient if your <code class="envar">${HOME}</code> disk space is limited.</li><li>any other Directory of your choice. In that case, when using IDL, you will need to define the variable <code class="varname">iodir</code> to the Directory you choose in order to let IDL find the data tests files. This can be done either through the init.pro file (see <a href="#generate_init" title="3.&nbsp;&#xA;Generate your init.pro file&#xA;      "><a href="#generate_init" title="3.&nbsp;&#xA;Generate your init.pro file&#xA;      ">Section&nbsp;3, &#8220; 
    9999        Generate your init.pro file 
    100       &#8221;</a></a>) or directly within IDL with the following commad: <code class="prompt">idl&gt;</code> <strong class="userinput"><code><span><strong class="command">iodir = <em class="replaceable"><code>the chosen directory</code></em></strong></span></code></strong></li></ul></div><p> 
     100      &#8221;</a></a>) or directly within IDL with the following command: <code class="prompt">idl&gt;</code> <strong class="userinput"><code><span><strong class="command">iodir = <em class="replaceable"><code>the chosen directory</code></em></strong></span></code></strong></li></ul></div><p> 
    101101        </p><pre class="screen"> 
    102102  <code class="prompt">$</code> <strong class="userinput"><code><span><strong class="command">cd</strong></span> <em class="parameter"><code><code class="envar">${HOME}</code></code></em></code></strong> 
    … …  
    114114        Generate your init.pro file 
    115115      </h2></div></div></div><p> 
    116         To use <span class="application">SAXO</span>, we need to build an idl script that we usually call "<code class="filename">init.pro</code>". This file contains a set of IDL commands and default definitions (paths and variables of the common files) that are necessary to <span class="application">SAXO</span>. Once it has ben created, <code class="filename">init.pro</code> should the first executed command when starting IDL session. 
     116        To use <span class="application">SAXO</span>, we need to build an idl script that we usually call "<code class="filename">init.pro</code>". This file contains a set of IDL commands and default definitions (paths and variables of the common files) that are necessary to <span class="application">SAXO</span>. Once it has been created, <code class="filename">init.pro</code> should the first executed command when starting IDL session. 
    117117      </p><p> 
    118118        </p><pre class="screen"> 
Note: See TracChangeset for help on using the changeset viewer.