numpy-discussion — Discussion list for all users of Numerical Python

[Numpy-discussion] assigning to submatrix

[John H. <jdh...@ac...>]

If I have a large matrix, say

  a = zeros( (20,20) )

and a small matrix

  b = ones( 3,4 )

and a list of row indices and a list of col indices

  rind = [2,4,9,15]
  cind = [1,4,12]

what is the best way to assign the submatrix to a[rind,cind].  I
understand this is possible in numarray, but is there a good way to do
it in Numeric?

In matlab, you could do a(rind, cind)=b;  Is there some reshape, put
magic I can do to make this efficient in Numeric?

Thanks,
John Hunter

Re: [Numpy-discussion] ANNOUNCE: numarray-0.6

[Todd M. <jm...@st...>]

----- Original Message ----- 
From: "Sebastian Haase" <ha...@ms...>
To: "Todd Miller" <jm...@st...>
Cc: "numpy-discussion" <num...@li...>
Sent: Monday, July 28, 2003 5:02 PM
Subject: Re: [Numpy-discussion] ANNOUNCE: numarray-0.6

> Seems to work right away.
> But now I get this:
> >>> r = na.array( [ 2,3,4,5] , type=F.na.Float32 )
> >>> r
> array([ 2.,  3.,  4.,  5.], type=Float32)
> >>> r/10
> Traceback (most recent call last):
>   File "<input>", line 1, in ?
> TypeError: unsupported operand type(s) for /: 'NumArray' and 'int'
> >>> r/10.
> Traceback (most recent call last):
>   File "<input>", line 1, in ?
> TypeError: unsupported operand type(s) for /: 'NumArray' and 'float'
> >>>
>
> Sorry to frighten you... :-(
> I am just experimenting with
> from __future__ import division
>

We have't added support for future division yet.

> Apparently taking that line out again fixes the problem.

Good.

> I am actually not sure what the "proposed policy" is on that future
division
> thing; I just thought I could simplify some explanation to non-Python
people
> if  1/3 is not 0.

I believe we're going to support future division eventually.  I'm not sure
how soon.

> Probably numarray has more important things to worry about - but maybe you
> can put it on the list..

It's on "the list".

> Thanks for your work.

You're welcome.  I hope you find it useful.

> Sebastian
>

Re: [Numpy-discussion] ANNOUNCE: numarray-0.6

[Sebastian H. <ha...@ms...>]

> > "However, there is a new API function which I added in
> > response to your
> >   last post: NA_NewAllFromBuffer() which enables you to
> > create arrays in C
> >   from existing buffer objects rather than just C arrays."
> >
> > The 0.6 documentation doesn't mention that function - for
> > now I probably have to read the source, right ?
>
> Yes.  The signature is:
>
> PyArrayObject * NA_NewAllFromBuffer  (int ndim, maybelong *shape,
> NumarrayType type, PyObject *bufferObject, maybelong byteoffset,
> maybelong bytestride, int byteorder, int aligned, int writeable)
>
Seems to work right away.
But now I get this:
>>> r = na.array( [ 2,3,4,5] , type=F.na.Float32 )
>>> r
array([ 2.,  3.,  4.,  5.], type=Float32)
>>> r/10
Traceback (most recent call last):
  File "<input>", line 1, in ?
TypeError: unsupported operand type(s) for /: 'NumArray' and 'int'
>>> r/10.
Traceback (most recent call last):
  File "<input>", line 1, in ?
TypeError: unsupported operand type(s) for /: 'NumArray' and 'float'
>>>

Sorry to frighten you... :-(
I am just experimenting with
from __future__ import division

Apparently taking that line out again fixes the problem.
I am actually not sure what the "proposed policy" is on that future division
thing; I just thought I could simplify some explanation to non-Python people
if  1/3 is not 0.
Probably numarray has more important things to worry about - but maybe you
can put it on the list..

Thanks for your work.
Sebastian

Re: [Numpy-discussion] Removing rows and columns of a matrix

[Nils W. <nw...@me...>]

Konrad Hinsen schrieb:
> 
> On Monday 28 July 2003 16:26, Nils Wagner wrote:
> > Konrad Hinsen schrieb:
> > > >  How can I delete a column/row from a matrix.
> > >
> > > As an in-place operation, not at all. To get a copy of an array with some
> > > columns/rows removed, use Numeric.take.
> >
> > The in-place operation of matlab is a nice feature. Is it thinkable to
> > have this
> > in scipy or numarray at a later date ?
> 
> I'd say that the obvious way to implement it is as
> 
>   del a[2:3,:]
> 
> That can certainly be done, but someone has to do it.
> 
> Personally, I am not convinced that it is very useful. The consequences of an
> in-place change can be disastrous when many references point to that array.
> But then, we have other in-place operations which sometimes are handy, so my
> usefulness estimation may be wrong.
> 
> Konrad.

In my opinion, this operation is quite useful. For example a finite
element model
where we have to impose several homogeneous boundary conditions. This
can be done 
by deleting columns and associated rows.

Nils

In any case I am interested in a reliable workaround for this feature.

A small example would be appreciated.
Thanks in advance.



> --
> -------------------------------------------------------------------------------
> Konrad Hinsen                            | E-Mail: hi...@cn...
> Centre de Biophysique Moleculaire (CNRS) | Tel.: +33-2.38.25.56.24
> Rue Charles Sadron                       | Fax:  +33-2.38.63.15.17
> 45071 Orleans Cedex 2                    | Deutsch/Esperanto/English/
> France                                   | Nederlands/Francais
> -------------------------------------------------------------------------------
> 
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
> _______________________________________________
> Numpy-discussion mailing list
> Num...@li...
> https://lists.sourceforge.net/lists/listinfo/numpy-discussion

RE: [Numpy-discussion] Removing rows and columns of a matrix

[Ralf J. <jue...@in...>]

On Mon, 2003-07-28 at 07:34, Perry Greenfield wrote:
> Speaking for numarray, no, not really. But I wonder what is
> really done for matlab. Either they have a more complex representation
> of arrays, or all they really are doing is making a new copy of
> the array and giving you the impression it is being done in place.

Right, this is how Matlab does it behind the scenes.

Ralf

Re: [Numpy-discussion] Removing rows and columns of a matrix

[Konrad H. <hi...@cn...>]

On Monday 28 July 2003 16:26, Nils Wagner wrote:
> Konrad Hinsen schrieb:
> > >  How can I delete a column/row from a matrix.
> >
> > As an in-place operation, not at all. To get a copy of an array with =
some
> > columns/rows removed, use Numeric.take.
>
> The in-place operation of matlab is a nice feature. Is it thinkable to
> have this
> in scipy or numarray at a later date ?

I'd say that the obvious way to implement it is as

  del a[2:3,:]

That can certainly be done, but someone has to do it.

Personally, I am not convinced that it is very useful. The consequences o=
f an=20
in-place change can be disastrous when many references point to that arra=
y.=20
But then, we have other in-place operations which sometimes are handy, so=
 my=20
usefulness estimation may be wrong.

Konrad.
--=20
-------------------------------------------------------------------------=
------
Konrad Hinsen                            | E-Mail: hi...@cn...
Centre de Biophysique Moleculaire (CNRS) | Tel.: +33-2.38.25.56.24
Rue Charles Sadron                       | Fax:  +33-2.38.63.15.17
45071 Orleans Cedex 2                    | Deutsch/Esperanto/English/
France                                   | Nederlands/Francais
-------------------------------------------------------------------------=
------

RE: [Numpy-discussion] Removing rows and columns of a matrix

[Perry G. <pe...@st...>]

> 
> Konrad Hinsen schrieb:
> > 
> > >  How can I delete a column/row from a matrix.
> > 
> > As an in-place operation, not at all. To get a copy of an array 
> with some
> > columns/rows removed, use Numeric.take.
> > 
> The in-place operation of matlab is a nice feature. Is it thinkable to
> have this
> in scipy or numarray at a later date ?
> 
> Nils
> 
Speaking for numarray, no, not really. But I wonder what is
really done for matlab. Either they have a more complex representation
of arrays, or all they really are doing is making a new copy of
the array and giving you the impression it is being done in place.
After all you are changing the size and structure of the array.

Perry

Re: [Numpy-discussion] Removing rows and columns of a matrix

[Nils W. <nw...@me...>]

Konrad Hinsen schrieb:
> 
> >  How can I delete a column/row from a matrix.
> 
> As an in-place operation, not at all. To get a copy of an array with some
> columns/rows removed, use Numeric.take.
> 
The in-place operation of matlab is a nice feature. Is it thinkable to
have this
in scipy or numarray at a later date ?

Nils

> Konrad.
> --
> -------------------------------------------------------------------------------
> Konrad Hinsen                            | E-Mail: hi...@cn...
> Centre de Biophysique Moleculaire (CNRS) | Tel.: +33-2.38.25.56.24
> Rue Charles Sadron                       | Fax:  +33-2.38.63.15.17
> 45071 Orleans Cedex 2                    | Deutsch/Esperanto/English/
> France                                   | Nederlands/Francais
> -------------------------------------------------------------------------------
> 
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
> _______________________________________________
> Numpy-discussion mailing list
> Num...@li...
> https://lists.sourceforge.net/lists/listinfo/numpy-discussion

Re: [Numpy-discussion] Removing rows and columns of a matrix

[Konrad H. <hi...@cn...>]

>  How can I delete a column/row from a matrix.

As an in-place operation, not at all. To get a copy of an array with some=
=20
columns/rows removed, use Numeric.take.

Konrad.
--=20
-------------------------------------------------------------------------=
------
Konrad Hinsen                            | E-Mail: hi...@cn...
Centre de Biophysique Moleculaire (CNRS) | Tel.: +33-2.38.25.56.24
Rue Charles Sadron                       | Fax:  +33-2.38.63.15.17
45071 Orleans Cedex 2                    | Deutsch/Esperanto/English/
France                                   | Nederlands/Francais
-------------------------------------------------------------------------=
------

[Numpy-discussion] Removing rows and columns of a matrix

[Nils W. <nw...@me...>]

Hi all,

 How can I delete a column/row from a matrix.

In Matlab:

>> a=rand(4,4)

a =

    0.9501    0.8913    0.8214    0.9218
    0.2311    0.7621    0.4447    0.7382
    0.6068    0.4565    0.6154    0.1763
    0.4860    0.0185    0.7919    0.4057

use

>> a(:,2)=[]

a =

    0.9501    0.8214    0.9218
    0.2311    0.4447    0.7382
    0.6068    0.6154    0.1763
    0.4860    0.7919    0.4057

>> a(2,:)=[]

a =

    0.9501    0.8214    0.9218
    0.6068    0.6154    0.1763
    0.4860    0.7919    0.4057

>> 

Is there something similar in scipy, numpy or numarray ?

Any suggestion ?

Nils

[Numpy-discussion] new mail UwEuOebt

[<rmg...@tr...>]

Мы рады предложить вам новый бесплатный почтовый сервис http://www.mail15.com. Его отличительные особенности:
1) размер ящика 15 мб;
2) защищенность и надежность;
3) возможность использования любых почтовых программ(POP,IMAP,SMTP);
4) доступ из любого места в любое время;
5) простой и доступный вебинтерфейс с ПОЛНЫМ ОТСУТСТВИЕМ РЕКЛАМЫ;
6) антивирусный и антиспамовый контроль;
7) мгновенная пересылка почты.

