From: Brian Gough <bjg@gnu.org>
To: GSL Discuss Mailing List <gsl-discuss@sourceware.org>
Subject: Re: libflame version 4.0 announced
Date: Fri, 19 Feb 2010 18:19:00 -0000 [thread overview]
Message-ID: <87zl35p441.wl%bjg@network-theory.co.uk> (raw)
In-Reply-To: <1266446869.8015.201.camel@manticore.lanl.gov>
At Wed, 17 Feb 2010 15:47:49 -0700,
Gerard Jungman wrote:
> I just want to link against it, presumably through
> some GSL-owned insulation layer, which can be
> configured to point to any conforming implementation.
> Similar to the BLAS wrapper layer.
>
> But this requires some kind of interface design. With
> BLAS we were lucky that a standard C interface existed
> already. But it's not so clear what a "standard" LAPACK
> interface would look like. It's very nice that they have
> gifted us with their implementation and their interfaces
> for a model. But it doesn't leave us entirely off the hook.
>
> The other big problem is what to do with their data
> structures. Obviously we need an insulation layer to
> protect clients from changes in FLA_Obj and friends.
I envisioned two simple things to add FLAME support in GSL:
- a set of wrapper functions to call the high-level flame routines
(Cholesky, LU, QR etc) with gsl_vector/matrix arguments (via the
simple create+attach_buffer method, as in the FLAME/C examples in
the manual).
This would be a direct alternative to the gsl_linalg routines.
e.g. gsl_linalg_LU_decomp (gsl_matrix * A, gsl_permutation * p, int *signum)
=> gsl_flame_LU_decomp (gsl_matrix * A, gsl_permutation * p)
- a few (trivial) utility functions to convert from gsl_vector/matrix
to FLA_Obj.
--
Brian Gough
next prev parent reply other threads:[~2010-02-19 18:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-02 8:19 GSL extension ode-initval2-1.0 released Tuomo Keskitalo
2010-01-22 9:16 ` [Help-gsl] " Forest Yang
2010-01-23 11:15 ` Tuomo Keskitalo
2010-02-16 23:36 ` libflame version 4.0 announced Gerard Jungman
2010-02-17 21:20 ` Brian Gough
2010-02-17 22:49 ` Gerard Jungman
2010-02-17 23:10 ` Rhys Ulerich
2010-02-19 18:19 ` Brian Gough [this message]
2010-02-17 22:51 ` James Amundson
2010-02-14 6:15 Rhys Ulerich
2010-02-17 21:20 ` Brian Gough
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=87zl35p441.wl%bjg@network-theory.co.uk \
--to=bjg@gnu.org \
--cc=gsl-discuss@sourceware.org \
/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).