Michael McNeil Forbes wrote:
In article [EMAIL PROTECTED],
Travis Oliphant [EMAIL PROTECTED] wrote:
Hmm I know that the code was changed at some point a few months ago
specifically to this behavior because of some concerns Perry, Chris
(people at STScI) had. Originally, field
On Sunday 29 October 2006 02:40, Travis Oliphant wrote:
I've committed some fixes to this particular issue that allows setattr
to be used to set field names.
I just started playing with the new recarray: that works great !
Travis, Thanks a lot !
On Friday 27 October 2006 22:18, Michael McNeil Forbes wrote:
Is the following the desired behaviour for setting recarray attributes?
I ran into the same problem recently...
What about modifying __setattr__ to the following ?
def __setattr__(self, attr, val):
fielddict =
Michael McNeil Forbes wrote:
Is the following the desired behaviour for setting recarray attributes?
This seems to clash with the semantics for arrays.
from numpy import *
a = array([1,2,3])
b = a.view([('x',int),('y',int),('z',int)])
r = b.view(recarray)
b['x'] = 0
r.y = 0
On Saturday 28 October 2006 14:28, Travis Oliphant wrote:
Hmm I know that the code was changed at some point a few months ago
specifically to this behavior because of some concerns Perry, Chris
(people at STScI) had. Originally, field names came first, but we
changed it so they could
In article [EMAIL PROTECTED],
Travis Oliphant [EMAIL PROTECTED] wrote:
Hmm I know that the code was changed at some point a few months ago
specifically to this behavior because of some concerns Perry, Chris
(people at STScI) had. Originally, field names came first, but we
changed it
In article [EMAIL PROTECTED],
Pierre GM [EMAIL PROTECTED] wrote:
So that I could have a field named 'shape', and modifying
r.shape would change the shape of the array, not the content of the field ?
That makes sense, but isn't it a bit dangerous ? Shouldn't we have a list of
reserved
On Saturday 28 October 2006 22:45, Michael McNeil Forbes wrote:
Since the field names can be used with regular arrays without any
consequences, I think it would be bad to raise an exception with
recarrays where there was no problem with regular arrays, and regular
arrays should allow field
Is the following the desired behaviour for setting recarray attributes?
This seems to clash with the semantics for arrays.
from numpy import *
a = array([1,2,3])
b = a.view([('x',int),('y',int),('z',int)])
r = b.view(recarray)
b['x'] = 0
r.y = 0
a
array([0, 2, 3])
r.x
Le vendredi 15 septembre 2006 16:05, Francesc Altet a écrit :
Another possibility is to play with columns directly from the initial
recarray. The next is an example:
In [101]: ra=numpy.rec.array(1*36, dtype=a4,i4,f4, shape=3)
In [102]: ra
Out[102]:
recarray([('', 825307441,
Le lundi 18 septembre 2006 12:17, Francesc Altet a écrit :
You have two problems here. The first is that you shouldn't have missign
entries, or conversion from empty strings to ints (or whatever) will
fail:
int('')
Traceback (most recent call last):
File stdin, line 1, in ?
ValueError:
El dl 18 de 09 del 2006 a les 17:10 +0200, en/na Lionel Roubeyrie va
escriure:
Le lundi 18 septembre 2006 12:17, Francesc Altet a écrit :
You have two problems here. The first is that you shouldn't have missign
entries, or conversion from empty strings to ints (or whatever) will
fail:
Le lundi 18 septembre 2006 17:40, Francesc Altet a écrit :
I'm running NumPy 1.0b5. Please, check that you are using a recent
version of it.
Cheers,
Arg, sorry, version here was 0.9, an upgrade and it works fine.
thanks again
--
Lionel Roubeyrie - [EMAIL PROTECTED]
LIMAIR
Hi all,
I try to use recarray with rec.fromrecords on time-series, datas come from a
file where they are stored in csv format, with after each data colum there is
one column meanning the state of the data, and the first column is for dates.
Then, is it possible to directly transform column of
Lionel Roubeyrie wrote:
Hi all,
I try to use recarray with rec.fromrecords on time-series, datas come from a
file where they are stored in csv format, with after each data colum there is
one column meanning the state of the data, and the first column is for dates.
Then, is it possible to
A Divendres 15 Setembre 2006 15:57, Robert Kern va escriure:
Lionel Roubeyrie wrote:
Hi all,
I try to use recarray with rec.fromrecords on time-series, datas come
from a file where they are stored in csv format, with after each data
colum there is one column meanning the state of the
Howdy! I just wanted to voice my agreement with this statment by Erin Sheldon:
I brought up the issue a while back of having a simple way to
access the field names of an array. The quick summary: accessing
field names has some oddness that needs cleaning up.
Sometimes a['name'], sometimes
John Parejko wrote:
Howdy! I just wanted to voice my agreement with this statment by Erin Sheldon:
I brought up the issue a while back of having a simple way to
access the field names of an array. The quick summary: accessing
field names has some oddness that needs cleaning up.
Sometimes
John Parejko wrote:
Howdy! I just wanted to voice my agreement with this statment by Erin Sheldon:
I brought up the issue a while back of having a simple way to
access the field names of an array. The quick summary: accessing
field names has some oddness that needs cleaning up.
Sometimes
Just tested the lastest SVN and it works as advertised. Thanks
Travis.
An unrelated question: why does this work for arrays but not recarrays?
In [24]: mydescriptor = [('age',float64),('Nchildren',int8),('weight',float32)]
In [25]: a = array([(64,2,75.0),(25,0,60.0)], dtype=mydescriptor)
Erin Sheldon wrote:
Just tested the lastest SVN and it works as advertised. Thanks
Travis.
An unrelated question: why does this work for arrays but not recarrays?
In [24]: mydescriptor =
[('age',float64),('Nchildren',int8),('weight',float32)]
In [25]: a =
On 7/11/06, Travis Oliphant [EMAIL PROTECTED] wrote:
Erin Sheldon wrote:
Just tested the lastest SVN and it works as advertised. Thanks
Travis.
An unrelated question: why does this work for arrays but not recarrays?
In [24]: mydescriptor =
Hi everyone -
(sigh) These gmail issues are really annoying...so I apologize
if the gmail version of this message shows up in a few days.
I brought up the issue a while back of having a simple way to
access the field names of an array. The quick summary: accessing
field names has some oddness
It was suggested that I put off this discussion until we were closer
to the 1.0 release. Perhaps now is a good time to bring it up once
again? The quick summary: accessing field names has some
oddness that needs cleaning up.
On 3/15/06, Travis Oliphant [EMAIL PROTECTED] wrote:
Fernando Perez
Hi everyone -
Recarrays have convenience attributes such that
fields may be accessed through . in additioin to
the field() method. These attributes are designed for
read only; one cannot alter the data through them.
Yet they are writeable:
tr=numpy.recarray(10, formats='i4,f8,f8',
Hi everyone -
Recarrays have convenience attributes such that
fields may be accessed through . in additioin to
the field() method. These attributes are designed for
read only; one cannot alter the data through them.
Yet they are writeable:
tr=numpy.recarray(10, formats='i4,f8,f8',
El dv 16 de 06 del 2006 a les 14:46 -0700, en/na Andrew Straw va
escriure:
Erin Sheldon wrote:
Anyway - Recarrays have convenience attributes such that
fields may be accessed through . in additioin to
the field() method. These attributes are designed for
read only; one cannot alter the
On 6/17/06, Francesc Altet [EMAIL PROTECTED] wrote:
However, I think that this has its utility, specially when accessing to
nested fields (see later). In addition, I'd suggest introducing a
special accessor called, say, 'fields' in order to access the fields
themselves and not the attributes.
This reply sent 9:36 AM, Jun 17 (because it may not show up
for a day or so from my gmail account, if it shows up at all)
On 6/17/06, Francesc Altet [EMAIL PROTECTED] wrote:
El dv 16 de 06 del 2006 a les 14:46 -0700, en/na Andrew Straw va
escriure:
Erin Sheldon wrote:
Anyway - Recarrays
Hi everyone -
(this is my fourth try in the last 24 hours to post this.
Apparently, the gmail smtp server is in the blacklist!!
this is bad).
Anyway - Recarrays have convenience attributes such that
fields may be accessed through . in additioin to
the field() method. These attributes are
Hi everyone -
(this is my third try in the last 24 hours to post this.
For some reason it hasn't been making it through)
Recarrays have convenience attributes such that
fields may be accessed through . in additioin to
the field() method. These attributes are designed for
read only; one cannot
Erin Sheldon wrote:
Hi everyone -
(this is my fourth try in the last 24 hours to post this.
Apparently, the gmail smtp server is in the blacklist!!
this is bad).
I doubt it since that's where my email goes through. Sourceforge is frequently
slow, so please have patience if your mail does
Erin Sheldon wrote:
Anyway - Recarrays have convenience attributes such that
fields may be accessed through . in additioin to
the field() method. These attributes are designed for
read only; one cannot alter the data through them.
Yet they are writeable:
tr=numpy.recarray(10,
The initial bounces actually say, and I quote:
Technical details of temporary failure:
TEMP_FAILURE: SMTP Error (state 8): 550-rejected because your SMTP
server, 66.249.92.170, is in the Spamcop RBL.
550 See http://www.spamcop.net/bl.shtml for more information.
On 6/16/06, Robert Kern [EMAIL
34 matches
Mail list logo
