Hi Chad, yep, that was me. We do hope to open source some stuff soon.
First will probably be our wrappers for cascading/hadoop and s3.
Next might be some core language extensions which might be good in contrib or some other lib.
If we release any basic stats or machine learning stuff we may try to merge into incanter if it seems like a fit but haven't had time to check out incanter as I'd like.
For now this is all on the back burner since building stuff has to be the priority for us and we're people constrained. :)
On Aug 14, 2009 4:01 PM, "Chad Harrington" <chad.ha...@gmail.com> wrote:
Bradford,
I just bought the iPhone app. Looks very cool.
I saw a presentation at the JavaOne after-meeting with Rich Hickey about flightcaster. Were you the presenter? The machine learning notation seemed to work very well in Clojure. Are there any portions of this cool stuff that you can share with the community?
Chad Harrington
chad.ha...@gmail.com
On Fri, Aug 14, 2009 at 12:10 PM, bradford cross <bradford...@gmail.com> wrote:
> > We have just released flightcaster.com which uses statistical inference and machine learning to ...
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are sub...
Hi Chad, yep, that was me. We do hope to open source some stuff soon.
First will probably be our wrappers for cascading/hadoop and s3.
Next might be some core language extensions which might be good in contrib or some other lib.
If we release any basic stats or machine learning stuff we may try to merge into incanter if it seems like a fit but haven't had time to check out incanter as I'd like.
We have just released flightcaster.com which uses statistical inference and machine learning to predict flight delays in advance of airlines (initial results appear to do so with 85 - 90 % accuracy.)
The webserver and webapp are all rails running on the Heroku platform; which also serves our blackberry and iphone apps.
The research and data heavy lifting is all in Clojure.
Very cool - congrats!
Rich
Those would be of great interest to many of us. Please do.
--J.
Am 21.08.2009 um 20:02 schrieb Sigrid:
> Could someone point me to what the difference is? I know pattern
> matching e.g. from the PLT scheme implementation, and there the
> pattern matching also provides the binding and destructuring I
> think...?
The difference is, that in pattern matching you can also specify
values on the left side. For example in OCaml:
type foo = [ Foo of int ];
value frobnicate x =
match x with
[ Foo 5 -> do_something ()
| Foo 7 -> do_something_else ()
| Foo x -> do_more x ];
(Please bear with me if I don't remember all the details of the syntax.)
While this is not possible in Clojure:
(let [[x 5 y] [1 2 3]]
...)
The five on the left hand side is not allowed.
Hope this helps.
Sincerely
Meikel
length [] = 0
length (_:xs) = 1 + (length xs)
Regards,
--
Michel
Is there a performance hit with this style (due to using multimethods)
or will this be optimized away in practice?
--
Michel
Strictly speaking, an isa? test. That's where the ad hoc hierarchy
functionality ties in.
Cheers,
--
Michel
Hi Meikel, hi all,
thanks for the explanation, I think I got it now. I suppose something
in the sentence I quoted led me to think that pattern matching was
"less" in a way than destructuring, whereas in fact it seems to be the
opposite - pattern matching seems to presuppose destructuring if I'm
correct now.
Still then (regarding "The way that Rich elected to de-couple
destructuring bind from pattern matching was brilliant.") , it is
unclear to me why it was such a good idea not to include pattern
matching, or, to somehow keep them separate...
>
> Destructuring is useful all over the place, not just for pattern
> matching. For example, it is really useful in function parameter
> vectors.
I consider that to be an example of pattern matching, though.
--
Michel
--
Michel
Regards,
--
Michel