From: "Mike Lin" <mikelin@mit.edu>
To: caml-list <caml-list@yquem.inria.fr>
Subject: Re: Ocaml for Scientific computing
Date: Tue, 25 Sep 2007 13:27:27 -0400 [thread overview]
Message-ID: <2a1a1a0c0709251027v6dc42b38g1138b09f5627dbca@mail.gmail.com> (raw)
On Sep 25, 7:11 am, Alex Mikhalev <a.mikha...@cranfield.ac.uk> wrote:
> Dear all,
> I am wondering is anyone using Ocaml for scientific computing? I didn't
> mean parsing, but for number crunching applications, like signal/image
> analysis. Is it suitable for this kind of tasks in general? I would like
> to hear from someone practically using it, not just theoretical
> possibility.
I use it for a lot of genome sequence processing, comparative genomics
and phylogenetic modeling. Algorithmically this involves conditional
random fields (for which I have my own library) and some linear
algebra and numerical optimization (for which I use Lacaml and
ocamlgsl). I had a lot of frustrations at first, but it's been better
since we got exception stack traces and ocaml+twt.
For numerical computing, I wish ocamlopt would do at least basic loop
optimizations, like hoisting invariant values -- this type of stuff is
easily done manually, but often at the expense of code readability. I
can see how this may be a bottomless pit for the dev team though,
since I would probably always feel like we are one crucial
optimization short of not having to rewrite that tight loop in C.
In any case though, I work in a group where everyone else uses Python,
so I'm already beating their pants off :o)
Mike
next reply other threads:[~2007-09-25 17:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 17:27 Mike Lin [this message]
2007-09-25 18:46 ` [Caml-list] " skaller
2007-09-25 20:38 ` Jon Harrop
2007-09-25 21:01 ` skaller
2007-09-26 8:27 ` Florian Hars
2007-09-26 8:53 ` skaller
-- strict thread matches above, loose matches on Subject: below --
2007-09-25 11:01 Alex Mikhalev
2007-09-26 3:06 ` Jan Kybic
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=2a1a1a0c0709251027v6dc42b38g1138b09f5627dbca@mail.gmail.com \
--to=mikelin@mit.edu \
--cc=caml-list@yquem.inria.fr \
/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).