[SciPy-Dev] Initial support for Harwell Boeing sparse matrix format
Charles R Harris
Tue Mar 1 10:14:08 CST 2011
On Tue, Mar 1, 2011 at 5:44 AM, David Cournapeau <firstname.lastname@example.org> wrote:
> On Sun, Feb 27, 2011 at 10:48 AM, Nathan Bell <email@example.com> wrote:
> > On Sat, Feb 26, 2011 at 2:37 AM, David Cournapeau <firstname.lastname@example.org>
> > wrote:
> >> Indeed. I wonder how we want to export this into scipy.io: I think for
> >> file format it actually makes sense to say from scipy.io.format_name
> >> import function instead of putting everything into scipy.io, but I
> >> don't feel strongly about it either.
> >> cheers,
> > +1
> > Organizing the routines into
> > scipy.io.harwell_boeing.*
> > scipy.io.matrix_market.*
> > ...
> > would be clearer and provide a logical home for high-level and low-level
> > APIs.
> This is a good idea, I have added the code so that it works as follows:
> from scipy.io.hb import read, write
I think harwell_boeing would be a more informative name for the module than
hb. The latter is rather cryptic.
> and obtain a semi-standardized result (e.g. dictionary of name->value
> > where the names can be invented if not specified in the format).
> This made me realized: some (yet to be supported) cases of the
> HarwellBoeing format may return several matrices. Unfortunately, this
> is not very well documented, so I don't think I will add the feature
> any time soon.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the SciPy-Dev