From: RJ <lists@rj95.be>
To: yawar.amin@gmail.com
Cc: dra-news@metastack.com, caml-list@inria.fr
Subject: Re: [Caml-list] Machine Learning in OCaml
Date: Tue, 05 Feb 2019 20:39:27 +0000 [thread overview]
Message-ID: <6XFmeVMBOQuzMdwxtA6_8ZbmOinApPd8i6P7enWN5qy1GD_nXW7jtKmIoBHxsMUB87ywU7rbfPvWTr0A7nBE3cEZFYNd8LK2J6dYtQa4dY8=@rj95.be> (raw)
In-Reply-To: <CAJbYVJJ3hX3o=fcuZA5NEJvjXOVbzwhpKA+H4mpu1pNXnTmu5g@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1490 bytes --]
Ah that's cool. Supports GPU acceleration too it looks like. I'm really hoping for owl to advance a bit more. It looks great so far. I dislike python as a language but its libraries just can't be ignored...
R.
-------- Original Message --------
On Feb 5, 2019, 13:00, Yawar Amin wrote:
> Have you seen https://github.com/LaurentMazare/ocaml-torch ?
>
> On Tue, Feb 5, 2019 at 10:28 AM RJ <lists@rj95.be> wrote:
>
>> Yes I've seen OWL. I'm used to torch/tf/fast.ai paradigms. Obviously OWL won't be as functional, but how big is the gap among the tools?
>>
>> R.
>>
>> -------- Original Message --------
>> On Feb 5, 2019, 09:58, David Allsopp < dra-news@metastack.com> wrote:
>>
>>> RJ wrote:
>>>> What tools have you all used to access the standard ML toolkit using OCaml?
>>>
>>> Although this list remains perfectly active, you may get more answers on our Discuss forum – https://discuss.ocaml.org.
>>>
>>> I can immediately point you to http://ocaml.xyz/ for one example, though.
>>>
>>> HTH,
>>>
>>> David
>>>
>>> --
>>> Caml-list mailing list. Subscription management and archives:
>>> https://sympa.inria.fr/sympa/arc/caml-list https://inbox.ocaml.org/caml-list
>>> Forum: https://discuss.ocaml.org/
>>> Bug reports: http://caml.inria.fr/bin/caml-bugs
--
Caml-list mailing list. Subscription management and archives:
https://sympa.inria.fr/sympa/arc/caml-list https://inbox.ocaml.org/caml-list
Forum: https://discuss.ocaml.org/
Bug reports: http://caml.inria.fr/bin/caml-bugs
[-- Attachment #1.2: Type: text/html, Size: 2364 bytes --]
[-- Attachment #2: publickey - lists@rj95.be - 0x4CB26DA0.asc --]
[-- Type: application/pgp-keys, Size: 648 bytes --]
prev parent reply other threads:[~2019-02-05 20:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 15:19 RJ
2019-02-05 14:58 ` David Allsopp
2019-02-05 15:28 ` RJ
2019-02-05 18:00 ` Yawar Amin
2019-02-05 20:39 ` RJ [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='6XFmeVMBOQuzMdwxtA6_8ZbmOinApPd8i6P7enWN5qy1GD_nXW7jtKmIoBHxsMUB87ywU7rbfPvWTr0A7nBE3cEZFYNd8LK2J6dYtQa4dY8=@rj95.be' \
--to=lists@rj95.be \
--cc=caml-list@inria.fr \
--cc=dra-news@metastack.com \
--cc=yawar.amin@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).