This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-05-13
Channels
- # admin-announcements (17)
- # aleph (1)
- # arachne (2)
- # boot (152)
- # braveandtrue (8)
- # cljs-dev (12)
- # cljsjs (3)
- # cljsrn (1)
- # clojure (105)
- # clojure-austin (1)
- # clojure-belgium (5)
- # clojure-berlin (1)
- # clojure-brasil (5)
- # clojure-canada (2)
- # clojure-dev (6)
- # clojure-gamedev (1)
- # clojure-greece (9)
- # clojure-russia (39)
- # clojure-uk (9)
- # clojurescript (106)
- # component (4)
- # cursive (1)
- # data-science (3)
- # datascript (1)
- # datomic (9)
- # emacs (6)
- # hoplon (92)
- # jobs (1)
- # ldnproclodo (2)
- # lein-figwheel (1)
- # off-topic (19)
- # om (47)
- # om-next (1)
- # onyx (10)
- # other-languages (1)
- # proton (1)
- # re-frame (5)
- # reagent (36)
- # rethinkdb (1)
- # ring (2)
- # rum (1)
- # yada (14)
In part three of my k-means clustering jump method write-up, I address initialization methods and visualizing weirdnesses: https://gist.github.com/daveliepmann/67dde9f05df12af134ac344b7a2886d9
@daveliepmann: maybe a strange question given the channel but why did you choose Clojure/Incanter for this project?
@henripal: It's a totally reasonable question—I actually got it at the Clojure Berlin meet-up too! The answer is that this was for fun and I don't enjoy writing R as much as I enjoy writing Clojure. (I do wonder how that will affect readership in the pure data-science population.) Incanter was the logical choice after picking Clojure.