pysparse-developers — pysparse developer talk

[Pysparse-developers] A SIEMENS tem algo de melhor para lhe oferecer!!!

[NCom & S. <nc...@ra...>]

Seu cliente de email não pode visualizar esse email. Para ver a versão
online, por favor visite:
http://www.rainerdesign.eti.br/painel/display.php?M=128454&C=24c027aafac6ce3a45d0946c99c3a87c&S=13&L=12&N=5


Se não deseja mais receber esses emails
clique:http://www.rainerdesign.eti.br/painel/unsubscribe.php?M=128454&N=13&L=12&C=24c027aafac6ce3a45d0946c99c3a87c

[Pysparse-developers] Sua empresa na internet!

[Cassius M. - 1. C. <10...@ra...>]

Seu cliente de email não pode visualizar esse email. Para ver a versão
online, por favor visite:
http://www.rainerdesign.eti.br/painel/display.php?M=58247&C=92da78eb6d0f7d7f914609e120e27a99&S=4&L=2&N=2


Se não deseja mais receber esses emails
clique:http://www.rainerdesign.eti.br/painel/unsubscribe.php?M=58247&N=4&L=2&C=92da78eb6d0f7d7f914609e120e27a99

Re: [Pysparse-developers] a question

[Daniel W. <dan...@gm...>]

Hi Jose,

On Wed, Apr 16, 2008 at 3:24 PM, Jose Lopez <lo...@gm...> wrote:
> hi
>
> i am student  and i am working with sparse matrix and solver linear
> equations, but i am working  with python 2.5, so
>
> exist pysparse for python 2.5 under windows?

No. Not yet. When I do another release I'll include a binary version
for 2.5. You could also try using scipy or installing a version of
python that just includes everything you need. Try Enthought Python or
PythonXY.
Scipy has sparse solvers and both Enthought and PythonXY include scipy.

Cheers


-- 
Daniel Wheeler

[Pysparse-developers] a question

[Jose L. <lo...@gm...>]

hi

i am student  and i am working with sparse matrix and solver linear
equations, but i am working  with python 2.5, so

exist pysparse for python 2.5 under windows?

thanks

Re: [Pysparse-developers] Python 2.5 and memory management

[Adam C P. IV <haz...@de...>]

On Fri, 2008-03-28 at 10:18 -0400, Daniel Wheeler wrote:
> On Wed, Mar 26, 2008 at 8:18 AM, Adam C Powell IV <haz...@de...> wrote:
> 
> >  > I do have one related question for you. How does one test deb packages without a
> >  > clean system or root access? There doesn't seem to be an obvious way unpack and
> >  > install locally using apt-get. Any clues?
> >
> >  A .deb package is an ar archive with a tarball of package files, a
> >  tarball of control files, and a brief version file.  You can use "ar x
> >  package.deb" which will give you these three, and then unpack the
> >  package files and try to use them.  But you don't get the
> >  system-integrating scripts etc.
> >
> >  As far as I know there's no good way to unpack and use a .deb in one's
> >  home directory.
> >
> >  Do you have sufficient access to make a chroot environment?
> 
> Yes I do. I haven't tried it though. It may be the correct way to
> create a sandbox for testing
> packaging. I'll try it out and let you know. Thanks!

Just FYI: if you want to make a chroot, debootstrap is your friend...

-Adam
-- 
GPG fingerprint: D54D 1AEE B11C CE9B A02B  C5DD 526F 01E8 564E E4B6

Engineering consulting with open source tools
http://www.opennovation.com/

Re: [Pysparse-developers] Python 2.5 and memory management

[Daniel W. <dan...@gm...>]

On Wed, Mar 26, 2008 at 8:18 AM, Adam C Powell IV <haz...@de...> wrote:

>  > I do have one related question for you. How does one test deb packages without a
>  > clean system or root access? There doesn't seem to be an obvious way unpack and
>  > install locally using apt-get. Any clues?
>
>  A .deb package is an ar archive with a tarball of package files, a
>  tarball of control files, and a brief version file.  You can use "ar x
>  package.deb" which will give you these three, and then unpack the
>  package files and try to use them.  But you don't get the
>  system-integrating scripts etc.
>
>  As far as I know there's no good way to unpack and use a .deb in one's
>  home directory.
>
>  Do you have sufficient access to make a chroot environment?

