iFit: Changes and Bugs
- Releases and Changes
- Bugs list:
- Data set maximum size
- Convolution brings strange results (iFuncs/fconv)
- Too many warnings displayed
- Execution/compilation issue with text files importer (iLoad/iData/load, looktxt)
Releases and Changes
- 1.1.1: Reading of Chalk River CNBC data files, improved recursive reading of subdirectories and handling of iData arrays. New colormap plotting method. Improvements in the iOptim/McStas plotting. Speed up by +12% (March 16th, 2012)
- 1.1: new methods (save, diff, hyperbolic functions), fix of the Levenberg-Marquardt optimizer,
improved Error propagation for unary operators, support for import of
Analyze MRI (hdr/img) and Crystallographic Binary File (cbf) format,
import post-process for HDF RITA2@PSI files, direct drag-drop data
files using the open{ext} functions with Matlab >= 2010, added many fit models including 2D
functions signal=f(x,y). Improved speed by e.g. +25% (Feb 14th 2012)
- 1.0.4: significant performance improvements (speedup by factor 2-10). (Oct 24th 2011)
- 1.0.3: new fit criteria (others than least-square), link as external/distant resources, better INX import anchor in file names for selective import, plenty of new fit functions, a few bug fixes (e.g. McStas 2D labels). (Sept 22nd 2011)
- 1.0.2: McStas data files with Parameter member. New waterfall plot stype for 3D data sets (Sept 6th, 2011)
- 1.0.1:
Added correlation function method, plus a number of minor improvements
(esp. in plot contextual menus), and bug fix for McStas 1D data set
import (August 26th 2011)
- 1.0: First official iFit release (August 16th 2011)
Bugs list:
You may test the package integrity by issuing the command:
>> ifittest
which will test, in a few minutes, all the examples given in this documentation and report
failures. The test may be aborted by closing the progress bar window.
Please report bugs to
ifit-users@mccode.org or to me
[farhi (at) ill.fr]. You are encouraged to register to the
ifit-users list.
Data set maximum size
The iFit package may currently handle routinely data sets up to few 100
Mb. Larger data sets can still be loaded, but are restricted by the
disk access and the available memory. Currently, files can be read at
about 8 Mb/s, mainly limited by the hard disk speed. Some binary files
can be imported faster (HDF import is nearly immediate, whatever be the
size).
Convolution brings strange results (iFuncs/fconv)
The fconv function (FFT convolution) provided in the iFuncs sub-library requires the two signals sampling not to be too coarse. Axes values too
sparse will lead to inaccurate results. One solution is to re-sample
the signals with more points. For iData objects, this can be
achieved with e.g. the interp(object, 3) to triple the number of points along axes.
Too many warnings displayed
If the warnings being displayed produce too much output, you may reduce the level of verbosity with:
>> warning off backtrace % reduce the warning message length
>> warning off % suppress all warnings (not recommended)
Execution/compilation issue with text files importer (iLoad/iData/load, looktxt)
In some cases, the provided
iFit/iFiles/private/looktxt.mex* may fail to execute (wrong
architecture, missing library).
Under Windows 64bit systems,
you need the Visual C++ runtime libraries e.g. msvc[mpr]90.dll which
are provided with the Visual C++ installation (see below), to put in the
Windows system directory.
In case this is not a problem of library, remove the invalid mex file
(in
iFit/iFiles/private) , and
relaunch the importation process. A brand new MeX file will
automatically be generated, using the system C compiler.
Most systems provide a default C compiler.
- Linux systems usually ship with gcc.
- MacOSX systems require to install the Xcode development tools.
- Windows 32 systems may use the LCC compiler shipped with Matlab.
- Windows 64 systems must have Microsoft Visual C++ installed (refer to the Install page for the procedure).
You may need to select the compiler with the
mex -setup command from Matlab.
It has been reported that MeX compilation may fail when spaces are part of the path name to the iFit location.
Move iFit to an other location which does not include spaces in its name (e.g. avoid My Documents) for compilation.
E.
Farhi - iFit/Changes -
$Date: 2012-03-16 14:09:39 $ $Revision: 1.28 $
-
back to
Main
iFit Page