[SciPy-dev] scipy.sparse + umfpack + system_info

Robert Cimrman cimrman3 at ntc.zcu.cz
Wed Mar 29 05:03:40 CST 2006

Ed Schofield wrote:
> Robert Cimrman wrote:
>>Ed Schofield wrote:
>>>I suggest we move the solvers out of sparse.py, leaving only the data
>>>types.  We could put them instead into a separate module that depends on
>>>both sparse.py and umfpack.py.  We can still have them accessible under
>>>the scipy.sparse namespace by adding a line like
>>>    from umfsolvers import *
>>>to sparse/__init__.py.
>>Yes, ideally I would like to see having a direct solver module and an
>>iterative solver module, each working with both the dense and the
>>sparse matrices. But for the moment we could just move solve() and
>>lu_factor() somewhere else (linsolve package?). I am bad at coming
>>with names :-)
> I'm not sure about the ideal package structure.  A new linsolve package
> would make sense -- or we could leave the solvers as a separate module
> in the sparse package until we have wrappers for dense solvers too.  Or
> perhaps, eventually, we'd want to consolidate the linear solvers and
> non-linear solvers (e.g. minpack, currently in the optimize package)
> under a single "solve" package?

I have just done the following:

scipy/Lib/linsolve ... superlu, umfpack modules, spsolve, splu functions
scipy/Lib/sparse ... the rest

All tests pass for me, but I am afraid of making the changes public 
without any review. How do I make a new branch? Or, Ed, can I try it 
with your ejs branch (how?) - it is for testing the sparse stuff, right? :)

ps: I am just watching the partial solar eclipse from my window :-)

More information about the Scipy-dev mailing list