On Thu, Aug 20, 2009 at 1:32 PM, Christopher Hanley wrote:
> Also, I do not know how many people use this particular feature.
> However I would point out that many people who use numpy are not also
> on the mailing lists. Most of the STScI do not follow the numpy
> list. I serve as our point of
Hi, Stefan. Is this editable through the Wiki? I went to the Docstrings page
and searched for "numpydoc" and "tutorial" and got no hits.
DG
--- On Thu, 8/20/09, Stéfan van der Walt wrote:
> From: Stéfan van der Walt
> Subject: Re: [Numpy-discussion] itemsize() doesn't work
> To: "Discussion
tarball from sourceforge.
On Thu, Aug 20, 2009 at 6:33 PM, David Cournapeau wrote:
> On Thu, Aug 20, 2009 at 2:06 PM, Chris Colbert wrote:
>> the issue is that the files are executable. I have no idea why they
>> are set that way either. This is numpy 1.3.0 built from source.
>
> Which sources are
Thanks for the bug report!
DG
--- On Thu, 8/20/09, Dr. Phillip M. Feldman wrote:
> From: Dr. Phillip M. Feldman
> Subject: [Numpy-discussion] itemsize() doesn't work
> To: numpy-discussion@scipy.org
> Date: Thursday, August 20, 2009, 5:46 PM
>
> I've been reading the online NumPy tutorial at
20/08/09 @ 18:00 (-0700), thus spake Dr. Phillip M. Feldman:
> I have a 1-D array and would like to generate a list of indices for which a
> given condition is satisfied. What is the cleanest way to do this?
you can do something like this:
numpy.arange(len(x))[x > 5]
it'll give you the indices
2009/8/20 Dr. Phillip M. Feldman :
>
> I have a 1-D array and would like to generate a list of indices for which a
> given condition is satisfied. What is the cleanest way to do this?
np.where(x > 0)
Stéfan
___
NumPy-Discussion mailing list
NumPy-Discu
On Thu, Aug 20, 2009 at 18:00, Dr. Phillip M.
Feldman wrote:
>
> I have a 1-D array and would like to generate a list of indices for which a
> given condition is satisfied. What is the cleanest way to do this?
numpy.nonzero(condition)[0]
--
Robert Kern
"I have come to believe that the whole wo
2009/8/20 Stéfan van der Walt :
> 2009/8/20 Dr. Phillip M. Feldman :
>>
>> I've been reading the online NumPy tutorial at the following URL:
>>
>> http://numpy.scipy.org/numpydoc/numpy-10.html
>>
>> When I try the following example, I get an error message:
>>
>> In [1]: a=arange(10)
>> In [2]: a.it
I have a 1-D array and would like to generate a list of indices for which a
given condition is satisfied. What is the cleanest way to do this?
--
View this message in context:
http://www.nabble.com/how-to-find-array-indices-at-which-a-condition-is-satisfied--tp25072656p25072656.html
Sent from t
2009/8/20 Dr. Phillip M. Feldman :
>
> I've been reading the online NumPy tutorial at the following URL:
>
> http://numpy.scipy.org/numpydoc/numpy-10.html
>
> When I try the following example, I get an error message:
>
> In [1]: a=arange(10)
> In [2]: a.itemsize()
This is a mistake, and should be
I've been reading the online NumPy tutorial at the following URL:
http://numpy.scipy.org/numpydoc/numpy-10.html
When I try the following example, I get an error message:
In [1]: a=arange(10)
In [2]: a.itemsize()
---
TypeErr
2009/8/20 Christopher Hanley :
> Will the Image Processing Scikit be dedicated to working with a single
> image or stacks of images?
Thanks for the reminder -- I have to add ImageCollection to the set of
features. Fernando started working on something similar in 2006, and
I've implemented a cache
On Thu, Aug 20, 2009 at 5:06 PM, Travis Oliphant wrote:
>
> On Aug 20, 2009, at 2:04 PM, David Cournapeau wrote:
>
>> On Thu, Aug 20, 2009 at 10:32 AM, Christopher
>> Hanley wrote:
>>
>>>
>>> Another concern is that we told people coming from numarray to use
>>> this module. It is my opinion that
On Aug 20, 2009, at 2:04 PM, David Cournapeau wrote:
> On Thu, Aug 20, 2009 at 10:32 AM, Christopher
> Hanley wrote:
>
>>
>> Another concern is that we told people coming from numarray to use
>> this module. It is my opinion that at this point in the numpy
>> release
>> cycle that an API cha
Hi Chris & Stefan,
I will be around for most of the weekend (as I believe will Perry).
I'm not sure I'll be able to contribute a lot to coding, but if
there's any stuff you want to co-ordinate between STScI and Stefan's
scikit, let me know if I can help. That's probably about the most
useful thing
Hi Stefan,
Never mind. I just found the Sprint website and read the
description. I'm sorry I hadn't found this sooner. I would have made
plans to stay and help. My apologizes.
Sorry,
Chris
--
Christopher Hanley
Senior Systems Software Engineer
Space Telescope Science Institute
3700 San
On Aug 20, 2009, at 7:48 PM, Stéfan van der Walt wrote:
Hi Stefan,
> We'll be spriting on an Image Processing Scikit this weekend. If you
> have any functions you'd like to include, let me know.
>
> Regards
> Stéfan
Will the Image Processing Scikit be dedicated to working with a single
image
Hi Chris
2009/8/20 Christopher Hanley :
> That should clean some code up. If someday a generic image processing
> library is added to scipy we can consider incorporating our modules
> back into scipy. Until that time I would rather remove the
> redundancy. It also help scipy's maintainability a
I agree with David's comments. In that theme I have removed
scipy.stsci from scipy. Users get it directly from us at STScI via
STSCI_PYTHON. It doesn't have any documentation in the doc system.
It isn't by default in the scipy namespace. And as a recent bug
report indicates they can't
On Thu, Aug 20, 2009 at 2:06 PM, Chris Colbert wrote:
> the issue is that the files are executable. I have no idea why they
> are set that way either. This is numpy 1.3.0 built from source.
Which sources are you using ? The tarball on sourceforge, from svn, etc... ?
cheers,
David
___
On Thu, Aug 20, 2009 at 14:13, Chris Colbert wrote:
> nope.
>
> I build Atlas, and modified site.cfg to find those libs in
> /usr/local/lib/atlas/
>
> then i did:
>
> python setup.py build
> sudo python setup.py install
>
> that's it.
Huh. I don't know. Are the source files executable?
--
Rober
nope.
I build Atlas, and modified site.cfg to find those libs in /usr/local/lib/atlas/
then i did:
python setup.py build
sudo python setup.py install
that's it.
On Thu, Aug 20, 2009 at 5:09 PM, Robert Kern wrote:
> On Thu, Aug 20, 2009 at 14:06, Chris Colbert wrote:
>> the issue is that the fi
On Thu, Aug 20, 2009 at 14:06, Chris Colbert wrote:
> the issue is that the files are executable. I have no idea why they
> are set that way either. This is numpy 1.3.0 built from source.
Are you sure that those are exactly the commands that you executed?
You didn't invoke setuptools in any way?
this happens with scipy too...
On Thu, Aug 20, 2009 at 5:06 PM, Chris Colbert wrote:
> the issue is that the files are executable. I have no idea why they
> are set that way either. This is numpy 1.3.0 built from source.
>
> the default install location for setup.py install is the local
> dist-pac
the issue is that the files are executable. I have no idea why they
are set that way either. This is numpy 1.3.0 built from source.
the default install location for setup.py install is the local
dist-packages. So that's where it is.
On Thu, Aug 20, 2009 at 5:03 PM, Keith Goodman wrote:
> On Thu
On Thu, Aug 20, 2009 at 1:52 PM, Chris Colbert wrote:
> when I build numpy from source via:
>
> python setup.py build
> sudo python setup.py install
>
>
> the nosetests fail because of permissions:
>
> In [5]: np.test()
> Running unit tests for numpy
> NumPy version 1.3.0
> NumPy is installed in /u
On Thu, Aug 20, 2009 at 13:52, Chris Colbert wrote:
> when I build numpy from source via:
>
> python setup.py build
> sudo python setup.py install
>
>
> the nosetests fail because of permissions:
What permissions do your files have? If they're not readable for
whatever reason, you would be SOL no
when I build numpy from source via:
python setup.py build
sudo python setup.py install
the nosetests fail because of permissions:
In [5]: np.test()
Running unit tests for numpy
NumPy version 1.3.0
NumPy is installed in /usr/local/lib/python2.6/dist-packages/numpy
Python version 2.6.2 (release26
On Thu, Aug 20, 2009 at 10:32 AM, Christopher Hanley wrote:
>
> Another concern is that we told people coming from numarray to use
> this module. It is my opinion that at this point in the numpy release
> cycle that an API change needs a very strong justification. Anecdotes
> about the number of
Here is what I know about the chararray usage at STScI since first
looking into it this morning.
It is used in PyFITS and within the COS instrument calibration code.
I have not heard back from the other projects yet given most of our
developers are away at this time.
It appears that the CO
--- On Thu, 8/20/09, Christopher Hanley wrote:
> I'd like to respectfully request that we move any
> discussion of what
> to do with the numpy.char module to the numpy list.
NP, done.
> I'm a little concerned about some of the assumptions that
> are being
> made about the number of users of
On Thu, Aug 20, 2009 at 09:18, Ralf Gommers wrote:
> [this discussion moved here from the SciPy list]
>
> On Thu, Aug 20, 2009 at 9:50 AM, Christopher Hanley
> wrote:
>>
>> Hi,
>>
>> I'd like to respectfully request that we move any discussion of what
>> to do with the numpy.char module to the num
[this discussion moved here from the SciPy list]
On Thu, Aug 20, 2009 at 9:50 AM, Christopher Hanley wrote:
> Hi,
>
> I'd like to respectfully request that we move any discussion of what
> to do with the numpy.char module to the numpy list.
>
> I'm a little concerned about some of the assumptions
El dj 20 de 08 del 2009 a les 00:37 -0700, en/na Erik Tollerud va
escriure:
> > NumPy arrays on the GPU memory is an easy task. But then I would have to
> > write the computation in OpenCL's dialect of C99? But I'd rather program
> > everything in Python if I could. Details like GPU and OpenCL shou
I realize this topic is a bit old, but I couldn't help but add
something I forgot to mention earlier...
>> I mean, once the computations are moved elsewhere numpy is basically a
>> convenient way to address memory.
>
> That is how I mostly use NumPy, though. Computations I often do in
> Fortran 95
35 matches
Mail list logo
