Fuzzy markup language: Difference between revisions

Revision as of 23:13, 27 April 2013

Revision as of 22:35, 4 June 2013

Line 67:

<KnowledgeBase>

<FuzzyVariable name="food" domainleft="0.0" domainright="10.0" scale="" type="input">

<FuzzyTerm name="deliciusdelicious" complement="false">

<LeftLinearShape Param1="5.5" Param2="10.0"/>

</FuzzyTerm>

Line 83:

<TriangularShape Param1="0.0" Param2="5.0" Param3="10.0"/>

</FuzzyTerm>

<FuzzyTerm name="generousegenerous" complement="false">

<TriangularShape Param1="10.0" Param2="15.0" Param3="20.0"/>

</FuzzyTerm>

Line 141:

<TSKValue>6.0</TSKValue>

</TSKTerm>

<TSKTerm name="generousegenerous" order="1">

<TSKValue>0.6</TSKValue>

<TSKValue>1.3</TSKValue>

Line 350:

===FML Synthesis===

Since an FML program realizes only a static view of a fuzzy system, the so-called eXtensible Stylesheet Language Translator (XSLT) is provided to change this static view to a computable version. In particular, the XSLT technology is used convert a fuzzy controller description into a general-purpose computer language to be computed on several hardware platforms. Currently, a XSLT converting FML program in runnable Java code has been implemented. In this way, thanks to the transparency capabilities provided by Java virtual machines, it is possible to obtain a fuzzy controller modeled in high level way by means of FML and runnable on a plethora of hardware architectures through Java technologies. However, XSLT can be also used for converting FML programs in legacy languages related to a particular hardware or in other general purpose languages.

==References==