Context Navigation

Changes between Version 129 and Version 130 of UvmatHelp

Timestamp:: Jan 13, 2015, 7:32:07 PM (10 years ago)
Author:: sommeria
Comment:: --

Legend:

: Unmodified
: Added
: Removed
: Modified

UvmatHelp

-                      v129
+                      v130
 The master piece is a Matlab GUI, made of a Matlab figure '''uvmat.fig''' and an associated set of sub-functions in the file ''uvmat.m''. The menu bar at the top of the GUI, push buttons and editing box in  '''uvmat.fig''' activate the Matlab sub-functions (''callback'' functions) in ''uvmat.m''.  The package also contains the following set of GUI.
  * '''browse_data.fig:''' scans the data directory of a project
+ * '''browse_data.fig:''' scans the data directory of a project.
  * '''editxml.fig:'''  displays and edits XML files according to an XML schema. XML reading and editing is performed by the toolbox [http://www.artefact.tk/software/matlab/xml/ xmltree], integrated in the package ''UVMAT'' as a subdirectory /@xmltree.
  * '''geometry_calib.fig''': determines geometric calibration parameters for relating image to physical coordinates. The toolbox http://www.vision.caltech.edu/bouguetj/calib_doc/ is used, integrated in the package ''UVMAT'' as a subdirectory /toolbox_calib.
 …
  * '''[Tools]''':
    * '''[Geometric calibration]''' for geometric calibration of images
    * '''[LIF calibration]''':  calibration of images for Laser Induced Fluorescence
    * '''[Make mask]''': for creating mask images (for PIV)
    * '''[Make grid]:''': for making measurement grids for PIV
+   * '''[Geometric calibration]''' for geometric calibration of images.
+   * '''[LIF calibration]''':  calibration of images for Laser Induced Fluorescence.
+   * '''[Make mask]''': for creating mask images (for PIV).
+   * '''[Make grid]:''': for making measurement grids for PIV.
    * '''[ruler]''': displays a ruler to measure lengths and angles of any line.
 …
  * '''<!GeometryCalib>''' contains the parameters of the geometric calibration relating the pixel position to the real space coordinates (see [#a8-Geometriccalibration section 8]]). In the case of volume scanning, it also describes the set of laser plane positions and angles.
  * '''<Illumination>''' describes the illumination system used, including the position of the laser source.
  * '''<Tracor>''' describes the properties of the flow tracor (particle, dye...)
+ * '''<Tracor>''' describes the properties of the flow tracor (particle, dye...).
 === 3.6 Ancillary input files ===
  * ''' Mask:''' Masks are used to avoid PIV computations in specified areas. The file is a B&W 8 bit png image, with the same size as the image it has to mask. The grayscale code used is :
    * Intensity < 20: ('black mask') the vector in this place will be set to zero
    * 20 < Intensity < 200:('gray mask') the vector in this place will be absent
+   * Intensity < 20: ('black mask') the vector in this place will be set to zero.
+   * 20 < Intensity < 200:('gray mask') the vector in this place will be absent.
    * Intensity>200  the vector will be computed  The mask corresponding to an image or velocity field can be displayed in '''uvmat.fig''' by selecting the check box '''[view_mask]([!CheckMask])''' on the upper left. Images with appropriate name can be automatically recognised by '''uvmat.fig''' and civ functions, see [#a9-Masksandgrids section 9.1]. Otherwise file selection by a browser is proposed when '''[view_mask]''' is selected.
 …
  * 'rgb':  color ranging from red, for the scalar value set by '''[num_MinVec]''', to blue, for the scalar value set by  '''[num_MaxVec]'''. The  color thresholds from red to green and green to blue are set by '''[ColCode1]''' and '''[ColCode2]''' respectively, or the sliders  '''[Slider1]''' and '''[Slider2]'''. By unselecting the check box [!CheckFixVecColor], these thresholds can be set to match the min and max scalar values.
  * 'black' or 'white': set the color for all vectors
+ * 'black' or 'white': set the color for all vectors.
  * 'brg': same as rgb but in reverse order, with blue for the lowest scalar values.
  * '64 colors': quasi-continuous color representation, ranging from blue (for the scalar value given by '''[num_MinVec]''', to red, for the scalar value given by '''[num_MaxVec]'''.
 …
  * fist line: the position coordinates ''x'', ''y'', ''z'' for 3D cases).
  * second line: the vector components
+ * second line: the vector components.
  * third line: the vector index in the file, the values of the scalar (C), the warning flag (F) and the error flag (FF). The meaning of the flag values is given in [#a11.3FIX section 11.3].
 …
 In some cases, it is useful to define the field object independently from its data content. Then the variables .Var1... are replaced by the lists of dimension names and values.
  * '''!ListDimName''' list of dimension names (cell array of character strings)
+ * '''!ListDimName''' list of dimension names (cell array of character strings).
  * '''!DimValue''' array of dimension values corresponding to !LisDimName.
 …
  * '''!ProjModeRequest'''= ''interp_lin'' or ''interp_tps'' indicates whether lin interpolation  or derivatives by tps is needed to calculate the requested field.
  * '''Operation''': name (char string) of the operation to be performed to finalise the field cell after projection.
  * '''!SubCheck'''= 0 /1 indicate that the field must be substracted (second entry in UVMAT)
+ * '''!SubCheck'''= 0 /1 indicate that the field must be substracted (second entry in UVMAT).
 Any other element can be added, but will not be taken into account if they are not listed in  ''!ListGlobalAttribute'' or ''!ListVarName''.
 …
  * 'Conventions':
    * ='uvmat': indicate that the conventions described here are followed
+   * ='uvmat': indicate that the conventions described here are followed.
    * ='uvmat/civdata': indicate that the variables are named according to [#civdata #civdata].
  * '!CoordMesh': typical mesh for coordinates, used to define default projection grids and mouse selection action. Calculated automatically from the data if not specified.
 …
 -'''Global attributes , unactive''' those are merely used for information purpose
  * Project: recalls the project name
  * Campaign: recalls the campaign name
  * Experiment:  recalls the experiment name(s) of the raw data
  * !DataSeries:  recalls the device name (s), if defined, of the raw data
+ * Project: recalls the project name.
+ * Campaign: recalls the campaign name.
+ * Experiment:  recalls the experiment name(s) of the raw data.
+ * !DataSeries:  recalls the device name (s), if defined, of the raw data.
  * !ObjectStyle: ='points', 'line', 'plane', denotes the style of geometric object on which the data have been 'projected'. For instance a profiler project a physical field along a line.
  * !ObjectCoord:  Coordinates defining a geometric object on which the data have been projected.
 …
 -'''The attribute 'Role':''' the following options are used for the attribute 'Role':
  * 'ancillary': information of secondary use, indicating for instance an error estimate of field variables within a field cell (omitted in plotting)
+ * 'ancillary': information of secondary use, indicating for instance an error estimate of field variables within a field cell (omitted in plotting).
  * 'coord_x', 'coord_y',  'coord_z': represents a  sets of unstructured coordinates x, y  and z for the field variables sharing the same dimension name.
  * 'coord_tps': coordinates of thin plate shell (tps) centres used for spline interpolation.
 …
  * 'errorflag': provides an error flag marking the field variables  as false or true within a field cell , default=0, no error. Different non zero values can mark different criteria of elimination, see [section 10.3->#sec10.3] for PIV data. Such flagging is reversible, since the data themselves are not lost.
  * 'grad_x', 'grad_y', 'grad_z'  :represents the x, y or z  component of a contravariant vector** (like gradients).
  * 'image_rgb': represents a color image. The last dimension of the array corresponds to the three color components 'rgb'. -* 'scalar': (default) represents a scalar field
+ * 'image_rgb': represents a color image. The last dimension of the array corresponds to the three color components 'rgb'. -* 'scalar': (default) represents a scalar field.
  * 'tensor': represents a tensor field whose components correspond to the two last   dimensions of the array.**
  * vector: matrix whose last dimension states for the vector components.**
  * 'vector_x', 'vector_y', 'vector_z'  : represents the x, y or z  component of a vector (covariant)
+ * 'vector_x', 'vector_y', 'vector_z'  : represents the x, y or z  component of a vector (covariant).
  * 'warnflag': provides a warning flag about the quality of data for the field variables within a field cell., default=0, no warning.
 …
 The field structure is furthermore indicated by using appropriate names for dimensions, but this is only for documentation, without  use in processing functions (except for coordinate dimensions denoting coordinate range, see above). The following conventions are used:
  * coord_1,_2,_3: dimension with the same name as a coordinate variable array (coordinate dimension)
  * 'nb_coord': denotes the space dimension for vector components
  * 'nb_coord_j', 'nb_coord_i': denotes the space dimensions for the two tensor components
+ * coord_1,_2,_3: dimension with the same name as a coordinate variable array (coordinate dimension).
+ * 'nb_coord': denotes the space dimension for vector components.
+ * 'nb_coord_j', 'nb_coord_i': denotes the space dimensions for the two tensor components.
  * 'rgb' : denotes the diemension of the color component in a true color  image.
  * 'nb_point' or 'nb_vec' (for vectors) denotes the set of positions with unstructured coordinates.
  * 'nb_tps': dimension of the index for the tps centres
  * 'nb_subdomain' denotes the dimension for the subdomain index for tps coefficients
+ * 'nb_tps': dimension of the index for the tps centres.
+ * 'nb_subdomain' denotes the dimension for the subdomain index for tps coefficients.
 ----
 …
   The objects are defined by the following set of properties:
  * ''' Name: ''' any name given to the object
+ * ''' Name: ''' any name given to the object.
  * ''' Type: ''' classify the object with the following choice:
    * 'points': set of n points
    * 'line': simple straight segment, defined by its two end points
    * 'polyline': open line made of n-1 consecutive segments (defined by n points)
    * 'rectangle': defined by its center, half width and half height, and possibly angle of axis..
    * 'polygon': closed line made of n consecutive segments (defined by n points)
+   * 'points': set of n points.
+   * 'line': simple straight segment, defined by its two end points.
+   * 'polyline': open line made of n-1 consecutive segments (defined by n points).
+   * 'rectangle': defined by its center, half width and half height, and possibly angle of axis.
+   * 'polygon': closed line made of n consecutive segments (defined by n points).
    * 'ellipse': defined by its center, half width, half height, and possibly angle of axis.
    * 'plane': plane with associated cartesian coordinates
    * 'volume': volume with associated cartesian coordinates
+   * 'plane': plane with associated cartesian coordinates.
+   * 'volume': volume with associated cartesian coordinates.
  * ''' !ProjMode: ''': specifies the method of projection of coordinates and field, as described in [#a6.3Projectionmodes next sub-section].
 …
  * 'polygon', 'rectangle', 'ellipse' are drawn as lines. In the case !ProjMode ='inside' or 'outside' the corresponding area is painted in magenta (or blue when they are not selected).
  * 'plane' are shown by their axis ending with arrows. When the projection is limited to a sub-domain, by [RangeX] or [RangeY], the bounds are indicated by dashed lines.
  * 'volume' are shown like 'plane', except that they are painted in magenta (or blue) **
+ * 'volume' are shown like 'plane', except that they are painted in magenta (or blue) **.
 Object can be interactively drawn with the mouse on the GUI '''uvmat.fig ''' . First activate the creation mode by selecting the appropriate item in the menu bar Tools, and possibly adjust parameters on the GUI '''set_object.fig'''. Then mark the set of point coordinates by pressing (then release) the left mouse button. Those appear in the table '''[Coord]''' of '''set_object.fig'''. For 'polyline' or 'polygon', press the right hand mouse button to end the line. 'Plane' and 'volume' cannot be created or modified with the mouse.
 …
 The ''physical coordinates'' are defined from the experimental set-up. The correspondance with images is obtained by identifying a set of calibration points whose positions are known in the physical coordinate system. A cartesian calibration grid covering the whole image is the best option, but any set of calibration points can be used. We handle three kinds of transforms:
 -'''rescale''': linear rescaling along ''x'' and ''y'' + translation (no rotation nor deformation)
 -'''linear''': general linear transform, including translation and rotation (but no projection effects)
+-'''rescale''': linear rescaling along ''x'' and ''y'' + translation (no rotation nor deformation).
+-'''linear''': general linear transform, including translation and rotation (but no projection effects).
 -'''3D_linear:''' this transform handles projection effects, needed if the observed plane is not perpendicular to the line of sight. It involves a 3D calibration needed to account for the depth effects occuring in volume scan.
 …
 === 8.2 The GUI geometry_calib.fig ===
+[[Image(geometry_calib.jpg)]]
+-''' Opening the GUI: ''' it is made visible  from the GUI '''uvmat.fig''' by  the menu bar command '''[!Tools/Geometric calibration] '''.  If calibration data already exist in the current file <!ImaDoc>, the corresponding parameters and the list of reference points are displayed in the table '''[!ListCoord]'''. The three first columns indicate the physical coordinates and the two last ones the corresponding image coordinates (in pixels). The physical unit is imposed as centimeter by the menu '''[!CoordUnit]''' to avoid mistakes. Calibration points can be alternatively introduced by opening any XML file <!ImaDoc> with the menu bar command '''[Import]''' of '''geometry_calib.fig'''. It is possible to import the whole information, option 'All', the calibration point coordinates only, or the calibration parameters only.
+[[Image(geometry_calib.jpg)]] -''' Opening the GUI: ''' it is made visible  from the GUI '''uvmat.fig''' by  the menu bar command '''[!Tools/Geometric calibration] '''.  If calibration data already exist in the current file <!ImaDoc>, the corresponding parameters and the list of reference points are displayed in the table '''[!ListCoord]'''. The three first columns indicate the physical coordinates and the two last ones the corresponding image coordinates (in pixels). The physical unit is imposed as centimeter by the menu '''[!CoordUnit]''' to avoid mistakes. Calibration points can be alternatively introduced by opening any XML file <!ImaDoc> with the menu bar command '''[Import]''' of '''geometry_calib.fig'''. It is possible to import the whole information, option 'All', the calibration point coordinates only, or the calibration parameters only.
 -''' Plotting calibration points: ''' press the button '''[PLOT PTS] ''' to visualise the current list of calibration points. The physical or image coordinates will be used in the list '''[!ListCoord]''', depending on the option blank or 'phys' in the menu '''[transform_fct]''' of ''' uvmat.fig''' .
 …
 -'''Section planes:''' deducing the physical coordinates from image coordinates requires information on the section plane. The default assumption is that the objects in the image are in the plane used for calibration, but uvmat can handle volume scanning by a laser plane. A set of section planes can be defined by their origin positions and rotation angle vectors. Theses planes are labelled by a ''z index'', assumed to be the frame index j (case of volume scan), or the index i modulo the number of slices !NbSlice (case of 'multilevel' scan). These settings are stored in the xml file <!ImaDoc> as part of the section <!GeometryCalib> and can be edited from '''uvmat.fig''' with the menu bar command '''[Tools/set slice]'''. A dialog box '''set_slices''' appears for entering the first and last section plane positions ''z'', as well as the number of slices and the option 'volume_scan' ('multilevel' otherwise). In the absence of 3D scan put twice the same value for first and last z.  Finally a tilt angle of the laser sheet, around the ''x'' and ''y'' axis, can be introduced, with a possible angular scanning from first to last section planes. After introduction of the plane position information, the z-index is displayed in the frame '''[FileIndices]''' of '''uvmat.fig'''. The local ''z'' position of the mouse pointer, assumed to lay on the current section plane, is then displayed in '''[text_display]'''.
+-'''Refraction effect:''' refraction effect can be accounted for if calibration was done in air by selecting the check box refraction, and introducing the water height (assumed at ''z''=cte) and refraction index. The apparent distance reduction for objects below the water height will be then taken into account.
+[[Image(browse_data_small.jpg)]]
+[[Image(set_slices_small.jpg)]]
+-'''Refraction effect:''' refraction effect can be accounted for if calibration was done in air by selecting the check box refraction, and introducing the water height (assumed at ''z''=cte) and refraction index. The apparent distance reduction for objects below the water height will be then taken into account.
+[[Image(browse_data_small.jpg)]] [[Image(set_slices_small.jpg)]]
 === 8.3 Structure of the XML file ===
 The coefficients are recorded in the XML element <!ImaDoc/GeometryCalib> as follows:
  * <!CalibrationType>: type of calibration ('rescale', 'linear', '3D...')
+ * <!CalibrationType>: type of calibration ('rescale', 'linear', '3D...').
  * <fx_fy>: focal length along each coordinate of the image sensor, expressed in pixels/cm.
 …
  * <Cx_Cy>: position coordinates of the optical axis on the image sensor.
  * <kc>: coefficient of quadratic deformation (=0 for the options calib_lin and calib_rescale)
+ * <kc>: coefficient of quadratic deformation (=0 for the options calib_lin and calib_rescale).
  * <!CoordUnit>: coordinate unit in physical space.
  * `<Tx_Ty_Tz>`: translation, (Tz=1 for the options calib_lin and calib_rescale)
+ * `<Tx_Ty_Tz>`: translation, (Tz=1 for the options calib_lin and calib_rescale).
  * `<R>`: rotation matrix (in 3 lines). For the option <[https://servforge.legi.grenoble-inp.fr/projects/soft-uvmat/search?q=wiki%3ACalibrationType !CalibrationType]>= 'rescale', [[BR]] R (i=1)= [pxcmx 0 0] R (i=2)= [0 pxcmy 0] R (i=3)= [0 0 1], [[BR]]where pxcmx and pxcmy are the scaling factors along ''x'' and ''y''.
  * <omc> 3 components of the rotation vector (this is for diagnostic use, it is redondant with the matrix R used for actual coordinate transforms).  The physical coordinate axis are transformed to the image coordinate axis by a composition of the translation T and the rotation)
  * <!ErrorRms>: rms difference (in X and Y direction) between the image coordinates measured for the calibration points and the coordinates transformed from their physical coordinates (using the function ''px_XYZ.m in UVMAT'')
  * <!ErrorMax> : maximum difference (in X and Y direction) between the image coordinates measured for the calibration points and the coordinates transformed from their physical coordinates. (using the function ''px_XYZ.m'' in UVMAT)
  * <!SourceCalib> set of the point coordinates used for calibration
  * <!PointCoord> [x y z X Y] , where x,y,z are the physical coordinates of each point, X Y its image coordinates
+ * <omc> 3 components of the rotation vector (this is for diagnostic use, it is redondant with the matrix R used for actual coordinate transforms).  The physical coordinate axis are transformed to the image coordinate axis by a composition of the translation T and the rotation).
+ * <!ErrorRms>: rms difference (in X and Y direction) between the image coordinates measured for the calibration points and the coordinates transformed from their physical coordinates (using the function ''px_XYZ.m in UVMAT'').
+ * <!ErrorMax> : maximum difference (in X and Y direction) between the image coordinates measured for the calibration points and the coordinates transformed from their physical coordinates. (using the function ''px_XYZ.m'' in UVMAT).
+ * <!SourceCalib> set of the point coordinates used for calibration.
+ * <!PointCoord> [x y z X Y] , where x,y,z are the physical coordinates of each point, X Y its image coordinates.
  * <!NbSlice_i> nbre of slices for the first field  index i (multilevel case), =1 by default.
 …
  * <!SliceCoord> [x y z] positions (nb lines) of the nb planes, where nb=NbSlice_i (multilevel case) or nb=NbSlice_j of j indices (volume scan), for parallel volume scan, x=y=0, z= slice height, for angular scan, [x,y,z]=[origin].
  * <SliceDZ>   step distance between planes, or
+ * <SliceDZ>   step distance between planes.
  * <SliceDPhi> step angle for angular scan.
 …
  * ''ima_levels.m'': provides images with modified grey scale intensity to avoid blinking effects on particles.''''''''''
  * ''ima2vol.m'' produce volume images for 3D3C PIV.
  * ''turb_stat.m'': produces turbulent statistics (Reynolds stress tensor)
+ * ''turb_stat.m'': produces turbulent statistics (Reynolds stress tensor).
 These can be used as template to create other functions. The general input of these functions in Matlab structure 'Param' which contains all the input parameters as given by the GUI series (see comments in the function for details). For batch operations, as needed for the cluster, this input is replaced by the name of an XML file which contains these parameters (this is the file produced in the floder '''/0_XML''' under the result directrory Output Subdir ). The first part of the function must give some options for the requested input information and may interactively introduce specific parameters needed for the function. The second part of the function, where the processing itself takes place, is then free from any input (so the operation can be easily dispatched to a remote computer).
 …
 PIV can be performed by selecting the Matlab function ''civ_series'' as '''[!ActionName]''' in the GUI '''series.fig''': then the '''GUI civ_input''' appears to enter the processing parameters. An image file series must have been entered as input of '''series.fig''', or alternatively a Netcdf file resulting form a previous PIV processing (with conventions '''civdata''').
+An alternative possibility is to use the older Fortran program ''CivX'' from the GUI '''civ.fig'''. This can be called directly on the Matlab prompt, by typing  ''>>civ'', or from UVMAT by the menu bar command '''[RUN/PIV (old civ)]'''.    '''-Modes of frame pair indexing''' A first menu '''[!ListCompareMode]''' selects one among four modes of operation:
+An alternative possibility is to use the older Fortran program ''CivX'' from the GUI '''civ.fig'''. This can be called directly on the Matlab prompt, by typing  ''>>civ'', or from UVMAT by the menu bar command '''[RUN/PIV (old civ)]'''.    ''''''
+'''-Modes of frame pair indexing''' A first menu '''[!ListCompareMode]''' selects one among four modes of operation:
  * '''PIV''': makes image comparisons on sliding index pairs, as usual for measuring velocities by particle displacements. A second menu '''[!ListPairMode]''' in the panel '''[!PairIndices]''' then selects one among three possibilities (not always available depending on the file indexing):
 …
  * constant_pixcm: =1 for a simple linear calibration provided by the scaling factors pixcmx and pixcmy, =0 otherwise.
  * pixcmx: scale pixel/space unit (cm by default) along the x direction (only if constant_pixcm=1).
  * pixcmy: scale pixel/space unit (cm by default) along the y direction (only if constant_pixcm=1)
+ * pixcmy: scale pixel/space unit (cm by default) along the y direction (only if constant_pixcm=1).
  * absolut_time_T0: time elapsed since the time origin of the series (the mean time for the two images of the pair is taken).
  * dt: time interval between the two images of the pair.
 …
  * dt2: same as dt for the fields obtained by the second iteration (civ2).
  * hart: =1 if the Hart option has been used for processing (see ref.???), =0 otherwise.
  * civ: =1 if a civ1 operation has been performed (=0 if the field is not obtained from an image pair)
  * fix: =1 if a fix1 operation has been performed,
+ * civ: =1 if a civ1 operation has been performed (=0 if the field is not obtained from an image pair).
+ * fix: =1 if a fix1 operation has been performed.
  * patch: =1 if a patch1 operation has been performed.
  * civ2: =1 if a civ2 operation has been performed.
  * fix2:=1 if a fix2 operation has been performed.
  * patch2: =1 if a Patch2 operation has been performed.
  * patch_nx: number of grid points in the x direction for the patch field
  * patch_ny: number of grid points in the y direction for the patch field
  * ro_patch: smoothing coefficient rho used for patch
  * patch2_nx: number of grid points in the x direction for the patch2 field
  * patch2_ny: number of grid points in the y direction for the patch2 field
  * ro2_patch: smoothing coefficient rho used for patch2
+ * patch_nx: number of grid points in the x direction for the patch field.
+ * patch_ny: number of grid points in the y direction for the patch field.
+ * ro_patch: smoothing coefficient rho used for patch.
+ * patch2_nx: number of grid points in the x direction for the patch2 field.
+ * patch2_ny: number of grid points in the y direction for the patch2 field.
+ * ro2_patch: smoothing coefficient rho used for patch2.
 -'''List of field variables (old CIVx conventions):''' a set of velocity vectors is defined by a 1D array of position coordinates x, y, and z for 3D civ, and a corresponding array for each of the velocity components u, v, and w for 3C civ. The field is therefore defined on an arbitrary set of point, without restriction to a regular mesh. Additional arrays are used to keep track of the quality of the PIV process leading to each vector. The image correlation maximum is represented by vec_C (a real number between 0 and 1). A flag vec_F represents a warning on the vector quality (see the list of values below). Another flag FixFlag marks false vectors: !FixFlag=0 for good vectors, and FixFlag is set to a non-zero value when it has been detected as false (using a 'fix' operation).
 …
 == 14 - Appendix: overview of the package functions == #overview
 === Master GUI ===
  * 'uvmat';...% master function for file scanning and visualisation of 2D fields
+ * 'uvmat';...% master function for file scanning and visualisation of 2D fields.
 === Other GUIs(function .m and associated figure .fig) ===
  * 'browse_data';...% function, associated with the GUI 'browse_data.fig' for scanning directories in a project/campaign
  * 'civ';...   %function associated with the interface 'civ.fig' for PIV and spline interpolation (to be replaced by civ_series in series fcts)
  * 'create_grid';...% called by the GUI geometry_calib to create a physical grid
  * 'dataview';...% function for scanning directories in a campaign
  * 'editxml';...%display and edit XML files using a xls schema
  * 'geometry_calib';...%performs geometric calibration from a set of reference points
  * 'get_field';...% choose and plot a field from a NetCDF file
  * 'msgbox_uvmat';... associated with GUI msgbox_uvmat.fig to display message boxes, for error, warning or input calls
  * 'rotate_points';...%'rotate_points': associated with GUI rotate_points.fig to introduce (2D) rotation parameters
  * 'series';...% master function for analysis field series, with interface 'series.fig'
  * 'set_grid';...% creates a grid for PIV
  * 'set_object';...%  edit a projection object
  * 'translate_points';...% associated with GUI translate_points.fig to display translation parameters
  * 'view_field';...% function for visualisation of projected fields'
 === Functions activated by mouse and keybord in GUI  ===
  * 'keyboard_callback';... % function activated when a key is pressed on the keyboard
  * 'mouse_down';% function activated when the mouse button is pressed on a figure (callback for '!WindowButtonDownFcn')
  * 'mouse_motion';...% permanently called by mouse motion over a figure (callback for '!WindowButtonMotionFcn')
  * 'mouse_up';... % function to be activated when the mouse button is released (callback for '!WindowButtonUpFcn')
+ * 'civ';...   %function associated with the interface 'civ.fig' for PIV and spline interpolation (to be replaced by civ_series in series fcts).
+ * 'create_grid';...% called by the GUI geometry_calib to create a physical grid.
+ * 'dataview';...% function for scanning directories in a campaign.
+ * 'editxml';...%display and edit XML files using a xls schema.
+ * 'geometry_calib';...%performs geometric calibration from a set of reference points.
+ * 'get_field';...% choose and plot a field from a NetCDF file.
+ * 'msgbox_uvmat';... associated with GUI msgbox_uvmat.fig to display message boxes, for error, warning or input calls.
+ * 'rotate_points';...%'rotate_points': associated with GUI rotate_points.fig to introduce (2D) rotation parameters.
+ * 'series';...% master function for analysis field series, with interface 'series.fig'.
+ * 'set_grid';...% creates a grid for PIV.
+ * 'set_object';...%  edit a projection object.
+ * 'translate_points';...% associated with GUI translate_points.fig to display translation parameters.
+ * 'view_field';...% function for visualisation of projected fields'.
+=== Functions activated by mouse and keybord in GUI ===
+ * 'keyboard_callback';... % function activated when a key is pressed on the keyboard.
+ * 'mouse_down';% function activated when the mouse button is pressed on a figure (callback for '!WindowButtonDownFcn').
+ * 'mouse_motion';...% permanently called by mouse motion over a figure (callback for '!WindowButtonMotionFcn').
+ * 'mouse_up';... % function to be activated when the mouse button is released (callback for '!WindowButtonUpFcn').
 === Main functions used ===
  * 'civ_matlab';...% civ programs, Matlab version (called by civ.m, option Civprogram/Matlab in the upper menu bar)
  * 'plot_field';...%displays a vector field and/or scalar or images
  * 'plot_object';...%draws a projection object (points, line, plane...)
  * 'proj_field';...%project a field on a projection object (plane, line,...)
+ * 'civ_matlab';...% civ programs, Matlab version (called by civ.m, option Civprogram/Matlab in the upper menu bar).
+ * 'plot_field';...%displays a vector field and/or scalar or images.
+ * 'plot_object';...%draws a projection object (points, line, plane...).
+ * 'proj_field';...%project a field on a projection object (plane, line,...).
  * 'RUN_STLIN';...% combine 2 displacement fields for stereo PIV * 'sub_field';...% combine the two input fields,
 === convert and I/O functions ===
  * 'cell2tab';... % transform a Matlab cell in a character array suitable for display in a table
  * 'fill_GUI';... % fill a GUI with handles 'handles' from input data Param
  * 'imadoc2struct';...% convert the image documentation file <!ImaDoc> into a Matlab structure
  * 'nomtype2pair';... creates nomenclature for index pairs knowing the image nomenclature, used by series fct
  * 'nc2struct';...% transform a NetCDF file in a corresponding Matlab structure
+ * 'cell2tab';... % transform a Matlab cell in a character array suitable for display in a table.
+ * 'fill_GUI';... % fill a GUI with handles 'handles' from input data Param.
+ * 'imadoc2struct';...% convert the image documentation file <!ImaDoc> into a Matlab structure.
+ * 'nomtype2pair';... creates nomenclature for index pairs knowing the image nomenclature, used by series fct.
+ * 'nc2struct';...% transform a NetCDF file in a corresponding Matlab structure.
  * 'num2stra';...% transform number to the corresponding character string depending on the nomenclature.
  * 'read_field':...% read the fields from files in different formats (NetCDF files, images, video)
  * 'read_GUI'::...% read a GUI and provide the data as a Matlab structure
  * 'read_image';... read images or video objects
  * 'read_multimadoc';... %read a set of Imadoc files and compare their timing of different file series 'read_xls';...%read excel files containing the list of the experiments
  * 'stra2num';...% transform letters (a, b, A, B,) or numerical strings ('1','2'..) to the corresponding numbers
  * 'struct2nc';...% write fields in NetCDF files
+ * 'read_field':...% read the fields from files in different formats (NetCDF files, images, video).
+ * 'read_GUI'::...% read a GUI and provide the data as a Matlab structure.
+ * 'read_image';... read images or video objects.
+ * 'read_multimadoc';... %read a set of Imadoc files and compare their timing of different file series 'read_xls';...%read excel files containing the list of the experiments.
+ * 'stra2num';...% transform letters (a, b, A, B,) or numerical strings ('1','2'..) to the corresponding numbers.
+ * 'struct2nc';...% write fields in NetCDF files.
  * 'struct2xml';... transform a Matlab structure to a XML tree.
  * 'xml2struct'...% read an XML file as a Matlab structure, converts numeric character strings into numbers
+ * 'xml2struct'...% read an XML file as a Matlab structure, converts numeric character strings into numbers.
 === ancillary functions ===
  * 'activate';...% emulate the mouse selection of a GUI element, for demo
  * 'calc_field_interp': defines fields (velocity, vort, div...) from civ data and calculate them for projection with linear interpolation
  * 'calc_field_tps': defines fields (velocity, vort, div...) from civ data and calculate them with tps interpolation
  * calc_tps': calculate the thin plate spline (tps) coefficients for interpolation
+ * 'activate';...% emulate the mouse selection of a GUI element, for demo.
+ * 'calc_field_interp': defines fields (velocity, vort, div...) from civ data and calculate them for projection with linear interpolation.
+ * 'calc_field_tps': defines fields (velocity, vort, div...) from civ data and calculate them with tps interpolation.
+ * calc_tps': calculate the thin plate spline (tps) coefficients for interpolation.
  * 'check_files';...% check the path, modification date and svn version for all the function in the toolbox UVMAT.
  * 'close_fig';...% function  activated when a figure is closed
  * 'compile';...% compile a Matlab function, create a binary in a subdirectory /bin
  * 'copyfields';...% copy fields between two Matlab structures
  * 'delete_object';...%delete a projection object, defined by its index in the Uvmat list or by its graphic handle
  * 'displ_uvmat';...% display a message using  msgbox_uvmat or on the log file in batch mode
  * 'fileparts_uvmat': splits a file name in root and indices and recognize file naming convention
  * 'filter_tps';...% find the thin plate spline coefficients for interpolation-smoothing
  * 'find_field_cells';...% group the variables of a nc-formated Matlab structure into 'fields' with common dimensions
  * find_field_cells': test field structure for input in proj_field and plot_field, group the variables  into 'fields' with common dimensions
  * 'find_file_series';...%check the content of an input file and find the corresponding file series
  * 'find_imadoc';...% find the <!ImaDoc> XML file associated with a given input file
+ * 'close_fig';...% function  activated when a figure is closed.
+ * 'compile';...% compile a Matlab function, create a binary in a subdirectory /bin.
+ * 'copyfields';...% copy fields between two Matlab structures.
+ * 'delete_object';...%delete a projection object, defined by its index in the Uvmat list or by its graphic handle.
+ * 'displ_uvmat';...% display a message using  msgbox_uvmat or on the log file in batch mode.
+ * 'fileparts_uvmat': splits a file name in root and indices and recognize file naming convention.
+ * 'filter_tps';...% find the thin plate spline coefficients for interpolation-smoothing.
+ * 'find_field_cells';...% group the variables of a nc-formated Matlab structure into 'fields' with common dimensions.
+ * find_field_cells': test field structure for input in proj_field and plot_field, group the variables  into 'fields' with common dimensions.
+ * 'find_file_series';...%check the content of an input file and find the corresponding file series.
+ * 'find_imadoc';...% find the <!ImaDoc> XML file associated with a given input file.
  * 'fullfile_uvmat';...%creates a file name from a root name and indices.
  * 'get_file_series';...% determine the list of file names and file indices for functions called by 'series'.
  * 'get_file_type': determine info about a file (image, multimage, civdata,...)
  * 'griddata_uvmat';...%make 2D linear interpolation using griddata, with input appropriate for both Matlab 6.5 and 7
  * 'hist_update';...%  update of a current global histogram by inclusion of a new field
  * 'imadoc2struct';...%convert the image documentation file <!ImaDoc> into a Matlab structure
  * 'interp2_uvmat';...% linearly interpolate an image or scalar defined on a regular grid
  * '!ListDir';... scan the structure of the directory tree (for dataview.m)
  * 'mask_proj';...% restrict input fields to a mask region, set to 0 outside
+ * 'get_file_type': determine info about a file (image, multimage, civdata,...).
+ * 'griddata_uvmat';...%make 2D linear interpolation using griddata, with input appropriate for both Matlab 6.5 and 7.
+ * 'hist_update';...%  update of a current global histogram by inclusion of a new field.
+ * 'imadoc2struct';...%convert the image documentation file <!ImaDoc> into a Matlab structure.
+ * 'interp2_uvmat';...% linearly interpolate an image or scalar defined on a regular grid.
+ * '!ListDir';... scan the structure of the directory tree (for dataview.m).
+ * 'mask_proj';...% restrict input fields to a mask region, set to 0 outside.
  * 'peaklock';...%
  * 'phys_XYZ';...% transform coordinates from pixels to phys
  * 'px_XYZ';...% transform coordiantes from phys to pixels
  * 'read_civxdata';...reads CIVx data from NetCDF files
  * 'read_civdata';... reads new civ data from NetCDF files
  * 'read_geometry_calib';... read data on the GUI geometry_calib
  * 'read_imatext';...%read .civ files (obsolete, but can be adapted to other text documentation files)
  * 'read_xls';...%read excel files containing the list of the experiments
  * 'reinit';...% suppress the personal parameter file 'uvmat_perso.mat'
  * 'set_col_vec';...% sets the color code for vectors depending on a scalar and input parameters (used for plot_field)
  * 'set_subdomains';...% sort a set of points defined by scattered coordinates in subdomains, as needed for tps interpolation
  * 'tps_coeff';...% calculate the thin plate spline (tps) coefficients
  * 'tps_coeff_field';...% calculate the thin plate spline (tps) coefficients with subdomains for a field structure
+ * 'phys_XYZ';...% transform coordinates from pixels to phys.
+ * 'px_XYZ';...% transform coordiantes from phys to pixels.
+ * 'read_civxdata';...reads CIVx data from NetCDF files.
+ * 'read_civdata';... reads new civ data from NetCDF files.
+ * 'read_geometry_calib';... read data on the GUI geometry_calib.
+ * 'read_imatext';...%read .civ files (obsolete, but can be adapted to other text documentation files).
+ * 'read_xls';...%read excel files containing the list of the experiments.
+ * 'reinit';...% suppress the personal parameter file 'uvmat_perso.mat'.
+ * 'set_col_vec';...% sets the color code for vectors depending on a scalar and input parameters (used for plot_field).
+ * 'set_subdomains';...% sort a set of points defined by scattered coordinates in subdomains, as needed for tps interpolation.
+ * 'tps_coeff';...% calculate the thin plate spline (tps) coefficients.
+ * 'tps_coeff_field';...% calculate the thin plate spline (tps) coefficients with subdomains for a field structure.
  * 'tps_eval';... %calculate the thin plate spline (tps) interpolation at a set of points
  * 'tps_eval_dxy';...% calculate the derivatives of thin plate spline (tps) interpolation at a set of points (limited to the 2D case)
  * 'uigetfile_uvmat';... browser, and display of directories, faster than the Matlab fct uigetfile
+ * 'tps_eval_dxy';...% calculate the derivatives of thin plate spline (tps) interpolation at a set of points. (limited to the 2D case).
+ * 'uigetfile_uvmat';... browser, and display of directories, faster than the Matlab fct uigetfile.
  * 'update_imadoc';...  %update the XML file <!ImaDoc>.
  * 'update_waitbar';... update the waitbar display, used for ACTION functions in the GUI 'series'
+ * 'update_waitbar';... update the waitbar display, used for ACTION functions in the GUI 'series'.
 === series functions ===
  * 'aver_stat': calculate field average over a time series
+ * 'aver_stat': calculate field average over a time series.
  * 'avi2png': copy an avi movie to a series of B/W .png images (take the average of green and blue color components)
  * 'check_data_files': check the existence, type and status of the files selected by series.fig
+ * 'check_data_files': check the existence, type and status of the files selected by series.fig.
  * 'ima_levels': rescale the image intensity to reduce strong luminosity peaks (their blinking
  * 'civ_input': function associated with the GUI 'civ_input.fig' to set the input parameters for civ_series
  * 'civ_series': PIV function activated by the general GUI series (replaces civ)
  * 'merge_proj': concatene several fields from series, can project them on a regular grid in phys coordinates
  * 'sub_background': subtract a sliding background to an image series
  * 'time_series': extract a time series after projection on an object (points , line..)
+ * 'civ_input': function associated with the GUI 'civ_input.fig' to set the input parameters for civ_series.
+ * 'civ_series': PIV function activated by the general GUI series (replaces civ).
+ * 'merge_proj': concatene several fields from series, can project them on a regular grid in phys coordinates.
+ * 'sub_background': subtract a sliding background to an image series.
+ * 'time_series': extract a time series after projection on an object (points , line..).
 === transform functions ===
  * 'ima_filter': low-pass filter of an image (builtin filtering parameter)
  * 'ima_remove_background': removes backgound from an image (using the local minimum)
  * 'ima_remove_particles': removes particles from an image (keeping the local minimum)
+ * 'ima_filter': low-pass filter of an image (builtin filtering parameter).
+ * 'ima_remove_background': removes backgound from an image (using the local minimum).
+ * 'ima_remove_particles': removes particles from an image (keeping the local minimum).
  * 'FFT2_detrend': calculate the 2D spectrum of the input scalar after removing the linear trend (requires the Matlab image processing toolbox).
  * 'phys': transforms image (Unit='pixel') to real world (phys) coordinates using geometric calibration parameters. It acts if the input field contains the tag '!CoordUnit' with value 'pixel'
+ * 'phys': transforms image (Unit='pixel') to real world (phys) coordinates using geometric calibration parameters. It acts if the input field contains the tag '!CoordUnit' with value 'pixel'.
  * 'phys_polar': this transforms the fields to polar coordinates, radius in abscissa (same unit as x, y) and azimuth in ordinate (unit =degree).