From: RJ <lists@rj95.be>
To: dra-news@metastack.com, caml-list@inria.fr
Subject: Re: [Caml-list] Machine Learning in OCaml
Date: Tue, 05 Feb 2019 15:28:05 +0000 [thread overview]
Message-ID: <0jl1SxkDt_C2ayTjaPZx02V-Ultgn6woZHy_nZFOq--8NqTXwHTKYFM6lyiLKC1_kxzM6YW7XvPZW5f7FmroepZeXYoRW3saw2ERdYps_UU=@rj95.be> (raw)
In-Reply-To: <E51C5B015DBD1348A1D85763337FB6D901AE69D062@Remus.metastack.local>
[-- Attachment #1.1: Type: text/plain, Size: 998 bytes --]
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 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: 1261 bytes --]
[-- Attachment #2: publickey - lists@rj95.be - 0x4CB26DA0.asc --]
[-- Type: application/pgp-keys, Size: 648 bytes --]
next prev parent reply other threads:[~2019-02-05 15:28 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 [this message]
2019-02-05 18:00 ` Yawar Amin
2019-02-05 20:39 ` RJ
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='0jl1SxkDt_C2ayTjaPZx02V-Ultgn6woZHy_nZFOq--8NqTXwHTKYFM6lyiLKC1_kxzM6YW7XvPZW5f7FmroepZeXYoRW3saw2ERdYps_UU=@rj95.be' \
--to=lists@rj95.be \
--cc=caml-list@inria.fr \
--cc=dra-news@metastack.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).