Yes I do. I haven't tried it though. It may be the correct way to
create a sandbox for testing
packaging. I'll try it out and let you know. Thanks!

-- 
Daniel Wheeler

Re: [Pysparse-developers] Python 2.5 and memory management

[Adam C P. IV <haz...@de...>]

Hello Dan, it's good to hear from you.

On Tue, 2008-03-25 at 10:06 -0400, Daniel Wheeler wrote:
> Hi Adam,
> 
> I'll look into this in the near future. Thanks for taking care of the
> deb packaging.

You're welcome.

> I do have one related question for you. How does one test deb packages without a
> clean system or root access? There doesn't seem to be an obvious way unpack and
> install locally using apt-get. Any clues?

A .deb package is an ar archive with a tarball of package files, a
tarball of control files, and a brief version file.  You can use "ar x
package.deb" which will give you these three, and then unpack the
package files and try to use them.  But you don't get the
system-integrating scripts etc.

As far as I know there's no good way to unpack and use a .deb in one's
home directory.

Do you have sufficient access to make a chroot environment?

-Adam

> On Mon, Mar 24, 2008 at 4:17 PM, Adam C Powell IV <haz...@de...> wrote:
> > Greetings,
> >
> >  First, let me introduce myself: I'm the maintainer of the Debian package
> >  of pysparse.  The package takes a somewhat different approach from
> >  upstream: instead of building the superlu, umfpack and amd sources in
> >  the pysparse package, it links to existing Debian packages for those.
> >
> >  This is an "FYI" on Debian bug 468991, viewable at
> >  http://bugs.debian.org/468991 .  The bug submitter asserts that the
> >  memory management model of python 2.5 has changed, such that objects
> >  created using PyObject_NEW should use PyObject_Del in their destructors,
> >  not PyMem_DEL.
> >
> >  According to Thomas Viehmann, this will not cause a segfault in
> >  pysparse, but should be cleaned up eventually.  I figured you should be
> >  aware of this as a maintenance "To-Do" item.
> >
> >  I'll leave this bug open until pysparse changes.
> >
> >  Thanks,
> >  -Adam
-- 
GPG fingerprint: D54D 1AEE B11C CE9B A02B  C5DD 526F 01E8 564E E4B6

Engineering consulting with open source tools
http://www.opennovation.com/

Re: [Pysparse-developers] Python 2.5 and memory management

[Daniel W. <dan...@gm...>]

On Tue, Mar 25, 2008 at 10:16 AM, Andreas Klöckner
<li...@in...> wrote:

>
>  Hit enter on a deb in midnight commander (mc).
>
>  :)

That much seems good, but what about dependencies?

I'd like to set up a secondary "/usr" type directory in my local area
and specify
apt-get to download and install everything in that area. There doesn't seem to
be command line options for apt-get that allows that. Anyhow, this is
probably the
wrong list for this discussion.



-- 
Daniel Wheeler

Re: [Pysparse-developers] Python 2.5 and memory management

[Andreas K. <li...@in...>]

On Dienstag 25 März 2008, Daniel Wheeler wrote:
> Hi Adam,
>
> I'll look into this in the near future. Thanks for taking care of the
> deb packaging.
>
> I do have one related question for you. How does one test deb packages
> without a clean system or root access? There doesn't seem to be an obvious
> way unpack and install locally using apt-get. Any clues?

Hit enter on a deb in midnight commander (mc).

:)

Andreas

Re: [Pysparse-developers] Python 2.5 and memory management

[Daniel W. <dan...@gm...>]

Hi Adam,

I'll look into this in the near future. Thanks for taking care of the
deb packaging.

I do have one related question for you. How does one test deb packages without a
clean system or root access? There doesn't seem to be an obvious way unpack and
install locally using apt-get. Any clues?

Cheers

