On Thu, Mar 11, 2010 at 3:57 PM, Johann Cohen-Tanugi wrote:
> is your fix committed?
>
>
No. Pauli thinks the problem may lie elsewhere. I haven't had time to look
things over, but it is possible that the changes in the generated api
exposed a bug elsewhere.
Chuck
_
On 11 March 2010 19:30, Tom K. wrote:
>
>
>
> davefallest wrote:
>>
>> ...
>> In [3]: np.arange(1.01, 1.1, 0.01)
>> Out[3]: array([ 1.01, 1.02, 1.03, 1.04, 1.05, 1.06, 1.07, 1.08,
>> 1.09, 1.1 ])
>>
>> Why does the ... np.arange command end up including my stop value?
Don't use arange for
davefallest wrote:
>
> ...
> In [3]: np.arange(1.01, 1.1, 0.01)
> Out[3]: array([ 1.01, 1.02, 1.03, 1.04, 1.05, 1.06, 1.07, 1.08,
> 1.09, 1.1 ])
>
> Why does the ... np.arange command end up including my stop value?
>
>From the help for arange:
For floating point arguments,
Hi Pauli,
On Thu, Mar 11, 2010 at 3:38 PM, Pauli Virtanen wrote:
> Thanks for testing. I wish the test suite was more complete (hint!
> hint! :)
I'll be happy to contribute, but lately I get a few 15-30 minute
blocks a week for this kind of work (hence the short attempt to work
on Quantities thi
is your fix committed?
On 03/11/2010 09:47 PM, Bruce Southey wrote:
On 03/11/2010 02:01 PM, Johann Cohen-Tanugi wrote:
hi there, I am adding this to this thread and not to the trac,
because I am not sure whether it adds noise or a piece of info. I
just downloaded the scipy trunk and built it,
On 03/11/2010 02:01 PM, Johann Cohen-Tanugi wrote:
hi there, I am adding this to this thread and not to the trac, because
I am not sure whether it adds noise or a piece of info. I just
downloaded the scipy trunk and built it, and ran nosetests on it,
which bombed instantly
So I tried to get
Hi Darren,
to, 2010-03-11 kello 11:11 -0500, Darren Dale kirjoitti:
> Now that the trunk has some support for python3, I am working on
> making Quantities work with python3 as well. I'm running into some
> problems related to subclassing ndarray that can be illustrated with a
> simple script, repr
hi there, I am adding this to this thread and not to the trac, because I
am not sure whether it adds noise or a piece of info. I just downloaded
the scipy trunk and built it, and ran nosetests on it, which bombed
instantly
So I tried to get into subdirs to check test scripts separately.
Now that the trunk has some support for python3, I am working on
making Quantities work with python3 as well. I'm running into some
problems related to subclassing ndarray that can be illustrated with a
simple script, reproduced below. It looks like there is a problem with
the reflected operations,
A Thursday 11 March 2010 14:35:49 Gael Varoquaux escrigué:
> > So, in my experience, numpy.memmap is really using that large chunk of
> > memory (unless my testbed is badly programmed, in which case I'd be
> > grateful if you can point out what's wrong).
>
> OK, so what you are saying is that my a
On Thu, Mar 11, 2010 at 02:26:49PM +0100, Francesc Alted wrote:
> > I believe that your above assertion is 'half' right. First I think that
> > it is not SWAP that the memapped file uses, but the original disk space,
> > thus you avoid running out of SWAP. Second, if you open several times the
> >
A Thursday 11 March 2010 10:36:42 Gael Varoquaux escrigué:
> On Thu, Mar 11, 2010 at 10:04:36AM +0100, Francesc Alted wrote:
> > As far as I know, memmap files (or better, the underlying OS) *use* all
> > available RAM for loading data until RAM is exhausted and then start to
> > use SWAP, so the "
On Thu, 11 Mar 2010 13:42:43 +0100
Dag Sverre Seljebotn
wrote:
> Nils Wagner wrote:
>> On Thu, 11 Mar 2010 13:01:33 +0100
>> Dag Sverre Seljebotn
>> wrote:
>>
>>> Nils Wagner wrote:
>>>
On Mon, 22 Feb 2010 22:18:23 +0900
David Cournapeau wrote:
>
Nils Wagner wrote:
> On Thu, 11 Mar 2010 13:01:33 +0100
> Dag Sverre Seljebotn
> wrote:
>
>> Nils Wagner wrote:
>>
>>> On Mon, 22 Feb 2010 22:18:23 +0900
>>> David Cournapeau wrote:
>>>
>>>
On Mon, Feb 22, 2010 at 10:01 PM, Nils Wagner
wrote:
On Thu, 11 Mar 2010 13:01:33 +0100
Dag Sverre Seljebotn
wrote:
> Nils Wagner wrote:
>> On Mon, 22 Feb 2010 22:18:23 +0900
>> David Cournapeau wrote:
>>
>>> On Mon, Feb 22, 2010 at 10:01 PM, Nils Wagner
>>> wrote:
>>>
>>>
ar x test.a
gfortran -shared *.o -o libtest.so -lg2c
Here is a strange thing I am getting with multiprocessing and memory mapped
array:
The below script generates the error message 30 times (for every slice access):
Exception AttributeError: AttributeError("'NoneType' object has no attribute
'tell'",) in ignored
Although I get the correct answ
Nils Wagner wrote:
> On Mon, 22 Feb 2010 22:18:23 +0900
> David Cournapeau wrote:
>
>> On Mon, Feb 22, 2010 at 10:01 PM, Nils Wagner
>> wrote:
>>
>>
>>> ar x test.a
>>> gfortran -shared *.o -o libtest.so -lg2c
>>>
>>> to build a shared library. The additional option -lg2c
>>> was
>>> n
On Mon, 22 Feb 2010 22:18:23 +0900
David Cournapeau wrote:
> On Mon, Feb 22, 2010 at 10:01 PM, Nils Wagner
> wrote:
>
>>
>> ar x test.a
>> gfortran -shared *.o -o libtest.so -lg2c
>>
>> to build a shared library. The additional option -lg2c
>>was
>> necessary due to an undefined symbol: s_cmp
On Thu, Mar 11, 2010 at 10:04:36AM +0100, Francesc Alted wrote:
> As far as I know, memmap files (or better, the underlying OS) *use* all
> available RAM for loading data until RAM is exhausted and then start to use
> SWAP, so the "memory pressure" is still there. But I may be wrong...
I believ
A Sunday 07 March 2010 20:03:21 Gael Varoquaux escrigué:
> On Sun, Mar 07, 2010 at 07:00:03PM +, René Dudfield wrote:
> > 1. Mmap'd files are useful since you can reuse disk cache as program
> > memory. So large files don't waste ram on the disk cache.
>
> I second that. mmaping has worked ve
20 matches
Mail list logo
