This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-07-17
Channels
- # beginners (42)
- # cider (1)
- # cljs-dev (20)
- # clojure (73)
- # clojure-italy (8)
- # clojure-nl (53)
- # clojure-spec (11)
- # clojure-uk (88)
- # clojurescript (170)
- # clojutre (6)
- # core-async (26)
- # css (2)
- # cursive (13)
- # data-science (10)
- # datomic (15)
- # editors (3)
- # figwheel (28)
- # figwheel-main (67)
- # fulcro (57)
- # graphql (2)
- # immutant (2)
- # jobs (1)
- # jvm (4)
- # lein-figwheel (3)
- # leiningen (1)
- # off-topic (5)
- # pedestal (28)
- # re-frame (86)
- # reagent (18)
- # reitit (8)
- # ring (3)
- # ring-swagger (2)
- # shadow-cljs (78)
- # spacemacs (10)
- # specter (12)
- # tools-deps (32)
- # vim (3)
Here we are: https://gitlab.com/alanmarazzi/numpy-vs-neanderthal/blob/master/README.md
I included Numpy results with both eig
and eigh
(that's the only difference), Neanderthal is almost always faster and I would say more reliable (less variance)
@chrisblom Neanderthal has a subset of Numpy functions (though @blueberry was adding some for the next releases), and then has some more advanced methods that if I understand correctly are material for a library built on top of Neanderthal
To better understand: calculating covariance (Numpy's cov
function) will probably never be implemented in Neanderthal
some experiments of using R from clojurescript: https://www.maria.cloud/gist/6a0b78b82f52f5b1bff64053a00660dd -- would love to hear your comments! worth mentioning here: @mhuebert, for the maria.cloud tool @carsten.behring, for the idea of using opencpu @jonyepsilon, for the gg4clj syntax