Context Navigation

Changes between Version 47 and Version 48 of UvmatHelp

Timestamp:: Jun 6, 2013, 8:55:27 PM (12 years ago)
Author:: sommeria
Comment:: --

Legend:

: Unmodified
: Added
: Removed
: Modified

UvmatHelp

-                      v47
+                      v48
 The grid will be limited to an  image , or to the common region of two images, depending whether one or two image names are indicated in the edit boxes image_1 and image_2. Press save to save the corresponding grid file (s). A dialog box appears to edit the name of the output grid file, and a second one in case of two images.
 == 10- Processing field series: ==
 === 10.1 The GUI series.fig: ===
 Operations on field series are controled by the GUI '''series.fig''', which allows the user to set the root name(s) and file indices over which a processing function operates. The root path, subdirectory, root file name and extension are introduced in the same way as with the uvmat interface, in the different columns of the table '''InputTable'''. The nomenclature for file indexing is represented in the column '''[NomType]'''.
 Several input file series can be introduced simultaneously by the menu bar command''' [Open_append]''', filling the successive lines of '''InputTable'''. By contrast, the current input series is refreshed by the browser displayed by the menu bar command''' [Open]'''. The cells in the table can be also edited manually.
 The velocity type and field is automatioally chosen by default, but it can be specified by VelType and Field. For that purpose use the menus VelTypeMenu and fieldsinput. In case of multiple input file series, these menus act only on the first line.
 The processing function is chosen in the menu '''[ActionName]'''.  All actions operate on the same series of input files, whose list can be obtained with the first option 'check_data_files'. The option 'aver_stat' calculates  a global average on the successive fields, while 'time_series' provides a time series. The option 'merge_proj' is used to project a whole series on a given grid, or to create a file series by concatenation of different fields. The option civ_series gives acees to the PIV processsing, see section [#a11-PIV:ParticleImagingVelocimetry: section 11]. Finally any additional function can be called and included in the menu by selecting the option 'more...' . The corresponding path is displayed in '''ActionPath'''.
+== 10 - Processing field series ==
+=== 10.1 The GUI series.fig ===
+Operations on field series are controled by the GUI '''series.fig''', which allows the user to set the root name(s) and file indices over which a processing function operates. The root path, subdirectory, root file name and extension are introduced in the different columns of the table '''!InputTable'''. The nomenclature for file indexing is represented in the column '''[!NomType]'''.
+Several input file series can be introduced simultaneously by the menu bar command''' [Open_append]''', filling the successive lines of '''!InputTable'''. By contrast, the table of input files is fully refreshed by the browser of the menu bar command '''[Open]'''. The cells in the table can be also edited manually. Then press the button '''[REFRESH]''' to validate the input.
+The velocity type and field are automatioally chosen by default, but can be specified by the menus '''[VelType]''' and '''[Field]'''. For that purpose use the menus VelTypeMenu and fieldsinput. In case of multiple input file series, these menus act only on the first line.
+The processing function is chosen in the menu '''[!ActionName]'''.  All actions operate on the same series of input files, whose list can be obtained with the first option 'check_data_files'. The option 'aver_stat' calculates  a global average on the successive fields, while 'time_series' provides a time series. The option 'merge_proj' is used to project a whole series on a given grid, or to create a file series by concatenation of different fields. The option civ_series gives acees to the PIV processsing, see section [#a11-PIV:ParticleImagingVelocimetry section 11]. Finally any additional function can be called and included in the menu by selecting the option 'more...' . The corresponding path is displayed in '''!ActionPath'''.
 Each function in series can be run in local mode, i;e. on the current Matlab session, or as background, by selecting the corresponding option in '''!RunMode'''. In background mode, calculation is done a new Matlab session (without graphics) so that the current Matlab session is free for new operations. If a cluster system has been detected, a third option 'cluster' appears in the menu, allowing to dispatch parallel computations on a computer cluster. For the latter option, a compiled version of the Action function is useful, to avoid installing Matlab on each node of the cluster. This is achieved by selecting the option .sh in the menu '''ActionExt'''. If the compiled version is not yet available, or outdated, the GUI proposes a new compilation of the selected function.
 …
 === 10.3 aver_stat: ===
   This option provides any average over the processed files. If nb_slice is not equal to 1, the average is performed slice by slice, providing nb_slice results.   If a projection object is selected (check box GetObject), the field is projected before averaging.
   For unstructured coordinates varying for successive fields, the data is linearly interpolated on the coordinates of the first field in the series. It is then advised to project the fields on a regular grid, creating a projection object of type 'plane' with projection mode 'interp'.
   With a projection object with title PATCH, the global histogram of field variables on the selected region will be obtained.
+This option provides any average over the processed files. If nb_slice is not equal to 1, the average is performed slice by slice, providing nb_slice results.   If a projection object is selected (check box GetObject), the field is projected before averaging.
+For unstructured coordinates varying for successive fields, the data is linearly interpolated on the coordinates of the first field in the series. It is then advised to project the fields on a regular grid, creating a projection object of type 'plane' with projection mode 'interp'.
+With a projection object with title PATCH, the global histogram of field variables on the selected region will be obtained.
 In the case of two input files series, the field difference will be perfomed like with the interface uvmat.fig. It is not possible to use more than two input series for this funtion.
 === 10.4 time_series ===
   This action provides a time series of the input field. It is advised to use a POINTS projection object, so the series is limited to the selected points.
+This action provides a time series of the input field. It is advised to use a POINTS projection object, so the series is limited to the selected points.
 In the case of two input files series, the field difference will be perfomed like with the interface uvmat.fig. It is not possible to use more than two input series for this funtion.
 === 10.5 merge_proj } ===
   This option allows to merge several field series  in a single one. This is useful to merge fields obtained with different cameras. Select the different series, activating the check box add. In this case, it is generally useful to first interpolate the fields on a single grid. For that purpose select the check box GetObject, creating a projection object of type 'plane' with projection mode 'interp'.
   Since the different views have their own calibration, it is important to use the option 'phys' (menu menu_coord), and to create the grid in phys coordinates.
+=== 10.5 merge_proj ===
+This option allows to merge several field series  in a single one. This is useful to merge fields obtained with different cameras. Select the different series, activating the check box add. In this case, it is generally useful to first interpolate the fields on a single grid. For that purpose select the check box GetObject, creating a projection object of type 'plane' with projection mode 'interp'.
+Since the different views have their own calibration, it is important to use the option 'phys' (menu menu_coord), and to create the grid in phys coordinates.
 === 10.6 more... ===
 …
 === 11.2 CIV1: ===
  The image pair is selected in the menu '''[list_pair_civ1]''', see sub-section 10.1. The time interval of the image pair must be chosen sufficiently small to provide a good correlation, and sufficiently large to provide good measurment precision: a displacement of 5-10 pixels is generally optimum.
+The image pair is selected in the menu '''[list_pair_civ1]''', see sub-section 10.1. The time interval of the image pair must be chosen sufficiently small to provide a good correlation, and sufficiently large to provide good measurment precision: a displacement of 5-10 pixels is generally optimum.
 The time interval for each image pair is indicated in '''[list_pair_civ1]''' iif the information is made available, either from a movie file, or from a detected xml file (with the name RootName.xml). The source of the timing information is indicated in the edit box '''[ImaDoc]'''. Examples of xml files are provides in /XML_SCHEMAS/ImaDoc_templates. In the absence of information, the file index is taken for the time.  The time interval for a given index pair may change with time, so the time interval display is taken for given reference indices, given by '''[i_ref]''' and ''' [j_ref].'''.