Changeset 120 for trunk/SRC/Documentation/xmldoc/getsaxo.xml
- Timestamp:
- 06/29/06 12:30:03 (18 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/SRC/Documentation/xmldoc/getsaxo.xml
r117 r120 21 21 <articleinfo> 22 22 <authorgroup> 23 <author><firstname>Sébastien</firstname><surname>Masson</surname><email>smasson_at_lo dyc.jussieu.fr</email></author>24 <author><firstname>Françoise</firstname><surname>Pinsard</surname><email>fplod_at_lo dyc.jussieu.fr</email></author>23 <author><firstname>Sébastien</firstname><surname>Masson</surname><email>smasson_at_locean-ipsl.upmc.fr</email></author> 24 <author><firstname>Françoise</firstname><surname>Pinsard</surname><email>fplod_at_locean-ipsl.upmc.fr</email></author> 25 25 </authorgroup> 26 26 <keywordset> … … 79 79 <listitem><simpara>LOCEAN: <filename class='directory'>/usr/home/smasson/SAXO_DIR</filename></simpara></listitem> 80 80 </itemizedlist> 81 If you can access one of theses directories, there is no need to re-install <application>SAXO</application> again! In that case, you only have to link <filename class='directory'><envar>${HOME}</envar>/SAXO_DIR</filename> to the approp iate directory:81 If you can access one of theses directories, there is no need to re-install <application>SAXO</application> again! In that case, you only have to link <filename class='directory'><envar>${HOME}</envar>/SAXO_DIR</filename> to the appropriate directory: 82 82 <variablelist> 83 83 <varlistentry><term><command>IDRIS</command></term> … … 192 192 If you want to use the tests programs, you need to download the data tests files (<filename>SAXO_DATA_&date2;.tar.gz</filename>), You may download theses files in 193 193 <itemizedlist> 194 <listitem><simpara><filename class='directory'><envar>${HOME}</envar>/My_IDL</filename>. This is the easiest solution but it could be unconvenient if your <envar>${HOME}</envar> disk space is limited.</simpara></listitem>195 <listitem><simpara>any other Directory of your choice. In that case, when using IDL, you will need to define the variable <varname>iodir</varname> 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 <link linkend="generate_init"><xref linkend="generate_init"/></link>) or directly within IDL with the following comma d: <prompt>&promptidl;</prompt> <userinput><command>iodir = <replaceable>the chosen directory</replaceable></command></userinput></simpara></listitem>194 <listitem><simpara><filename class='directory'><envar>${HOME}</envar>/My_IDL</filename>. This is the easiest solution but it could be inconvenient if your <envar>${HOME}</envar> disk space is limited.</simpara></listitem> 195 <listitem><simpara>any other Directory of your choice. In that case, when using IDL, you will need to define the variable <varname>iodir</varname> 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 <link linkend="generate_init"><xref linkend="generate_init"/></link>) or directly within IDL with the following command: <prompt>&promptidl;</prompt> <userinput><command>iodir = <replaceable>the chosen directory</replaceable></command></userinput></simpara></listitem> 196 196 </itemizedlist> 197 197 <screen format="linespecific"> … … 224 224 </title> 225 225 <para> 226 To use <application>SAXO</application>, we need to build an idl script that we usually call "<filename>init.pro</filename>". This file contains a set of IDL commands and default definitions (paths and variables of the common files) that are necessary to <application>SAXO</application>. Once it has be n created, <filename>init.pro</filename> should the first executed command when starting IDL session.226 To use <application>SAXO</application>, we need to build an idl script that we usually call "<filename>init.pro</filename>". This file contains a set of IDL commands and default definitions (paths and variables of the common files) that are necessary to <application>SAXO</application>. Once it has been created, <filename>init.pro</filename> should the first executed command when starting IDL session. 227 227 </para> 228 228 <para>
Note: See TracChangeset
for help on using the changeset viewer.