On Mon, Mar 24, 2008 at 4:17 PM, Adam C Powell IV <haz...@de...> wrote:
> Greetings,
>
>  First, let me introduce myself: I'm the maintainer of the Debian package
>  of pysparse.  The package takes a somewhat different approach from
>  upstream: instead of building the superlu, umfpack and amd sources in
>  the pysparse package, it links to existing Debian packages for those.
>
>  This is an "FYI" on Debian bug 468991, viewable at
>  http://bugs.debian.org/468991 .  The bug submitter asserts that the
>  memory management model of python 2.5 has changed, such that objects
>  created using PyObject_NEW should use PyObject_Del in their destructors,
>  not PyMem_DEL.
>
>  According to Thomas Viehmann, this will not cause a segfault in
>  pysparse, but should be cleaned up eventually.  I figured you should be
>  aware of this as a maintenance "To-Do" item.
>
>  I'll leave this bug open until pysparse changes.
>
>  Thanks,
>  -Adam
>  --
>  GPG fingerprint: D54D 1AEE B11C CE9B A02B  C5DD 526F 01E8 564E E4B6
>
>  Engineering consulting with open source tools
>  http://www.opennovation.com/
>
>
>  -------------------------------------------------------------------------
>  This SF.net email is sponsored by: Microsoft
>  Defy all challenges. Microsoft(R) Visual Studio 2008.
>  http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>  _______________________________________________
>  Pysparse-developers mailing list
>  Pys...@li...
>  https://lists.sourceforge.net/lists/listinfo/pysparse-developers
>



-- 
Daniel Wheeler

[Pysparse-developers] Python 2.5 and memory management

[Adam C P. IV <haz...@de...>]

Greetings,

First, let me introduce myself: I'm the maintainer of the Debian package
of pysparse.  The package takes a somewhat different approach from
upstream: instead of building the superlu, umfpack and amd sources in
the pysparse package, it links to existing Debian packages for those.

This is an "FYI" on Debian bug 468991, viewable at
http://bugs.debian.org/468991 .  The bug submitter asserts that the
memory management model of python 2.5 has changed, such that objects
created using PyObject_NEW should use PyObject_Del in their destructors,
not PyMem_DEL.

According to Thomas Viehmann, this will not cause a segfault in
pysparse, but should be cleaned up eventually.  I figured you should be
aware of this as a maintenance "To-Do" item.

I'll leave this bug open until pysparse changes.

Thanks,
-Adam
-- 
GPG fingerprint: D54D 1AEE B11C CE9B A02B  C5DD 526F 01E8 564E E4B6

Engineering consulting with open source tools
http://www.opennovation.com/

Re: [Pysparse-developers] [Pysparse-users] Factors in Umfpack: contribution to PySparse

[Daniel W. <dan...@gm...>]

I think that was initiated before my time using pysparse. It is not a
branch but a new project.

We have wraped a lot of the pysparse functionality. Take a look at the
following.

    <http://matforge.org/fipy/browser/trunk/fipy/tools/pysparseMatrix.py>

and

   <http://matforge.org/fipy/browser/trunk/fipy/solvers/pysparse/linearCGSSolver.py>

Maybe some of these classes should be added back in.

Cheers

