Index: /trunk/SRC/Documentation/xmldoc/forxxxdoc.sh
===================================================================
--- /trunk/SRC/Documentation/xmldoc/forxxxdoc.sh	(revision 144)
+++ /trunk/SRC/Documentation/xmldoc/forxxxdoc.sh	(revision 144)
@@ -0,0 +1,198 @@
+#! /bin/sh
+#
+# module :
+# add frame and callouts image to an existing one
+#
+# !! exists only because graphics callouts are not yet avalaible
+# with xsl processing on XML/Docbook files (xsl stylesheet 1.70 and
+# DocBook DTD 4.2)
+#
+# thanks to the authors of the following web pages
+# http://www.win.tue.nl/~aeb/linux/misc/convert/convert-draw-text.html
+# http://www.cit.gu.edu.au/~anthony/graphics/imagick6/draw/
+# http://www.cit.gu.edu.au/~anthony/graphics/imagick6/annotating/
+#
+# update :
+# $Id$
+# fplod 2006-07-20T16:05:19Z aedon.locean-ipsl.upmc.fr (Darwin)
+# add a parameter = the number of figpng/xxx_n.png
+# fplod 2006-07-19T12:40:02Z aedon.locean-ipsl.upmc.fr (Darwin)
+# first release 
+#
+#
+set -u
+set -o posix
+#
+case "${1}" in
+1|2)
+# screen capture to be commented by frames and callouts images
+capture="figpng/xxx_${1}.png"
+;;
+*)
+  echo "eee : unknown parameter ${1}"
+  exit 1
+;;
+esac
+#
+if [ ! -f ${capture} ]
+then
+  echo " eee : ${capture} not found"
+  exit 1
+fi
+#
+#
+callout_path=images/callouts/
+callout_xsize=12 # ++ should be obtain by parsing identify result
+callout_ysize=12 # ++ should be obtain by parsing identify result
+#
+case ${capture} in 
+figpng/xxx_2.png)
+capture_xsize=1211 #++ should be obtain by parsing identify result
+capture_ysize=630 #++ should be obtain by parsing identify result
+#
+# description of frames (title, xmin,ymin, xmax,ymax)
+# nb : title and label are not yet used but they may be added in a kind of 
+# comments
+# later in xml as id or label
+# now they are only here to remind us what we do
+zone_nb=4
+zone_t[1]="Page layout"
+zone_l[1]="pagelayout"
+zone_rect[1]="70,55 200,80"
+zone_t[2]="Calendar"
+zone_l[2]="calendar"
+zone_rect[2]="10,140 230,180"
+zone_t[3]="Domain"
+zone_l[3]="domain"
+zone_rect[3]="10,200 300,400"
+zone_t[4]="Specify"
+zone_l[4]="specify"
+zone_rect[4]="10,450 350,500"
+#
+# the next three lines are here to check calcultation of CALSPAIR units
+# see http://www.docbook.org/tdg/en/html/area.html
+# if you want to use it, please add one to zone_nb
+zone_t[5]="just to check full size rectangle"
+zone_l[5]="check"
+zone_rect[5]="0,0 ${capture_xsize},${capture_ysize}"
+;;
+figpng/xxx_1.png)
+capture_xsize=520 #++ should be obtain by parsing identify result
+capture_ysize=309 #++ should be obtain by parsing identify result
+#
+# description of frames (title, xmin,ymin, xmax,ymax)
+# nb : title and label are not yet used but they may be added in a kind of 
+# comments
+# later in xml as id or label
+# now they are only here to remind us what we do
+zone_nb=2
+zone_t[1]="Data file"
+zone_l[1]="datafile"
+zone_rect[1]="5,55 515,90"
+zone_t[2]="Init file"
+zone_l[2]="initfile"
+zone_rect[2]="5,150 515,200"
+;;
+*)
+   echo " eee : ${capture} not implemented"
+   exit 3
+;;
+esac
+
+#
+# calculation of % of the rectangle of each zone for Calspair 
+iz=1
+while [ ${iz} -le ${zone_nb} ]
+do
+   xymin=$(echo ${zone_rect[${iz}]} | awk '{print $1}')
+   xymax=$(echo ${zone_rect[${iz}]} | awk '{print $2}')
+   xmin=$(echo ${xymin} | awk -F "," '{print $1}')
+   xmax=$(echo ${xymax} | awk -F "," '{print $1}')
+   ymin=$(echo ${xymin} | awk -F "," '{print $2}')
+   ymax=$(echo ${xymax} | awk -F "," '{print $2}')
+   xmin_pc=$(echo "(${xmin} / ${capture_xsize}) * 10000" | bc -l)
+   xmin_pc=$(echo ${xmin_pc} } | awk -F "." '{print $1}')
+   ymin_pc=$(echo "(${ymin} / ${capture_ysize}) * 10000" | bc -l)
+   ymin_pc=$(echo ${ymin_pc} } | awk -F "." '{print $1}')
+   xmax_pc=$(echo "(${xmax} / ${capture_xsize}) * 10000" | bc -l)
+   xmax_pc=$(echo ${xmax_pc} } | awk -F "." '{print $1}')
+   ymax_pc=$(echo "(${ymax} / ${capture_ysize}) * 10000" | bc -l)
+   ymax_pc=$(echo ${ymax_pc} } | awk -F "." '{print $1}')
+   #echo "xmin_pc zone ${iz} = ${xmin_pc}"
+   #echo "ymin_pc zone ${iz} = ${ymin_pc}"
+   #echo "xmax_pc zone ${iz} = ${xmax_pc}"
+   #echo "ymax_pc zone ${iz} = ${ymax_pc}"
+   #read a
+   zone_rect_pc[${iz}]="${xmin_pc},${ymin_pc} ${xmax_pc},${ymax_pc}"
+   iz=$(( ${iz} + 1 ))
+done
+# build the new image ie build the convert command to be run
+# first part : use the capture image and prepare black border and white
+# rectangles insertion
+cmd="convert -size ${capture_xsize}x${capture_ysize} \
+    ${capture} \
+    -linewidth 2 \
+    -stroke black \
+    -fill transparent"
+#
+# then loop on the frames to be drawed
+iz=1
+while [ ${iz} -le ${zone_nb} ]
+do
+   leftcorner=$(echo ${zone_rect[${iz}]} | awk '{print $1}')
+   cmd="${cmd} -draw \"rectangle ${zone_rect[${iz}]}\" \
+   -draw \"image over ${leftcorner} ${callout_xsize},${callout_ysize} 'images/callouts/${iz}.png'\""
+   iz=$(( ${iz} + 1 ))
+done
+#
+# last component of the convert command : the name of the output image
+framecallouts=$(dirname ${capture})/$(basename ${capture} .png)_complete.png
+cmd="${cmd} ${framecallouts}"
+#
+#echo "cmd = ${cmd}"
+#read a
+#
+# run the convert command
+eval ${cmd}
+convert_status=${?}
+if [ ${convert_status} -ne 0 ]
+then
+   echo " eee : convert doesn't work properly"  >> ${log} 
+   echo " eee : return status = ${return_convert}"  >> ${log}
+   exit 2
+fi
+echo " iii : image ${framecallouts} is ready"
+echo " iii : you can add the following lines in XML/Docbook"
+cat << EOF
+<imageobjectco>
+<areaspec units="calspair">
+EOF
+iz=1
+while [ ${iz} -le ${zone_nb} ]
+do
+   echo "<area id=\"${zone_l[${iz}]}\" coords=\"${zone_rect_pc[${iz}]}\"/>"
+   iz=$(( ${iz} + 1 ))
+done
+cat << EOF
+</areaspec>
+<imageobject>
+<imagedata fileref="${framecallouts}"/> <!-- ++ instead of ${capture} -->
+</imageobject>
+<calloutlist>
+EOF
+iz=1
+while [ ${iz} -le ${zone_nb} ]
+do
+   cat << EOF
+<callout arearefs="${zone_l[${iz}]}">
+<para>${zone_t[${iz}]}</para>
+</callout>
+EOF
+   iz=$(( ${iz} + 1 ))
+done
+cat << EOF
+</calloutlist>
+</imageobjectco>
+EOF
+#
+exit 0
Index: /trunk/SRC/Documentation/xmldoc/getsaxo.html
===================================================================
--- /trunk/SRC/Documentation/xmldoc/getsaxo.html	(revision 143)
+++ /trunk/SRC/Documentation/xmldoc/getsaxo.html	(revision 144)
@@ -159,5 +159,5 @@
 <dl>
 <dt><span class="term"><span class=
-"bold"><strong>IDRIS</strong></span>&gt;</span></dt>
+"bold"><strong>IDRIS</strong></span></span></dt>
 <dd>
 <pre class="screen">
@@ -219,5 +219,5 @@
 </div>
 <p>The <span class="bold"><strong>complete</strong></span> latest
-revision (source + tests data files: 779 Mb) can be checked out
+revision (source + tests data files: 780 Mb) can be checked out
 with the following command executed in your <code class=
 "envar">${HOME}</code>:</p>
@@ -261,7 +261,7 @@
 </div>
 </div>
-<p><span class="bold"><strong>Contributors</strong></span>&gt;
-should better use the following command (and replace login by your
-own login):</p>
+<p><span class="bold"><strong>Contributors</strong></span> should
+better use the following command (and replace login by your own
+login):</p>
 <pre class="screen">
   <code class="prompt">$</code> <strong class=
@@ -528,6 +528,7 @@
 </div>
 </div>
