This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-04-23
Channels
- # announcements (2)
- # beginners (82)
- # calva (13)
- # cider (12)
- # clara (4)
- # cljdoc (22)
- # clojure (89)
- # clojure-dev (23)
- # clojure-europe (16)
- # clojure-italy (39)
- # clojure-nl (8)
- # clojure-spec (28)
- # clojure-uk (36)
- # clojurescript (40)
- # cursive (10)
- # data-science (1)
- # datomic (27)
- # devcards (4)
- # emacs (1)
- # fulcro (25)
- # jobs (1)
- # jobs-discuss (3)
- # kaocha (5)
- # luminus (1)
- # nrepl (68)
- # off-topic (64)
- # pedestal (23)
- # planck (1)
- # quil (4)
- # re-frame (6)
- # reitit (5)
- # remote-jobs (4)
- # shadow-cljs (16)
- # spacemacs (11)
- # testing (1)
thanks... that second question. I was able to look at the session and see a fired rule, so that seems workable. The link you sent looks good, it looks like it uses something called "meta" to determine (query or rule), but doesn't seem to work for me.
@ethanc --- is there any examples around activation-group-fn. Maybe the documentation is good enough, but being a clojure newbie, I'm really not understanding what that function should be receiving (a map that always represents rules only? or the metadata?) Also the it's sort sibling is fuzzy to me.
@joel380,
This is a test demonstrating the usage of the activation-group-fn
:
https://github.com/cerner/clara-rules/blob/0.19.1/src/test/clojurescript/clara/test_salience.cljs#L76-L99
Please note that the manipulation of salience is typically reserved for tuning poor preforming rules. By poor performing, I mean rule scenarios where a pattern can be established where the execution order of rules will drastically impact the time that subsequent rules will take to execute and maintain truth.