> You need to give an array for each axis. Each of these arrays will be
> broadcast against each other to form three arrays of the desired shape
> of composite. This is discussed in the manual here:
>
>
> http://mentat.za.net/numpy/refguide/indexing.xhtml#indexing-multi-dimensional-arrays
>
> Con
On Wed, Oct 8, 2008 at 20:00, Zachary Pincus <[EMAIL PROTECTED]> wrote:
> Hello all,
>
> I'm doing something silly with images and am unable to figure out the
> right way to express this with "fancy indexing" -- or anything other
> than a brute for-loop for that matter.
>
> The basic gist is that I
Hello all,
I'm doing something silly with images and am unable to figure out the
right way to express this with "fancy indexing" -- or anything other
than a brute for-loop for that matter.
The basic gist is that I have an array representing n images, of shape
(n, x, y). I also have a "map"
On Oct 8, 2008, at 1:36 PM, Anne Archibald wrote:
> How important did you find the ability to select priority versus
> non-priority search?
>
> How important did you find the ability to select other splitting
> rules?
In both cases, I included those things just because they were options
in
My version of a wrapper of ANN is attached. I wrote it when I had
some issues installing the scikits.ann package. It uses ctypes, and
might be useful in deciding on an API.
Please feel free to take what you like,
-Rob
ann.tar.gz
Description: GNU Zip compressed data
Rob Hetland
Just to note, on the compilation issue, I encountered this a while ago with
numpy 1.1.1 and I think Python 2.6b2, again because we wanted to skip Python
2.5 in my organization, largely because it was an issue to get working on
64-bit. I couldn't find anywhere 7.1 was available.
We discussed errors
On 10/8/2008 10:29 AM Ravi apparently wrote:
> I sometimes wonder about the motivation for an
> unpaid volunteer to take on an utterly thankless job in which help is never
> forthcoming from users ...
> Thank for taking on this arduous task.
See, it is not entirely thankless. ;-)
I would like
Ravi wrote:
>
> The reasons above are why I don't try to do anything on Windows unless there
> is support from some external source, e.g., CMake taking care of build
> issues.
> The reasons above are also why I admire your heroic efforts at making Windows
> binaries available. But, then, I some
On Wednesday 08 October 2008 09:44:25 David Cournapeau wrote:
> For one, the manifest madness introduced with VS 2005 may be painful to
> handle, since it severly lacks any serious documentation. I am still
> unsure whether we will need to care at all, though.
>
> Another problem is that python hea
On Wednesday 08 October 2008 09:40:58 David Cournapeau wrote:
> > How about python 2.5 and numpy 1.2 instead? Python 2.6 makes some
> > important changes to python 2.5 (in preparation for Python 3.0), so
> > you may find several other packages will take a couple of months to
> > work 100% with pyt
>Could you compress win-amd64-2.6\numpy\core\src\umathmodule.c -- it
>should be in the build directory -- and attach it if possible, or at
>least that part that seems to be a problem? Mind that the list has a
rather small size limit.
I think this is the pertinent section:
#ifndef HAVE_F
Ravi wrote:
> On Wednesday 08 October 2008 03:39:32 David Cournapeau wrote:
>
>> Note that 1.2.0 does not officially support python 2.6, specially on
>> windows. Because python 2.6 uses a new toolchain (VS 2008 by default
>> instead of 2003), it requires some non trivial changes.
>>
>
> How
Peter wrote:
>
> How about python 2.5 and numpy 1.2 instead? Python 2.6 makes some
> important changes to python 2.5 (in preparation for Python 3.0), so
> you may find several other packages will take a couple of months to
> work 100% with python 2.6 - so check this out if you do plan to use
> mor
On Wed, Oct 8, 2008 at 2:41 PM, Ravi <[EMAIL PROTECTED]> wrote:
> The majority of my colleagues work on Windows and are very resistant to
> toolset changes. Hence, from my perspective, whenever a new project starts, it
> is very important to start with the latest version of any software packages
>
On Wednesday 08 October 2008 03:39:32 David Cournapeau wrote:
> Note that 1.2.0 does not officially support python 2.6, specially on
> windows. Because python 2.6 uses a new toolchain (VS 2008 by default
> instead of 2003), it requires some non trivial changes.
How extensive are these non-trivial
Hi,
I wonder if there's a "behavior bug" in atleast_3d, with respect to
atleast_2d. In atleast_2d, the results on a 1D-array or on a single-element
list of 1D-arrays are the same:
In [22]: atleast_2d(arange(3)).shape
Out[22]: (1, 3)
In [23]: atleast_2d([arange(3),]).shape
Out[23]: (1, 3)
On t
Paul Lucek wrote:
>
> I get the following errors in umathmodule.c.src:
>
>
>
> D:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\BIN\amd64\cl.exe
> /c /nolog
>
> o /Ox /MD /W3 /GS- /DNDEBUG -Ibuild\src.win-amd64-2.6\numpy\core\src
> -Inumpy\cor
>
> e\include -Ibuild\src.win-amd64-2.6\numpy\co
17 matches
Mail list logo