Если вы не хотите получать более данную рассылку, пишите mailto:uns...@ma...?subject=unsubscribe

*************

 We are glad to invite you at new free mail service http://www.mail15.com. The advantages of this service are:
 1) mailbox, up to 15 Mb;
 2) absolute privacy and high reliability;
 3) ability to use mail clients (POP3, IMAP4, SMTP);
 4) access from anywhere, anytime;
 5) flexible light-weight web interface without advertising banners;
 6) antivirus and antispam control;
 7) fast mail transfer;
 8) high speed network channel;
 9) flexible light-weight web interface;
 10) wide spread ability of mail filtering and forwarding mail;
 11) clock around support;

 If you wish to be removed:
mailto:uns...@ma...?subject=unsubscrib

R2t0vLtgLZ

[Numpy-discussion] [ANN] SciPy 03 Workshop - Scientific Computing with Python

[Travis N. V. <tr...@en...>]

------------------
SciPy '03 Workshop
------------------

The SciPy '03 Workshop on Scientific Computing with Python is being held
at Cal Tech again this year.  Online registration is now available.
After last year's success, we expect another great turnout with
compelling presentations/tutorials.

It is a two day workshop held September 11-12 in Pasadena, CA.

More information may be found at:
http://www.scipy.org/site_content/scipy03 

