Hi,
On Sun, Mar 4, 2012 at 8:32 PM, Mark Wiebe wrote:
> On Sun, Mar 4, 2012 at 10:08 PM, Matthew Brett
> wrote:
>>
>> Hi,
>>
>> On Sun, Mar 4, 2012 at 11:41 AM, Mark Wiebe wrote:
>> > On Sun, Mar 4, 2012 at 11:27 AM, Matthew Brett
>> > wrote:
>> >>
>> >> Hi,
>> >>
>> >> On Sat, Mar 3, 2012 at
On Sun, Mar 4, 2012 at 10:08 PM, Matthew Brett wrote:
> Hi,
>
> On Sun, Mar 4, 2012 at 11:41 AM, Mark Wiebe wrote:
> > On Sun, Mar 4, 2012 at 11:27 AM, Matthew Brett
> > wrote:
> >>
> >> Hi,
> >>
> >> On Sat, Mar 3, 2012 at 12:07 AM, Matthew Brett >
> >> wrote:
> >> > Hi,
> >> >
> >> > On Fri,
Hi,
On Sun, Mar 4, 2012 at 11:41 AM, Mark Wiebe wrote:
> On Sun, Mar 4, 2012 at 11:27 AM, Matthew Brett
> wrote:
>>
>> Hi,
>>
>> On Sat, Mar 3, 2012 at 12:07 AM, Matthew Brett
>> wrote:
>> > Hi,
>> >
>> > On Fri, Mar 2, 2012 at 9:05 PM, Charles R Harris
>> > wrote:
>> >>
>> >>
>> >> On Fri, Ma
On 3/4/12 3:18 PM, Luis Pedro Coelho wrote:
> On Saturday, March 03, 2012 04:38:53 PM David Cournapeau wrote:
>> I don't think the code is comparable either - some of the stuff done
>> in the C code is done in the C++ code your are calling. The C code
>> could be significantly improved.
> Actually,
On Saturday, March 03, 2012 04:38:53 PM David Cournapeau wrote:
> I don't think the code is comparable either - some of the stuff done
> in the C code is done in the C++ code your are calling. The C code
> could be significantly improved.
Actually, that's not 100% accurate. The C code calls the sa
On Sat, Feb 18, 2012 at 10:13 AM, Ralf Gommers
wrote:
>
>
> 2012/2/17 Stéfan van der Walt
>
>> Hi Ralf
>>
>> On Thu, Feb 16, 2012 at 11:05 AM, Ralf Gommers
>> wrote:
>> > Last week we merged https://github.com/numpy/numpy/pull/201, which
>> causes
>> > DeprecationWarning's and RuntimeWarning's t
On Sun, Mar 4, 2012 at 12:27 PM, Matthew Brett wrote:
> Hi,
>
> On Sat, Mar 3, 2012 at 12:07 AM, Matthew Brett
> wrote:
> > Hi,
> >
> > On Fri, Mar 2, 2012 at 9:05 PM, Charles R Harris
> > wrote:
> >>
> >>
> >> On Fri, Mar 2, 2012 at 4:36 PM, Matthew Brett
> >> wrote:
> >>>
> >>> Hi,
> >>>
> >>
On Sun, Mar 4, 2012 at 11:27 AM, Matthew Brett wrote:
> Hi,
>
> On Sat, Mar 3, 2012 at 12:07 AM, Matthew Brett
> wrote:
> > Hi,
> >
> > On Fri, Mar 2, 2012 at 9:05 PM, Charles R Harris
> > wrote:
> >>
> >>
> >> On Fri, Mar 2, 2012 at 4:36 PM, Matthew Brett
> >> wrote:
> >>>
> >>> Hi,
> >>>
> >>
Hi,
On Sat, Mar 3, 2012 at 12:07 AM, Matthew Brett wrote:
> Hi,
>
> On Fri, Mar 2, 2012 at 9:05 PM, Charles R Harris
> wrote:
>>
>>
>> On Fri, Mar 2, 2012 at 4:36 PM, Matthew Brett
>> wrote:
>>>
>>> Hi,
>>>
>>> Sorry that this report is not complete, I don't have full access to
>>> this box but
Should work with:
b = numpy.ma.masked_array(b, mask=a.mask)
-=- Olivier
Le 4 mars 2012 13:01, Chao YUE a écrit :
> Dear all,
>
> I have a matrix with dimension of (360,720) but with all global data.
> I have another land-sea mask matrix with only 2 unique values in it
> (land=1, sea=-1).
> So I
Dear all,
I have a matrix with dimension of (360,720) but with all global data.
I have another land-sea mask matrix with only 2 unique values in it
(land=1, sea=-1).
So I can easily create transform the second array to a masked array.
the problem is, how can I quickly transform the first one to a
On Sat, Mar 03, 2012 at 04:38:53PM -0800, David Cournapeau wrote:
> This is really the kind of code that should be done in cython, as it is
> mostly about wrapping C code into the python C API.
+1
Gael
___
NumPy-Discussion mailing list
NumPy-Discussion@
12 matches
Mail list logo