FUZZEKS [to Index]
Requirements and limitations
FUZZEKS 1.0 Demo is for demonstrational purposes only.
For legal information read the notice that appears on program start.
Requirements
In order to run FUZZEKS you need at least
- PC running Windows 3.1, 386 processor or better, 4 MB or more.
(The limitations are because Windows must run in enhanced mode:
with 286 PC or less than 3 MB memory free before starting Windows,
you can only run Windows in real mode; otherwise enhanced mode is
chosen by Windows automatically.)
- Color graphics card (VGA or better)
- Mouse (or equivalent pointing device)
Demo limitations
- Data export: Kriging to ASCII output file: max. 10 * 10 values.
- Data export: Copying graphics to clipboard: max. 40000 pixel.
Main technical limitations
- There is a maximum of 1300 values per input parameter
(because of a 16MB-limit of Windows 3.1 memory blocks and
all input points are used for the interpolation of each value).
- The kriging resolution is limited to 279000 nodes (x*y)
(the same reason; 279000 nodes are only possible if 2 cuts are defined in
int the input data file).
Remark: This does not affect the display of isolines very much, because
an additional interpolation method is used between the points that
are estimated by the fuzzy kriging procedure.
- Only five kriging windows (or e.g. three kriging windows and three
membership function windows) can be open at the same time.
- All parts of the program need memory to execute. Therefore the amount
of RAM can be a limiting factor. It is possible to weaken this limit
by using the swapping mechanism of windows (virtual memory).
Memory and time consumption in detail
The memory requirements depend on the size of your input data files.
If the file contains one parameter with n data points, you need about
n * (n+2) * 8 bytes of continuous free RAM memory.
As example: One parameter with 100 data points and another one with 200 data
points need altogether 81600+323200 bytes (404800 bytes or 396 KB).
The memory may be virtual, but if one single parameter uses more memory
than you really have, the calculation times would increase so immense
(because of swapping delays) that this swapping mechanism of Windows
is of no value.
Another property can also be considered a limitation: The calculation time
increases very fast when n increases. The calculation time is
about some constant time multiplied by
n * n * n.
As example: For n=100 you have to wait about 20 seconds for the results
(33MHz-486, experimental variogram and kriging without variance calculated).
For n=50, the half amount of data points, only about the eigth part of
that time is needed. But for n=1300 you have to wait about half a day.