Changes between Version 109 and Version 110 of UvmatHelp
- Timestamp:
- Aug 13, 2014, 7:56:46 PM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
UvmatHelp
v109 v110 178 178 * 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. 179 179 180 * ''' Grid:''' List of numbers (in ASCII text) specifying the set of points where the PIV processing is performed. It specifies the number of points n and a corresponding list of x and y coordinates expressed in image pixels, as follows 181 {{{ 180 * ''' Grid:''' List of numbers (in ASCII text) specifying the set of points where the PIV processing is performed. 181 It specifies the number of points n and a corresponding list of x and y coordinates expressed in image pixels, as follows 182 {{{ 182 183 n X1 Y1 X2 Y2 ...... Xn Yn 183 184 }}} … … 188 189 189 190 * ''''.civ' ''' (obsolete) ASCII text file containing the list of image times and the scaling in pixels/cm. This is an obsolete version of the XML image documentation file. It is stored in the same directory as the corresponding series of images, with name ''root .civ''. It is automatically sought by '''uvmat.fig''' and '''series.fig''', in the absence of an XML file <!ImaDoc>. (it is read by the function ''read_imatext.m''). The following example is from an experience with 19 bursts of 4 images, named aa001a,aa001b,aa001c,aa001d,aa002a,aa002b,...,aa019c,aa019d, with an extension .png. The corresponding .civ file is named aa.civ. Comments (not included in the file) are indicated with %... 190 191 {{{ 191 {{{ 192 192 19 % number of bursts 193 193 1024 1024 % image size npx npy … … 204 204 19 450.000824 30 60 30 1 205 205 }}} 206 206 207 * '''.cmx''' ASCII text files containing the parameters sent by the GUI '''civ.fig''' to the CIV fortran programmes. Each velocity field named *.nc results from a parameter file *.cmx. It can be opened by the browser of '''uvmat.fig'''. In a later version of CIVx**, the .cmx file is replaced by a .xml ’!CivDoc’ file. 207 208 … … 517 518 ---- 518 519 == 7 - NetCDF files and the GUI get_field == 519 === 7.1 The NetCDF format === 520 === 7.1 The NetCDF format === #netcdf 520 521 NetCDF (Network Common Data Form) is a machine-independent format for representing scientific data, suitable for large arrays (http://www.unidata.ucar.edu/software/netcdf/). Each piece of data can be directly accessed by its tag name without reading the whole file. New records can be added to the file without perturbing the remaining information. The next release of NetCDF is now connected to the more recent HDF format. 521 522 … … 829 830 830 831 === 11.7 Description of the velocity files: === #civdata 831 The velocity fields obtained by PIV, as well as their spatial derivatives, are stored in the machine independent binary format [ 'NetCDF'->#netcdf]. The file contains constants ('global attributes') and fields ('variables') whose values can be directly accessed by their name.832 The velocity fields obtained by PIV, as well as their spatial derivatives, are stored in the machine independent binary format [#netcdf NetCDF]. The file contains constants ('global attributes') and fields ('variables') whose values can be directly accessed by their name. 832 833 833 834 Several fields, corresponding to the successive operations 'civ1', 'fix1', 'patch1', 'civ2', 'fix2', 'patch2' are stored in the same .nc file. When a third or higher order civ iteration is performed, a new .nc file is created, containing the two last iterations as civ1 and civ2.