On Jan 29, 2008 11:25 AM, Dominique Orban <dom...@gm...> wrote:
> Ok, thanks.
>
> I had a question about the development of PySparse. I saw a branch
> called 'pysparse2' in the CVS tree. At first glance, it seemed like an
> effort to have nice Python wrappers around the C modules. Is there
> still any effort going into that?
>
> Cheers,
> Dominique
>
>
>
> On 1/29/08, Daniel Wheeler <dan...@gm...> wrote:
> > I committed the changes and bumped the version number. I'll hold off
> > on a release
> > unless there is a pressing need.
> >
> > Cheers
> >
> > On Jan 28, 2008 4:34 PM, Dominique Orban <dom...@gm...> wrote:
> > > Hello,
> > >
> > > I wrote an addition to the UMFPack module of PySparse that lets users
> > > retrieve the details of the factorization. Here is an example:
> > >
> > >  from pysparse import spmatrix, umfpack
> > >  A = spmatrix.ll_mat_from_mtx('bcsstk11.mtx')
> > >  LU = umfpack.factorize(A)
> > >  (L, U, P, Q, R, do_recip) = LU.lu()
> > >
> > > The help of lu() is as follows:
> > >
> > > -------
> > > lu(...)
> > >     self.lu()
> > >     Returns L and U factors, permutation and scaling information.
> > >
> > >     Use: (L, U, P, Q, R, do_recip) = self.lu().
> > >     The original matrix A is factorized into
> > >          L U = P R A Q
> > >     where L is unit lower triangular,
> > >           U is upper triangular,
> > >           P and Q are permutation matrices,
> > >           R is a row-scaling diagonal matrix such that
> > >            the i-th row of A has been divided    by R[i] if do_recip = True,
> > >            the i-th row of A has been multiplied by R[i] if do_recip = False.
> > >
> > >     L and U are returned as ll_mat sparse matrices.
> > >     P, Q and R are returned as NumPy arrays.
> > > -------
> > >
> > > I would very much like to see this function included in PySparse. I
> > > will e-mail the code directly to Daniel Wheeler.
> > >
> > > Comments welcome.
> > >
> > > Cheers,
> > > Dominique
> > >
> > > -------------------------------------------------------------------------
> > > This SF.net email is sponsored by: Microsoft
> > > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > > _______________________________________________
> > > Pysparse-users mailing list
> > > Pys...@li...
> > > https://lists.sourceforge.net/lists/listinfo/pysparse-users
> > >
> >
> >
> >
> > --
> > Daniel Wheeler
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > _______________________________________________
> > Pysparse-developers mailing list
> > Pys...@li...
> > https://lists.sourceforge.net/lists/listinfo/pysparse-developers
> >
>



-- 
Daniel Wheeler

Re: [Pysparse-developers] [Pysparse-users] Factors in Umfpack: contribution to PySparse

[Daniel W. <dan...@gm...>]

I committed the changes and bumped the version number. I'll hold off
on a release
unless there is a pressing need.

Cheers

On Jan 28, 2008 4:34 PM, Dominique Orban <dom...@gm...> wrote:
> Hello,
>
> I wrote an addition to the UMFPack module of PySparse that lets users
> retrieve the details of the factorization. Here is an example:
>
>  from pysparse import spmatrix, umfpack
>  A = spmatrix.ll_mat_from_mtx('bcsstk11.mtx')
>  LU = umfpack.factorize(A)
>  (L, U, P, Q, R, do_recip) = LU.lu()
>
> The help of lu() is as follows:
>
> -------
> lu(...)
>     self.lu()
>     Returns L and U factors, permutation and scaling information.
>
>     Use: (L, U, P, Q, R, do_recip) = self.lu().
>     The original matrix A is factorized into
>          L U = P R A Q
>     where L is unit lower triangular,
>           U is upper triangular,
>           P and Q are permutation matrices,
>           R is a row-scaling diagonal matrix such that
>            the i-th row of A has been divided    by R[i] if do_recip = True,
>            the i-th row of A has been multiplied by R[i] if do_recip = False.
>
>     L and U are returned as ll_mat sparse matrices.
>     P, Q and R are returned as NumPy arrays.
> -------
>
> I would very much like to see this function included in PySparse. I
> will e-mail the code directly to Daniel Wheeler.
>
> Comments welcome.
>
> Cheers,
> Dominique
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Pysparse-users mailing list
> Pys...@li...
> https://lists.sourceforge.net/lists/listinfo/pysparse-users
>



-- 
Daniel Wheeler

[Pysparse-developers] Factors in Umfpack: contribution to PySparse

[Dominique O. <dom...@gm...>]

Hello,

I wrote an addition to the UMFPack module of PySparse that lets users
retrieve the details of the factorization. Here is an example:

 from pysparse import spmatrix, umfpack
 A = spmatrix.ll_mat_from_mtx('bcsstk11.mtx')
 LU = umfpack.factorize(A)
 (L, U, P, Q, R, do_recip) = LU.lu()

The help of lu() is as follows:

-------
lu(...)
    self.lu()
    Returns L and U factors, permutation and scaling information.

    Use: (L, U, P, Q, R, do_recip) = self.lu().
    The original matrix A is factorized into
         L U = P R A Q
    where L is unit lower triangular,
          U is upper triangular,
          P and Q are permutation matrices,
          R is a row-scaling diagonal matrix such that
           the i-th row of A has been divided    by R[i] if do_recip = True,
           the i-th row of A has been multiplied by R[i] if do_recip = False.

    L and U are returned as ll_mat sparse matrices.
    P, Q and R are returned as NumPy arrays.
