I am trying to replace an old code (biliteral filter) that rely on
ndimage.generic_filter with the neighborhood iterator. In the old code, the
generic_filter generates a contiguous copy of the neighborhood, thus the
(cython) code could use C loop to iterate over the neighbourhood copy. In the
n
On Sun, Oct 23, 2011 at 8:07 PM, Eric Firing wrote:
> On 10/23/2011 12:34 PM, Nathaniel Smith wrote:
>
>> like. And in this case I do think we can come up with an API that will
>> make everyone happy, but that Mark's current API probably can't be
>> incrementally evolved to become that API.)
>>
>
On 10/23/2011 12:34 PM, Nathaniel Smith wrote:
> like. And in this case I do think we can come up with an API that will
> make everyone happy, but that Mark's current API probably can't be
> incrementally evolved to become that API.)
>
No one could object to coming up with an API that makes every
On Sun, Oct 23, 2011 at 2:29 PM, Eric Firing wrote:
> Ultimately, though, the numpy core developers must decide what goes in
> and what does not. Consensus is desirable but may not always be
> possible or optimal, especially if "consensus" is interpreted as
> "unanimity". There is a risk in deci
On Sun, Oct 23, 2011 at 3:28 PM, Benjamin Root wrote:
>
>
> On Sunday, October 23, 2011, Nathaniel Smith wrote:
> > On Sun, Oct 23, 2011 at 12:53 PM, Charles R Harris
> > wrote:
> >> On Sun, Oct 23, 2011 at 12:54 PM, Matthew Brett <
> matthew.br...@gmail.com>
> >> wrote:
> >>> I think this emai
On 10/23/2011 10:49 AM, Nathaniel Smith wrote:
> But I (and presumably others) were unaware of the pull request,
> because it turns out that actually Mark did*not* point to the pull
> request, at least in email to either me or numpy-discussion. As far as
> I can tell, the first time that pull requ
On Sunday, October 23, 2011, Nathaniel Smith wrote:
> On Sun, Oct 23, 2011 at 12:53 PM, Charles R Harris
> wrote:
>> On Sun, Oct 23, 2011 at 12:54 PM, Matthew Brett
>> wrote:
>>> I think this email might be a plea to the numpy steering group, and to
>>> Travis in particular, to see if we can use
On Sun, Oct 23, 2011 at 12:53 PM, Charles R Harris
wrote:
> On Sun, Oct 23, 2011 at 12:54 PM, Matthew Brett
> wrote:
>> I think this email might be a plea to the numpy steering group, and to
>> Travis in particular, to see if we can use a discussion of this series
>> of events to decide on a good
On 10/23/2011 04:07 PM, Robert Kern wrote:
> On Sun, Oct 23, 2011 at 20:58, Matthew Brett wrote:
>> Hi,
>>
>> On Sun, Oct 23, 2011 at 12:53 PM, Charles R Harris
>> wrote:
>>>
>>>
>>> On Sun, Oct 23, 2011 at 12:54 PM, Matthew Brett
>>> wrote:
Hi,
On Sun, Oct 23, 2011 at 11:21
Hi,
On Sun, Oct 23, 2011 at 1:07 PM, Robert Kern wrote:
> On Sun, Oct 23, 2011 at 20:58, Matthew Brett wrote:
>> Hi,
>>
>> On Sun, Oct 23, 2011 at 12:53 PM, Charles R Harris
>> wrote:
>>>
>>>
>>> On Sun, Oct 23, 2011 at 12:54 PM, Matthew Brett
>>> wrote:
Hi,
On Sun, Oct 23,
On Sun, Oct 23, 2011 at 20:58, Matthew Brett wrote:
> Hi,
>
> On Sun, Oct 23, 2011 at 12:53 PM, Charles R Harris
> wrote:
>>
>>
>> On Sun, Oct 23, 2011 at 12:54 PM, Matthew Brett
>> wrote:
>>>
>>> Hi,
>>>
>>> On Sun, Oct 23, 2011 at 11:21 AM, Nathaniel Smith wrote:
>>> > Hi all,
>>> >
>>> > I w
On Sun, Oct 23, 2011 at 12:21 PM, Nathaniel Smith wrote:
> Hi all,
>
> I was surprised today to notice that Mark's NA mask support appears to
> have been merged into numpy master and is described in the draft
> release notes[1]. My surprise is because merging it to mainline
> without any discussi
Hi,
On Sun, Oct 23, 2011 at 12:53 PM, Charles R Harris
wrote:
>
>
> On Sun, Oct 23, 2011 at 12:54 PM, Matthew Brett
> wrote:
>>
>> Hi,
>>
>> On Sun, Oct 23, 2011 at 11:21 AM, Nathaniel Smith wrote:
>> > Hi all,
>> >
>> > I was surprised today to notice that Mark's NA mask support appears to
>>
On Sun, Oct 23, 2011 at 12:54 PM, Matthew Brett wrote:
> Hi,
>
> On Sun, Oct 23, 2011 at 11:21 AM, Nathaniel Smith wrote:
> > Hi all,
> >
> > I was surprised today to notice that Mark's NA mask support appears to
> > have been merged into numpy master and is described in the draft
> > release not
Hi,
On Sun, Oct 23, 2011 at 11:21 AM, Nathaniel Smith wrote:
> Hi all,
>
> I was surprised today to notice that Mark's NA mask support appears to
> have been merged into numpy master and is described in the draft
> release notes[1]. My surprise is because merging it to mainline
> without any disc
23.10.2011 20:21, Nathaniel Smith kirjoitti:
> I was surprised today to notice that Mark's NA mask support appears to
> have been merged into numpy master and is described in the draft
> release notes[1]. My surprise is because merging it to mainline
> without any discussion on the list seems to co
Hi all,
I was surprised today to notice that Mark's NA mask support appears to
have been merged into numpy master and is described in the draft
release notes[1]. My surprise is because merging it to mainline
without any discussion on the list seems to contradict what what
Travis wrote in July, tha
I coded a bilateral filter class in cython based on numpy's neighborhood
iterator (thanks to T. J's code example). I tried to parallel the code by
replacing the standard loop (commented line 150) by a prange loop (line 151).
The result are series of compilation errors mainly due the the use of
Hi,
i changed site.cfg :
site.cfg
[MKL}
mkl_libs = mkl_def, mkl_intel_lp64, mkl_intel_thread, mkl_core, mkl_mc
lapack_libs = mkl_lapack95_lp64, mkl_lapack, mkl_scalapack_ilp64,
mkl_scalapack_lp64
#lapack_libs
=mkl_lapack,mkl_scalapack_ilp64,mkl_scalapack_lp64,mkl_lapack95_lp64
library_
Hi,
libmkl_lapack.so is added in site.cfg and now the matrix function is not
giving an error, but numpy.test hangs.
On Sun, Oct 23, 2011 at 11:24 AM, akshar bhosale
wrote:
> i am getting following error.
>python -c 'import numpy;numpy.matrix([[1, 5, 10], [1.0, 3j, 4]],
>numpy.complex128
20 matches
Mail list logo
