I compiled the recent numpy from svn on gentoo-amd64, since then I often get
the error message:
RuntimeError: FATAL: module compiled aslittle endian, but detected different
endianness at runtime
Of course AMD64 is little endian, and array's byteorder is little endian by
default.
Grepping show
On Sep 15, 2009, at 12:50 AM, Skipper Seabold wrote:
>>
>> Fixed-width fields should already be supported. Instead of delimiter=
>> [1-6, 7-10, 11-15, 16]..., use delimiter=[6, 4, 4, 1] (that is, just
>> give the widths of the fields).
>> Note that I wouldn't be surprised at all if it failed for s
On Mon, Sep 14, 2009 at 11:40 PM, Pierre GM wrote:
>
> On Sep 14, 2009, at 10:55 PM, Skipper Seabold wrote:
>>
>> While we're on the subject, the other thing on my wishlist (unless I
>> just don't know how to do this) is being able to define a "column map"
>> for datasets that have no delimiters.
On Sep 14, 2009, at 10:55 PM, Skipper Seabold wrote:
>
> While we're on the subject, the other thing on my wishlist (unless I
> just don't know how to do this) is being able to define a "column map"
> for datasets that have no delimiters. At first each observation of my
> data was just one long s
On Mon, Sep 14, 2009 at 10:55 PM, Skipper Seabold wrote:
> On Mon, Sep 14, 2009 at 10:41 PM, Pierre GM wrote:
>>
>> On Sep 14, 2009, at 10:31 PM, Skipper Seabold wrote:
>>>
>>> I actually figured out a workaround with converters, since my missing
>>> values are " "," "," " ie., irregular numbe
On Mon, Sep 14, 2009 at 10:41 PM, Pierre GM wrote:
>
> On Sep 14, 2009, at 10:31 PM, Skipper Seabold wrote:
>>
>> I actually figured out a workaround with converters, since my missing
>> values are " "," "," " ie., irregular number of spaces and the
>> values aren't stripped of white spaces. I
On Sep 14, 2009, at 10:31 PM, Skipper Seabold wrote:
>
> I actually figured out a workaround with converters, since my missing
> values are " "," "," " ie., irregular number of spaces and the
> values aren't stripped of white spaces. I just define {# : lambda s:
> float(s.strip() or 0)}, and I
On Mon, Sep 14, 2009 at 9:59 PM, Pierre GM wrote:
>
> On Sep 13, 2009, at 3:51 PM, Skipper Seabold wrote:
>
>> On Sun, Sep 13, 2009 at 1:29 PM, Skipper Seabold
>> wrote:
>>> Is there a reason that the missing argument in genfromtxt only
>>> takes a string?
>
> Because we check strings. Note that
On Sep 13, 2009, at 3:51 PM, Skipper Seabold wrote:
> On Sun, Sep 13, 2009 at 1:29 PM, Skipper Seabold
> wrote:
>> Is there a reason that the missing argument in genfromtxt only
>> takes a string?
Because we check strings. Note that you can specify several characters
at once, provided the
Thanks for the help.
I think that deleting the old build directory before rebuilding may have
been the trick.
The output below shows i'm no longer reproducing the error.
best wishes,
- Sebastian Gurovich
In [3]: numpy.__version__
Out[3]: '1.3.0'
In [4]: a=numpy.zeros(0x8000,dtype='b1')
In [5]:
Hi,
I would like to change the dtype of just one field of a structured or
record array without copying the original array. I can not change the
creation of the original array because it was created using genfromtxt.
For example,
r=np.rec.array([(1, 1.0), (1, 1.0), (1, 1.0)],dtype=[('foo', int),
On Mon, Sep 14, 2009 at 4:46 AM, Ruben Salvador wrote:
> Hi there!
>
> It's a time since I'm asking this question to myself, and still don't know
> a Pythonic way to solve it. I want to create a 2D array where each *row* is
> a copy of an already existing 1D array. For example:
>
> In [21]: a = np
Hello,
does anyone on this list have any idea what might cause SuperLU to not
solve on my computer when the associated code works perfectly well on
somebody else's? On my computer the code crashes with the error message
'SuperLU solve failed: info=9'
thanks
Michael Walker
Plant Modelling Group
C
Folks,
this simple timeit -> a largish speed ratio that surprised me --
but perhaps I've done something stupid ?
""" timeit one big vs many little a[ogrid] = f(ogrid)
Consider evaluating a function on an NxN grid, in 2 ways:
a) in one shot:
y,x = ogrid[0:N, 0:N]
a[y,x] = f(x,y)
b) piece
Perfect, that's exactly what I need! Somehow I missed this routine when
checking documentation :S
In [58]: a
Out[58]: array([1, 2, 3])
In [59]: np.tile(a, (5,1))
Out[59]:
array([[1, 2, 3],
[1, 2, 3],
[1, 2, 3],
[1, 2, 3],
[1, 2, 3]])
Thanks a lot!
On Mon, Sep 14, 2009 at 1:07 PM, Citi, Luca wr
if I get your question correctly, np.tile could be what you need
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Ruben Salvador skrev:
> [...] I want to create a 2D array where each
> *row* is a copy of an already existing 1D array. For example:
> In [25]: a
> Out[25]: array([1, 2, 3])
> [...]
> In [30]: b
> Out[30]:
> array([[1, 2, 3],
> [1, 2, 3],
> [1, 2, 3],
> [1, 2, 3],
> [1, 2, 3]])
>
Without unders
Hi there!
It's a time since I'm asking this question to myself, and still don't know a
Pythonic way to solve it. I want to create a 2D array where each *row* is a
copy of an already existing 1D array. For example:
In [21]: a = np.array[1, 2, 3]
In [25]: a
Out[25]: array([1, 2, 3])
To create a 2D
Mon, 14 Sep 2009 09:08:34 +0200, Mads Ipsen wrote:
[clip]
> Well, I don't know you consider this as a valid argument, but to me its
> a matter of removing a single comma, which will make the source less
> sensitive to compilers and compiler flags.
That's done.
--
Pauli Virtanen
On Sun, Sep 13, 2009 at 11:55:43PM -0400, David Warde-Farley wrote:
> On 13-Sep-09, at 8:51 PM, brechmos wrote:
> > I have a large dataset (e.g., 70 x 500 x 500) and want to
> > interpolate points
> > (for example to double the size). What it seems I want is:
> > []: newx,newy,newz=mgrid[1:70
Pauli Virtanen wrote:
> su, 2009-09-13 kello 01:47 +0300, Pauli Virtanen kirjoitti:
> [clip]
>
>> The error you get from the comma at the end of the enum must be because
>> you have
>>
>> -pedantic -Werror
>>
>> in your CFLAGS. Just
>>
>> unset CFLAGS
>>
>> or so before compilati
21 matches
Mail list logo