-<p>You are now ready to do your <a href="firststeps.html" target=
-"_top">First steps with SAXO</a>.</p>
+<p>You are now ready to do your <a href=
+"firststeps.html?format=raw" target="_top">First steps with
+SAXO</a>.</p>
 </div>
 </div>
Index: /trunk/SRC/Documentation/xmldoc/getsaxo.xml
===================================================================
--- /trunk/SRC/Documentation/xmldoc/getsaxo.xml	(revision 143)
+++ /trunk/SRC/Documentation/xmldoc/getsaxo.xml	(revision 144)
@@ -90,5 +90,5 @@
 	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:
 	<variablelist>
-	  <varlistentry><term><emphasis role="bold">IDRIS</emphasis>></term>
+	  <varlistentry><term><emphasis role="bold">IDRIS</emphasis></term>
 	  <listitem><screen>
   <prompt>$</prompt> <userinput><command>ln</command> <option>-s</option> <parameter>/home/rech/eee/reee217/SAXO_DIR</parameter> <parameter><envar>${HOME}</envar>/SAXO_DIR</parameter></userinput>
@@ -148,5 +148,5 @@
 	</title>
       <para>
-	<emphasis role="bold">Contributors</emphasis>> should better use the following command (and replace login by your own login):
+	<emphasis role="bold">Contributors</emphasis> should better use the following command (and replace login by your own login):
 	<screen  format="linespecific">
   <prompt>$</prompt> <userinput><command>svn</command> <option>checkout</option> <parameter>svn+ssh://<replaceable>login</replaceable>@forge.ipsl.jussieu.fr/ipsl/forge/projets/saxo/svn/trunk/</parameter> <parameter>SAXO_DIR</parameter></userinput>
@@ -341,5 +341,5 @@
 <para>
 You are now ready to do your 
-<ulink url="firststeps.html">First steps with SAXO</ulink>.
+<ulink url="firststeps.html?format=raw">First steps with SAXO</ulink>.
 </para>
 </sect1>
Index: /trunk/SRC/Documentation/xmldoc/makehtml.sh
===================================================================
--- /trunk/SRC/Documentation/xmldoc/makehtml.sh	(revision 143)
+++ /trunk/SRC/Documentation/xmldoc/makehtml.sh	(revision 144)
@@ -8,4 +8,6 @@
 # released on 1 September 2005) doesn't handle carriage returns
 #
+# fplod 2006-07-21T08:25:05Z aedon.locean-ipsl.upmc.fr (Darwin)
+# add prerequisites for mini_notice production
 # fplod 2006-07-12T11:57:24Z aedon.locean-ipsl.upmc.fr (Darwin)
 # add style.css
@@ -85,6 +87,11 @@
       sed -e "s/\(^.* THEN \)\(.*\)\( = \)\(.*\)/<row><entry colname='old'><varname>\2<\/varname><\/entry> <entry colname='new'><varname>\4<\/varname><\/entry><\/row>/" > /tmp/rowscm.xml
    ;;
+   mini_notice)
+      # production of images with frames and callouts
+      ./forxxxdoc.sh 1
+      ./forxxxdoc.sh 2
+   ;;
    *)
-      echo "iii : no ndate determination needed"
+      echo "iii : no prerequisites needed"
    ;;
 esac
