caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jan Kybic <kybic@fel.cvut.cz>
To: Alex Mikhalev <a.mikhalev@cranfield.ac.uk>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: Ocaml for Scientific computing
Date: Wed, 26 Sep 2007 05:06:59 +0200	[thread overview]
Message-ID: <87y7euunu4.fsf@fel.cvut.cz> (raw)
In-Reply-To: <1190718078.5901.18.camel@mikhaa> (Alex Mikhalev's message of "Tue, 25 Sep 2007 12:01:18 +0100")

> 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 have used Ocaml for several projects involving numerical
calculations, including image processing, boundary element methods and
optimization. I use Lacaml, fftw, MPI and Gsl libraries, the
installation was not difficult.  Ocaml has performed very well for me 
so far, it is faster than Python or Matlab and more "friendly" than
C/C++. Some minor issues:

- There is too many different representations of vectors and matrices:
  float arrays, plain big arrays, Lacaml Fortran style big arrays,
  several kinds of Gsl vectors with yet separate styles. I found I
  often had to convert vectors or matrices from one format to another
  because the function I wanted to use was available for a different
  interface. 

- Limited interactivity - it would help if you could call native compiled
  modules from the toplevel.

- Limited debugging - it is not possible to debug compiled modules.
  I would like to see an interface to gdb (I work on Linux), or a
  possibility for the byte compiled code being debugged to call
  natively compiled modules.

- I still find Ocaml object system less natural for me and more
  limiting than for example Python's. Also, often you can do the same
  thing with the objects as with the module system, so the choice of the
  best design pattern is sometimes not obvious at the first sight and
  requires a lot of foresight. But I assume this is just a matter of
  practice.

Good luck,

Jan

-- 
-------------------------------------------------------------------------
Jan Kybic <kybic@fel.cvut.cz>                       tel. +420 2 2435 5721
http://cmp.felk.cvut.cz/~kybic                      ICQ 200569450


  parent reply	other threads:[~2007-09-26  3:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-25 11:01 Alex Mikhalev
2007-09-25 11:32 ` [Caml-list] " Erik de Castro Lopo
2007-09-25 15:22   ` Jon Harrop
2007-09-25 16:11 ` Hezekiah M. Carty
2007-09-25 16:23   ` Jon Harrop
2007-09-25 17:01     ` Markus E L
2007-09-25 17:03       ` Jon Harrop
2007-09-25 17:35       ` Hezekiah M. Carty
2007-09-26 18:53       ` Vu Ngoc San
2007-09-26  3:06 ` Jan Kybic [this message]
2007-09-25 17:27 Mike Lin

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=87y7euunu4.fsf@fel.cvut.cz \
    --to=kybic@fel.cvut.cz \
    --cc=a.mikhalev@cranfield.ac.uk \
    --cc=caml-list@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).