source: trunk/SRC/Documentation/xmldoc/firststeps.xml @ 291

Last change on this file since 291 was 291, checked in by pinsard, 17 years ago

small changes (lodyc became locean, trailing blanks)
  • Property svn:keywords set to Id
File size: 34.1 KB
Line 
1<?xml version='1.0' encoding='iso-8859-1'?>
2<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
3"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
4[
5<!ENTITY hellip "&#x2026;">
6<!ENTITY promptidl "idl&gt;">
7<!ENTITY numb1 '<inlinemediaobject><imageobject><imagedata fileref="images/callouts/1.png" format="PNG"/></imageobject><textobject><phrase>1</phrase></textobject></inlinemediaobject>'>
8<!ENTITY numb2 '<inlinemediaobject><imageobject><imagedata fileref="images/callouts/2.png" format="PNG"/></imageobject><textobject><phrase>2</phrase></textobject></inlinemediaobject>'>
9<!ENTITY showfig '<inlinemediaobject><imageobject><imagedata fileref="images/showfig.png" format="PNG"/></imageobject><textobject><phrase>show result</phrase></textobject></inlinemediaobject>'>
10]>
11
12<!--
13instructions to create html file
14xsltproc ?-?-param  section.autolabel 1 -output firststep.html /sw/share/xml/xsl/docbook-xsl/xhtml/docbook.xsl firststep.xml
15xsltproc -output firststep.html /sw/share/xml/xsl/docbook-xsl/xhtml/docbook.xsl firststep.xml
16xsltproc  /sw/share/xml/xsl/docbook-xsl/xhtml/chunk.xsl  firststep.xml
17xsltproc ?-?-param  section.autolabel 1 /sw/share/xml/xsl/docbook-xsl/xhtml/chunk.xsl firststep.xml
18
19-->
20
21<!--
22module :
23first steps with SAXO ...
24
25source :
26./SRC/Documentation/xmldoc/firststeps.xml
27
28-->
29<article lang="en">
30  <title>
31    First steps with <application>SAXO</application>
32  </title>
33
34  <articleinfo>
35    <authorgroup>
36      <author><firstname>Sébastien</firstname> <surname>Masson</surname> <email>Sebastien.Masson_at_locean-ipsl.upmc.fr</email></author>
37      <author><firstname>Françoise</firstname> <surname>Pinsard</surname> <email>Francoise.Pinsard_at_locean-ipsl.upmc.fr</email></author>
38    </authorgroup>
39    <keywordset>
40      <keyword>IDL</keyword>
41      <keyword>SAXO</keyword>
42    </keywordset>
43    <revhistory>
44      <revision>
45        <revnumber>0.0</revnumber>
46        <date>29 July 2005</date>
47        <revremark>First draft</revremark>
48      </revision>
49      <revision>
50        <revnumber>0.1</revnumber>
51        <date>29 August 2005</date>
52        <revremark>last Japanese version!</revremark>
53      </revision>
54      <revision>
55        <revnumber>0.2</revnumber>
56        <date>May 2006</date>
57        <revremark>split with getsaxo</revremark>
58      </revision>
59     </revhistory>
60     <pubdate>$Id$</pubdate>
61  </articleinfo>
62<sect1 id="beforefirststeps">
63<title>Before this</title>
64<para>
65In this document, we supposed that you followed <ulink url="./getsaxo.html">Get SAXO</ulink> recommendations.
66</para>
67</sect1>
68
69  <sect1 id="first_plots">
70    <title>
71      First plots &hellip;
72    </title>
73    <sect2 id="start_with_init">
74      <title>
75        Start IDL session: <userinput><command>@init</command></userinput>
76      </title>
77      <para>
78        Each IDL session using <application>SAXO</application> must always start with: <prompt>&promptidl;</prompt> <userinput><command>@init</command></userinput>.
79      </para>
80      <para>
81        <emphasis>The @ is equivalent to an include. It is used to execute a set of IDL commands that will be directly executed without any compilation (as it is the case for a procedure or a function). All variables defined and used in the @&hellip; file will still be accessible after the execution of the @&hellip; is finished (which is not the case for procedures and functions that ends with the return instruction).</emphasis>
82        <screen format="linespecific">
83  <prompt>$</prompt> <userinput><command>cd</command> <filename class="directory"><envar>${HOME}</envar>/My_IDL/</filename></userinput>
84  <prompt>$</prompt> <userinput><command>idl</command></userinput>
85  <computeroutput>IDL Version 6.0, Mac OS X (darwin ppc m32). (c) 2003, Research Systems, Inc.</computeroutput>
86  <computeroutput>Installation number: 35411.</computeroutput>
87  <computeroutput>Licensed for personal use by Jean-Philippe BOULANGER only.</computeroutput>
88  <computeroutput>All other use is strictly prohibited.</computeroutput>
89  <prompt>&promptidl;</prompt> <userinput><command>@init</command></userinput>
90  <computeroutput>% Compiled module: KEEP_COMPATIBILITY.</computeroutput>
91  <computeroutput>% Compiled module: FIND.</computeroutput>
92  <computeroutput>% Compiled module: PATH_SEP.</computeroutput>
93  <computeroutput>% Compiled module: STRSPLIT.</computeroutput>
94  <computeroutput>% Compiled module: DEF_MYUNIQUETMPDIR.</computeroutput>
95  <computeroutput>We forget the compatibility with the old version</computeroutput>
96  <computeroutput>% Compiled module: DEMOMODE_COMPATIBILITY.</computeroutput>
97  <computeroutput>% Compiled module: ISADIRECTORY.</computeroutput>
98  <computeroutput>% Compiled module: LCT.</computeroutput>
99  <computeroutput>% Compiled module: RSTRPOS.</computeroutput>
100  <computeroutput>% Compiled module: REVERSE.</computeroutput>
101  <computeroutput>% Compiled module: STR_SEP.</computeroutput>
102  <computeroutput>% Compiled module: LOADCT.</computeroutput>
103  <prompt>&promptidl;</prompt>
104        </screen>
105        As an IDL session using <application>SAXO</application> must always start with <prompt>&promptidl;</prompt> <userinput><command>@init</command></userinput>, it could be convenient to define the environment variable <envar>IDL_STARTUP</envar> to <filename><envar>${HOME}</envar>/My_IDL/init.pro</filename>. In that way, <filename>init.pro</filename> will automatically been executed when starting IDL. This can be done with the following command:
106      <variablelist>
107        <varlistentry><term><command>csh</command></term>
108        <listitem><screen><prompt>$</prompt> <userinput><command>setenv</command> <envar>IDL_STARTUP</envar> <filename><envar>${HOME}</envar>/My_IDL/init.pro</filename></userinput></screen></listitem>
109        </varlistentry>
110        <varlistentry><term><command>ksh</command></term>
111        <listitem><screen><prompt>$</prompt> <userinput><command>export</command> <envar>IDL_STARTUP</envar>=<filename><envar>${HOME}</envar>/My_IDL/init.pro</filename></userinput></screen></listitem>
112        </varlistentry>
113      </variablelist>
114      </para>
115    </sect2>
116    <sect2 id="basic_plots">
117      <title>
118        Basic plots &hellip;
119      </title>
120      <sect3 id="basic_splot">
121      <title>
122        splot
123      </title>
124
125      <para>
126        <screenco>
127          <areaspec>
128            <area id="findgen" coords='2'/>
129          </areaspec>
130        <screen format="linespecific">
131   <prompt>&promptidl;</prompt> <userinput><command>n = 10</command></userinput>
132   <prompt>&promptidl;</prompt> <userinput><command>y = findgen(n)</command></userinput> &numb1;
133   <prompt>&promptidl;</prompt> <userinput><command>plot, y</command></userinput> <ulink url="./figpng/basic_plot.png">&showfig;</ulink>
134        </screen>
135          <calloutlist>
136            <callout arearefs="findgen">
137              <para>
138                <command>findgen</command> stands for
139<emphasis role="bold">f</emphasis>loat <emphasis role="bold">ind</emphasis>ex <emphasis role="bold">gen</emphasis>erator.
140                <screen format="linespecific">
141  <prompt>&promptidl;</prompt> <userinput><command>print, findgen(6)</command></userinput>
142  <computeroutput>      0.00000      1.00000      2.00000      3.00000      4.00000      5.00000</computeroutput>
143                </screen>
144              </para>
145            </callout>
146          </calloutlist>
147        </screenco>
148     </para>
149      <para>
150        Using IDL <command>plot</command> command is quite inconvenient to save the figure as a postscript. In addition, positioning the figure on the window/page by using <varname>!p.position</varname>, <varname>!p.region</varname> and <varname>!p.multi</varname> is often a nightmare. That's why we developed <command>splot</command> (like super-plot) which can be used in the same way as plot but is much more convenient to make postscript and position the figure.
151        <screen format="linespecific">
152  <prompt>&promptidl;</prompt> <userinput><command>splot, y</command></userinput> <ulink url="./figpng/basic_splot1.png">&showfig;</ulink>
153  <computeroutput>% Compiled module: SPLOT.</computeroutput>
154  <computeroutput>% Compiled module: REINITPLT.</computeroutput>
155  <computeroutput>% Compiled module: PLACEDESSIN.</computeroutput>
156  <computeroutput>% Compiled module: CALIBRE.</computeroutput>
157  <computeroutput>% Compiled module: GIVEWINDOWSIZE.</computeroutput>
158  <computeroutput>% Compiled module: GET_SCREEN_SIZE.</computeroutput>
159  <computeroutput>% Compiled module: TERMINEDESSIN.</computeroutput>
160        </screen>
161        Save the figure seen on the screen as a (real, not a screen capture) postscript in only one command.
162        <screenco>
163          <areaspec>
164            <area id="make_ps" coords='6'/>
165          </areaspec>
166        <screen format="linespecific">
167  <prompt>&promptidl;</prompt> <userinput><command>@ps</command></userinput>
168  <computeroutput>% Compiled module: GETFILE.</computeroutput>
169  <computeroutput>% Compiled module: PUTFILE.</computeroutput>
170  <computeroutput>% Compiled module: OPENPS.</computeroutput>
171  <computeroutput>% Compiled module: XQUESTION.</computeroutput>
172  <computeroutput>Name of the postscript file? (default answer is idl.ps)</computeroutput><userinput>first_ps</userinput> &numb1;
173  <computeroutput>% Compiled module: ISAFILE.</computeroutput>
174  <computeroutput>% Compiled module: XNOTICE.</computeroutput>
175  <computeroutput>% Compiled module: CLOSEPS.</computeroutput>
176  <computeroutput>% Compiled module: PRINTPS.</computeroutput>
177  <computeroutput>% Compiled module: FILE_WHICH.</computeroutput>
178  <computeroutput>% Compiled module: CW_BGROUP.</computeroutput>
179  <computeroutput>% Compiled module: XMANAGER.</computeroutput>
180        </screen>
181          <calloutlist>
182            <callout arearefs="make_ps">
183              <para>
184                <remark>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: <filename>idl.ps</filename>.</remark>
185              </para>
186            </callout>
187          </calloutlist>
188        </screenco>
189        Check that the <quote><filename>first_ps.ps</filename></quote> file is now existing &hellip;
190        <screen format="linespecific">
191  <prompt>&promptidl;</prompt> <userinput><command>print, file_test(psdir + 'first_ps.ps')</command></userinput>
192  <computeroutput>           1</computeroutput>
193  <prompt>&promptidl;</prompt> <userinput><command>help, file_info(psdir + 'first_ps.ps'), /structure</command></userinput>
194  <computeroutput>** Structure FILE_INFO, 21 tags, length=64, data length=63:</computeroutput>
195  <computeroutput>   NAME            STRING    '/Users/sebastie/IDL/first_ps.ps'</computeroutput>
196  <computeroutput>   EXISTS          BYTE         1</computeroutput>
197  <computeroutput>   READ            BYTE         1</computeroutput>
198  <computeroutput>   WRITE           BYTE         1</computeroutput>
199  <computeroutput>   EXECUTE         BYTE         0</computeroutput>
200  <computeroutput>   REGULAR         BYTE         1</computeroutput>
201  <computeroutput>   DIRECTORY       BYTE         0</computeroutput>
202  <computeroutput>   BLOCK_SPECIAL   BYTE         0</computeroutput>
203  <computeroutput>   CHARACTER_SPECIAL</computeroutput>
204  <computeroutput>                   BYTE         0</computeroutput>
205  <computeroutput>   NAMED_PIPE      BYTE         0</computeroutput>
206  <computeroutput>   SETUID          BYTE         0</computeroutput>
207  <computeroutput>   SETGID          BYTE         0</computeroutput>
208  <computeroutput>   SOCKET          BYTE         0</computeroutput>
209  <computeroutput>   STICKY_BIT      BYTE         0</computeroutput>
210  <computeroutput>   SYMLINK         BYTE         0</computeroutput>
211  <computeroutput>   DANGLING_SYMLINK</computeroutput>
212  <computeroutput>                   BYTE         0</computeroutput>
213  <computeroutput>   MODE            LONG               420</computeroutput>
214  <computeroutput>   ATIME           LONG64                1122424373</computeroutput>
215  <computeroutput>   CTIME           LONG64                1122424373</computeroutput>
216  <computeroutput>   MTIME           LONG64                1122424373</computeroutput>
217  <computeroutput>   SIZE            LONG64                      4913</computeroutput>
218        </screen>
219      </para>
220      <para id="splot_description">
221        <command>splot</command> accepts the same keywords as <command>plot</command> (<computeroutput id="plot_kwd">/ISOTROPIC, MAX_VALUE=value, MIN_VALUE=value, NSUM=value, /POLAR, THICK=value, /XLOG, /YLOG, /YNOZERO</computeroutput>), including the graphics keywords (<computeroutput id="gr_kwd">BACKGROUND, CHARSIZE, CHARTHICK, CLIP, COLOR, DATA, DEVICE, FONT, LINESTYLE, NOCLIP, NODATA, NOERASE, NORMAL, POSITION, PSYM, SUBTITLE, SYMSIZE, T3D, THICK, TICKLEN, TITLE, [XYZ]CHARSIZE, [XYZ]GRIDSTYLE, [XYZ]MARGIN, [XYZ]MINOR, [XYZ]RANGE, [XYZ]STYLE, [XYZ]THICK, [XYZ]TICKFORMAT, [XYZ]TICKINTERVAL, [XYZ]TICKLAYOUT, [XYZ]TICKLEN, [XYZ]TICKNAME, [XYZ]TICKS, [XYZ]TICKUNITS, [XYZ]TICKV, [XYZ]TICK_GET, [XYZ]TITLE, ZVALUE</computeroutput>).
222      </para>
223      <simpara>
224        It can therefore be customized <emphasis>as much as you want</emphasis>. See this short example:
225      </simpara>
226      <para>
227        <screen format="linespecific">
228  <prompt>&promptidl;</prompt> <userinput><command>splot, y, y^2, linestyle = 2, thick = 2, title = 'y = x^2', /portrait</command></userinput> <ulink url="./figpng/basic_splot2.png">&showfig;</ulink>
229        </screen>
230        <command>splot</command> can be used to setup the graphic environment (<varname>!p</varname>, <varname>!x</varname>, <varname>!y</varname>, <varname>!z</varname> variables) needed by procedures like <command>oplot</command>
231        <screen format="linespecific">
232  <prompt>&promptidl;</prompt> <userinput><command>splot, y, yrange = [0, (n-1)^2], title = 'x and x^2'</command></userinput>
233  <prompt>&promptidl;</prompt> <userinput><command>oplot, y^2, color = 50, linestyle = 2</command></userinput> <ulink url="./figpng/basic_splot4.png">&showfig;</ulink>
234        </screen>
235        Use the keyword small to produce multi plots figures.
236        <screenco>
237          <areaspec>
238            <areaset id="small" coords="">
239              <area id="small.1" coords='1'/>
240              <area id="small.2" coords='2'/>
241            </areaset>
242            <area id="noerase" coords='2'/>
243          </areaspec>
244        <screen format="linespecific">
245  <prompt>&promptidl;</prompt> <userinput><command>splot, y, y^2, title = 'y = x^2', psym = 2, small &numb1; = [1, 2, 1]</command></userinput>
246  <prompt>&promptidl;</prompt> <userinput><command>splot, findgen(360)/36., findgen(360)*2.*!dtor, /polar $</command></userinput>
247  <prompt>&promptidl;</prompt> <userinput><command>    , small &numb1; = [1, 2, 2], /noerase &numb2;</command></userinput> <ulink url="./figpng/basic_splot3.png">&showfig;</ulink>
248        </screen>
249          <calloutlist>
250            <callout arearefs="small">
251              <para>
252                the <computeroutput>small</computeroutput> 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.
253              </para>
254            </callout>
255            <callout arearefs="noerase">
256              <simpara>
257                you must put <computeroutput>/noerase</computeroutput> otherwise the second plot will be done in a new window.
258              </simpara>
259            </callout>
260          </calloutlist>
261        </screenco>
262      </para>
263      </sect3>
264
265      <sect3 id="basic_contour">
266      <title>
267        scontour
268      </title>
269      <para>
270        Following <command><link linkend="basic_splot">splot</link></command> example, we provide <command>scontour</command> as a "super <command>contour</command>".
271        <screen format="linespecific">
272  <prompt>&promptidl;</prompt> <userinput><command>z = dist(n)</command></userinput>
273  <computeroutput>% Compiled module: DIST.</computeroutput>
274  <prompt>&promptidl;</prompt> <userinput><command>scontour, z</command></userinput> <ulink url="./figpng/basic_scontour1.png">&showfig;</ulink>
275  <computeroutput>% Compiled module: SCONTOUR.</computeroutput>
276  <computeroutput>% Compiled module: CHKSTRU.</computeroutput>
277        </screen>
278        <command>scontour</command> accepts the same keywords as <command>contour</command> (<computeroutput>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}</computeroutput>), including the <link linkend="gr_kwd">graphics keywords</link> (except <computeroutput>LINESTYLE, PSYM, SYMSIZE</computeroutput>).
279      </para>
280      <simpara>It can therefore be customized <emphasis>as much as you want</emphasis>. See these short examples:</simpara>
281      <para>
282        <screen format="linespecific">
283  <prompt>&promptidl;</prompt> <userinput><command>scontour, z, /fill, nlevels = 15, subtitle = 'nicer contour' $</command></userinput>
284  <prompt>&promptidl;</prompt> <userinput><command>    , xtitle = 'x index', charsize = 1.5</command></userinput> <ulink url="./figpng/basic_scontour2.png">&showfig;</ulink>
285        </screen>
286It can be used in combination with contour to make more complex plots:
287        <screenco>
288          <areaspec>
289            <area id="rebin" coords='1'/>
290          </areaspec>
291        <screen format="linespecific">
292  <prompt>&promptidl;</prompt> <userinput><command>ind = findgen(2*n)/(2.*n)</command></userinput>
293  <prompt>&promptidl;</prompt> <userinput><command>scontour, z, levels = n*ind, c_orientation = 180*ind, c_spacing = 0.4*ind</command></userinput>
294  <prompt>&promptidl;</prompt> <userinput><command>contour, z, /overplot, c_label = rebin([1, 0], 2, n) &numb1;, levels = n*ind $</command></userinput>
295  <prompt>&promptidl;</prompt> <userinput><command>    , c_charthick = 2, c_charsize = 1.5, c_colors = 250*ind</command></userinput> <ulink url="./figpng/basic_scontour3.png">&showfig;</ulink>
296        </screen>
297        <calloutlist>
298          <callout arearefs="rebin">
299            <para>
300              <command>rebin</command> is used to build an array containing an alternation of 1 and 0 in order to label one contour every two contours.
301                <screen format="linespecific">
302  <prompt>&promptidl;</prompt> <userinput><command>print, rebin([1, 0], 2, 3)</command></userinput>
303  <computeroutput>       1       0</computeroutput>
304  <computeroutput>       1       0</computeroutput>
305  <computeroutput>       1       0</computeroutput>
306                </screen>
307            </para>
308          </callout>
309        </calloutlist>
310        </screenco>
311        <command>scontour</command> is compatible with the positioning method associated with the <computeroutput>small</computeroutput> keyword. See for example the test file <ulink type="text" url="../../Tests/tst_basic.pro"><filename>tst_basic.pro</filename></ulink>:
312        <screen format="linespecific">
313  <prompt>&promptidl;</prompt> <userinput><command>tst_basic</command></userinput> <ulink url="./figpng/tst_basic.png">&showfig;</ulink>
314        </screen>
315      </para>
316      </sect3>
317
318      <sect3 id="tvplus">
319        <title>
320          Quick look and explore 2D arrays: tvplus
321        </title>
322        <para>
323          <command>tvplus</command> is a enhanced version of <command>tvscl</command> and allow you to have a quick look and perform basic exploration of 2D arrays.
324          <screen format="linespecific">
325  <prompt>&promptidl;</prompt> <userinput><command>tvplus, dist(20)</command></userinput> <ulink url="./figpng/tvplus.png">&showfig;</ulink>
326  <computeroutput>left button  : mouse position and associated array value</computeroutput>
327  <computeroutput>middle button: use it twice to define a zoom box</computeroutput>
328  <computeroutput>right button : quit</computeroutput>
329  <computeroutput>(x, y) = (  5,   5), value = 7.07107</computeroutput>
330  <computeroutput>(x, y) = ( 12,   8), value = 11.3137</computeroutput>
331          </screen>
332          For more informations on <command>tvplus</command>, try:
333          <screen format="linespecific">
334  <prompt>&promptidl;</prompt> <userinput><command>xhelp, 'tvplus'</command></userinput>
335          </screen>
336          To see the source code of <command>tvplus</command>, try:
337          <screen format="linespecific">
338  <prompt>&promptidl;</prompt> <userinput><command>xfile, 'tvplus'</command></userinput>
339          </screen>
340          <note><title>New Feature</title><para>
341          If you use an IDL 6.2 or later revision, you can simply get the help of any command by typing ?<replaceable>command_name</replaceable>, for example:
342          <screen format="linespecific">
343  <prompt>&promptidl;</prompt> <userinput><command>?tvplus</command></userinput>
344          </screen>
345          </para></note>
346        </para>
347      </sect3>
348
349      <sect3 id="pltv">
350        <title>
351          Formal quick look at 2D arrays: pltv
352        </title>
353        <para>
354          <command>pltv</command> is a mix between <link linkend="tvplus">tvplus</link> and <link linkend="plt">plt</link> and allow you to have formal quick look of 2D arrays.
355          <screen format="linespecific">
356  <prompt>&promptidl;</prompt> <userinput><command>pltv, dist(20)</command></userinput> <ulink url="./figpng/pltv.png">&showfig;</ulink>
357          </screen>
358        </para>
359      </sect3>
360    </sect2>
361  </sect1>
362
363  <sect1 id="gridded_data">
364    <title>
365      Explore gridded data (model outputs and observations)
366    </title>
367    <para>
368      This section briefly describes the main functionalities offered by SAXO to explore gridded data on regular or irregular grid.
369    </para>
370
371    <sect2 id="load_grid">
372      <title>
373        Load the data grid
374      </title>
375      <para>
376        As we focus in this section on the gridded data, we must first load the grid informations before reading and plotting the data. Loading the grid independently of the data allow you to reload the grid only when it is strictly necessary and not every time you access the data. In <filename class="directory"><envar>${HOME}</envar>/SAXO_DIR/Tests/</filename>, we provide several examples to load a grid.
377      </para>
378      <sect3 id="load_fromdata">
379        <title>
380          Easiest solution: load data grid (regular or not) directly from the data file
381        </title>
382        <para>
383          Example of Levitus temperature on a regular 1x1 grid.
384          <screen format="linespecific">
385  <prompt>&promptidl;</prompt> <userinput><command>@tst_initlev</command></userinput>
386  <computeroutput>% Compiled module: INITNCDF.</computeroutput>
387  <computeroutput>% Compiled module: ISAFILE.</computeroutput>
388  <computeroutput>% Compiled module: UNIQ.</computeroutput>
389  <computeroutput>% Loaded DLM: NCDF.</computeroutput>
390  <computeroutput>% Compiled module: COMPUTEGRID.</computeroutput>
391  <computeroutput>% Compiled module: DOMDEF.</computeroutput>
392  <computeroutput>% Compiled module: INTER.</computeroutput>
393  <computeroutput>% Compiled module: TRIANGULE.</computeroutput>
394  <computeroutput>% Compiled module: TRIANGULE_C.</computeroutput>
395  <computeroutput>% Compiled module: UNDEFINE.</computeroutput>
396  <computeroutput>% Compiled module: TESTVAR.</computeroutput>
397  <computeroutput>% Compiled module: DIFFERENT.</computeroutput>
398  <computeroutput>% Compiled module: DEFINETRI.</computeroutput>
399          </screen>
400          This <ulink type="text" url="../../Tests/tst_initlev.pro"><command>@tst_initlev</command></ulink> command allows us to define:
401          <itemizedlist>
402            <listitem><simpara>domain dimensions, stored in <varname>jpi, jpj and jpk</varname></simpara></listitem>
403            <listitem><simpara>points abscissa, stored in 2D array <varname></varname>glamt</simpara></listitem>
404            <listitem><simpara>points ordinates, stored in 2D array <varname></varname>gphit</simpara></listitem>
405            <listitem><simpara>points depths, stored in 1D array <varname></varname>gdept</simpara></listitem>
406            <listitem><simpara>cells corners abscissa, stored in 2D array <varname></varname>glamf</simpara></listitem>
407            <listitem><simpara>cells corners ordinates, stored in 2D array <varname></varname>gphif</simpara></listitem>
408            <listitem><simpara>cells upper boundary depth, stored in 1D array <varname></varname>gdepw</simpara></listitem>
409            <listitem><simpara>land-sea mask, stored in <varname>tmask</varname></simpara></listitem>
410            <listitem><simpara>the cells size in the longitudinal direction, stored in 2D array <varname></varname>e1t</simpara></listitem>
411            <listitem><simpara>the cells size in the latitudinal direction, stored in 2D array <varname></varname>e2t</simpara></listitem>
412            <listitem><simpara>the cells size in the vertical direction, stored in 1D array <varname></varname>e3t</simpara></listitem>
413            <listitem><simpara>the triangulation used to fill the land points, stored in <varname></varname>triangles_list</simpara></listitem>
414          </itemizedlist>
415
416          <screen format="linespecific">
417  <prompt>&promptidl;</prompt> <userinput><command>help, jpi,jpj,jpk</command></userinput>
418  <computeroutput>JPI (LOCAL_COORD)   LONG      =          360</computeroutput>
419  <computeroutput>JPJ (LOCAL_COORD)   LONG      =          180</computeroutput>
420  <computeroutput>JPK (LOCAL_COORD)   LONG      =           33</computeroutput>
421  <prompt>&promptidl;</prompt> <userinput><command>help, glamt, gphit,glamf, gphif</command></userinput>
422  <computeroutput>GLAMT (LONGITUDES)  FLOAT     = Array[360, 180]</computeroutput>
423  <computeroutput>GPHIT (LATITUDES)   FLOAT     = Array[360, 180]</computeroutput>
424  <computeroutput>GLAMF (LONGITUDES)  FLOAT     = Array[360, 180]</computeroutput>
425  <computeroutput>GPHIF (LATITUDES)   FLOAT     = Array[360, 180]</computeroutput>
426  <prompt>&promptidl;</prompt> <userinput><command>help, gdept, gdepw</command></userinput>
427  <computeroutput>GDEPT (VERTICAL)    FLOAT     = Array[33]</computeroutput>
428  <computeroutput>GDEPW (VERTICAL)    FLOAT     = Array[33]</computeroutput>
429  <prompt>&promptidl;</prompt> <userinput><command>help, e1t, e2t, e3t</command></userinput>
430  <computeroutput>E1T (SCALE_FACTORS) FLOAT     = Array[360, 180]</computeroutput>
431  <computeroutput>E2T (SCALE_FACTORS) FLOAT     = Array[360, 180]</computeroutput>
432  <computeroutput>E3T (VERTICAL)      FLOAT     = Array[33]</computeroutput>
433  <prompt>&promptidl;</prompt> <userinput><command>help, tmask</command></userinput>
434  <computeroutput>TMASK (MASKS)       BYTE      = Array[360, 180, 33]</computeroutput>
435  <prompt>&promptidl;</prompt> <userinput><command>help, triangles_list</command></userinput>
436  <computeroutput>TRIANGLES_LIST (LIEES_A_TRIANGULE) LONG      = Array[3, 128880]</computeroutput>
437  <prompt>&promptidl;</prompt> <userinput><command>tvplus, glamt*tmask[*,*,0]</command></userinput>
438  <prompt>&promptidl;</prompt> <userinput><command>tvplus, gphit*tmask[*,*,0]</command></userinput>
439          </screen>
440          We provide other initialization methods/examples
441          <itemizedlist>
442            <listitem><simpara><ulink type="text" url="../../Tests/tst_initorca2_short.pro">@tst_initorca2_short</ulink> : ORCA2 example</simpara></listitem>
443            <listitem><simpara><ulink type="text" url="../../Tests/tst_initorca05_short.pro">@tst_initorca05_short</ulink> : ORCA05 example</simpara></listitem>
444            <listitem><simpara><ulink type="text" url="../../Tests/tst_initlev_stride.pro">@tst_initlev_stride</ulink> : same as @tst_initlev but we skip on point over 2 in x and y direction</simpara></listitem>
445            <listitem><simpara><ulink type="text" url="../../Tests/tst_initorca2_short_stride.pro">@tst_initorca2_short_stride</ulink> : ORCA2 with stride</simpara></listitem>
446            <listitem><simpara><ulink type="text" url="../../Tests/tst_initorca05_short_stride.pro">@tst_initorca05_short_stride</ulink> : ORCA05 with stride</simpara></listitem>
447            <listitem><simpara><ulink type="text" url="../../Tests/tst_initlev_index.pro">@tst_initlev_index</ulink> : in that case we load the grid using points index as axis instead of the longitude/latitude position</simpara></listitem>
448            <listitem><simpara><ulink type="text" url="../../Tests/tst_initorca2_index.pro">@tst_initorca2_index</ulink> : load ORCA2 as it see by the model</simpara></listitem>
449            <listitem><simpara><ulink type="text" url="../../Tests/tst_initorca05_index.pro">@tst_initorca05_index</ulink> : load ORCA05 as it see by the model</simpara></listitem>
450            <listitem><simpara><ulink type="text" url="../../Tests/tst_initlev_index_stride.pro">@tst_initlev_index_stride</ulink> : @tst_initlev_index with stride</simpara></listitem>
451            <listitem><simpara><ulink type="text" url="../../Tests/tst_initorca2_index_stride.pro">@tst_initorca2_index_stride</ulink> : ORCA2 in index with stride</simpara></listitem>
452            <listitem><simpara><ulink type="text" url="../../Tests/tst_initorca05_index_stride.pro">@tst_initorca05_index_stride</ulink> : ORCA05 in index with stride</simpara></listitem>
453          </itemizedlist>
454        </para>
455      </sect3>
456      <sect3 id="load_meshmask">
457        <title>
458          Load the grid from OPA <filename>meshmask</filename> file
459        </title>
460        <para>
461          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 <link linkend="load_fromdata">grid definition from the data itself</link> (with <filename>initncdf</filename> or <filename>computegrid</filename>), 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.
462          <itemizedlist>
463            <listitem><simpara><ulink type="text" url="../../Tests/tst_initorca2.pro">@tst_initorca2</ulink> : ORCA2</simpara></listitem>
464            <listitem><simpara><ulink type="text" url="../../Tests/tst_initorca05.pro">@tst_initorca05</ulink> : ORCA05</simpara></listitem>
465            <listitem><simpara><ulink type="text" url="../../Tests/tst_initorca2_stride.pro">@tst_initorca2_stride</ulink> : ORCA2 with stride</simpara></listitem>
466            <listitem><simpara><ulink type="text" url="../../Tests/tst_initorca05_stride.pro">@tst_initorca05_stride</ulink> : ORCA05 with stride</simpara></listitem>
467            <listitem><simpara><ulink type="text" url="../../Tests/tst_initorca2_index.pro">@tst_initorca2_index</ulink> : load ORCA2 as it see by the model</simpara></listitem>
468            <listitem><simpara><ulink type="text" url="../../Tests/tst_initorca05_index.pro">@tst_initorca05_index</ulink> : load ORCA05 as it see by the model</simpara></listitem>
469            <listitem><simpara><ulink type="text" url="../../Tests/tst_initorca2_index_stride.pro">@tst_initorca2_index_stride</ulink> : ORCA2 in index with stride</simpara></listitem>
470            <listitem><simpara><ulink type="text" url="../../Tests/tst_initorca05_index_stride.pro">@tst_initorca05_index_stride</ulink> : ORCA05 in index with stride</simpara></listitem>
471          </itemizedlist>
472        </para>
473        </sect3>
474    </sect2>
475
476    <sect2 id="plt">
477      <title>
478        Horizontal plots and maps
479      </title>
480        <para>
481          A quick presentation of horizontal plots and maps is shown in <ulink type="text" url="../../Tests/tst_plt.pro">tst_plt</ulink>. After loading any of the grid (for example with one of the <link linkend="load_grid">above examples</link>). Just try:
482          <screen format="linespecific">
483  <prompt>&promptidl;</prompt> <userinput><command>tst_plt</command></userinput>
484          </screen>
485        </para>
486        <simpara><emphasis>Beware, the command is <command>tst_plt</command> and not <command>@tst_plt</command> as <filename>tst_plt.pro</filename> is a procedure and not an include.</emphasis></simpara>
487        <para>
488          See the results with
489          <itemizedlist>
490          <listitem><simpara><command>@tst_initlev</command>&figsplt_lev;</simpara></listitem>
491          <listitem><simpara><command>@tst_initorca2</command>&figsplt_orca2;</simpara></listitem>
492          <listitem><simpara><command>@tst_initorca05</command>&figsplt_orca05;</simpara></listitem>
493          <listitem><simpara><command>@tst_initlev_stride</command>&figsplt_lev_stride;</simpara></listitem>
494          <listitem><simpara><command>@tst_initorca2_stride</command>&figsplt_orca2_stride;</simpara></listitem>
495          <listitem><simpara><command>@tst_initorca05_stride</command>&figsplt_orca05_stride;</simpara></listitem>
496          </itemizedlist>
497        </para>
498    </sect2>
499
500    <sect2 id="pltz">
501      <title>
502        Vertical sections
503      </title>
504        <para>
505          A quick presentation of vertical sections is shown in <ulink type="text" url="../../Tests/tst_pltz.pro">tst_pltz</ulink>. After loading any of the grid (for example with one of the <link linkend="load_grid">above examples</link>). Just try:
506          <screen format="linespecific">
507  <prompt>&promptidl;</prompt> <userinput><command>tst_pltz</command></userinput>
508          </screen>
509        </para>
510          <simpara><emphasis>Beware, the command is <command>tst_pltz</command> and not <command>@tst_pltz</command> as <filename>tst_pltz.pro</filename> is a procedure and not an include.</emphasis></simpara>
511        <para>
512          See the results with
513          <itemizedlist>
514          <listitem><simpara><command>@tst_initlev</command>&figspltz_lev;</simpara></listitem>
515          <listitem><simpara><command>@tst_initorca2</command>&figspltz_orca2;</simpara></listitem>
516          <listitem><simpara><command>@tst_initorca05</command>&figspltz_orca05;</simpara></listitem>
517          <listitem><simpara><command>@tst_initlev_stride</command>&figspltz_lev_stride;</simpara></listitem>
518          <listitem><simpara><command>@tst_initorca2_stride</command>&figspltz_orca2_stride;</simpara></listitem>
519          <listitem><simpara><command>@tst_initorca05_stride</command>&figspltz_orca05_stride;</simpara></listitem>
520          </itemizedlist>
521        </para>
522    </sect2>
523
524    <sect2 id="pltt">
525      <title>
526        Hovmoellers and time series
527      </title>
528        <para>
529          A quick presentation of hovmoellers and time series is shown in <ulink type="text" url="../../Tests/tst_pltt.pro">tst_pltt</ulink>. After loading any of the grid (for example with one of the <link linkend="load_grid">above examples</link>). Just try:
530          <screen format="linespecific">
531  <prompt>&promptidl;</prompt> <userinput><command>tst_pltt</command></userinput>
532          </screen>
533        </para>
534          <simpara><emphasis>Beware, the command is <command>tst_pltt</command> and not <command>@tst_pltt</command> as <filename>tst_pltt.pro</filename> is a procedure and not an include.</emphasis></simpara>
535        <para>
536          See the results with
537          <itemizedlist>
538          <listitem><simpara><command>@tst_initlev</command>&figspltt_lev;</simpara></listitem>
539          <listitem><simpara><command>@tst_initorca2</command>&figspltt_orca2;</simpara></listitem>
540          <listitem><simpara><command>@tst_initorca05</command>&figspltt_orca05;</simpara></listitem>
541          <listitem><simpara><command>@tst_initlev_stride</command>&figspltt_lev_stride;</simpara></listitem>
542          <listitem><simpara><command>@tst_initorca2_stride</command>&figspltt_orca2_stride;</simpara></listitem>
543          <listitem><simpara><command>@tst_initorca05_stride</command>&figspltt_orca05_stride;</simpara></listitem>
544          </itemizedlist>
545        </para>
546    </sect2>
547
548    <sect2 id="plt1d">
549      <title>
550        1D plots
551      </title>
552        <para>
553          To be continued &hellip;
554        </para>
555   </sect2>
556
557
558  </sect1>
559
560</article>
Note: See TracBrowser for help on using the repository browser.