Online registration is available at: https://www.enthought.com/scipy03 

Please register early.  Last minute registrants will have to suffer the
indignity of a handwritten name tag.

It currently looks like breakfast (bagels, etc.), lunch and supper will
be provided Thursday, and breakfast and lunch will be provided Friday.

Discussion about the workshop may be directed to the SciPy-user mailing
list (http://www.scipy.org/site_content/MailList) to which you may post
messages at sci...@sc....


Presenters:

If you would like to present at the workshop, there are two formats:

- Lightning Talks:
Short (5-15 minute) presentations of a particular scientific problem
solved with Python.

- Presentations:
Traditional presentation format ~45 minute talks.

If you would like to present, contact Eric Jones at er...@en.... 

For any other questions, please feel free to call or email Travis
Vaught: tr...@en..., (512)536-1057.  You can call the same
number to register via phone (Business Hours CST).

Links:

SciPy.org community site:
http://www.scipy.org

Workshop Home:
http://www.scipy.org/site_content/scipy03

Summary of last year's workshop:
http://www.scipy.org/site_content/scipy02/scipy02summary.htm

Re: [Numpy-discussion] Object arrays for numarray / What do you use Numeric object arrays for?

[Todd M. <jm...@st...>]

On Thu, 2003-07-24 at 03:28, Francesc Alted wrote:
> Some time ago, talking about object arrays Todd Miller wrote:
> 
> A Dijous 17 Juliol 2003 00:36, Todd Miller va escriure:
> > The prototype currently uses common code for put/take on strings, object
> > arrays, and soon record arrays.  
> 
> I am thinking on supporting multimensional arrays of record arrays soon in
> pytables. From your words, it seems that you are planning implementing this
> in the next release of numarray, isn't it? That would be nice.

Yes.  The main feature of the next release will be support for arrays of
Objects, similar to Numeric's typecode='O' arrays.

> 
> -- 
> Francesc Alted
> 
> 
-- 
Todd Miller 			jm...@st...
STSCI / ESS / SSB

Re: [Numpy-discussion] How to compute gradients or derivatives.

[Jon S. <js...@wm...>]

take a look to some parts of the code in http://www.pyclimate.org.

There are some functions to compute gradients, divergence and vertical
component of the rotational of scalar and vector fields. BUT... we only
support regular grids in a certain ordering, which is the one most used
for climate data sets. Moreover, our derivatives are computed in
spherical coordinates, like the ones used in geophysical data sets. Still,
you can use the code as a starting point to develop your own functions.

Jon Saenz.				| Tfno: +34 946012445
Depto. Fisica Aplicada II               | Fax:  +34 944648500
Facultad de Ciencias.   \\ Universidad del Pais Vasco \\
Apdo. 644   \\ 48080 - Bilbao  \\ SPAIN

On Thu, 24 Jul 2003, Maurice van de Rijzen wrote:

> Dear all,
>
> I was lookogn for u numerical extension to python and was therefore glad
> that i ran into numpy.
> I did all the calculations on mataln and I want to migrate to python.
> Numpy and numarray pretend to have the basic functionality of matlab and
> therefore i expected als a function that is able to compute gradients of
> high-order arrays which is a basic matlab thing. I could not find
> something like that. I found something in SciPy but I think that this
> one cannot compute high-order arrays.
> I'm thinkin of something as in matlab e.g. say that T=f(x,y,z,p)
>
> [gx,gy] = gradientT;
>
> Is something like that possible?
>
> Thanks in advance
>
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
> _______________________________________________
> Numpy-discussion mailing list
> Num...@li...
> https://lists.sourceforge.net/lists/listinfo/numpy-discussion
>

[Numpy-discussion] How to compute gradients or derivatives.

[Maurice v. de R. <ma...@ak...>]

Dear all,

I was lookogn for u numerical extension to python and was therefore glad
that i ran into numpy.
I did all the calculations on mataln and I want to migrate to python.
Numpy and numarray pretend to have the basic functionality of matlab and 
therefore i expected als a function that is able to compute gradients of 
high-order arrays which is a basic matlab thing. I could not find 
something like that. I found something in SciPy but I think that this 
one cannot compute high-order arrays.
I'm thinkin of something as in matlab e.g. say that T=f(x,y,z,p)

[gx,gy] = gradientT;

Is something like that possible?

Thanks in advance

Re: [Numpy-discussion] Object arrays for numarray / What do you use Numeric object arrays for?

[Francesc A. <fa...@op...>]

Some time ago, talking about object arrays Todd Miller wrote:

A Dijous 17 Juliol 2003 00:36, Todd Miller va escriure:
> The prototype currently uses common code for put/take on strings, object
> arrays, and soon record arrays.  

I am thinking on supporting multimensional arrays of record arrays soon in
pytables. From your words, it seems that you are planning implementing this
in the next release of numarray, isn't it? That would be nice.

-- 
Francesc Alted

Re: [Numpy-discussion] ANNOUNCE: numarray-0.6

[Todd M. <jm...@st...>]

On Sun, 2003-07-20 at 16:12, Sebastian Haase wrote:
> Congratulations ! 

Thanks!

> And thanks for the nice work -- I'm 
> going upgrade tomorrow...

Great.  

> And this time even the new documentation is already online 
> ;-)   [It's just somewhat sad that google still points to 
> the 'numarray has moved!' page]
> 
> Question: In an email from May-20th (actually regarding 
> rel.0.5) Todd wrote:
> "However, there is a new API function which I added in 
> response to your
>   last post: NA_NewAllFromBuffer() which enables you to 
> create arrays in C
>   from existing buffer objects rather than just C arrays."
> 
> The 0.6 documentation doesn't mention that function - for 
> now I probably have to read the source, right ?

