iFit: Changes and Bugs


  1. Releases and Changes
  2. Bugs list:
    1. Data set maximum size
    2. Convolution brings strange results (iFuncs/fconv)
    3. Too many warnings displayed
    4. Execution/compilation issue with text files importer (iLoad/iData/load, looktxt)

Releases and Changes

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.
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 ILL, Grenoble, France <www.ill.eu>