This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-04-07
Channels
- # beginners (41)
- # boot (38)
- # cider (17)
- # cljs-dev (52)
- # cljsjs (3)
- # clojure (200)
- # clojure-italy (8)
- # clojure-russia (50)
- # clojure-spec (28)
- # clojure-uk (45)
- # clojurescript (28)
- # core-async (9)
- # core-matrix (2)
- # cursive (16)
- # datascript (15)
- # datomic (50)
- # dirac (5)
- # emacs (20)
- # figwheel (8)
- # flambo (2)
- # hoplon (10)
- # incanter (1)
- # jobs (1)
- # leiningen (2)
- # lumo (26)
- # mount (171)
- # off-topic (22)
- # om (54)
- # onyx (2)
- # pedestal (27)
- # re-frame (10)
- # reagent (12)
- # ring (27)
- # ring-swagger (3)
- # rum (2)
- # slack-help (1)
- # spacemacs (134)
- # specter (6)
- # sql (15)
- # testing (20)
- # uncomplicate (5)
- # unrepl (49)
- # untangled (9)
- # yada (29)
In attempting to come up with core.matrix indexing idioms analogous (or equivalent) to various examples from something like numpy, I came across
index
, index-seq
and company. But I can't seem to find how these are supposed to be used - select
and company do not seem to use them, nor do slice
, submatrix
, etc. Any information on this? Thanks in advance.Another question, with vector 'index args', why does select not perform typical integer indexing? For example, with (def a (m/matrix [[1,2], [3, 4], [5, 6]]))
why doesn't (select a [0 1 2] [0 1 0])
return [1.0,4.0,5.0]
instead of [[1.0,2.0,1.0],[3.0,4.0,3.0],[5.0,6.0,5.0]]
. I don't really understand the point behind the latter.