Index: /trunk/SRC/Documentation/xmldoc/mini_notice.html
===================================================================
--- /trunk/SRC/Documentation/xmldoc/mini_notice.html	(revision 144)
+++ /trunk/SRC/Documentation/xmldoc/mini_notice.html	(revision 144)
@@ -0,0 +1,946 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+<meta name="generator" content=
+"HTML Tidy for Mac OS X (vers 1 September 2005), see www.w3.org">
+<meta http-equiv="Content-Type" content=
+"text/html; charset=us-ascii">
+<title>Mini Guide for Basic Commands in the XXX Program</title>
+<link rel="stylesheet" href="style.css" type="text/css">
+<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, xxx">
+</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" id="d0e2"></a> Mini Guide for
+Basic Commands in the XXX Program</h2>
+</div>
+<div>
+<div class="authorgroup">
+<div class="author">
+<h3 class="author"><span class="firstname">S&eacute;bastien</span>
+<span class="surname">Masson</span> <code class=
+"email">&lt;<a href="mailto:Sebastien.Masson_at_locean-ipsl.upmc.fr">Sebastien.Masson_at_locean-ipsl.upmc.fr</a>&gt;</code></h3>
+</div>
+<div class="author">
+<h3 class="author"><span class="firstname">Albert</span>
+<span class="surname">Fisher</span></h3>
+</div>
+<div class="author">
+<h3 class="author"><span class="firstname">Fran&ccedil;oise</span>
+<span class="surname">Pinsard</span> <code class=
+"email">&lt;<a href=
+"mailto:Francoise.Pinsard_at_locean-ipsl.upmc.fr">Francoise.Pinsard_at_locean-ipsl.upmc.fr</a>&gt;</code></h3>
+</div>
+<div class="author">
+<h3 class="author"><span class="firstname">Steve</span>
+<span class="surname">Navarro</span></h3>
+</div>
+</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>
+<tr>
+<td align="left">Revision 0.0</td>
+<td align="left">May 29, 2000</td>
+</tr>
+<tr>
+<td align="left" colspan="2">French release by S&eacute;bastien
+Masson</td>
+</tr>
+<tr>
+<td align="left">Revision 0.1</td>
+<td align="left">July, 2002</td>
+</tr>
+<tr>
+<td align="left" colspan="2">Translation by Albert Fisher</td>
+</tr>
+<tr>
+<td align="left">Revision 0.2</td>
+<td align="left">July 20, 2006</td>
+</tr>
+<tr>
+<td align="left" colspan="2">HTML to XML/Docbook migration by
+Fran&ccedil;oise Pinsard</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="#intro">1. Introduction and
+assumptions</a></span></dt>
+<dt><span class="sect1"><a href="#beforefirststeps">2. Before
+this</a></span></dt>
+<dt><span class="sect1"><a href="#initfiles">3. Install the files
+<code class="filename">init.pro</code> and <code class=
+"filename">initgrid.pro</code></a></span></dt>
+<dd>
+<dl>
+<dt><span class="sect2"><a href="#modifinitgrid">3.1. Modification
+or creation of the <code class="filename">initgrid.pro</code>
+script</a></span></dt>
+</dl>
+</dd>
+<dt><span class="sect1"><a href="#introxxx">4. Starting the
+<span class="application">SAXO</span> package and an explanation of
+the XXX widget functions</a></span></dt>
+<dd>
+<dl>
+<dt><span class="sect2"><a href="#launchxxx">4.1. Launching
+XXX</a></span></dt>
+<dt><span class="sect2"><a href="#wigdets">4.2. An explanation of
+the different widgets</a></span></dt>
+</dl>
+</dd>
+<dt><span class="sect1"><a href="#examples">5. Concrete examples of
+XXX in practice</a></span></dt>
+<dd>
+<dl>
+<dt><span class="sect2"><a href="#example1">5.1. First
+plots</a></span></dt>
+<dt><span class="sect2"><a href="#example2">5.2. Work with more
+than one file</a></span></dt>
+<dt><span class="sect2"><a href="#mouse">5.3. Mouse actions in the
+graphics window on a horizontal plot</a></span></dt>
+<dt><span class="sect2"><a href="#multipleplots">5.4. Create
+multiple plots on the same sheet and make them
+interact</a></span></dt>
+</dl>
+</dd>
+<dt><span class="sect1"><a href="#crash">6. How to quit when it
+crashes</a></span></dt>
+</dl>
+</div>
+<div class="sect1" lang="en">
+<div class="titlepage">
+<div>
+<div>
+<h2 class="title" style="clear: both"><a name="intro" id=
+"intro"></a>1.&nbsp;Introduction and assumptions</h2>
+</div>
+</div>
+</div>
+<p>This micro guide is unfortunately not a user's guide for all the
+scripts that have been written for IDL (version 5.2 or higher
+required). The goal is simply to clarify a few points on the use of
+the <code class="filename">xxx.pro</code> program.</p>
+<p>For further help on the furnished scripts, here are several
+possibilities:</p>
+<div class="itemizedlist">
+<ul type="disc">
+<li>
+<p>execute in IDL the command</p>
+<pre class="screen">
+<code class="prompt">idl&gt;</code> <strong class=
+"userinput"><code>xhelp, '<em class=
+"replaceable"><code>script_name</code></em>'</code></strong>
+</pre></li>
+<li>
+<p>consult the IDL online help for scripts whose source is
+unavailable</p>
+</li>
+<li>
+<p>subscribe to the mailing list for updates and user
+questions/responses</p>
+<p>to subscribe, send a mail to: <a href=
+"mailto:majordomo@lmd.jussieu.fr" target=
+"_top">majordomo@lmd.jussieu.fr</a> with no subject, containing the
+message: <strong class="userinput"><code>subscribe forum-idl
+<em class="replaceable"><code>e-mail
+address</code></em></code></strong></p>
+</li>
+<li>
+<p>consult the archives of this mail list: <a href=
+"http://www.lmd.jussieu.fr/archives/form-idl/last/mail1.html"
+target=
+"_top">http://www.lmd.jussieu.fr/archives/form-idl/last/mail1.html</a></p>
+</li>
+<li>
+<p>consult in desperation the feeble web pages we have started to
+write (while waiting for something better) <a href=
+"http://www.ipsl.jussieu.fr/~smlod/" target=
+"_top">http://www.ipsl.jussieu.fr/~smlod/</a></p>
+</li>
+<li>
+<p>wait until we write a full user's manual!</p>
+</li>
+</ul>
+</div>
+<p>The XXX widget is a layer on top of the scripts in the
+<span class="application">SAXO</span> package (themselves layered
+on top of IDL). It is designed to permit the visualization and
+rapid exploration of data, offering a maximum in options, while not
+necessarily all those offered by the package and by IDL.</p>
+<p>Based on the use of files in the NetCDF format, it can easily
+work with other file formats. For this, all that is necessary is to
+write an IDL function capable of extracting a matrix from a file as
+a function of the following parameters: the variable name, two
+dates, an experiment name, and a domain.</p>
+<p>Developed to visualize the output of the OPA model, the
+<span class="application">SAXO</span> package was conceived to work
+on C grids. To use it on grids where the T, U, and V points are the
+same, one must nevertheless declare the parameters of the grid that
+correspond to the U and V points. Careful, for this type of
+discretization, the calculation scripts of type <code class=
+"filename">div.pro</code> and <code class=
+"filename">curl.pro</code> are wrong.</p>
+<p>The averaging routines are not adapted to warped grids, they sum
+following the i, j, and k indices, weighting each point by scale
+factors and the land-sea mask. Slices and Hovmoellers do not work
+in the diagonal, but are always done following i, j, or k. When a
+domain is given to one of the scripts, an average over the domain
+in the directions perpendicular to that displayed is automatically
+made before display.</p>
+<p>Before continuing on to the practical part of this guide, the
+installation and use of the <span class="application">SAXO</span>
+package, I'd like to thank Guillaume Roullet, who also participated
+in the writing of the scripts in the package (notably the drawing
+of vectors on warped grids).</p>
+</div>
+<div class="sect1" lang="en">
+<div class="titlepage">
+<div>
+<div>
+<h2 class="title" style="clear: both"><a name="beforefirststeps"
+id="beforefirststeps"></a>2.&nbsp;Before this</h2>
+</div>
+</div>
+</div>
+<p>In this document, we supposed that you followed <a href=
+"getsaxo.html" target="_top">Get SAXO</a> recommandations.</p>
+</div>
+<div class="sect1" lang="en">
+<div class="titlepage">
+<div>
+<div>
+<h2 class="title" style="clear: both"><a name="initfiles" id=
+"initfiles"></a>3.&nbsp;Install the files <code class=
+"filename">init.pro</code> and <code class=
+"filename">initgrid.pro</code></h2>
+</div>
+</div>
+</div>
+<p>This version of the <span class="application">SAXO</span>
+package depends a certain number of common variables that are
+primarily environmental parameters (working paths, color
+management, Postscript formatting) and the parameters of the grid
+on which you are working (longitude, latitude, depth, land-sea
+mask, scale factors, position of the zoom in relation to the
+original grid).</p>
+<p>These two types of parameters are kept separately:</p>
+<div class="itemizedlist">
+<ul type="disc">
+<li>
+<p>environmental parameters are defined at the very beginning of
+the IDL session, and are in principle never changed. They are
+initialized by the <code class="filename">init.pro</code>
+script.</p>
+</li>
+<li>
+<p>Those that belong to the grid are reinitialized every time the
+grid is changed. They can therefore be called at any time during a
+session. These parameters are initialized by the <code class=
+"filename">initgrid.pro</code> scripts, and are specific to each
+particular grid.</p>
+<p>For example: <code class="filename">initorca.pro</code> for the
+ORCA 2&deg; grid, <code class="filename">initorca05.pro</code> for
+the ORCA 0.5&deg; grid, or <code class=
+"filename">initorcapac.pro</code> for the ORCA grid zoomed on the
+Pacific.</p>
+</li>
+</ul>
+</div>
+<p>To begin, one must therefore copy <code class=
+"filename"><em class=
+"replaceable"><code>packagedir</code></em>/INIT/init.pro</code>
+into <em class="replaceable"><code>homedir</code></em>, and create
+in <em class="replaceable"><code>homedir</code></em> a script of
+the type <code class="filename">initgrid.pro</code>.</p>
+<div class="sect2" lang="en">
+<div class="titlepage">
+<div>
+<div>
+<h3 class="title"><a name="modifinitgrid" id=
+"modifinitgrid"></a>3.1.&nbsp;Modification or creation of the
+<code class="filename">initgrid.pro</code> script</h3>
+</div>
+</div>
+</div>
+<p>In the <em class="replaceable"><code>packagedir</code></em>/INIT
+directory you will find a certain number of scripts associated with
+the latest grids on which I've worked. If you are also working on
+one of these grids, for example ORCA, copy the file <code class=
+"filename"><em class=
+"replaceable"><code>packagedir</code></em>/INIT/initorca.pro</code>
+to your <em class="replaceable"><code>homedir</code></em>. If not,
+copy it nevertheless to use as a model. In the file <code class=
+"filename">initgrid.pro</code>, adjust the zoom parameters (if it
+has not already been done).</p>
+<p>Careful: unlike in previous versions of the <span class=
+"application">SAXO</span> package, all the zoom parameters must be
+defined. If you do not know them in advance, define their values to
+be -1.</p>
+<p>In the rest of the script, define iodir as <em class=
+"replaceable"><code>iodir</code></em>, and verify the name of the
+mask file, if one exists.</p>
+</div>
+</div>
+<div class="sect1" lang="en">
+<div class="titlepage">
+<div>
+<div>
+<h2 class="title" style="clear: both"><a name="introxxx" id=
+"introxxx"></a>4.&nbsp;Starting the <span class=
+"application">SAXO</span> package and an explanation of the XXX
+widget functions</h2>
+</div>
+</div>
+</div>
+<div class="sect2" lang="en">
+<div class="titlepage">
+<div>
+<div>
+<h3 class="title"><a name="launchxxx" id=
+"launchxxx"></a>4.1.&nbsp;Launching XXX</h3>
+</div>
+</div>
+</div>
+<p>The first command to type is</p>
+<pre class="screen">
+<code class="prompt">idl&gt;</code> <strong class=
+"userinput"><code>@init</code></strong>
+</pre>
+<p>Afterwards, to work directly with XXX, type:</p>
+<pre class="screen">
+
+<code class="prompt">idl&gt;</code> <strong class=
+"userinput"><code>xxx</code></strong>
+</pre>
+<p>To work without the XXX interface, initialize a grid</p>
+<pre class="screen">
+
+<code class="prompt">idl&gt;</code> <strong class=
+"userinput"><code>@initgrid</code></strong>
+</pre>
+<p>A window will open with 2 lines to complete.</p>
+<div class="figure"><a name="fig_xxx_1" id="fig_xxx_1"></a>
+<p class="title"><b>Figure&nbsp;1.&nbsp;Window xxx 1</b></p>
+<div class="figure-contents">
+<div class="mediaobjectco"><img border="0" usemap="d0e293" src=
+"figpng/xxx_1_complete.png" alt="Window xxx 1"><map name="d0e293"
+id="d0e293">
+<area shape="rect" coords="5,254,515,219">
+<area shape="rect" coords="5,159,515,109"></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">
+<p>datafile</p>
+</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">
+<p>initfile</p>
+</td>
+</tr>
+</table>
+</div>
+</div>
+</div>
+</div>
+<p><br class="figure-break"></p>
+<p>These lines must contain the address of a file. The name can be
+typed directly in the window provided, or selected with the help of
+the <span class="guibutton">browse</span> button. The first line
+must contain the name of the data file, the second the name of the
+<code class="filename">initgrid.pro</code> script which will permit
+the reading and processing of the grid associated with the data
+file.</p>
+<p>Once these two lines have been completed, click on <span class=
+"guibutton">let's go</span>. Two other windows will then open,
+giving you the parameters for reading the grid and the file (these
+parameters are read in the <code class=
+"filename">initgrid.pro</code> script). Click twice on <span class=
+"guibutton">OK</span>.</p>
+</div>
+<div class="sect2" lang="en">
+<div class="titlepage">
+<div>
+<div>
+<h3 class="title"><a name="wigdets" id="wigdets"></a>4.2.&nbsp;An
+explanation of the different widgets</h3>
+</div>
+</div>
+</div>
+<p>Now the XXX window will open.</p>
+<div class="figure"><a name="fig_xxx_2" id="fig_xxx_2"></a>
+<p class="title"><b>Figure&nbsp;2.&nbsp;Window xxx 2</b></p>
+<div class="figure-contents">
+<div class="mediaobjectco"><img border="0" usemap="d0e340" src=
+"figpng/xxx_2_complete.png" alt="Window xxx 2"><map name="d0e340"
+id="d0e340">
+<area shape="rect" coords="70,575,200,550">
+<area shape="rect" coords="10,490,230,450">
+<area shape="rect" coords="10,430,300,230">
+<area shape="rect" coords="10,180,350,130"></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">
+<p>Page layout</p>
+</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">
+<p>Calendar</p>
+</td>
+</tr>
+<tr>
+<td width="5%" valign="top" align="left"><img src=
+"images/callouts/3.png" alt="3" border="0"></td>
+<td valign="top" align="left">
+<p>Domain</p>
+</td>
+</tr>
+<tr>
+<td width="5%" valign="top" align="left"><img src=
+"images/callouts/4.png" alt="4" border="0"></td>
+<td valign="top" align="left">
+<p>Specify</p>
+</td>
+</tr>
+</table>
+</div>
+</div>
+</div>
+</div>
+<p><br class="figure-break"></p>
+<p>It's configuration will change depending on whether you are in
+portrait or in landscape, but here are the different parts
+available for your use.</p>
+<div class="sect3" lang="en">
+<div class="titlepage">
+<div>
+<div>
+<h4 class="title"><a name="menubar" id=
+"menubar"></a>4.2.1.&nbsp;The menu bar made up of 3 submenus</h4>
+</div>
+</div>
+</div>
+<div class="sect4" lang="en">
+<div class="titlepage">
+<div>
+<div>
+<h5 class="title"><a name="filesubmenu" id=
+"filesubmenu"></a>4.2.1.1.&nbsp;<span class=
+"guisubmenu">File</span> submenu</h5>
+</div>
+</div>
+</div>
+<div class="itemizedlist">
+<ul type="disc">
+<li>
+<p><span class="guimenuitem">Open:</span> to open a second file.
+Same procedure as during the launching of XXX. The new file can be
+on a different grid, with different variables, with a different
+time base.</p>
+</li>
+<li>
+<p><span class="guimenuitem">New XXX:</span> to open a second XXX
+window identical to the first.</p>
+</li>
+<li>
+<p><span class="guimenuitem">Close:</span> to close the XXX
+window.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect4" lang="en">
+<div class="titlepage">
+<div>
+<div>
+<h5 class="title"><a name="saveassubmenu" id=
+"saveassubmenu"></a>4.2.1.2.&nbsp;<span class="guisubmenu">Save
+As</span> submenu</h5>
+</div>
+</div>
+</div>
+<div class="itemizedlist">
+<ul type="disc">
+<li>
+<p><span class="guimenuitem">Postscript:</span> to save in
+Postscript format</p>
+</li>
+<li>
+<p><span class="guimenuitem">Animations:</span> to create an
+animation from the XXX window. Careful, 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.</p>
+</li>
+<li>
+<p><span class="guimenuitem">Image:</span> to save a gif of the XXX
+graphics window.</p>
+</li>
+<li>
+<p><span class="guimenuitem">Script:</span> to save the command
+history that has created the plot. For example if I save the
+commands in <code class="filename">xxx_figure.pro</code>, I can
+then launch a new IDL session and type:</p>
+<pre class="screen">
+<code class="prompt">idl&gt;</code> <strong class=
+"userinput"><code>@init</code></strong>
+<code class="prompt">idl&gt;</code> <strong class=
+"userinput"><code>xxx_figure</code></strong>
+</pre>
+<p>and I'll obtain the saved figure.</p>
+<pre class="screen">
+<code class="prompt">idl&gt;</code> <strong class=
+"userinput"><code>xxx_figure,/post </code></strong>
+</pre>
+<p>or</p>
+<pre class="screen">
+<code class="prompt">idl&gt;</code> <strong class=
+"userinput"><code>@ps</code></strong>
+</pre>
+<p>will then create a Postscript file of the figure.</p>
+</li>
+<li>
+<p><span class="guimenuitem">Prompt:</span> lists in the IDL window
+the command history that created the last plot. Useful primarily
+for debugging...</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect4" lang="en">
+<div class="titlepage">
+<div>
+<div>
+<h5 class="title"><a name="flagsubmenu" id=
+"flagsubmenu"></a>4.2.1.3.&nbsp;<span class="guisubmenu">Flag
+options</span> submenu</h5>
+</div>
+</div>
+</div>
+<div class="itemizedlist">
+<ul type="disc">
+<li>
+<p><span class="guibutton">OK</span> To show/hide the OK button in
+the upper left corner.</p>
+</li>
+<li>
+<p><span class="guibutton">Portrait/Landscape:</span> changes the
+configuration of the plot.</p>
+</li>
+<li>
+<p><span class="guibutton">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="guibutton">Vecteur:</span> to plot a vector field
+on top of contours. Only works on horizontal plots (<code class=
+"filename">plt.pro</code>). As for Overlay, a relaunch of the
+entire plot is necessary.</p>
+</li>
+<li>
+<p><span class="guibutton">Longitude / x index:</span> switches
+longitude labelling of the plot subdomain from degrees to indices
+following i.</p>
+</li>
+<li>
+<p><span class="guibutton">Latitude / y index:</span> switches
+latitude labelling of the plot subdomain from degrees to indices
+following j.</p>
+</li>
+</ul>
+</div>
+</div>
+</div>
+<div class="sect3" lang="en">
+<div class="titlepage">
+<div>
+<div>
+<h4 class="title"><a name="typeplot" id=
+"typeplot"></a>4.2.2.&nbsp;What type of plot and where?</h4>
+</div>
+</div>
+</div>
+<div class="itemizedlist">
+<ul type="disc">
+<li>
+<p><span class="guibutton">OK</span> Show/hide the OK button in the
+upper left. When present, a click is required to make a new plot
+appear. Otherwise each action creates a new plot.</p>
+</li>
+<li>
+<p><span class="guimenuitem">Plot type list:</span> allows
+specification of the type of plot desired.</p>
+<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
+<h3 class="title">Note</h3>
+<p>If the type <code class="constant">plt</code> is selected, the
+selection of plot type is made by mouse. Cf <a href="#mouse" title=
+"5.3.&nbsp;Mouse actions in the graphics window on a horizontal plot">
+Section&nbsp;5.3, &ldquo;Mouse actions in the graphics window on a
+horizontal plot&rdquo;</a></p>
+</div>
+</li>
+<li>
+<p><span class="guimenuitem">Layout configuration:</span> specify
+the number of columns and rows for plots on the sheet of paper.
+There's no code behind the undo command! The <span class=
+"guibutton">clear</span> button erases all plots.</p>
+</li>
+<li>
+<p><span class="guimenuitem">List of open files:</span> you can
+choose the file to work on.</p>
+</li>
+<li>
+<p><span class="guimenuitem">Command window:</span> this window
+permits simple operations on the fields:</p>
+<p>for example:</p>
+<div class="literallayout">
+<p>toto&nbsp;-&nbsp;10*field&nbsp;+&nbsp;36</p>
+</div>
+<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
+<h3 class="title">Note</h3>
+<p>In the default case, the name given to a field is of no
+importance.</p>
+</div>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3" lang="en">
+<div class="titlepage">
+<div>
+<div>
+<h4 class="title"><a name="sect_calendar" id=
+"sect_calendar"></a>4.2.3.&nbsp;Calendar</h4>
+</div>
+</div>
+</div>
+<p>The calendar is made up of two droplists, which allow
+specification of two dates, the beginning and end of a time series,
+or the period over which to average before plotting.</p>
+</div>
+<div class="sect3" lang="en">
+<div class="titlepage">
+<div>
+<div>
+<h4 class="title"><a name="sect_domain" id=
+"sect_domain"></a>4.2.4.&nbsp;Domain specification</h4>
+</div>
+</div>
+</div>
+<p>A series of widgets that allow specification of the min/max
+limits of the domain in longitude/x-index, latitude/y-index, and
+depth in levels or meters. For depth, one can specify in levels for
+a horizontal plot, and in meters for a vertical plot.</p>
+</div>
+<div class="sect3" lang="en">
+<div class="titlepage">
+<div>
+<div>
+<h4 class="title"><a name="details" id=
+"details"></a>4.2.5.&nbsp;Plot details</h4>
+</div>
+</div>
+</div>
+<p>You can specify the min, max, and contour interval by filling
+out the provided boxes! For the color palette, you can either
+specify the name or go search for one among the palettes
+available.</p>
+<p>The "keywords" window allows specification of all desired
+keywords. These keywords can be those of <code class=
+"filename">plt.pro</code>, <code class="filename">pltt.pro</code>,
+<code class="filename">pltz.pro</code>, <code class=
+"filename">plt1d.pro</code>, or those of contour, plot, or all
+other programs that are used. Cf <a href="#example1" title=
+"5.1.&nbsp;First plots">Section&nbsp;5.1, &ldquo;First
+plots&rdquo;</a></p>
+</div>
+</div>
+</div>
+<div class="sect1" lang="en">
+<div class="titlepage">
+<div>
+<div>
+<h2 class="title" style="clear: both"><a name="examples" id=
+"examples"></a>5.&nbsp;Concrete examples of XXX in practice</h2>
+</div>
+</div>
+</div>
+<div class="sect2" lang="en">
+<div class="titlepage">
+<div>
+<div>
+<h3 class="title"><a name="example1" id=
+"example1"></a>5.1.&nbsp;First plots</h3>
+</div>
+</div>
+</div>
+<p>One single file, one single plot per page</p>
+<p>Click on OK.</p>
+<p>Test the various basic functions: change the dates, the zoom,
+the field...</p>
+<p>Specify the min, max, and contour interval in the provided
+boxes.</p>
+<p>Add some keywords in the "keywords:" box, for example:</p>
+<div class="blockquote">
+<blockquote class="blockquote">
+<p>/nocontour, /carte</p>
+</blockquote>
+</div>
+<p>or the keywords for a northern hortographic polar
+projection:</p>
+<div class="blockquote">
+<blockquote class="blockquote">
+<p>/nocontour, map=[90,0,0], /horto</p>
+</blockquote>
+</div>
+<p>Test the various possibilities in the <span class="guimenu">Save
+As</span> menu.</p>
+<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
+<h3 class="title">Note</h3>
+<p>the creation of animations has a tendency to saturate the video
+memory of X-terminals, crashing the entire program...</p>
+</div>
+<p>Test the various possibilities in the <span class="guimenu">Flag
+options</span> menu.</p>
+<div class="caution" style=
+"margin-left: 0.5in; margin-right: 0.5in;">
+<h3 class="title">Caution</h3>
+<p>Careful, a selected option remains selected until it is
+reclicked.</p>
+</div>
+</div>
+<div class="sect2" lang="en">
+<div class="titlepage">
+<div>
+<div>
+<h3 class="title"><a name="example2" id=
+"example2"></a>5.2.&nbsp;Work with more than one file</h3>
+</div>
+</div>
+</div>
+<p>Open some other files and go between them by selecting them from
+the file list... Note that the different widgets (calendar, domain,
+...) follow the different file characteristics.</p>
+</div>
+<div class="sect2" lang="en">
+<div class="titlepage">
+<div>
+<div>
+<h3 class="title"><a name="mouse" id="mouse"></a>5.3.&nbsp;Mouse
+actions in the graphics window on a horizontal plot</h3>
+</div>
+</div>
+</div>
+<p>Select a domain and select the horizontal plot (<code class=
+"constant">plt</code>), vertical plot (<code class=
+"constant">pltz</code>), or the hovmoeller plot (<code class=
+"constant">pltt</code>):</p>
+<p>The domain we'd like to select for the plot is determined by one
+of its diagonals, defined therefore by two points. The first point
+is defined when the mouse button is pushed, then the mouse is
+moved, and the second point is defined as the mouse button is
+released (click-drag). The domains are thus defined by a long click
+(<abbr class="abbrev">LC</abbr>). To determine which type of plot
+should be made of selection, use:</p>
+<div class="variablelist">
+<dl>
+<dt><span class="term">If the plot selector is on <code class=
+"constant">plt</code></span></dt>
+<dd>
+<p>the left mouse button to create horizontal plots (<code class=
+"constant">plt</code>)</p>
+<p>the middle mouse button to create vertical plots (<code class=
+"constant">pltz</code>)</p>
+<p>the right mouse button to create common hovmoellers for xt and
+yt cuts (<code class="constant">pltt</code>)</p>
+<p>In summary: <abbr class="abbrev">LCL</abbr>---&gt;<code class=
+"constant">plt</code></p>
+<p>LCM---&gt;<code class="constant">pltz</code></p>
+<p>LCR---&gt;<code class="constant">pltt</code></p>
+</dd>
+<dt><span class="term">If the plot selector is on something other
+than <code class="constant">plt</code></span></dt>
+<dd>
+<p>the indicated plot type is made.</p>
+</dd>
+</dl>
+</div>
+</div>
+<div class="sect2" lang="en">
+<div class="titlepage">
+<div>
+<div>
+<h3 class="title"><a name="multipleplots" id=
+"multipleplots"></a>5.4.&nbsp;Create multiple plots on the same
+sheet and make them interact</h3>
+</div>
+</div>
+</div>
+<p>Select the number of columns and rows for the page.</p>
+<p>Create a first plot. It will appear in the first frame.</p>
+<p>To create a plot in another frame double-click in the frame with
+the middle button (<abbr class="abbrev">DCM</abbr>). A black dotted
+frame will surround the designated frame, the &ldquo;<span class=
+"quote">target</span>&rdquo; frame. A black frame will surround the
+first plot. This is the &ldquo;<span class=
+"quote">reference</span>&rdquo; frame, in other words the one that
+all the XXX widgets refer to. Change for example the date and
+create a new plot. With a left button double-click in the first
+frame, all the widgets change and refer again to the first plot. A
+double-click with the right button in the second frame will erase
+the plot.</p>
+<p>In summary: <abbr class=
+"abbrev">DCL</abbr>---&gt;&ldquo;<span class=
+"quote">reference</span>&rdquo; frame</p>
+<p><abbr class="abbrev">DCM</abbr>---&gt;&ldquo;<span class=
+"quote">target</span>&rdquo; frame</p>
+<p><abbr class="abbrev">DCR</abbr>---&gt;erase the frame</p>
+<p>Here's a series of commands to show how this works.</p>
+<div class="procedure">
+<ol type="1">
+<li>
+<p>Select a 3-D field and create 6 frames for the sheet of
+paper.</p>
+</li>
+<li>
+<p>Create a horizontal plot in Frame 1</p>
+</li>
+<li>
+<p><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>
+<p><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>
+<p><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.</p>
+</li>
+</ol>
+</div>
+<div class="procedure">
+<p>To redo the hovmoeller with the keyword</p>
+<div class="literallayout">
+<p>/nocontour</p>
+</div>
+<ol type="1">
+<li>
+<p><abbr class="abbrev">DCL</abbr> in frame 4 which now becomes the
+reference and target frame.</p>
+</li>
+<li>
+<p>Add the keyword</p>
+<div class="literallayout">
+<p>/nocontour</p>
+</div>
+</li>
+<li>
+<p>click <span class="guibutton">OK</span>, and the plot is
+redone.</p>
+</li>
+</ol>
+</div>
+<div class="procedure">
+<p>in frame 5, let's create the same plot as in frame 2 except with
+different dates</p>
+<ol type="1">
+<li>
+<p><abbr class="abbrev">DCL</abbr> on frame 2</p>
+</li>
+<li>
+<p><abbr class="abbrev">DCM</abbr> on frame 5</p>
+</li>
+<li>
+<p>change the date</p>
+</li>
+<li>
+<p>click on <span class="guibutton">OK</span> , and voil&agrave;,
+the new plot.</p>
+</li>
+</ol>
+</div>
+</div>
+</div>
+<div class="sect1" lang="en">
+<div class="titlepage">
+<div>
+<div>
+<h2 class="title" style="clear: both"><a name="crash" id=
+"crash"></a>6.&nbsp;How to quit when it crashes</h2>
+</div>
+</div>
+</div>
+<div class="orderedlist">
+<ol type="1">
+<li>
+<p>in the IDL window, type</p>
+<pre class="screen">
+<code class="prompt">idl&gt;</code> <strong class=
+"userinput"><code>retall</code></strong>
+</pre></li>
+<li>
+<p><abbr class="abbrev">DCR</abbr> to erase the problem frame</p>
+</li>
+<li>
+<p>press the <span class="guibutton">clear</span> button</p>
+</li>
+<li>
+<p>change the orientation of the plot</p>
+</li>
+<li>
+<p>quit XXX cleanly using <span class="guibutton">quit</span> from
+the <span class="guimenu">File</span> menu</p>
+</li>
+</ol>
+</div>
+<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
+<h3 class="title">Note</h3>
+<p>Always avoid if at all possible closing and killing the XXX
+window, but rather select <span class="guibutton">quit</span> from
+the <span class="guimenu">File</span> menu. XXX uses a large number
+of pointers, and wantonly killing the window will leave a large
+number of unused variables in memory, which could in the end
+overflow. To clean up this memory:</p>
+<pre class="screen">
+<code class="prompt">idl&gt;</code> <strong class=
+"userinput"><code>ptr_free, ptr_valid()</code></strong>
+</pre></div>
+</div>
+</div>
+</body>
+</html>
Index: /trunk/SRC/Documentation/xmldoc/mini_notice.xml
===================================================================
--- /trunk/SRC/Documentation/xmldoc/mini_notice.xml	(revision 144)
+++ /trunk/SRC/Documentation/xmldoc/mini_notice.xml	(revision 144)
@@ -0,0 +1,770 @@
+<?xml version='1.0' encoding='iso-8859-1'?>
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
+[
+<!ENTITY promptidl "idl&gt;">
+]
+>
+<!--
+
+./SAXO_DIR/SRC/Documentation/xmldoc/mini_notice.xml
+
+update :
+fplod 2006-07-20T08:45:14Z aedon.locean-ipsl.upmc.fr (Darwin)
+. creation by hand made migration from mini_notice.html to XML/Docbook
+. installation part has been removed
+. add images
+++ fake graphics callouts see forxxxdoc.sh
+
+-->
+<article lang="en">
+<title>
+Mini Guide for Basic Commands in the XXX Program
+</title>
+  <articleinfo>
+    <authorgroup>
+      <author><firstname>Sébastien</firstname><surname>Masson</surname><email>Sebastien.Masson_at_locean-ipsl.upmc.fr</email></author>
+      <author><firstname>Albert</firstname><surname>Fisher</surname></author>
+      <author><firstname>Françoise</firstname><surname>Pinsard</surname><email>Francoise.Pinsard_at_locean-ipsl.upmc.fr</email></author>
+      <author><firstname>Steve</firstname><surname>Navarro</surname></author>
+    </authorgroup>
+    <keywordset>
+      <keyword>idl</keyword>
+      <keyword>SAXO</keyword>
+      <keyword>xxx</keyword>
+    </keywordset>
+    <revhistory>
+      <revision>
+        <revnumber>0.0</revnumber>
+        <date>May 29, 2000</date>
+        <revremark>French release by Sébastien Masson</revremark>
+      </revision>
+      <revision>
+        <revnumber>0.1</revnumber>
+        <date>July, 2002</date>
+        <revremark>Translation by Albert Fisher</revremark>
+      </revision>
+      <revision>
+        <revnumber>0.2</revnumber>
+        <date>July 20, 2006</date>
+        <revremark>HTML to XML/Docbook migration by Françoise Pinsard</revremark>
+      </revision>
+     </revhistory>
+     <pubdate>$Id$</pubdate>
+  </articleinfo>
+
+
+<!--
+La partie suivante n'a plus tellement de sens maintenant que tout SAXO est disponible sur forge
+<para>
+Where to find the source code
+</para>
+The scripts are available in the IDL_29_5_2000 directory.
+</para>
+<para>
+In this directory are
+<itemizedlist>
+<listitem><para>a tar file IDL_29_5_2000.tar with all the files</para></listitem>
+<listitem><para>the scripts in ASCII, in subdirectories by theme</para></listitem>
+</itemizedlist>
+
+<para>
+This IDL_29_5_2000 directory is available:
+<itemizedlist>
+<listitem><para>at LODYC: adonis.lodyc.jussieu.fr:/usr/home/smasson/IDL_29_5_2000</para></listitem>
+<listitem><para>at IPSL: cook.ipsl.jussieu.fr:/home/smlod/IDL_29_5_2000</para></listitem>
+<listitem><para>at IDRIS: rhodes.idris.fr:/home/rech/eee/reee217/IDL_29_5_2000</para></listitem>
+<listitem><para>on the anonymous ftp site of LODYC (contact <ulink url="mailto:smasson@lodyc.jussieu.fr">smasson@lodyc.jussieu.fr</ulink>
+for access).</para></listitem>
+<listitem><para>soon, from <ulink url="http://www.lodyc.jussieu.fr/~opatlod/SAXO/"/></para></listitem>
+</itemizedlist>
+</para>
+<para>
+This mini guide is also found in the IDL_29_5_2000 directory, in
+different formats.  It is also consultable on the web at:
+</para>
+<para>
+<ulink url="http://www.ipsl.jussieu.fr/~smlod/mini_notice.html"/>
+</para>
+
+-->
+<sect1 id="intro"><title>Introduction and assumptions</title>
+
+<para>
+This micro guide is unfortunately not a user's guide for all the
+scripts that have been written for IDL (version 5.2 or higher
+required). The goal is simply to clarify a few points on the use of the <filename>xxx.pro</filename>
+program.
+</para>
+<para>
+For further help on the furnished scripts, here are
+several possibilities:
+
+<itemizedlist>
+<listitem><para>execute in IDL the command
+  <screen format="linespecific">
+<prompt>&promptidl;</prompt> <userinput>xhelp, '<replaceable>script_name</replaceable>'</userinput>
+</screen>
+</para></listitem>
+<listitem><para>consult the IDL online help for scripts whose source is unavailable</para></listitem>
+<listitem><para>
+subscribe to the mailing list for updates and user questions/responses
+</para>
+<para>
+to subscribe, send a mail to: <ulink url="mailto:majordomo@lmd.jussieu.fr">majordomo@lmd.jussieu.fr</ulink>
+with no subject, containing the message:
+<userinput>subscribe forum-idl <replaceable>e-mail address</replaceable></userinput>
+</para></listitem>
+<listitem><para>consult the archives of this mail list:
+    <ulink url="http://www.lmd.jussieu.fr/archives/form-idl/last/mail1.html"/></para></listitem>
+<listitem><para>consult in desperation the feeble web pages we have started to write
+  (while waiting for something better)
+  <ulink url="http://www.ipsl.jussieu.fr/~smlod/"/></para></listitem>
+<listitem><para>wait until we write a full user's manual!</para></listitem>
+</itemizedlist>
+</para>
+
+<para>
+The XXX widget is a layer on top of the scripts in the <application>SAXO</application> package
+(themselves layered on top of IDL). It is designed to permit the
+visualization and rapid exploration of data, offering a maximum in
+options, while not necessarily all those offered by the package and by
+IDL.
+</para>
+<para>
+Based on the use of files in the NetCDF format, it can easily work
+with other file formats.  For this, all that is necessary is to write
+an IDL function capable of extracting a matrix from a file as a
+function of the following parameters: the variable name, two dates, an
+experiment name, and a domain.
+</para>
+<para>
+Developed to visualize the output of the OPA model, the <application>SAXO</application> package was
+conceived to work on C grids.  To use it on grids where the T, U, and
+V points are the same, one must nevertheless declare the parameters of
+the grid that correspond to the U and V points.  Careful, for this
+type of discretization, the calculation scripts of type <filename>div.pro</filename> and
+<filename>curl.pro</filename> are wrong.
+</para>
+<para>
+The averaging routines are not adapted to warped grids, they sum
+following the i, j, and k indices, weighting each point by scale
+factors and the land-sea mask.  Slices and Hovmoellers do not work in
+the diagonal, but are always done following i, j, or k.  When a domain
+is given to one of the scripts, an average over the domain in the
+directions perpendicular to that displayed is automatically made before
+display.
+</para>
+<para>
+Before continuing on to the practical part of this guide, the
+installation and use of the <application>SAXO</application> package, I'd like to thank Guillaume
+Roullet, who also participated in the writing of the scripts in the
+package (notably the drawing of vectors on warped grids).
+</para>
+</sect1>
+
+<sect1 id="beforefirststeps">
+<title>Before this</title>
+<para>
+In this document, we supposed that you followed <ulink url="getsaxo.html">Get SAXO</ulink> recommandations.
+</para>
+</sect1>
+
+
+<sect1 id="initfiles"><title>Install the files <filename>init.pro</filename> and
+<filename>initgrid.pro</filename></title>
+
+<para>
+This version of the <application>SAXO</application> package depends a certain number of common
+variables that are primarily environmental parameters (working paths,
+color management, Postscript formatting) and the parameters of the
+grid on which you are working (longitude, latitude, depth, land-sea
+mask, scale factors, position of the zoom in relation to the original
+grid).
+</para>
+<para>
+These two types of parameters are kept separately:
+<itemizedlist>
+<listitem><para>environmental parameters are defined at the very beginning of the
+IDL session, and are in principle never changed.  They are initialized
+by the <filename>init.pro</filename> script.</para></listitem>
+<listitem><para>Those that belong to the grid are reinitialized every time the
+grid is changed.  They can therefore be called at any time during a
+session. These parameters are initialized by the <filename>initgrid.pro</filename>
+scripts, and are specific to each particular grid.
+</para>
+<para>
+For example: <filename>initorca.pro</filename> for the ORCA 2&deg; grid,
+<filename>initorca05.pro</filename> for
+the ORCA 0.5&deg; grid, or <filename>initorcapac.pro</filename> for the ORCA grid zoomed on
+the Pacific.</para></listitem>
+</itemizedlist>
+</para>
+<para>
+To begin, one must therefore copy <filename><replaceable>packagedir</replaceable>/INIT/init.pro</filename>
+into <replaceable>homedir</replaceable>, and create in <replaceable>homedir</replaceable> a script of the
+type <filename>initgrid.pro</filename>.
+</para>
+
+<!-- ++ n'a plus rien à faire ici
+<sect2 id="modifinit"><title>Modification of the <filename>init.pro</filename> script</title>
+
+<para>
+It is necessary to personalize the lines that correspond to the 6
+directories defined in &sect; 1.1.  That is:
+<itemizedlist>
+<listitem><para>The definition of !path.</para><para>
+The first expand_path must contain <replaceable>homedir</replaceable>, the second
+<replaceable>packagedir</replaceable>.  The directory declaration must be preceded by a +
+sign, and must take the form of a character chain. The + sign
+specifies that subdirectories must also be considered.  For those
+working on a Mac, <literallayout>"+':'+"</literallayout> must be replaced by <literallayout>"+','+"</literallayout> and for Windows
+by <literallayout>"+';'+"</literallayout>.</para>
+<warning>
+<para>
+In their definition, the directories must not finish with the
+directory separation character ("/" under UNIX/Linux).
+</para>
+</warning>
+</listitem>
+<listitem><para>Definition of the rest of the directories:</para><para>
+Define as necessary the variables homedir, workdir, iodir, animdir,
+psdir, and imagedir.</para>
+<warning>
+<para>
+Despite precautions taken, in order to avoid bugs it is
+recommended that these directories be defined with the directory
+separation character as the final character ("/" under UNIX/Linux).
+</para>
+</warning>
+</listitem>
+</itemizedlist>
+</para>
+<note>
+<para>
+Depending on the resolution of your screen and the type of
+machine used, it is possible that the graphics window which is created
+will be too large.  If this is the case, change the ccwindowsize
+variable which is a multiplicative coefficient applied to the window
+size.
+</para>
+</note>
+</sect2>
+-->
+<sect2 id="modifinitgrid"><title>Modification or creation of the <filename>initgrid.pro</filename> script</title>
+
+<para>
+In the <replaceable>packagedir</replaceable>/INIT directory you will find a certain
+number of scripts associated with the latest grids on which I've
+worked.  If you are also working on one of these grids, for example
+ORCA, copy the file  <filename><replaceable>packagedir</replaceable>/INIT/initorca.pro</filename> to your
+<replaceable>homedir</replaceable>.  If not, copy it nevertheless to use as a model.  In
+the file <filename>initgrid.pro</filename>, adjust the zoom parameters (if it has not
+already been done).
+</para>
+<para>
+Careful: unlike in previous versions of the <application>SAXO</application> package, all the zoom
+parameters must be defined.  If you do not know them in advance,
+define their values to be -1.
+</para>
+<para>
+In the rest of the script, define iodir as <replaceable>iodir</replaceable>, and verify
+the name of the mask file, if one exists.
+</para>
+</sect2>
+</sect1>
+<sect1 id="introxxx"><title>Starting the <application>SAXO</application> package and an explanation of the XXX widget functions</title>
+<sect2 id="launchxxx"><title>Launching XXX</title>
+
+<para>
+The first command to type is
+
+  <screen format="linespecific">
+<prompt>&promptidl;</prompt> <userinput>@init</userinput>
+</screen>
+
+</para>
+<para>
+Afterwards, to work directly with XXX, type:
+
+  <screen format="linespecific">
+
+<prompt>&promptidl;</prompt> <userinput>xxx</userinput>
+</screen>
+
+</para>
+
+<para>
+To work without the XXX interface, initialize a grid
+
+  <screen format="linespecific">
+
+<prompt>&promptidl;</prompt> <userinput>@initgrid</userinput>
+</screen>
+
+
+</para>
+<para>
+A window will open with 2 lines to complete.
+<figure id="fig_xxx_1">
+<title>Window xxx 1</title>
+<mediaobjectco>
+<!-- ++ pas encore au point cf. forxxxdoc.sh !! -->
+<imageobjectco>
+<areaspec units="calspair">
+<area id="datafile" coords="96,1779 9903,2912"/>
+<area id="initfile" coords="96,4854 9903,6472"/>
+</areaspec>
+<imageobject>
+<imagedata fileref="figpng/xxx_1_complete.png"/> <!-- ++ instead of xxx_1.png -->
+</imageobject>
+<calloutlist>
+<callout arearefs="datafile">
+<para>datafile</para>
+</callout>
+<callout arearefs="initfile">
+<para>initfile</para>
+</callout>
+</calloutlist>
+</imageobjectco>
+<!-- ++ si on met textobject, on ne voit plus l'image !!
+<textobject>[plot figpng/xxx_1_complete.png]</textobject>
+-->
+</mediaobjectco>
+</figure>
+</para>
+<para>
+These lines must contain
+the address of a file.  The name can be typed directly in the window
+provided, or selected with the help of the <guibutton>browse</guibutton> button.  The first
+line must contain the name of the data file, the second the name of
+the <filename>initgrid.pro</filename> script which will permit the reading and processing of the
+grid associated with the data file.
+</para>
+<para>
+Once these two lines have been completed, click on <guibutton>let's go</guibutton>.  Two
+other windows will then open, giving you the parameters for reading
+the grid and the file (these parameters are read in the <filename>initgrid.pro</filename>
+script).  Click twice on <guibutton>OK</guibutton>.
+</para>
+</sect2>
+<sect2 id="wigdets"><title>An explanation of the different widgets</title>
+
+<para>
+Now the XXX window will open.
+<!-- cf example in http://www.docbook.org/tdg/en/html/area.html
+sauf que dans l'exemple en question on ne donne que 2 nombres et pas 4
+voir aussi message http://www.oasis-open.org/archives/docbook-apps/200501/msg00089.html
+peut-etre du nouveau dans les xsl depuis le 16 janvier 2005
+peut-être essayé http://lists.kde.org/?l=kde-doc-english&m=112780764426265&w=2
+ce produit klickety est installable via fink sous mac
+ -->
+<figure id="fig_xxx_2">
+<title>Window xxx 2</title>
+<mediaobjectco>
+<!-- ++ pas encore au point cf. forxxxdoc.sh !! -->
+<imageobjectco>
+<areaspec units="calspair">
+<area id="pagelayout" coords="578,873 1651,1269"/>
+<area id="calendar" coords="82,2222 1899,2857"/>
+<area id="domain" coords="82,3174 2477,6349"/>
+<area id="specify" coords="82,7142 2890,7936"/>
+</areaspec>
+<imageobject>
+<imagedata fileref="figpng/xxx_2_complete.png"/> <!-- ++ instead of xxx_2.png -->
+</imageobject>
+<calloutlist>
+<callout arearefs="pagelayout">
+<para> Page layout </para>
+</callout>
+<callout arearefs="calendar">
+<para> Calendar </para>
+</callout>
+<callout arearefs="domain">
+<para> Domain </para>
+</callout>
+<callout arearefs="specify">
+<para> Specify </para>
+</callout>
+</calloutlist>
+</imageobjectco>
+<!-- ++ si on met textobject, on ne voit plus l'image
+<textobject>[plot figpng/xxx_2_complete.png]</textobject>
+-->
+</mediaobjectco>
+</figure>
+</para>
+<para>
+It's configuration will change
+depending on whether you are in portrait or in landscape, but here are
+the different parts available for your use.
+</para>
+
+<sect3 id="menubar"><title>The menu bar made up of 3 submenus</title>
+<sect4 id="filesubmenu"><title><guisubmenu>File</guisubmenu> submenu</title>
+
+<para>
+<itemizedlist>
+<listitem>
+<para>
+<guimenuitem>Open:</guimenuitem> to open a second file.  Same procedure as during the
+launching of XXX.  The new file can be on a different grid, with
+different variables, with a different time base.
+</para></listitem>
+<listitem><para><guimenuitem>New XXX:</guimenuitem> to open a second XXX window identical to the first.</para></listitem>
+<listitem><para><guimenuitem>Close:</guimenuitem> to close the XXX window.</para></listitem>
+</itemizedlist>
+</para>
+
+</sect4>
+<sect4 id="saveassubmenu"><title><guisubmenu>Save As</guisubmenu> submenu</title>
+
+<para>
+<itemizedlist>
+<listitem><para><guimenuitem>Postscript:</guimenuitem> to save in Postscript format</para></listitem>
+<listitem><para><guimenuitem>Animations:</guimenuitem> to create an animation from the XXX window.
+Careful, 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.</para></listitem>
+<listitem><para><guimenuitem>Image:</guimenuitem> to save a gif of the XXX graphics window.</para></listitem>
+<listitem><para><guimenuitem>Script:</guimenuitem> to save the command history that has created the
+plot.  For example if I save the commands in <filename>xxx_figure.pro</filename>, I can
+then launch a new IDL session and type:
+  <screen format="linespecific">
+<prompt>&promptidl;</prompt> <userinput>@init</userinput>
+<prompt>&promptidl;</prompt> <userinput>xxx_figure</userinput>
+</screen>
+</para>
+<para>
+and I'll obtain the saved figure.
+  <screen format="linespecific">
+<prompt>&promptidl;</prompt> <userinput>xxx_figure,/post </userinput>
+</screen>
+or
+  <screen format="linespecific">
+<prompt>&promptidl;</prompt> <userinput>@ps</userinput>
+</screen>
+will then create a Postscript file of the figure.</para><para></para></listitem>
+<listitem><para><guimenuitem>Prompt:</guimenuitem> lists in the IDL window the command history that
+created the last plot.  Useful primarily for debugging...</para></listitem>
+</itemizedlist>
+</para>
+</sect4>
+<sect4 id="flagsubmenu"><title><guisubmenu>Flag options</guisubmenu> submenu</title>
+
+<para>
+<itemizedlist>
+<listitem><para><guibutton>OK</guibutton> To show/hide the OK button in the upper left corner.</para></listitem>
+<listitem><para><guibutton>Portrait/Landscape:</guibutton> changes the configuration of the plot.</para></listitem>
+<listitem><para><guibutton>Overlay:</guibutton> 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>
+<listitem><para><guibutton>Vecteur:</guibutton> to plot a vector field on top of contours. Only
+works on horizontal plots (<filename>plt.pro</filename>).  As for Overlay, a relaunch of
+the entire plot is necessary.</para></listitem>
+<listitem><para><guibutton>Longitude / x index:</guibutton> switches longitude labelling of the plot
+subdomain from degrees to indices following i. </para></listitem>
+<listitem><para><guibutton>Latitude / y index:</guibutton> switches latitude labelling of the plot
+subdomain from degrees to indices following j. </para></listitem>
+</itemizedlist>
+</para>
+</sect4>
+</sect3>
+<sect3 id="typeplot"><title>What type of plot and where?</title>
+<para>
+<itemizedlist>
+<listitem><para><guibutton>OK</guibutton> Show/hide the OK button in the upper left.  When
+present, a click is required to make a new plot appear. Otherwise
+each action creates a new plot. </para></listitem>
+<listitem><para><guimenuitem>Plot type list:</guimenuitem> allows specification of the type of plot
+desired.
+</para>
+<note>
+<para>
+If the type <constant>plt</constant> is selected, the selection of plot type
+is made by mouse. Cf <xref linkend="mouse"/></para>
+</note>
+</listitem>
+<listitem><para><guimenuitem>Layout configuration:</guimenuitem> specify the number of columns and
+rows for plots on the sheet of paper.  There's no code behind the undo
+command!  The <guibutton>clear</guibutton> button erases all plots.</para></listitem>
+<listitem><para><guimenuitem>List of open files:</guimenuitem> you can choose the file to work on.</para></listitem>
+<listitem><para><guimenuitem>Command window:</guimenuitem> this window permits simple operations on
+the fields:</para><para>
+for example: <literallayout>toto - 10*field + 36</literallayout></para>
+<note>
+<para>
+In the default case, the name given to a field is of no importance.</para>
+</note>
+</listitem>
+</itemizedlist>
+</para>
+</sect3>
+<sect3 id="sect_calendar"><title>Calendar</title>
+<para>
+The calendar is made up of two droplists, which allow specification of
+two dates, the beginning and end of a time series, or the period over
+which to average before plotting.
+</para>
+</sect3>
+<sect3 id="sect_domain"><title>Domain specification</title>
+<para>
+A series of widgets that allow specification of the min/max limits of
+the domain in longitude/x-index, latitude/y-index, and depth in levels
+or meters.  For depth, one can specify in levels for a horizontal
+plot, and in meters for a vertical plot.
+</para>
+</sect3>
+<sect3 id="details"><title>Plot details</title>
+<para>
+You can specify the min, max, and contour interval by filling out the
+provided boxes! For the color palette, you can either specify the name
+or go search for one among the palettes available.
+</para>
+<para>
+The "keywords" window allows specification of all desired
+keywords. These keywords can be those of
+<filename>plt.pro</filename>, <filename>pltt.pro</filename>, <filename>pltz.pro</filename>,
+<filename>plt1d.pro</filename>, or those of contour, plot, or all other programs that are
+used. Cf <xref linkend="example1"/>
+</para>
+</sect3>
+</sect2>
+</sect1>
+<sect1 id="examples"><title>Concrete examples of XXX in practice</title>
+
+<sect2 id="example1"><title>First plots</title>
+
+<para>
+One single file, one single plot per page
+</para>
+<para>
+Click on OK.
+</para>
+<para>
+Test the various basic functions: change the dates, the zoom, the
+field...</para>
+<para>
+Specify the min, max, and contour interval in the provided boxes.</para>
+<para>
+Add some keywords in the "keywords:" box, for example: </para>
+<blockquote>
+<para>
+/nocontour, /carte
+</para>
+</blockquote>
+<para>
+or the keywords for a northern hortographic polar projection:</para>
+<blockquote>
+<para>
+/nocontour, map=[90,0,0], /horto
+</para>
+</blockquote>
+<para>
+Test the various possibilities in the <guimenu>Save As</guimenu> menu.</para>
+<note>
+<para>
+the creation of animations has a tendency to saturate the video
+memory of X-terminals, crashing the entire program...</para>
+</note>
+<para>
+Test the various possibilities in the <guimenu>Flag options</guimenu> menu.
+</para>
+<caution>
+<para>
+Careful, a selected option remains selected until it is reclicked.
+</para>
+</caution>
+</sect2>
+
+<sect2 id="example2"><title>Work with more than one file</title>
+<para>
+Open some other files and go between them by selecting them from the
+file list...  Note that the different widgets (calendar, domain, ...)
+follow the different file characteristics.
+</para>
+</sect2>
+
+<sect2 id="mouse"><title>Mouse actions in the graphics window on a horizontal plot</title>
+
+<para>
+Select a domain and select the horizontal plot (<constant>plt</constant>), vertical plot
+(<constant>pltz</constant>), or the hovmoeller plot (<constant>pltt</constant>):</para>
+<para>
+The domain we'd like to select for the plot is determined by one of
+its diagonals, defined therefore by two points.  The first point is
+defined when the mouse button is pushed, then the mouse is moved, and
+the second point is defined as the mouse button is released
+(click-drag).  The domains are thus defined by a long click (<abbrev>LC</abbrev>).  To
+determine which type of plot should be made of selection, use:
+<variablelist>
+<varlistentry>
+<term>
+If the plot selector is on <constant>plt</constant>
+</term>
+<listitem>
+<para>
+the left mouse button to create horizontal plots (<constant>plt</constant>)</para>
+<para>
+the middle mouse button to create vertical plots (<constant>pltz</constant>)</para>
+<para>
+the right mouse button to create common hovmoellers for xt and yt cuts
+(<constant>pltt</constant>)</para>
+<para>
+In summary: <abbrev>LCL</abbrev>---><constant>plt</constant></para>
+<para>
+LCM---><constant>pltz</constant></para>
+<para>
+LCR---><constant>pltt</constant></para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term>
+If the plot selector is on something other than <constant>plt</constant>
+</term>
+<listitem>
+<para>
+the indicated plot type is made.
+</para>
+</listitem>
+</varlistentry>
+</variablelist>
+</para>
+</sect2>
+<sect2 id="multipleplots"><title>Create multiple plots on the same sheet and make them interact</title>
+
+<para>
+Select the number of columns and rows for the page.</para>
+<para>
+Create a first plot.  It will appear in the first frame.</para>
+<para>
+To create a plot in another frame double-click in the frame with the
+middle button (<abbrev>DCM</abbrev>).  A black dotted frame will surround the
+designated frame, the <quote>target</quote> frame.  A black frame will surround the
+first plot.  This is the <quote>reference</quote> frame, in other words the one
+that all the XXX widgets refer to.  Change for example the date and
+create a new plot.  With a left button double-click in the first
+frame, all the widgets change and refer again to the first plot.  A
+double-click with the right button in the second frame will erase the
+plot.</para>
+<para>
+In summary: <abbrev>DCL</abbrev>---><quote>reference</quote> frame</para>
+<para>
+<abbrev>DCM</abbrev>---><quote>target</quote> frame</para>
+<para>
+<abbrev>DCR</abbrev>--->erase the frame</para>
+<para>
+Here's a series of commands to show how this works.
+</para>
+<procedure>
+<step>
+<para>
+Select a 3-D field and create 6 frames for the sheet of paper.
+</para>
+</step>
+<step>
+<para>
+Create a horizontal plot in Frame 1
+</para>
+</step>
+<!-- je n'arrive pas à utliser <stepalternatives> -->
+<step>
+<para>
+<abbrev>DCM</abbrev> in frame 2, <abbrev>LCL</abbrev> on the plot in frame 1, to create a horizontal
+zoom in frame 2.</para>
+<para>
+<abbrev>DCM</abbrev> in frame 3, <abbrev>LCM</abbrev> on the plot in frame 1, to create a vertical cut
+in frame 3.</para>
+<para>
+<abbrev>DCM</abbrev> in frame 4, <abbrev>LCR</abbrev> on the plot in frame 1, to create a hovmoeller in frame 4.
+</para>
+</step>
+</procedure>
+<procedure>
+<para>
+To redo the hovmoeller with the keyword <literallayout>/nocontour</literallayout>
+</para>
+<step>
+<para>
+<abbrev>DCL</abbrev> in frame 4 which now becomes the reference and target frame.
+</para>
+</step>
+<step>
+<para>
+Add the keyword
+<literallayout>/nocontour</literallayout>
+</para>
+</step>
+<step>
+<para>
+click <guibutton>OK</guibutton>, and the plot is redone.
+</para>
+</step>
+</procedure>
+<procedure>
+<para>
+in frame 5, let's create the same plot as in frame 2 except with different dates
+</para>
+<step>
+<para>
+<abbrev>DCL</abbrev> on frame 2
+</para>
+</step>
+<step>
+<para>
+<abbrev>DCM</abbrev> on frame 5
+</para>
+</step>
+<step>
+<para>
+change the date
+</para>
+</step>
+<step>
+<para>
+click on <guibutton>OK</guibutton>
+, and voilà, the new plot.
+</para>
+</step>
+</procedure>
+</sect2>
+</sect1>
+<sect1 id="crash"><title>How to quit when it crashes</title>
+
+<para>
+<orderedlist>
+<listitem>
+<para>
+in the IDL window, type
+  <screen format="linespecific">
+<prompt>&promptidl;</prompt> <userinput>retall</userinput>
+</screen>
+</para></listitem>
+<listitem>
+<para><abbrev>DCR</abbrev> to erase the problem frame
+</para>
+</listitem>
+<listitem><para>press the <guibutton>clear</guibutton> button
+</para></listitem>
+<listitem><para>change the orientation of the plot
+</para></listitem>
+<listitem><para>quit XXX cleanly using <guibutton>quit</guibutton> from the <guimenu>File</guimenu> menu
+</para></listitem>
+</orderedlist>
+</para>
+<note>
+<para>
+Always avoid if at all possible closing and killing the XXX
+window, but rather select <guibutton>quit</guibutton> from the <guimenu>File</guimenu> menu.  XXX uses a
+large number of pointers, and wantonly killing the window will leave a
+large number of unused variables in memory, which could in the end
+overflow.  To clean up this memory:
+  <screen format="linespecific">
+<prompt>&promptidl;</prompt> <userinput>ptr_free, ptr_valid()</userinput>
+</screen>
+</para>
+</note>
+</sect1>
+</article>
Index: /trunk/SRC/Documentation/xmldoc/savesaxo.sh
===================================================================
--- /trunk/SRC/Documentation/xmldoc/savesaxo.sh	(revision 143)
+++ /trunk/SRC/Documentation/xmldoc/savesaxo.sh	(revision 144)
@@ -1,6 +1,8 @@
-#!/bin/bash -x
+#!/bin/bash
 # 
 # update :
 # $Id$
