dolfin team mailing list archive

[Anders Logg <logg@xxxxxxxxx>]

On Wed, Feb 25, 2009 at 08:48:37AM +0100, Johan Hake wrote:
> On Wednesday 25 February 2009 03:27:54 Luke Olson wrote:
> > Kent,
> >
> > Thanks for the shout-out.  PyAMG is nearing a stable release and we're
> > looking for compatibility with related projects.  We'd love to hear any
> > success stories.
> >
> > I'm also interested in hearing about any attempts at more closely
> > integrating the scipy.sparse module with Dolfin.
> 
> There aren't any :( but, I have to admit, it would be cool :)
> 
> I had a _brief_ look at the code in scipy/sparse/sparsetools and I see that 
> you have a minimal C++ interface, which is glued together by swig, right?
> 
> I am not very familiar to the SciPy family or more precise the scipy.sparse 
> module, so it would be nice with some thoughts of how deep this integration 
> should be. From the top of my head:
> 
> SciPy integration in the c++ layer of DOLFIN:
> As SciPy is a "pure" python library this can feel a bit (please correct me) 
> unnesessary. However I see that you have some sort of c++ interface, which 
> could be used. Then we need to be able to wrap it into the GenericMatrix 
> class, and we also need the SciPy version of the other GenericFoo classes in 
> dolfin/la. To be able to full integrate SciPy's structures in DOLFIN we 
> probably need to wrap it into the DOLFIN layer. 

This would be the best option as we could then send in a SciPy matrix
directly to the assembler.

> SciPy integration in the python layer of DOLFIN:
> This should be more feasable but probably unsatisfactory, as DOLFIN and 
> PyDOLIN are more or less just two sides of the same coin.

In this case, we could just have some simple conversion utilities,
like we have now for vectors with

  xx = x.array()
  x.set(xx)

-- 
Anders

Attachment: signature.asc
Description: Digital signature