-------

I would very much like to see this function included in PySparse. I
will e-mail the code directly to Daniel Wheeler.

Comments welcome.

Cheers,
Dominique

Re: [Pysparse-developers] [Pysparse-users] SpMatrix_API bug

[Jonathan G. <gu...@ni...>]

On May 21, 2007, at 10:32 AM, Daniel Wheeler wrote:

> On May 4, 2007, at 8:33 PM, Dominique Orban wrote:
>
>> Not that I have noticed. Since I sent the bug report, I observed  
>> that the above also affected
>> PySparse itself. For instance, the statement
>>
>> 	from pysparse import spmatrix, itsolvers, precon
>
> It was broken for me too, but now it seems to be working. Weird.  
> Jon, Is this something that you repaired?

I doubt it. I don't have checkin privileges for pysparse.

Re: [Pysparse-developers] SpMatrix_API bug

[Daniel W. <dan...@ni...>]

I just fixed the problem below and made a new release. Please take a  
look and check that it works.
If I don't hear any complaints, I'll put together the window binaries  
and Jon will do the dmg in the next few weeks.

On May 4, 2007, at 8:33 PM, Dominique Orban wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Daniel Wheeler wrote:
>> On May 4, 2007, at 6:46 PM, Dominique Orban wrote:
>>
>>>
>>> The bug is in spmatrix_api.h, in the "import_spmatrix" macro. I
>>> believe the first line should read
>>>
>>>  PyObject *spmatrix = PyImport_ImportModule("pysparse.spmatrix");
>>>
>>> instead of
>>>
>>>  PyObject *spmatrix = PyImport_ImportModule("spmatrix");
>>
>> Thanks for the bug report. Are there any other places with similar
>> problems?
>
> Not that I have noticed. Since I sent the bug report, I observed  
> that the above also affected
> PySparse itself. For instance, the statement
>
> 	from pysparse import spmatrix, itsolvers, precon

It was broken for me too, but now it seems to be working. Weird. Jon,  
Is this something that you repaired?

>
> caused the error message "no module named spmatrix". I presume the  
> error was coming from itsolvers
> and/or precon.

--
Daniel Wheeler

Re: [Pysparse-developers] SpMatrix_API bug

