All,
I just commited some updates on mrecords (numpy.maskedarray branch). Overall,
it's a reorganization/simplification of the code. Regular masked arrays can
already recognize named fields, but the mask works only at the record level
(ie, all the fields of one record are masked). In comparison
Pearu Peterson wrote:
> On Fri, February 1, 2008 8:39 pm, Robert Kern wrote:
>> Pearu Peterson wrote:
>>> On Fri, February 1, 2008 1:28 pm, Andrea Gavana wrote:
Hi All,
I sent a couple of messages to f2py mailing list, but it seems
like my problem has no simple solution so I
On Fri, February 1, 2008 8:39 pm, Robert Kern wrote:
> Pearu Peterson wrote:
>> On Fri, February 1, 2008 1:28 pm, Andrea Gavana wrote:
>>> Hi All,
>>>
>>> I sent a couple of messages to f2py mailing list, but it seems
>>> like my problem has no simple solution so I thought to ask for some
>>> s
Pearu Peterson wrote:
> On Fri, February 1, 2008 1:28 pm, Andrea Gavana wrote:
>> Hi All,
>>
>> I sent a couple of messages to f2py mailing list, but it seems
>> like my problem has no simple solution so I thought to ask for some
>> suggestions here.
>
> Sorry, I haven't been around there long
A Thursday 31 January 2008, Francesc Altet escrigué:
> A Wednesday 30 January 2008, Timothy Hochberg escrigué:
> > [...a fine explanation by Anne and Timothy...]
>
> Ok. As it seems that this subject has interest enough, I went ahead
> and created a small document about views vs copies at:
>
> http
Hi Lars,
[...]
2008/2/1, Lars Friedrich <[EMAIL PROTECTED]>:
>
>
> 1) How can I tell histogramdd to use another dtype than float64? My bins
> will be very little populated so an int16 should be sufficient. Without
> normalization, a Integer dtype makes more sense to me.
There is no way you'll b
On Fri, February 1, 2008 4:18 pm, Andrea Gavana wrote:
> Hi Lisandro,
>
> On Feb 1, 2008 1:59 PM, Lisandro Dalcin wrote:
>> Sorry if I'm making noise, my knowledge of fortran is really little,
>> but in your routine AllocateDummy your are fist allocating and next
>> deallocating the arrays. Are you
On Fri, February 1, 2008 1:28 pm, Andrea Gavana wrote:
> Hi All,
>
> I sent a couple of messages to f2py mailing list, but it seems
> like my problem has no simple solution so I thought to ask for some
> suggestions here.
Sorry, I haven't been around there long time.
> Basically, I read some
Hi Lisandro,
On Feb 1, 2008 1:59 PM, Lisandro Dalcin wrote:
> Sorry if I'm making noise, my knowledge of fortran is really little,
> but in your routine AllocateDummy your are fist allocating and next
> deallocating the arrays. Are you sure you can then access the contents
> of your arrays after d
Sorry if I'm making noise, my knowledge of fortran is really little,
but in your routine AllocateDummy your are fist allocating and next
deallocating the arrays. Are you sure you can then access the contents
of your arrays after deallocating them?
How much complicated is your binary format? For si
Hi All,
I sent a couple of messages to f2py mailing list, but it seems
like my problem has no simple solution so I thought to ask for some
suggestions here.
Basically, I read some huge unformatted binary files which contain
time-step data from a reservoir simulation. I don't know the
dimensio
Hello,
I use numpy.histogramdd to compute three dimensional histograms with a
total number of bins in the order of 1e7. It is clear to me, that such a
histogram will take a lot of memory. For a dtype=N.float64, it will take
roughly 80 megabytes. However, I have the feeling that during the
hist
> Try out latest SVN. It should have this problem fixed.
Thanks for this. I've realized that for my case, using object arrays
is probably best. I still think that long term it would be good to
allow comparison functions to take different types, so that one could
compare say integer arrays with flo
13 matches
Mail list logo