Yes.  The signature is:

PyArrayObject * NA_NewAllFromBuffer  (int ndim, maybelong *shape,
NumarrayType type, PyObject *bufferObject, maybelong byteoffset,
maybelong bytestride, int byteorder, int aligned, int writeable)

Please try it out.

> BTW - We are already using a self-made version of that - 
> allowing us to access the CCD images that get acquired 
> from our Microspcope (mostly C++ code) as a 16-bit 
> unsigned int numarray - in real time! --- It's just great, 
> and people love it.

Excellent.  That's good to hear!

> Thanks,
> Sebastian Haase
-- 
Todd Miller <jm...@st...>

Re: [Numpy-discussion] ANNOUNCE: numarray-0.6

[Sebastian H. <ha...@ms...>]

Congratulations ! And thanks for the nice work -- I'm 
going upgrade tomorrow...
And this time even the new documentation is already online 
;-)   [It's just somewhat sad that google still points to 
the 'numarray has moved!' page]

Question: In an email from May-20th (actually regarding 
rel.0.5) Todd wrote:
"However, there is a new API function which I added in 
response to your
  last post: NA_NewAllFromBuffer() which enables you to 
create arrays in C
  from existing buffer objects rather than just C arrays."

The 0.6 documentation doesn't mention that function - for 
now I probably have to read the source, right ?

BTW - We are already using a self-made version of that - 
allowing us to access the CCD images that get acquired 
from our Microspcope (mostly C++ code) as a 16-bit 
unsigned int numarray - in real time! --- It's just great, 
and people love it.

Thanks,
Sebastian Haase





On 19 Jul 2003 06:51:53 -0400
  Todd Miller <jm...@st...> wrote:
