public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: JJ Gomez-Cadenas <gomez@ific.uv.es>
To: Alan Aspuru-Guzik <aspuru@okra.cchem.Berkeley.edu>,
	gsl-discuss@sources.redhat.com
Subject: RE: About coordinated efforts on scientific software.
Date: Tue, 05 Nov 2002 11:36:00 -0000	[thread overview]
Message-ID: <OEEFLAKOGNGPDBONDBGACEDNCFAA.gomez@ific.uv.es> (raw)
In-Reply-To: <Pine.LNX.4.21.0210210958090.19745-100000@okra.cchem.Berkeley.edu>

Hi again,
I have been looking into Babel
http://www.llnl.gov/CASC/components/babel.html

And it looks as a promising way of generating common interfaces for all
major scientific dialects.

However, I have a number of doubts. Let's see:

1) How much is the overhead to be payed? Very often in numerical
calculations performance is an issue.

2) SIDL, the scientific interface design language in which BABEL is based
has its own arrays and complex numbers. So it does GSL. Does that mean a lot
of copying to and fro, if one wants to stick to Babel types? Or one could
define GSL types, this seems to be easy enough in SIDL.

3) Python internals are based on Numphy which also has its own arrays. Same
question.

4) Is it worth? It depends on how many languages one really needs to glue
together. For C++ only it would clearly be an overkill. Add python and it
starts to be interesting. This two, I am sure are heavily used. Babel also
supports Java and Fortran. That makes it quite interesting, there is a lot
of people out there using FORTRAN still.

I would like that some body else (Alan?, Brian?) takes a look to this Babel
business and bring the discussion on line. I am becoming convinced that it
is a fundamental issue to be answered in order to help GSL to become the
core library for scientific calculations.

Best, JJ

-----Mensaje original-----
De: gsl-discuss-owner@sources.redhat.com
[mailto:gsl-discuss-owner@sources.redhat.com]En nombre de Alan
Aspuru-Guzik
Enviado el: lunes, 21 de octubre de 2002 19:05
Para: gsl-discuss@sources.redhat.com
Asunto: About coordinated efforts on scientific software.



This e-mail is a reply to Cristoph Siopi's email.

Some points:

There is a relevant coordinated effort by the Department of Energy for
creating a common base for scientific software. I actually went to a
workshop for the ACTS Toolkit:
http://acts.nersc.gov/

Which is a collection of software that is released using the GPL licencse
for most cases, and that is well suited for some of the tasks that people
need.  For example, if one needs parallel Matrix and Vector operations, I
recommend to take a look at PetSc. It looks really good.

I have been using GSL, and doing my vector MPI distribution by hand, just
because I did not know that such tools were in such advanced state, and
that they were actually written in C, etc.

Another very, VERY interesting effort, similar to what the GNOME people
wanted to do using CORBA as a glue for their component architecture,
Bonobo, is the Common Components Architecture:
http://www.cca-forum.org/

During the same workshop, I attended a one day tutorial on it, and it
seems very promising. When it becomes more mature, it would be very
interesting for one of us (maybe me) to CCA-ize the GSL, in such a way
that it can be used in conjuction with the tools from ACTS, that are
already starting to be CCAized (like TAO, the Toolkit for Advanced
Optimization).

So there are some people that are indeed looking at the big picture. Maybe
what we need in the volunteer arena is leadership and organization like
the one that started umbrella projects, such as GNOME or KDE, that brought
a lot of people together.

Greetings,
Alan

--

Alan Aspuru-Guzik                    Dios mueve al jugador, y éste, la
pieza.
(510)642-5911 UC Berkeley           ¿Qué Dios detrás de Dios la trama
empieza
(925)422-8739 LLNL                de polvo y tiempo y sueño y
agonías? -Borges

  parent reply	other threads:[~2002-11-05 12:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-21 11:32 Alan Aspuru-Guzik
2002-10-22  1:32 ` Manoj Warrier
2002-10-22  2:26   ` JJ Gomez-Cadenas
2002-10-22  3:02     ` Wartan Hachaturow
2002-10-22 16:33     ` Brian Gough
2002-10-22 16:55   ` Christos Siopis
2002-10-23 13:43     ` Alan Aspuru-Guzik
2002-11-05 11:36 ` JJ Gomez-Cadenas [this message]
2002-11-06  7:36   ` Brian Gough
2002-10-22 20:49 Christos Siopis

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=OEEFLAKOGNGPDBONDBGACEDNCFAA.gomez@ific.uv.es \
    --to=gomez@ific.uv.es \
    --cc=aspuru@okra.cchem.Berkeley.edu \
    --cc=gsl-discuss@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).