File Storage

NAVIGATION

Summary : Users guide
Previous page : Density information
Next page : Dataset handling

In order to save and recall the FIS parameters, SLIFIS::Read() and SLIFIS::Write() are provided.

Introduction

The Write() function saves all the parameters (set of membership functions, input and output, and rules) into a file whose name is given as argument. Data can be saved into several formats, at present these are:

compact binary (not human-readable),
xml, through the usage of TinyXML library (see http://sourceforge.net/projects/tinyxml/ and see http://www.grinninglizard.com/tinyxmldocs/index.html);
Please note that the used xml format is not the same as FML (http://en.wikipedia.org/wiki/Fuzzy_markup_language), although it might one day...
FCL (at present only writing implemented).

Writing to file is as simple as this (you should use for "ext" the appropriate extension, "xml", "fcl" or "fis" for binary format. On failure, it will throw an error (see Error handling).

fis.Write( "MyFile.ext" );

Reading from file is achieved with this:

SLIFIS fis;
Read( "MyFis.ext" );

If you want to catch errors on reading, then the code will become:

SLIFIS fis;
try
{
        Read( "MyFis.ext" );
}
catch( std::exception const& e )
{
        cout << "unable to read file, msg:" << e.what();
}

To select the format, just call the static function SLIFIS::SetDefaultIO() with one of the values in slifis::EN_FF_TYPE, as in the following example:

SLIFIS::SetDefaultIO( IO_XML );

Additional information:

For binary format, choice of extension is free, but it is recommended to keep .fis extension. This way, you can associate this extension with the provided application try-fis.cpp, so your desktop will run it when activating (=double-clic) such a file.
All the I/O functions will return true in case of success, or false in case of I/O problem. In this latter case, a message will be written to the logfile.
All the content of the Fis is saved on file, including defuzzyfication and inference parameters.

XML format

XML I/O is achieved using the additional tinyxml library, currently. It is included in source tree, but user can disable XML support at build time using an appropriate flag when calling makefile (see Build options).

See below an example of generated xml file:

<?xml version="1.0" ?>
<slifis lib_version="0.7.1">
    <file_version>xml_1.2</file_version>
    <name>tipping</name>
    <type>MAMDANI</type>
    <date>Wed May 22 23:51:53 2013&#x0A;</date>
    <infer_params DefuzzMethod="0" ImplicationMethod="0" OutputAggregation="0" RuleAndMethod="0" RuleOrMethod="0" />
    <input_sets nb_inputs="2">
        <mf_set name="service" nb_mf="3">
            <mf name="poor" nb_pts="2">
                <pt x="0" y="1" />
                <pt x="3" y="0" />
            </mf>
            <mf name="good" nb_pts="4">
                <pt x="0" y="0" />
                <pt x="3" y="1" />
                <pt x="7" y="1" />
                <pt x="10" y="0" />
            </mf>
            <mf name="excellent" nb_pts="2">
                <pt x="7" y="0" />
                <pt x="10" y="1" />
            </mf>
        </mf_set>
        <mf_set name="food" nb_mf="2">
            <mf name="rancid" nb_pts="2">
                <pt x="0" y="1" />
                <pt x="10" y="0" />
            </mf>
            <mf name="delicious" nb_pts="2">
                <pt x="0" y="0" />
                <pt x="10" y="1" />
            </mf>
        </mf_set>
    </input_sets>
    <output>
        <mf_set name="tip" nb_mf="3">
            <mf name="cheap" nb_pts="3">
                <pt x="0" y="0" />
                <pt x="0.05" y="1" />
                <pt x="0.15" y="0" />
            </mf>
            <mf name="average" nb_pts="3">
                <pt x="0.05" y="0" />
                <pt x="0.15" y="1" />
                <pt x="0.25" y="0" />
            </mf>
            <mf name="generous" nb_pts="3">
                <pt x="0.15" y="0" />
                <pt x="0.25" y="1" />
                <pt x="0.3" y="0" />
            </mf>
        </mf_set>
    </output>
    <rule_base nb_rules="3">
        <rule type="MAMDANI" operation="OR" nb_terms="2" degree="1" output="0">
            <term input="0" value="0" />
            <term input="1" value="0" />
        </rule>
        <rule type="MAMDANI" operation="OR" nb_terms="1" degree="1" output="1">
            <term input="0" value="1" />
        </rule>
        <rule type="MAMDANI" operation="OR" nb_terms="2" degree="1" output="2">
            <term input="0" value="2" />
            <term input="1" value="1" />
        </rule>
    </rule_base>
</slifis>

FCL format

Slifis can export the fis in the FCL format. Importing is planned in further release. For additional information on FCL format, please see:

http://en.wikipedia.org/wiki/Fuzzy_Control_Language (has a link on the IEC document)
http://www.dmitry-kazakov.de/ada/ifcl.htm
http://jfuzzylogic.sourceforge.net/html/fcl.html

See below an example of a produced FCL file (build-time generated, if nothing below, please rebuild with 'make-test', and/or check Building the software).

-- FCL definition file (IEC 61131-7)
-- This file was generated by the SLIFIS libray, version 0.7.1, on Wed May 22 23:51:53 2013

FUNCTION_BLOCK shower
VAR_INPUT
    temperature:        REAL;
    pressure:   REAL;
END_VAR
VAR_OUTPUT
    output: REAL;
END_VAR
FUZZIFY temperature
    TERM Cold := (0,1) (26.6667,0) ;
    TERM Warm := (0,0) (26.6667,1) (53.3333,0) ;
    TERM Hot := (26.6667,0) (53.3333,1) (80,0) ;
    TERM Too hot := (53.3333,0) (80,1) ;
END_FUZZIFY
FUZZIFY pressure
    TERM Low := (0,1) (0.5,0) ;
    TERM Fine := (0,0) (0.5,1) (1,0) ;
    TERM High := (0.5,0) (1,1) ;
END_FUZZIFY
DEFUZZIFY value
        Very Bad := (0,0) (0.25,1) (0.5,0) 
        Bad := (0.25,0) (0.5,1) (0.75,0) 
        Good := (0.5,0) (0.75,1) (1,0) 
        METHOD : COG;
        DEFAULT := 0;
END_DEFUZZIFY
RULEBLOCK first
        AND : MIN
        RULE  1 : IF temperature IS Cold THEN output IS Very Bad;
        RULE  2 : IF temperature IS Hot THEN output IS Bad;
        RULE  3 : IF temperature IS Too hot THEN output IS Very Bad;
        RULE  4 : IF pressure IS Low THEN output IS Bad;
        RULE  5 : IF pressure IS High THEN output IS Bad;
        RULE  6 : IF temperature IS Warm AND pressure IS Fine THEN output IS Good;
END_RULEBLOCK
END_FUNCTION_BLOCK
-- (eof)

NAVIGATION

Summary : Users guide
Previous page : Density information
Top of page : File Storage
Next page : Dataset handling