Hi,
So I have a square 2D array, and I want to fill the array with sine values.
The values need to be generated by their coordinates within the array.
The center of the array should be treated as the angle 90 degrees. Each of
the four edges should be 0 degrees. The corners, therefore, ought to
On Sat, Jul 24, 2010 at 4:14 PM, Martin Galpin wrote:
> Hello,
>
> Given the following example:
>
> import numpy as np
> foo = np.array([], dtype=np.float32)
> print a.dtype
> >> float32
> foo = np.append(foo, 1)
> print foo.dtype
> >> float64
>
> Is this the correct behaviour? I realise that num
On Jul 24, 2010, at 11:39 AM, Benjamin Root wrote:
> I have to wonder why this question keeps coming up. Do we need to make the
> build/installation instructions on the website clearer?
Yes. I was one who asked recently. I've not seen easy_install nor pip
mentioned on the website nor INSTALL
>> Yes, you should be worried. To run the numpy tests you need to install
> nose. That's what your output said:
>
> ImportError: Need nose >= 0.10.0 for tests - see
> http://somethingaboutorange.com/mrl/projects/nose
>
> For h5py, you might want to try the h5py list. Did you remove the
> build di
On Sat, Jul 24, 2010 at 3:39 PM, Jonathan Tu wrote:
>
> On Jul 24, 2010, at 6:21 PM, David Cournapeau wrote:
>
>> On Sun, Jul 25, 2010 at 7:12 AM, Jonathan Tu wrote:
>>
>>>
>>> What does that part do? It turns out that by fixing my library path, numpy
>>> now imports. I assume that my installa
On Jul 24, 2010, at 6:21 PM, David Cournapeau wrote:
> On Sun, Jul 25, 2010 at 7:12 AM, Jonathan Tu wrote:
>
>>
>> What does that part do? It turns out that by fixing my library path, numpy
>> now imports. I assume that my installation of h5py doesn't need to be
>> redone just because I re
On Sun, Jul 25, 2010 at 7:12 AM, Jonathan Tu wrote:
>
> What does that part do? It turns out that by fixing my library path, numpy
> now imports. I assume that my installation of h5py doesn't need to be redone
> just because I reinstalled Numpy?
Actually, you may have to if you installed h5p
On Sat, Jul 24, 2010 at 3:12 PM, Jonathan Tu wrote:
>
> On Jul 24, 2010, at 6:09 PM, David Cournapeau wrote:
>
>> On Sun, Jul 25, 2010 at 7:00 AM, Jonathan Tu wrote:
If you install shared libraries into a directory which is not looked
in by default by ld, you should add it to the LD_LIB
On Jul 24, 2010, at 6:09 PM, David Cournapeau wrote:
> On Sun, Jul 25, 2010 at 7:00 AM, Jonathan Tu wrote:
>>> If you install shared libraries into a directory which is not looked
>>> in by default by ld, you should add it to the LD_LIBRARY_PATH, e.g.:
>>>
>>> LD_LIBRARY_PATH=$HOME/local/lib:$L
On Sun, Jul 25, 2010 at 7:00 AM, Jonathan Tu wrote:
>> If you install shared libraries into a directory which is not looked
>> in by default by ld, you should add it to the LD_LIBRARY_PATH, e.g.:
>>
>> LD_LIBRARY_PATH=$HOME/local/lib:$LD_LIBRARY_PATH python -c "import numpy"
>>
>> David
>
> Ok, th
> If you install shared libraries into a directory which is not looked
> in by default by ld, you should add it to the LD_LIBRARY_PATH, e.g.:
>
> LD_LIBRARY_PATH=$HOME/local/lib:$LD_LIBRARY_PATH python -c "import numpy"
>
> David
Ok, that makes sense to me. I tried to see what the current value
On Sun, Jul 25, 2010 at 6:50 AM, Jonathan Tu wrote:
>
> Also, I recently tried this all again, only doing make shared, and only
> using the list of libraries without "pt." In both cases, when I ran Python
> interactively and tried to load the numpy module, I got the following:
import numpy
On Jul 24, 2010, at 5:46 PM, Jonathan Tu wrote:
>> Here is what I would do for RHEL4:
>> - use python 2.6, not 2.7, because the released numpy does not support 2.7
>> yet.
>> - build atlas 3.8.3 and lapack 3.1.1 by yourself: this is your core
>> issue here. Both lapack and atlas should be built
> Here is what I would do for RHEL4:
> - use python 2.6, not 2.7, because the released numpy does not support 2.7
> yet.
> - build atlas 3.8.3 and lapack 3.1.1 by yourself: this is your core
> issue here. Both lapack and atlas should be built with the -fPIC flag
> on x86_64 arch (modify the make.i
On Sun, Jul 25, 2010 at 6:21 AM, Benjamin Root wrote:
>
> On Sat, Jul 24, 2010 at 2:38 PM, David Cournapeau
> wrote:
>>
>> On Sun, Jul 25, 2010 at 3:39 AM, Benjamin Root wrote:
>>
>> > I have to wonder why this question keeps coming up.
>>
>> In general, because the packaging/build infrastructur
On Sat, Jul 24, 2010 at 2:38 PM, David Cournapeau wrote:
> On Sun, Jul 25, 2010 at 3:39 AM, Benjamin Root wrote:
>
> > I have to wonder why this question keeps coming up.
>
> In general, because the packaging/build infrastructure in python is
> horrible.
>
> However, in this precise case, the iss
On Sun, Jul 25, 2010 at 5:18 AM, Jonathan Tu wrote:
>> It shows you don't use either atlas or even simple lapack. If your
>> install used atlas, the atlas libraries would show up on those .so
>> with ldd,
>>
>> David
>>
>
> Hmm. Ok. What I did for Numpy installation was check out the source code
> It shows you don't use either atlas or even simple lapack. If your
> install used atlas, the atlas libraries would show up on those .so
> with ldd,
>
> David
>
Hmm. Ok. What I did for Numpy installation was check out the source code
using svn. Then I did
python setup.py build
where
On Sun, Jul 25, 2010 at 5:13 AM, David Cournapeau wrote:
> On Sun, Jul 25, 2010 at 5:11 AM, Jonathan Tu wrote:
>>
>> On Jul 24, 2010, at 4:04 PM, Keith Goodman wrote:
>>
>>> On Sat, Jul 24, 2010 at 12:58 PM, David Cournapeau
>>> wrote:
On Sun, Jul 25, 2010 at 4:50 AM, Jonathan Tu wrote:
>
On Sun, Jul 25, 2010 at 5:11 AM, Jonathan Tu wrote:
>
> On Jul 24, 2010, at 4:04 PM, Keith Goodman wrote:
>
>> On Sat, Jul 24, 2010 at 12:58 PM, David Cournapeau
>> wrote:
>>> On Sun, Jul 25, 2010 at 4:50 AM, Jonathan Tu wrote:
>>>
I am unable to find the files lapack_lite.so or _dotblas.s
On Jul 24, 2010, at 4:04 PM, Keith Goodman wrote:
> On Sat, Jul 24, 2010 at 12:58 PM, David Cournapeau wrote:
>> On Sun, Jul 25, 2010 at 4:50 AM, Jonathan Tu wrote:
>>
>>> I am unable to find the files lapack_lite.so or _dotblas.so. I used the
>>> locate command to look for them.
>>
>> If y
On Sat, Jul 24, 2010 at 12:58 PM, David Cournapeau wrote:
> On Sun, Jul 25, 2010 at 4:50 AM, Jonathan Tu wrote:
>
>> I am unable to find the files lapack_lite.so or _dotblas.so. I used the
>> locate command to look for them.
>
> If you just installed numpy, locate won't find them as locate uses
On Sun, Jul 25, 2010 at 4:50 AM, Jonathan Tu wrote:
> I am unable to find the files lapack_lite.so or _dotblas.so. I used the
> locate command to look for them.
If you just installed numpy, locate won't find them as locate uses a
database which is usually updated once in a while.
Depending on
On Sat 24/07/10 3:39 PM , David Cournapeau wrote:
> On Sun, Jul 25, 2010 at 4:23 AM, Jonathan Tu wrote:
> >
> > On Jul 24, 2010, at 3:08 PM, Benjamin Root wrote:
> >
> > On Fri, Jul 23, 2010 at 10:10 AM, Jonathan Tu wrote:
> >>
> >> Hi,
> >> I am trying to install Numpy on a Linux cluster
Hi,
If I create a structured array with vector columns:
>>> array = np.array(zip([[1,2],[1,2],[1,3]]),dtype=[('a',float,2)])
then examine the type of the column, I get:
>>> array.dtype[0]
dtype(('float64',(2,)))
Then, if I try and view the numerical type, I see:
>>> array.dtype[0].type
I ha
On Sun, Jul 25, 2010 at 4:23 AM, Jonathan Tu wrote:
>
> On Jul 24, 2010, at 3:08 PM, Benjamin Root wrote:
>
> On Fri, Jul 23, 2010 at 10:10 AM, Jonathan Tu wrote:
>>
>> Hi,
>> I am trying to install Numpy on a Linux cluster running RHEL4. I
>> installed a local copy of Python 2.7 because RHEL4 u
On Sun, Jul 25, 2010 at 3:39 AM, Benjamin Root wrote:
> I have to wonder why this question keeps coming up.
In general, because the packaging/build infrastructure in python is horrible.
However, in this precise case, the issue is simply that numpy 1.4.1
does not support python2.7.
cheers,
Dav
On Jul 24, 2010, at 3:08 PM, Benjamin Root wrote:
> On Fri, Jul 23, 2010 at 10:10 AM, Jonathan Tu wrote:
> Hi,
>
> I am trying to install Numpy on a Linux cluster running RHEL4. I installed a
> local copy of Python 2.7 because RHEL4 uses Python 2.3.4 for various internal
> functionalities.
On Fri, Jul 23, 2010 at 10:10 AM, Jonathan Tu wrote:
> Hi,
>
> I am trying to install Numpy on a Linux cluster running RHEL4. I installed
> a local copy of Python 2.7 because RHEL4 uses Python 2.3.4 for various
> internal functionalities. I downloaded the Numpy source code using
>
> svn co http
On Sat, Jul 24, 2010 at 1:44 AM, Ralf Gommers
wrote:
>
>
> On Fri, Jul 23, 2010 at 11:46 AM, celil wrote:
>
>> Hello,
>>
>> I just installed numpy on Snow Leopard using pip. However, running the
>> tests results in a segmentation fault. Has anybody else encountered this
>> problem? How did you so
Hi Mark,
On Mon, Jul 19, 2010 at 11:49 AM, Mark Bakker wrote:
> Thanks for fixing this, Pearu.
> Complex arrays with intent(inout) don't seem to work either.
> They compile, but a problem occurs when calling the routine.
What problem?
> Did you fix that as well?
I guess so, see below.
> Here'
Sat, 24 Jul 2010 18:22:33 +0800, Ralf Gommers wrote:
> There is a bug report asking for the example files under doc/cython,
> doc/swig etc. to be included in the released binaries. This thread,
> http://thread.gmane.org/gmane.comp.python.numeric.general/26913/
focus=26917,
> seems to indicate the d
Hi all,
There is a bug report asking for the example files under doc/cython,
doc/swig etc. to be included in the released binaries. This thread,
http://thread.gmane.org/gmane.comp.python.numeric.general/26913/focus=26917,
seems to indicate the docs should still be integrated in the main
documentat
33 matches
Mail list logo
