This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-11-19
Channels
- # announcements (5)
- # beginners (68)
- # boot (1)
- # cider (27)
- # clara (11)
- # cljdoc (10)
- # clojure (129)
- # clojure-europe (2)
- # clojure-italy (16)
- # clojure-nl (15)
- # clojure-spec (74)
- # clojure-uk (31)
- # clojurescript (62)
- # core-async (17)
- # cursive (28)
- # datomic (22)
- # duct (29)
- # emacs (10)
- # fulcro (65)
- # hoplon (2)
- # hyperfiddle (16)
- # instaparse (3)
- # kaocha (2)
- # lein-figwheel (3)
- # leiningen (1)
- # mount (1)
- # nrepl (21)
- # off-topic (23)
- # re-frame (59)
- # reitit (18)
- # ring-swagger (2)
- # shadow-cljs (2)
- # spacemacs (16)
- # timbre (2)
- # tools-deps (22)
I've been reading Rete algorithm stuff, and I've been wondering why I haven't seen references to this paper in them: http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.6.5507 -- (I couldn't remember the name of the paper until it appeared on the Clojure list just recently.)
It seems like this is a bunch more thought that applies to how to build an alpha network than I've seen mentioned before.
looks like it’d take a bit to parse through it to see how the ideas relate to other rete things that are out there
I have yet to see anything about optimizing the order of alpha tests, except for specific things like hashing 8 ways to find an alpha memory when using triplets.
AFAICT, there's no cases of filtering with user tests before storing in an alpha memory, even, and I presume that's because it's hard to know when you can do that and not duplicate memories?
those will be filtered as they come in and will not be stored in alpha mem if they don’t match