+# fplod 2006-07-21T08:23:52Z aedon.locean-ipsl.upmc.fr (Darwin)
+# add mini_notice production
 # fplod 2006-07-11T08:26:05Z aedon.locean-ipsl.upmc.fr (Darwin)
 # commented tidy in dohtml section is moved in makehtml
@@ -149,5 +151,5 @@
 #
     cd ${memopwd}
-    for docxml in firststeps.xml getsaxo.xml mailing.xml main.xml tiplink.xml updatesaxo.xml whatissaxo.xml whatsnew.xml
+    for docxml in firststeps.xml getsaxo.xml mailing.xml main.xml tiplink.xml updatesaxo.xml whatissaxo.xml whatsnew.xml infoupdatekwd.xml infoupdatecm.xml mini_notice.xml
     do
       ./makehtml.sh $(basename ${docxml} .xml)
Index: /trunk/SRC/Documentation/xmldoc/saxo.css
===================================================================
--- /trunk/SRC/Documentation/xmldoc/saxo.css	(revision 143)
+++ /trunk/SRC/Documentation/xmldoc/saxo.css	(revision 144)
@@ -7,4 +7,6 @@
 update :
 $Id$
+fplod 2006-07-20T14:03:51Z aedon.locean-ipsl.upmc.fr (Darwin)
+add style for gui* moche mais c'est juste pour voir
 */
 
@@ -14,2 +16,15 @@
     background-color: #98fb98;
     font-style: italic; }
+
+*[class~="guimenu"] {
+    background-color: #green;
+    font-weight: bold;
+    font-style: italic; }
+*[class~="guisubmenu"] {
+    background-color: #yellow;
+    font-weight: bold;
+    font-style: italic; }
+*[class~="guibutton"] {
+    background-color: #cyan;
+    font-weight: bold;
+    font-style: italic; }
