Wonderful, gg4clj is really nice!
Regarding ggvis, it might be worth knowing that it can generate not only
interactive htmls, but also a static JSONs in Vega format (which is of
course fun to edit from Clojure).
For example:
capture.output(data.frame(x=c(1,2)) %% ggvis(x=~x) %% show_spec);
Here is a little belated Christmas present for Clojure data aficionados:
;; setup
(use 'clojure.core.matrix)
(set-current-implementation :vectorz)
;; create a big sparse matrix with a trillion elements (initially zero)
(def A (new-sparse-array [100 100]))
;; we are hopefully smart
I just noticed that there was an extra line of code (which doesn't work) in
my original post. Sorry. I edited it out below.
In molecular dynamics a popular format for writing out the positions of the
atoms in a system is the xyz file format (see:
In the interest of thoroughness, it should be noted here that a protocol *named
InTimeUnitProtocol *appears in the ChangeLog referenced in the recent
announcement of clj-time
https://groups.google.com/forum/#!topic/clojure/rKKOkj-qKvc.
--
You received this message because you are subscribed
clj-time seems to be naming protocols inconsistently. It uses ISomething,
Something and SomethingProtocol naming.
On Sat, Dec 27, 2014 at 4:20 PM, Matching Socks phill.w...@gmail.com
wrote:
In the interest of thoroughness, it should be noted here that a protocol
*named
InTimeUnitProtocol
On 27 December 2014 at 19:10:38, Jozef Wagner (jozef.wag...@gmail.com) wrote:
clj-time seems to be naming protocols inconsistently. It uses
ISomething, Something and SomethingProtocol naming.
I suspect it is because it has 60 contributors and most users never have to
extend the protocols.
Changing old protocol names should trigger a major revision change in the
minimum because it breaks backwards compatibility.
--Ashton
Sent from my iPhone
On Dec 27, 2014, at 11:18 AM, Michael Klishin michael.s.klis...@gmail.com
wrote:
On 27 December 2014 at 19:10:38, Jozef Wagner
Quartzite [1] is a scheduling library built on top of Quartz scheduler.
Release notes:
http://blog.clojurewerkz.org/blog/2014/12/27/quartzite-2-dot-0-is-released/
1. http://clojurequartz.info
--
@michaelklishin, github.com/michaelklishin
--
You received this message because you are
I would like to replay all changes since a specific timestamp. It seems as
if I can get all transactions with
(q '[:find ?t :where
[_ :db/txInstant ?t]
] (db conn))
Using as-of would allow me to replay the state at a given point in time.
But that would replay the complete state
I think this conj video covered that.
http://m.youtube.com/watch?v=7lm3K8zVOdY
--Ashton
Sent from my iPhone
On Dec 27, 2014, at 1:57 PM, rogergl ro...@gilliar.de wrote:
I would like to replay all changes since a specific timestamp. It seems as
if I can get all transactions with
(q
Hahaha; Well, you beat me to it... But awesome!
I'd still love to work on a native clojure implementation, but also
acknowledge that it might be a while before I'm able to given a shift in
focus of late. In the mean time, this will be super useful when base
gorilla-repl plotting functionality
Very cool!
On the data representation front, would you be open to making it support
the core.matrix Dataset protocols as well as regular Clojure maps? That
would make it much easier to integrate with Incanter 2.0 etc., and
potentially avoid some copying overhead.
It should be a simple change
That depends if the protocols are part of your user-facing API or not - a
lot of the time I find that protocols are best hidden as implementation
details rather than exposed to users.
In core.matrix, for example, users never see the protocols directly: only
implementers of new matrix libraries
Protocols should never ever be part of public API. Protocols can be part of
the SPI, if custom extensions are to be supported. Otherwise they are an
implementation detail. See Rich's talk at 4:30 http://vimeo.com/100518968
Jozef
On Sun, Dec 28, 2014 at 8:11 AM, Mikera
14 matches
Mail list logo
