From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8137 invoked by alias); 19 Feb 2010 18:19:42 -0000 Received: (qmail 8120 invoked by uid 22791); 19 Feb 2010 18:19:41 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail.network-theory.co.uk (HELO mail.network-theory.co.uk) (66.199.228.187) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 19 Feb 2010 18:19:36 +0000 Date: Fri, 19 Feb 2010 18:19:00 -0000 Message-ID: <87zl35p441.wl%bjg@network-theory.co.uk> From: Brian Gough To: GSL Discuss Mailing List Subject: Re: libflame version 4.0 announced In-Reply-To: <1266446869.8015.201.camel@manticore.lanl.gov> References: <4B3F0184.2030505@iki.fi> <1266363451.8015.153.camel@manticore.lanl.gov> <87aav7r2u4.wl%bjg@network-theory.co.uk> <1266446869.8015.201.camel@manticore.lanl.gov> User-Agent: Wanderlust/2.14.0 (Africa) Emacs/22.1 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Message-Mac: fc42b2e4a6344cbce2c5acd8edeeb94c Mailing-List: contact gsl-discuss-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gsl-discuss-owner@sourceware.org X-SW-Source: 2010-q1/txt/msg00031.txt.bz2 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