[Dominique O. <dom...@gm...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Daniel Wheeler wrote:
> On May 4, 2007, at 6:46 PM, Dominique Orban wrote:
> 
>> Hello,
>>
>> Since the new pysparse namespace was introduced, I believe there is a
>> minor bug in the SpMatrix_API that affects external packages that
>> build against PySparse.
>>
>> The bug is in spmatrix_api.h, in the "import_spmatrix" macro. I
>> believe the first line should read
>>
>>  PyObject *spmatrix = PyImport_ImportModule("pysparse.spmatrix");
>>
>> instead of
>>
>>  PyObject *spmatrix = PyImport_ImportModule("spmatrix");
> 
> Thanks for the bug report. Are there any other places with similar  
> problems?

Not that I have noticed. Since I sent the bug report, I observed that the above also affected
PySparse itself. For instance, the statement

	from pysparse import spmatrix, itsolvers, precon

caused the error message "no module named spmatrix". I presume the error was coming from itsolvers
and/or precon. However, as long as you wrote things as

	from pysparse import spmatrix
	from pysparse import itsolvers
	from pysparse import precon

you wouldn't notice because the imports succeed. I am not sure why.

> I'll try and make the change on HEAD ASAP. Probably do it next week.
> I also need to a new release as the numpy header stuff has now been  
> sorted out.

Thanks.

Dominique

> 
> Cheers
> 
>>
>> since spmatrix.so is now located under pysparse/. Not doing the above
>> change has the following disadvantage. In order to build against
>> PySparse and to successfully import spmatrix, one would have to add
>> the directory 'pysparse' to their PYTHONPATH. But then, that defeats
>> the purpose of the new namespace.
>>
>> Cheers,
>> Dominique
> 
> --
> Daniel Wheeler
> 
> 
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGO5iI2vhdTNgbn8wRAgexAJ9rkTpMija5QRqbbzq/QBFatV4r9QCggnIe
laHV6WzqPnG9jmTNnIHk0gw=
=AVD4
-----END PGP SIGNATURE-----

Re: [Pysparse-developers] SpMatrix_API bug

[Daniel W. <dan...@ni...>]

On May 4, 2007, at 6:46 PM, Dominique Orban wrote:

> Hello,
>
> Since the new pysparse namespace was introduced, I believe there is a
> minor bug in the SpMatrix_API that affects external packages that
> build against PySparse.
>
> The bug is in spmatrix_api.h, in the "import_spmatrix" macro. I
> believe the first line should read
>
>  PyObject *spmatrix = PyImport_ImportModule("pysparse.spmatrix");
>
> instead of
>
>  PyObject *spmatrix = PyImport_ImportModule("spmatrix");

Thanks for the bug report. Are there any other places with similar  
problems?
I'll try and make the change on HEAD ASAP. Probably do it next week.
I also need to a new release as the numpy header stuff has now been  
sorted out.

Cheers

>
> since spmatrix.so is now located under pysparse/. Not doing the above
> change has the following disadvantage. In order to build against
> PySparse and to successfully import spmatrix, one would have to add
> the directory 'pysparse' to their PYTHONPATH. But then, that defeats
> the purpose of the new namespace.
>
> Cheers,
> Dominique

--
Daniel Wheeler

[Pysparse-developers] SpMatrix_API bug

[Dominique O. <dom...@gm...>]

Hello,

Since the new pysparse namespace was introduced, I believe there is a
minor bug in the SpMatrix_API that affects external packages that
build against PySparse.

The bug is in spmatrix_api.h, in the "import_spmatrix" macro. I
believe the first line should read

  PyObject *spmatrix = PyImport_ImportModule("pysparse.spmatrix");

instead of

  PyObject *spmatrix = PyImport_ImportModule("spmatrix");

since spmatrix.so is now located under pysparse/. Not doing the above
change has the following disadvantage. In order to build against
PySparse and to successfully import spmatrix, one would have to add
the directory 'pysparse' to their PYTHONPATH. But then, that defeats
the purpose of the new namespace.

Cheers,
Dominique

Re: [Pysparse-developers] [Pysparse-users] list archive

[Roman G. <rom...@gm...>]

2007/2/28, Daniel Wheeler <dan...@ni...>:
> Does anyone else have problems accessing the mailing list archive at
> sourceforge?
Seems to work for me, at least currently.

> I think this list would be better served by archiving at gmane.
> <http://www.gmane.org>
> Not that I am volunteering to do the set up. Any thoughts?
I wouldn't mind, but since these are very low volume lists, I don't
feel a strong urge to change them myself ;-)

Roman

>
>
> --
>
> Daniel Wheeler
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Pysparse-users mailing list
> Pys...@li...
> https://lists.sourceforge.net/lists/listinfo/pysparse-users
>
>

[Pysparse-developers] list archive

[Daniel W. <dan...@ni...>]

Does anyone else have problems accessing the mailing list archive at  
sourceforge?

I think this list would be better served by archiving at gmane.  
<http://www.gmane.org>
Not that I am volunteering to do the set up. Any thoughts?

--
Daniel Wheeler

Re: [Pysparse-developers] update_add_mask 'bug' or user-error?

[Daniel W. <dan...@ni...>]

Hi William,

When I run this I just get an error saying:

       >>> A.update_add_mask( A,ind,ind,mask,mask )
      Traceback (most recent call last):
      File "<stdin>", line 1, in ?
      TypeError: a float is required

I don't think "update_add_mask" is particularly useful as a method.  
We tend to use
"update_add_at" as it provides more useful functionality.

Cheers

On Feb 15, 2007, at 12:32 PM, William Hunter wrote:

