Next step would be to visually check if the plots match your expectations...

Ah, interesting. They have an fuzz.interp_membership function - smart. Let's steal that 😁 (probably just a wrapper for a np interpolation, but still)

You're using the Rule class to map the use of OR in their code? I'd immediately think of fuzzylogic.combinators.MAX when I read OR... or the | operator between fuzzy-functions, which maps to MAX.

Next step would be to visually check if the plots match your expectations...

Food:
image

Service
image

Tip:
image

I find it a bit hard to read their mix of rules, plots and functions, tbh.. but here we go

While, of course, I hope that my code is correct, it's possible that I made a mistake. That's why I rewrote it - to better scrutinize and improve.

My code does the following:

1. for every domain:value in the input calculate the membership values for all relevant fuzzy sets
2. for every IF-THEN rule take the min (AND) of the membership values and associate the THEN fuzzy set with the result as weight
3. calculate the weighted average for the cog of all THEN fuzzy sets as dimensionless index on the domain array
4. adjust for the limits and resolution of the domain to translate the index to the actual end value.

I guess it shows I never really cared much for defuzzification and put my emphasis on correctness and efficiency of the membership functions and combinators... 🤔

Hey,

thanks for the explanation. I cannot claim to being able to evaluate your code, but it is read-, and understandable. How it works in the bigger picture is yet beyond my scope. But I will look further into the options your package offers for me =D

Heya,

hope you're doing great.

I played around with your fuzzylogic package in a separate python environment (called fuzzy). Now that my main project is far enough to add fuzzy logic to it, i re-installed your package in a different env (called gis). The same example we posted above is not working in the gis environment. Neither does the new one. But it still works in the fuzzy.
Thus either there is a bad interaction betwenn different packages in the gis environment or you changed something in your code that causes that error (code see below). What do you think?
(PS: does github not offer to have collabseable sections in posts?)

from fuzzylogic.classes import Domain, Rule
from fuzzylogic.functions import R, S, triangular
res = 1
food = Domain("food_quality", 0, 10, res=res)
serv = Domain("service_quality", 0, 10, res=res)
tip = Domain("tip_amount", 0, 25, res=res)
food.lo = S(0, 5)
food.md = triangular(0, 10)
food.hi = R(5, 10)
serv.lo = S(0, 5)
serv.md = triangular(0, 10)
serv.hi = R(5, 10)
tip.lo = S(0, 13)
tip.md = triangular(0, 25)
tip.hi = R(13, 25)
rules = Rule({
 (food.lo, serv.lo): tip.lo,
 (food.md, serv.md): tip.md,
 (food.hi, serv.hi): tip.hi,
})
values = {food: 6.5, serv: 9.8}
print(rules(values))
ohalala
Traceback (most recent call last):
 Cell In[13], line 30
 print(rules(values))
 File ~\AppData\Local\miniconda3\envs\gis\Lib\site-packages\fuzzylogic\classes.py:447 in __call__
 index = sum(v.center_of_gravity * x for v, x in weights) / sum(x for v, x in weights)
 File ~\AppData\Local\miniconda3\envs\gis\Lib\site-packages\fuzzylogic\classes.py:447 in <genexpr>
 index = sum(v.center_of_gravity * x for v, x in weights) / sum(x for v, x in weights)
TypeError: unsupported operand type(s) for *: 'method' and 'float'

That's the old (fixed, but not released) bug. It's just missing a () at v.center_of_gravity(). I really should push a release. Possibly later today.

Oh nos. I am sorry I should have known... I once corrected it.