Ok, there ends our primer on fuzzy logic.  Now, how is fuzzy logic implemented in the IECS?  Version 2 has extended the CLIPS syntax to accomodate fuzzy logic.  Fuzzy Types are defined using a new def construct, similar to deftemplate or defrule, called deftype.  The deftype construct accepts the name of the type, followed by its base types (in this case FUZZY), and then the definition of the type.  To define the Temperature type used above, the user would write:

 

(deftype Temperature extends (type FUZZY)
    (range 0.0000 100.0000)
    (units Celcius)
    (values
        (term hot (s 50.0000 90.0000))
        (term warm (pi 50.0000 50.0000))
        (term cold (z 10.0000 50.0000))
    ))

 

Now, to actually use the Temperature type, we need to define it in a deftemplate slot, using the optional type modifier:

 

(deftemplate water
    (slot temp (type Temperature))
)

 

After defining the deftemplate, we can create facts normally using the fuzzy sets and hedges:

 

(water (temp hot or [very cold and not warm]))

(water (temp not somewhat hot))

(water (temp about 30))

 

Rules can also be written:

 

(defrule water-hot
    (water (temp ?temp&hot) )
    =>
    (printout t "Water is hot " (moment-defuzzify ?temp)))

 

The IECS also provides very powerful inferencing capabilities based on Fuzzy Logic.  Not only does it calculate the strength of the rule activations, but provides both methods of Fuzzy Correlation: product and minimum.  It also supports FIVE different Fuzzy Inference methods: min-max, sum, mean, product, and bounded-sum.

 

Finally, it provides both defuzzification methods: maximum and center of gravity.  To get a scalar value for a fuzzy set, you use either the maximum-defuzzify or moment-defuzzify functions:

 

(moment-defuzzify (create-fuzzy-value Temperature [warm > 0.6500] or [very [extremely hot]]))

 

Button1 := TButton.Create(Self);

Button1.Parent := Self;

 

Much better!  However, if we execute the following code, it creates a standard button all the way in the top-left corner, no caption or text, and no code to execute when the user clicks the button.  We obviously need a few more things.  How would we do it at design time?  We would set the Top and Text properties and define an OnClick event handler.  Alternatively (and actually much better), we would use a TAction component setting its Text property and creating an OnExecute event handler, and then assign the Button's Action property to our action. 

 

Let's assume we have created the TAction component at design-time.  Therefore, to create and hook up our button at run-time, our code would look like this:

 

Button1 := TButton.Create(Self);