> Daniel/Roman;
>
> Please check out the following behaviour, or else I'm doing  
> something wrong:
>
> A = spmatrix.ll_mat( 2,2 )
> B = asarray( [[1,2][3,4]] )
> ind = asarray( [0,1] )
> mask = ones( (2),dtype=int )
> A.update_add_mask( A,ind,ind,mask,mask )
>
> First, am I using it correctly? (I'm sure I am...)
>
> Secondly, one expects an array:
>
> A = B,
>
> but instead get the following:
>
> A = B.T
>
> Of course one can enter the transpose (B.T) as the update array,  
> but that's a work around, also,
> if B is symmetric, it doesn't make a difference anyway, it's just  
> that it's confusing at first...
>
> This is fairly trivial to fix (*if* it is a minor bug) in the src  
> code, I think, haven't looked yet.
>
> So, while I'm on the subject of src code, I notice that the  
> docstrings aren't all the same -- can I correct
> the above mentioned assumed 'bug' and change the docstrings while  
> I'm at it?

Whatever you think is the most sensible approach.

>  I'll also attempt to fix setup.py so that it finds the NumPy  
> headers, this however, will not be trivial, unless
> I assume a standard installation (lib/python/site-packages or  
> prefix=/usr/local).

Isn't this a problem with numpy? If you think it is a numpy problem I  
think we should approach the numpy people
about it. What do you think?

>  By the way, still busy with the manual, adding the other methods  
> too (e.g. update_add_at)...

Thanks!

>
> Cheers,
> William
>
>
>

--
Daniel Wheeler

Re: [Pysparse-developers] PySparse docstrings

[Daniel W. <dan...@ni...>]

On Feb 6, 2007, at 3:56 AM, Roman Geus wrote:

> Hi Daniel
>
>> Should I join as a developer or send the strings via the
>> developer mailing list?
>>
>> Unfortunately, I am not the author of pysparse and I don't have  
>> sufficient
>> administrative privileges
>> to add you as a developer. If Roman is reading these emails he may  
>> add you,
>> I am not sure. Failing that
>> you can just send me your changes and I will try and add them. I am
>> forwarding this to the list so Roman
>> can see it.
>
> Since you are the most active pysparse developer and user I have given
> you full access to the sourceforge admin interface. I hope that's is
> OK with you.

Thanks Roman.

>
> -- Roman

--
Daniel Wheeler

Re: [Pysparse-developers] PySparse docstrings

[Roman G. <rom...@gm...>]

Hi Daniel

> Should I join as a developer or send the strings via the
> developer mailing list?
>
> Unfortunately, I am not the author of pysparse and I don't have sufficient
> administrative privileges
> to add you as a developer. If Roman is reading these emails he may add you,
> I am not sure. Failing that
> you can just send me your changes and I will try and add them. I am
> forwarding this to the list so Roman
> can see it.

Since you are the most active pysparse developer and user I have given
you full access to the sourceforge admin interface. I hope that's is
OK with you.

-- Roman

Re: [Pysparse-developers] PySparse docstrings

[Daniel W. <dan...@ni...>]

Hi William,

Thanks for your interest.

On Feb 5, 2007, at 7:11 AM, Africanis wrote:

>
> Message body follows:
>
> Daniel;
>
> How can I contribute in terms of docstrings?

Docstrings would certainly be useful for the project. Arguably, the  
project needs another level
of python wrapping to make the interface more pythonic. We actually  
have a wrapper class that
we use for our project:

      <http://matdl-osi.org/fipy/browser/trunk/fipy/tools/ 
sparseMatrix.py>

Anyhow, I guess this should be included with pysparse, but I haven't  
got round it.
If you'd like to get involved with that process then go ahead.  
Failing that, I think docstrings would be very useful.

> Should I join as a developer or send the strings via the
> developer mailing list?

Unfortunately, I am not the author of pysparse and I don't have  
sufficient administrative privileges
to add you as a developer. If Roman is reading these emails he may  
add you, I am not sure. Failing that
you can just send me your changes and I will try and add them. I am  
forwarding this to the list so Roman
can see it.

Cheers

>
> William
>
> --
> This message has been sent to you, a registered SourceForge.net user,
> by another site user, through the SourceForge.net site.  This message
> has been delivered to your SourceForge.net mail alias.  You may reply
> to this message using the "Reply" feature of your email client, or
> using the messaging facility of SourceForge.net at:
> https://sourceforge.net/sendmessage.php?touser=1496516
>

--
Daniel Wheeler