Getting started

[bioinformed]

It sounds like fwap is nearing release and I'd like to start poking
around. I know from the recent blog post that one of the primary test
cases is wrapping LAPACK. This would be an ideal "quick start", since
generating the full set of wrappers for LAPACK would be immediately
useful (at least for me) and give me plenty of incentive to do more
than kick the tires. I've previously used f2py to wrap the GLMnet F90
code, which would be my first de novo project.

Thanks,
-Kevin

[Kamaraju Kusumanchi]

It is fun to have a wrapper from fortran to C. But just want to point
out that there is a package called CLAPACK which is basically C
version of LAPACK.

raju

[bioinformed]

On Jul 31, 10:05 am, Kamaraju Kusumanchi <kamar...@gmail.com> wrote:

Hi Raju,

My request is more to see how fwrap is applied to a non-trivial
library than to obtain access to specific LAPACK routines. For most
uses in Python I have the subset of LAPACK exposed by SciPy and the
more complete version provided by the CVXOPT package. It will be
useful to see not only how fwrap is able to provide C interfaces, but
also how those can be exposed to Python, hopefully in an automated
fashion and with features that simply and intuitively accommodate
array types (e.g., NumPy arrays or CVXOPT matricies). I do realize
that code to do much of this may not yet exist, which is why I was
hoping to better understand what can currently be accomplished with
fwrap.

Best regards,
-Kevin

[Kamaraju Kusumanchi]

> Hi Raju,
>
> My request is more to see how fwrap is applied to a non-trivial
> library than to obtain access to specific LAPACK routines.

I understand and agree with your point!

raju