Ignore:
Timestamp:
04/17/14 10:49:43 (10 years ago)
Author:
pinsard
Message:

fix thanks to coding rules; typo; dupe empty lines; trailing blanks

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/SRC/Documentation/xmldoc/getsaxo.html

    r431 r495  
    1717    </div></div><div><span class="pubdate">svn Id of xml source file : $Id$<br /><br /></span></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> 
    1818      <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> 
    19       <tr><td align="left">Revision 0.1</td><td align="left">April 2008</td></tr><tr><td align="left" colspan="2">migration from DocBook 4.2 to Docbook 5.0</td></tr> 
     19      <tr><td align="left">Revision 0.1</td><td align="left">April 2008</td></tr><tr><td align="left" colspan="2">migration from DocBook 4.2 to DocBook 5.0</td></tr> 
    2020    </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.  Create SAXO environment </a></span></dt><dt><span class="sect1"><a href="#get_saxo_files">2.  Get SAXO files </a></span></dt><dd><dl><dt><span class="sect2"><a href="#saxo_local">2.1.  If you work at IDRIS, IPSL or LOCEAN </a></span></dt><dt><span class="sect2"><a href="#saxo_svn">2.2.  If ??? is installed on your machine </a></span></dt><dt><span class="sect2"><a href="#saxo_tar">2.3.  Get SAXO from a tar file </a></span></dt></dl></dd><dt><span class="sect1"><a href="#generate_init">3.  Generate your init.pro file </a></span></dt><dt><span class="sect1"><a href="#aftergetsaxo">4. After this</a></span></dt></dl></div> 
    2121 
    22    
    23  
    24    
    25  
    26    
     22 
     23 
     24 
     25 
     26 
    2727 
    2828  <div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="create_saxo_env" id="create_saxo_env"></a>1.  Create <span class="application">SAXO</span> environment </h2></div></div></div> 
    29      
     29 
    3030    <p> 
    3131      To simplify the explanation, we suppose that we install <span class="application">SAXO</span> in your <code class="filename">${HOME}</code>. 
     
    3333      </p><div class="itemizedlist"><ul type="disc"><li> 
    3434         <code class="filename">${HOME}/SAXO_DIR</code> that will contain the source files of <span class="application">SAXO</span>. It should not be modified by the user to simplify later updates. 
    35           
     35 
    3636        </li><li> 
    3737         <code class="filename">${HOME}/My_IDL</code> that will contain user personal files (including modified <span class="application">SAXO</span> files, if needed). 
    38           
     38 
    3939       </li></ul></div><p> 
    4040    </p> 
     
    4747  </div> 
    4848 
    49    
     49 
    5050 
    5151 <div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="get_saxo_files" id="get_saxo_files"></a>2.  Get <span class="application">SAXO</span> files </h2></div></div></div> 
    52      
    53  
    54    
     52 
     53 
     54 
    5555 
    5656    <div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="saxo_local" id="saxo_local"></a>2.1.  If you work at IDRIS, IPSL or LOCEAN </h3></div></div></div> 
    57        
     57 
    5858      <p> 
    5959<span class="application">SAXO</span> is already installed at 
    6060</p><div class="itemizedlist"><ul type="disc"><li> 
    6161           IDRIS, on <code class="systemitem">rhodes</code>: <code class="filename">/home/rech/eee/reee217/SAXO_DIR</code> 
    62             
     62 
    6363          </li><li> 
    6464           IPSL: <code class="filename">/home/smlod/SAXO_DIR</code> 
    65             
     65 
    6666          </li><li> 
    6767           LOCEAN: <code class="filename">/usr/home/smasson/SAXO_DIR</code> 
    68             
     68 
    6969         </li></ul></div><p> 
    7070If you can access one of these 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">${HOME}/SAXO_DIR</code> to the appropriate directory: 
     
    8282    </div> 
    8383 
    84    
     84 
    8585 
    8686    <div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="saxo_svn" id="saxo_svn"></a>2.2.  If <a class="link" href="http://subversion.tigris.org/" target="_top"><span class="application"> Subversion (svn)</span></a> is installed on your machine </h3></div></div></div> 
    87        
    88   
     87 
     88 
    8989      <div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="saxo_svn_users" id="saxo_svn_users"></a>2.2.1.  Regular users </h4></div></div></div> 
    9090 
     
    120120    </div> 
    121121 
    122    
     122 
    123123 
    124124    <div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="saxo_tar" id="saxo_tar"></a>2.3.  Get <span class="application">SAXO</span> from a tar file </h3></div></div></div> 
    125        
    126    
     125 
     126 
    127127      <div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="saxo_src_tar" id="saxo_src_tar"></a>2.3.1.  Get <span class="application">SAXO</span> source files ( Mb) </h4></div></div></div> 
    128128 
     
    156156 
    157157      </div> 
    158    
     158 
    159159      <div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="saxo_data_tar" id="saxo_data_tar"></a>2.3.2.  Get <span class="application">SAXO</span> tests data files (238M Mb) </h4></div></div></div> 
    160160 
     
    163163</p><div class="itemizedlist"><ul type="disc"><li> 
    164164           <code class="filename">${HOME}/My_IDL</code>. This is the easiest solution but it could be inconvenient if your <code class="envar">${HOME}</code> disk space is limited. 
    165             
    166           </li><li> 
    167            <p>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 <code class="filename">init.pro</code> file (see <a class="xref" href="#generate_init" title="3.  Generate your init.pro file">Section 3, “ Generate your init.pro file ”</a>) or directly within IDL with the following command:  
     165 
     166          </li><li> 
     167           <p>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 <code class="filename">init.pro</code> file (see <a class="xref" href="#generate_init" title="3.  Generate your init.pro file">Section 3, “ Generate your init.pro file ”</a>) or directly within IDL with the following command: 
    168168</p><pre class="screen"> 
    169169 <code class="prompt">idl&gt;</code> <strong class="userinput"><code><span class="command"><strong>iodir = <em class="replaceable"><code>the chosen directory</code></em></strong></span></code></strong> 
     
    189189    </div> 
    190190  </div> 
    191    
     191 
    192192    <div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="generate_init" id="generate_init"></a>3.  Generate your init.pro file </h2></div></div></div> 
    193        
     193 
    194194      <p> 
    195195To 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. 
Note: See TracChangeset for help on using the changeset viewer.