>I forgot to regenerate the MANIFEST so the .tar.gz source 
>was
>incomplete.  It's fixed now.  
>
>Todd
>
>On Sat, 2003-07-19 at 04:09, Francesc Alted wrote:
>> Hi,
>> 
>> I've detected a problem during installation. It seems 
>>like if safethread
>> module is out of the final package:
>> 
>> inspiron:~/PyTables/pytables-0.6$ python2.3
>> Python 2.3b2 (#1, Jul  7 2003, 18:07:41)
>> [GCC 3.3.1 20030626 (Debian prerelease)] on linux2
>> Type "help", "copyright", "credits" or "license" for 
>>more information.
>> >>> from numarray import *
>> Traceback (most recent call last):
>>   File "<stdin>", line 1, in ?
>>   File 
>>"/usr/local/lib/python2.3/site-packages/numarray/__init__.py", 
>>line 1, 
>> in ?
>>     from numarrayall import *
>>   File 
>>"/usr/local/lib/python2.3/site-packages/numarray/numarrayall.py", 
>>line 
>> 2, in ?
>>     from generic import *
>>   File 
>>"/usr/local/lib/python2.3/site-packages/numarray/generic.py", 
>>line 918, 
>> in ?
>>     import numarraycore as _nc
>>   File 
>>"/usr/local/lib/python2.3/site-packages/numarray/numarraycore.py", 
>>line 
>> 1125, in ?
>>     import ufunc
>>   File 
>>"/usr/local/lib/python2.3/site-packages/numarray/ufunc.py", 
>>line 16, in 
>> ?
>>     import safethread
>> ImportError: No module named safethread
>> 
>> However, I have copied it after a previous CVS version, 
>>and that seems enough:
>> 
>> >>> from numarray import *
>> >>> import numarray.testall as testall
>> >>> testall.test()
>> *** Tester.merge: 'numarray.numtest.ratioarr' in both 
>>testers; summing 
>> outcomes.
>> *** Tester.merge: 'numarray.numtest.comparr' in both 
>>testers; summing 
>> outcomes.
>> *** Tester.merge: 'numarray.numtest' in both testers; 
>>summing outcomes.
>> *** Tester.merge: 'numarray.numtest.dtp' in both 
>>testers; summing outcomes.
>> *** Tester.merge: 'numarray.numtest.test' in both 
>>testers; summing outcomes.
>> *** Tester.merge: 'numarray.numtest.dummy' in both 
>>testers; summing outcomes.
>> numeric:  (0, 1037)
>> records:  (0, 48)
>> strings:  (0, 168)
>> memmap:  (0, 75)
>-- 
>Todd Miller <jm...@st...>
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: VM Ware
>With VMware you can run multiple operating systems on a 
>single machine.
>WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual 
>machines at the
>same time. Free trial click here: 
>http://www.vmware.com/wl/offer/345/0
>_______________________________________________
>Numpy-discussion mailing list
>Num...@li...
>https://lists.sourceforge.net/lists/listinfo/numpy-discussion

Re: [Numpy-discussion] ANNOUNCE: numarray-0.6

[Todd M. <jm...@st...>]

I forgot to regenerate the MANIFEST so the .tar.gz source was
incomplete.  It's fixed now.  

Todd

On Sat, 2003-07-19 at 04:09, Francesc Alted wrote:
> Hi,
> 
> I've detected a problem during installation. It seems like if safethread
> module is out of the final package:
> 
> inspiron:~/PyTables/pytables-0.6$ python2.3
> Python 2.3b2 (#1, Jul  7 2003, 18:07:41)
> [GCC 3.3.1 20030626 (Debian prerelease)] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> >>> from numarray import *
> Traceback (most recent call last):
>   File "<stdin>", line 1, in ?
>   File "/usr/local/lib/python2.3/site-packages/numarray/__init__.py", line 1, 
> in ?
>     from numarrayall import *
>   File "/usr/local/lib/python2.3/site-packages/numarray/numarrayall.py", line 
> 2, in ?
>     from generic import *
>   File "/usr/local/lib/python2.3/site-packages/numarray/generic.py", line 918, 
> in ?
>     import numarraycore as _nc
>   File "/usr/local/lib/python2.3/site-packages/numarray/numarraycore.py", line 
> 1125, in ?
>     import ufunc
>   File "/usr/local/lib/python2.3/site-packages/numarray/ufunc.py", line 16, in 
> ?
>     import safethread
> ImportError: No module named safethread
> 
> However, I have copied it after a previous CVS version, and that seems enough:
> 
> >>> from numarray import *
> >>> import numarray.testall as testall
> >>> testall.test()
> *** Tester.merge: 'numarray.numtest.ratioarr' in both testers; summing 
> outcomes.
> *** Tester.merge: 'numarray.numtest.comparr' in both testers; summing 
> outcomes.
> *** Tester.merge: 'numarray.numtest' in both testers; summing outcomes.
> *** Tester.merge: 'numarray.numtest.dtp' in both testers; summing outcomes.
> *** Tester.merge: 'numarray.numtest.test' in both testers; summing outcomes.
> *** Tester.merge: 'numarray.numtest.dummy' in both testers; summing outcomes.
> numeric:  (0, 1037)
> records:  (0, 48)
> strings:  (0, 168)
> memmap:  (0, 75)
-- 
Todd Miller <jm...@st...>

Re: [Numpy-discussion] ANNOUNCE: numarray-0.6

[Jerzy K. <ka...@in...>]

Todd Miller wrote:
> I have just uploaded numarray-0.6 to Source Forge. 
> 
> http://sourceforge.net/project/showfiles.php?group_id=1369
> 
> This is the first release with numarray repackaged as a Python package.


GREAT.
And what is even more great - I see that the version adapted to Python 2.3
is there. In some private exchange I read "of course we will upgrade, but
2.3 is beta, let's wait when it stabilizes".

I sincerely think that all essential goodies (and numarray is one of them)
should evolve in parallel with the kernel. Personally I wouldn't touch new
versions of Python without having those additional goodies, since I wouldn't
know what to do with it. Just playing with Guido's tutorial, or what?

Thank you.


Jerzy Karczmarczuk
Caen, France

Re: [Numpy-discussion] ANNOUNCE: numarray-0.6

[Francesc A. <fa...@op...>]

Hi,

I've detected a problem during installation. It seems like if safethread
module is out of the final package:

inspiron:~/PyTables/pytables-0.6$ python2.3
Python 2.3b2 (#1, Jul  7 2003, 18:07:41)
[GCC 3.3.1 20030626 (Debian prerelease)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from numarray import *
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File "/usr/local/lib/python2.3/site-packages/numarray/__init__.py", line 1, 
in ?
    from numarrayall import *
  File "/usr/local/lib/python2.3/site-packages/numarray/numarrayall.py", line 
2, in ?
    from generic import *
  File "/usr/local/lib/python2.3/site-packages/numarray/generic.py", line 918, 
in ?
    import numarraycore as _nc
  File "/usr/local/lib/python2.3/site-packages/numarray/numarraycore.py", line 
1125, in ?
    import ufunc
  File "/usr/local/lib/python2.3/site-packages/numarray/ufunc.py", line 16, in 
?
    import safethread
ImportError: No module named safethread

However, I have copied it after a previous CVS version, and that seems enough:

>>> from numarray import *
>>> import numarray.testall as testall
>>> testall.test()
*** Tester.merge: 'numarray.numtest.ratioarr' in both testers; summing 
outcomes.
*** Tester.merge: 'numarray.numtest.comparr' in both testers; summing 
outcomes.
*** Tester.merge: 'numarray.numtest' in both testers; summing outcomes.
*** Tester.merge: 'numarray.numtest.dtp' in both testers; summing outcomes.
*** Tester.merge: 'numarray.numtest.test' in both testers; summing outcomes.
*** Tester.merge: 'numarray.numtest.dummy' in both testers; summing outcomes.
numeric:  (0, 1037)
records:  (0, 48)
strings:  (0, 168)
memmap:  (0, 75)


-- 
Francesc Alted

[Numpy-discussion] ANNOUNCE: numarray-0.6

[Todd M. <jm...@st...>]

I have just uploaded numarray-0.6 to Source Forge. 

http://sourceforge.net/project/showfiles.php?group_id=1369

This is the first release with numarray repackaged as a Python package.

I. ENHANCEMENTS

1. Repackaging

numarray has been modified from a collection of Python modules into a
Python package.   See Doc/Repackaging in the source distribution for
more details.

2. Median Filter Function

See numarray.image.combine.median for a function which computes the
median pixels in a stack of images.

3. Thread Safety Work

Modifications to ufunc caching and IEEE error handling enable numarray
to work in multi-threaded programs.  

II. BUGS FIXED

733534 Broadcasts of non-array sequences fails 
733535 NA_typeNoToTypeObject sometimes fails 
736674 PyArray_ContiguousFromObject() fails for some scalars 
737041 Build failure on Cygwin 1.3.22 (very current install).
750320 CharArray.raw() is broken
750326 building RPMS fails
754836 Missing Src/_convmodule.c during setup
756050 chararray multi-d copy fails for recarray
772519 memory.new_memory() 64-bit scanning bug

III. CAUTIONS

1. Due to the distribution repackaging, numarray-0.6 will not install
correctly on top of an existing numarray installation. Before
installing numarray-0.6 remove your old version of numarray.

-- 
Todd Miller 			jm...@st...
STSCI / ESS / SSB

[Numpy-discussion] you didn't reply my email ? why ? ???

[<ye...@16...>]

DQo8Ym9keT4NCg0KPGk+DQo8cD48Yj48Zm9udCBmYWNlPSJBcmlhbCIgc2l6ZT0iMyI+UDwv
Zm9udD48Zm9udCBmYWNlPSJBcmlhbCIgc2l6ZT0iMyI+bGVhc2Ugbm90ZSANCnRvIHNlbmQg
QUxMIFJFUExZIGUtbWFpbCBkaXJlY3QgdG8gb3VyIFNhbGVzIFJlcHJlc2VudGF0aXZlIGF0
OjwvZm9udD48L2I+PC9wPg0KPHU+DQo8cD48Zm9udCBmYWNlPSJBcmlhbCIgc2l6ZT0iMyIg
Y29sb3I9IiNGRjAwMDAiPjxiPlF1ZXN0aW9uc0BQZXJmZWN0V2F0Y2hQaWVjZS5jb208L2I+
PC9mb250PjwvcD4NCjwvdT48L2k+DQo8cD48Zm9udCBmYWNlPSJBcmlhbCIgc2l6ZT0iMyI+
SGksPGJyPg0KVGhhbmsgeW91IGZvciBleHByZXNzaW5nIGludGVyZXN0IGluIEFUR1dTIHdh
dGNoZXMuPGJyPg0KV2Ugd291bGQgbGlrZSB0byB0YWtlIHRoaXMgb3Bwb3J0dW5pdHkgdG8g
b2ZmZXIgeW91IG91ciBmaW5lIHNlbGVjdGlvbiBvZiANCkl0YWxpYW4gY3JhZnRlZCBSb2xl
eCBUaW1lcGllY2VzLjwvZm9udD48L3A+DQo8cD48Zm9udCBmYWNlPSJBcmlhbCIgc2l6ZT0i
MyI+WW91IGNhbiB2aWV3IG91ciBsYXJnZSBzZWxlY3Rpb24gb2YgUm9sZXhlcyANCihpbmNs
dWRpbmcgQnJlaXRsaW5nLCBUYWcgSGV1ZXIsIENhcnRpZXIgZXRjKSBhdDo8L2ZvbnQ+PC9w
Pg0KPHU+DQo8cD48Zm9udCBmYWNlPSJBcmlhbCIgc2l6ZT0iMyI+PGI+PGEgaHJlZj0iaHR0
cDovL3d3dy5QZXJmZWN0V2F0Y2hQaWVjZS5jb20iPnd3dy5QZXJmZWN0V2F0Y2hQaWVjZS5j
b208L2E+IA0KPC9iPjwvZm9udD48L3A+DQo8L3U+DQo8cD48Zm9udCBmYWNlPSJBcmlhbCIg
c2l6ZT0iMyI+Rm9yIGFsbCBvcmRlcnMgcGxhY2VkIGluIHRoZSBtb250aCBvZiBKdWx5LCA8
Yj5hbGwgDQpzaGlwcGluZyBhbmQgaGFuZGxpbmcgY2hhcmdlcyB3aWxsIGJlIGZyZWU8L2I+
LjwvZm9udD48L3A+DQo8cD48Zm9udCBmYWNlPSJBcmlhbCIgc2l6ZT0iMyI+QXMgd2UgYXJl
IHRoZSBkaXJlY3QgbWFudWZhY3R1cmVycywgeW91IGFyZSANCmd1YXJhbnRlZWQgb2YgbG93
ZXN0IHByaWNlcyBhbmQgaGlnaGVzdCBxdWFsaXR5IGVhY2ggYW5kIGV2ZXJ5IHRpbWUgeW91
IHB1cmNoYXNlIA0KZnJvbSB1cy48L2ZvbnQ+PC9wPg0KPHA+PGZvbnQgZmFjZT0iQXJpYWwi
IHNpemU9IjMiPllvdSBtYXkgYWxzbyBiZSBpbnRlcmVzdGVkIHRvIGtub3cgdGhhdCB3ZSBo
YXZlIA0KdGhlIGZvbGxvd2luZyBicmFuZHMgYXZhaWxhYmxlIGluIG91ciB3aWRlIHNlbGVj
dGlvbiBhcyB3ZWxsOjwvZm9udD48L3A+DQo8cD48Zm9udCBmYWNlPSJBcmlhbCIgc2l6ZT0i
MyI+PGJyPg0KMS4gTGVhdGhlciBiYW5kIERheXRvbmEgKGxhZGllcyBhbmQgbWVuoa9zKTxi
cj4NCjIuIEJsYW5jcGFpbjwvZm9udD48L3A+DQo8cD48Zm9udCBmYWNlPSJBcmlhbCIgc2l6
ZT0iMyI+My4gRm9ydGlzPC9mb250PjwvcD4NCjxwPjxmb250IGZhY2U9IkFyaWFsIiBzaXpl
PSIzIj40LiBKYWVnZXIgTGVDb3V0cmU8L2ZvbnQ+PC9wPg0KPHA+PGZvbnQgZmFjZT0iQXJp
YWwiIHNpemU9IjMiPjUuIExvbmdpbmVzPC9mb250PjwvcD4NCjxwPjxmb250IGZhY2U9IkFy
aWFsIiBzaXplPSIzIj42LiBNb250IEJsYW5jPC9mb250PjwvcD4NCjxwPjxmb250IGZhY2U9
IkFyaWFsIiBzaXplPSIzIj43LiBNb3ZhZG88L2ZvbnQ+PC9wPg0KPHA+PGZvbnQgZmFjZT0i
QXJpYWwiIHNpemU9IjMiPjguIE9yaXM8L2ZvbnQ+PC9wPg0KPHA+PGZvbnQgZmFjZT0iQXJp
YWwiIHNpemU9IjMiPjkuIFJvZ2VyIER1YnVpczwvZm9udD48L3A+DQo8cD48Zm9udCBmYWNl
PSJBcmlhbCIgc2l6ZT0iMyI+MTAuIFVseXNzZTwvZm9udD48L3A+DQo8cD48Zm9udCBmYWNl
PSJBcmlhbCIgc2l6ZT0iMyI+MTEuIFplbml0aDwvZm9udD48L3A+DQo8cD48Zm9udCBmYWNl
PSJBcmlhbCIgc2l6ZT0iMyI+MTIuIEF1ZGVtYXIgUGlndWV0PC9mb250PjwvcD4NCjxwPjxm
b250IGZhY2U9IkFyaWFsIiBzaXplPSIzIj4xMy4gQnJlaXRsaW5nPC9mb250PjwvcD4NCjxw
Pjxmb250IGZhY2U9IkFyaWFsIiBzaXplPSIzIj4xNC4gQnZnbGFyaTwvZm9udD48L3A+DQo8
cD48Zm9udCBmYWNlPSJBcmlhbCIgc2l6ZT0iMyI+MTUuIENhcnRpZXI8L2ZvbnQ+PC9wPg0K
PHA+PGZvbnQgZmFjZT0iQXJpYWwiIHNpemU9IjMiPjE2LiBDb3J1bTwvZm9udD48L3A+DQo8
cD48Zm9udCBmYWNlPSJBcmlhbCIgc2l6ZT0iMyI+MTcuIER1bmhpbGw8L2ZvbnQ+PC9wPg0K
PHA+PGZvbnQgZmFjZT0iQXJpYWwiIHNpemU9IjMiPjE4LiBGcmFuY2sgTXVsbGVyPC9mb250
PjwvcD4NCjxwPjxmb250IGZhY2U9IkFyaWFsIiBzaXplPSIzIj4xOS4gR2VyYXJkIFBlcnJl
Z2F1eDwvZm9udD48L3A+DQo8cD48Zm9udCBmYWNlPSJBcmlhbCIgc2l6ZT0iMyI+MjAuIElX
QzwvZm9udD48L3A+DQo8cD48Zm9udCBmYWNlPSJBcmlhbCIgc2l6ZT0iMyI+MjEuIElXQzwv
Zm9udD48L3A+DQo8cD48Zm9udCBmYWNlPSJBcmlhbCIgc2l6ZT0iMyI+MjIuIFBhbmVyYWk8
L2ZvbnQ+PC9wPg0KPHA+PGZvbnQgZmFjZT0iQXJpYWwiIHNpemU9IjMiPjIzLiBQYXRlayBQ
aGlsaXBwZTwvZm9udD48L3A+DQo8cD48Zm9udCBmYWNlPSJBcmlhbCIgc2l6ZT0iMyI+MjQu
IFRhZyBIZXVlcjwvZm9udD48L3A+DQo8cD48Zm9udCBmYWNlPSJBcmlhbCIgc2l6ZT0iMyI+
MjUuIFZhY2hlcm9uIENvbnN0YW50aW48L2ZvbnQ+PC9wPg0KPGZvbnQgRkFDRT0iVGltZXMg
TmV3IFJvbWFuIj4NCjxwPqGhPC9wPg0KPC9mb250Pg0KPHA+PGZvbnQgZmFjZT0iQXJpYWwi
IHNpemU9IjMiPklmIHlvdSBzZWUgYW55dGhpbmcgdGhhdCBtaWdodCBpbnRlcmVzdCB5b3Us
IG9yIA0KaWYgeW91IGhhdmUgYW55IHF1ZXN0aW9ucywgcGxlYXNlIGRvbid0IGhlc2l0YXRl
IHRvIHZpc2l0IG91ciB3ZWJzaXRlIGF0Ojxicj4NCjwvZm9udD48L3A+DQo8dT4NCjxwPjxm
b250IGZhY2U9IkFyaWFsIiBzaXplPSIzIj48Yj48YSBocmVmPSJodHRwOi8vd3d3LlBlcmZl
Y3RXYXRjaFBpZWNlLmNvbSI+d3d3LlBlcmZlY3RXYXRjaFBpZWNlLmNvbTwvYT4gDQo8L2I+
PC9mb250PjwvcD4NCjwvdT4NCjxwPjxmb250IGZhY2U9IkFyaWFsIiBzaXplPSIzIj48YnI+
DQpJIGNlcnRhaW5seSBsb29rIGZvcndhcmQgdG8gaGVhcmluZyBmcm9tIHlvdS48YnI+DQo8
YnI+DQpCZXN0IHJlZ2FyZHMsPGJyPg0KPGJyPg0KQ2FsPC9mb250PjwvcD4NCjxwPjxmb250
IGZhY2U9IkFyaWFsIiBzaXplPSIzIj48YnI+DQpEaXZpc2lvbiBTYWxlcyBNYW5hZ2VyPGJy
Pg0KQVRHV1M8L2ZvbnQ+PC9wPg0KPHA+PGk+PGZvbnQgU0laRT0iMiI+PC9wPg0KPC9mb250
PjwvaT4NCjxwPjxmb250IGZhY2U9IkFyaWFsIiBzaXplPSIzIj5Zb3UgcmVjZWl2ZWQgdGhp
cyBlbWFpbCBiZWNhdXNlIHlvdXIgaGF2ZSANCnByZXZpb3VzIHB1cmNoYXNlZCBmcm9tLCBv
ciBpbnF1aXJlZCBhYm91dCBvdXIgcHJvZHVjdCBsaW5lIHVuZGVyIEFUR1dTLiBJZiB5b3Ug
DQpkbyBub3Qgd2FudCB0byByZWNlaXZlIGZ1cnRoZXIgbWFpbGluZ3MgZnJvbSBBVEdXUywg
dW5zdWJzY3JpYmUgYnkgc2VuZGluZyBhbiANCmVtYWlsIHdpdGggdGhlIHRpdGxlIGhlYWRp
bmc6IERFTEVURSBpbiB0aGUgc3ViamVjdCBsaW5lIHRvIDx1PnVuc3Vic2NyaWJlQFBlcmZl
Y3RXYXRjaFBpZWNlLmNvbTwvdT48L2ZvbnQ+PC9wPg0KPGk+DQo8cD48Zm9udCBmYWNlPSJB
cmlhbCIgc2l6ZT0iMyIgY29sb3I9IiMwMDAwRkYiPjxiPnBsZWFzZSBub3RlIHRvIHNlbmQg
QUxMIFJFUExZIA0KZS1tYWlsIGRpcmVjdCB0byBvdXIgU2FsZXMgUmVwcmVzZW50YXRpdmUg
YXQ6PC9iPjwvZm9udD48L3A+DQo8dT4NCjxwPjxmb250IGZhY2U9IkFyaWFsIiBzaXplPSIz
IiBjb2xvcj0iI0ZGMDAwMCI+PGI+UXVlc3Rpb25zQFBlcmZlY3RXYXRjaFBpZWNlLmNvbTwv
Yj48L2ZvbnQ+PC9wPg0KPC91PjwvaT48Zm9udCBGQUNFPSJUaW1lcyBOZXcgUm9tYW4iPg0K
PHA+oaE8L3A+DQo8L2ZvbnQ+DQoNCjwvYm9keT4NCg0KDQogICAg

Re: [Numpy-discussion] Object arrays for numarray / What do you use Numeric object arrays for?

[Dave C. <dj...@ob...>]

>>>>> "Todd" == Todd Miller <jm...@st...> writes:

Todd> I don't understand the difference between your module and
Todd> Python's mmap.

>> The code could use probably the Python mmap module.  It would be
>> difficult because all access to the Python mmap object is via
>> Python.
>> 
>> A CObject exported API in the Python mmap module would be very
>> useful.
>> 

Todd> What do you want to get via the CObject API?  Since any mmap can
Todd> be treated as a buffer, it's easy to get a pointer and size via
Todd> the Python buffer API in C. Is there something else you need?

Nope.  I wonder why I didn't realise that...  Too stupid I suppose.

- Dave

-- 
http://www.object-craft.com.au

Re: [Numpy-discussion] Object arrays for numarray / What do you use Numeric object arrays for?

[Todd M. <jm...@st...>]

On Thu, 2003-07-17 at 06:44, Dave Cole wrote:
> >>>>> "Todd" == Todd Miller <jm...@st...> writes:
> 
> Todd> I don't understand the difference between your module and
> Todd> Python's mmap.
> 
> >> The code could use probably the Python mmap module.  It would be
> >> difficult because all access to the Python mmap object is via
> >> Python.
> >> 
> >> A CObject exported API in the Python mmap module would be very
> >> useful.
> >> 
> 
> Todd> What do you want to get via the CObject API?  Since any mmap can
> Todd> be treated as a buffer, it's easy to get a pointer and size via
> Todd> the Python buffer API in C. Is there something else you need?
> 
> Nope.  I wonder why I didn't realise that...  Too stupid I suppose.

I doubt that or you wouldn't be using Python...  The buffer API is just
a little obscure.

> 
> - Dave
-- 
Todd Miller <jm...@st...>