Re: [Numpy-discussion] GSoC'15 - mentors & ideas

[Sebastian Berg]

On Do, 2015-02-26 at 07:09 -0800, Jaime Fernández del Río wrote:

> 
> 
> To add one of my own: the old iterator is still being used in many,
> many places throughout the numpy code base. Wouldn't it make sense to
> port those to the new one? In doing so, it would probably lead to
> producing simplified interfaces to the new iterator, e.g. reproducing
> the old PyIter_AllButAxis is infinitely more verbose with the new
> iterator.
> 
> 

Might be a bit off topic. But I used to wonder if it could make sense to
create a Cython code generation support for nditer? NDiter is pretty
powerful, but we often have things like the contiguous special case,
buffering, etc. that is always identical code but without having
something ready in cython nobody will ever use nditer from cython, even
though for some things it might make a lot of sense.

- Sebastian


> 
> ___
> NumPy-Discussion mailing list
> NumPy-Discussion@scipy.org
> http://mail.scipy.org/mailman/listinfo/numpy-discussion



signature.asc
Description: This is a digitally signed message part
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] GSoC'15 - mentors & ideas

[Jaime Fernández del Río]

On Thu, Feb 26, 2015 at 2:54 AM, Todd  wrote:

> I am not able to mentor, but I have some ideas about easier projects.
> These may be too easy, too hard, or not even desirable so take them or
> leave them as you please.
>
> scipy:
>
> Implement a set of circular statistics functions comparable to those in R
> or MATLAB circular statistics toolbox.
>
> Either implement some window functions that only apply to the beginning
> and end of an array, or implement a wrapper that takes a window function
> and some parameters and creates a new window that only applies to the
> beginning and end of an array.
>
> numpy:
>
> Integrate the bottleneck project optimizations into numpy proper.
>
> Not sure how much of the bottleneck optimizations can be fitted into the
ufunc machinery. But I'd be more than happy to mentor or co-mentor an
implementation in numpy of the moving window functions. I have already
contributed some work on some of those in scipy.ndimage and pandas, and
find the subject fascinating.

> Integrate as much as possible the matplotlib.mlab functionality into numpy
> (and, optionally, also scipy).
>
> In many places different approaches to the same task have substantially
> different performance (such as indexing vs. take) and check for one
> approach being substantially slower.  If it is, fix the performance problem
> if possible (perhaps by using the same implementation), and if not document
> the difference.
>
The take performance advantage is no longer there since seberg's rewrite of
indexing. Are there any other obvious examples?

> Modify ufuncs so their documentation appears in help() in addition to
> numpy.info().
>
To add one of my own: the old iterator is still being used in many, many
places throughout the numpy code base. Wouldn't it make sense to port those
to the new one? In doing so, it would probably lead to producing simplified
interfaces to the new iterator, e.g. reproducing the old PyIter_AllButAxis
is infinitely more verbose with the new iterator.



> Hi all,
>
>
> On Fri, Feb 20, 2015 at 10:05 AM, Ralf Gommers 
> wrote:
>
>> Hi all,
>>
>> It's time to start preparing for this year's Google Summer of Code. There
>> is actually one urgent thing to be done (before 19.00 UTC today), which is
>> to get our ideas page in decent shape. It doesn't have to be final, but
>> there has to be enough on there for the organizers to judge it. This page
>> is here: https://github.com/scipy/scipy/wiki/GSoC-project-ideas. I'll be
>> reworking it and linking it from the PSF page today, but if you already
>> have new ideas please add them there. See
>> https://wiki.python.org/moin/SummerOfCode/OrgIdeasPageTemplate for this
>> year's template for adding a new idea.
>>
>
> The ideas page is now in pretty good shape. More ideas are very welcome
> though, especially easy or easy/intermediate ideas. Numpy right now has
> zero easy ones and Scipy only one and a half.
>
> What we also need is mentors. All ideas already have a potential mentor
> listed, however some ideas are from last year and I'm not sure that all
> those mentors really are available this year. And more than one potential
> mentor per idea is always good. So can everyone please add/remove his or
> her name on that page?
>
> I'm happy to take care of most of the organizational aspects this year,
> however I'll be offline for two weeks in July and from the end of August
> onwards, so I'll some help in those periods. Any volunteers?
>
> Thanks,
> Ralf
>
>
>
>
> ___
> NumPy-Discussion mailing list
> NumPy-Discussion@scipy.org
> http://mail.scipy.org/mailman/listinfo/numpy-discussion
>
>
> ___
> NumPy-Discussion mailing list
> NumPy-Discussion@scipy.org
> http://mail.scipy.org/mailman/listinfo/numpy-discussion
>
>


-- 
(\__/)
( O.o)
( > <) Este es Conejo. Copia a Conejo en tu firma y ayúdale en sus planes
de dominación mundial.
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] GSoC'15 - mentors & ideas

[Todd]

I am not able to mentor, but I have some ideas about easier projects.
These may be too easy, too hard, or not even desirable so take them or
leave them as you please.

scipy:

Implement a set of circular statistics functions comparable to those in R
or MATLAB circular statistics toolbox.

Either implement some window functions that only apply to the beginning and
end of an array, or implement a wrapper that takes a window function and
some parameters and creates a new window that only applies to the beginning
and end of an array.

numpy:

Integrate the bottleneck project optimizations into numpy proper.

Integrate as much as possible the matplotlib.mlab functionality into numpy
(and, optionally, also scipy).

In many places different approaches to the same task have substantially
different performance (such as indexing vs. take) and check for one
approach being substantially slower.  If it is, fix the performance problem
if possible (perhaps by using the same implementation), and if not document
the difference.

Modify ufuncs so their documentation appears in help() in addition to
numpy.info().


 Hi all,


On Fri, Feb 20, 2015 at 10:05 AM, Ralf Gommers 
wrote:

> Hi all,
>
> It's time to start preparing for this year's Google Summer of Code. There
> is actually one urgent thing to be done (before 19.00 UTC today), which is
> to get our ideas page in decent shape. It doesn't have to be final, but
> there has to be enough on there for the organizers to judge it. This page
> is here: https://github.com/scipy/scipy/wiki/GSoC-project-ideas. I'll be
> reworking it and linking it from the PSF page today, but if you already
> have new ideas please add them there. See
> https://wiki.python.org/moin/SummerOfCode/OrgIdeasPageTemplate for this
> year's template for adding a new idea.
>

The ideas page is now in pretty good shape. More ideas are very welcome
though, especially easy or easy/intermediate ideas. Numpy right now has
zero easy ones and Scipy only one and a half.

What we also need is mentors. All ideas already have a potential mentor
listed, however some ideas are from last year and I'm not sure that all
those mentors really are available this year. And more than one potential
mentor per idea is always good. So can everyone please add/remove his or
her name on that page?

I'm happy to take care of most of the organizational aspects this year,
however I'll be offline for two weeks in July and from the end of August
onwards, so I'll some help in those periods. Any volunteers?

Thanks,
Ralf




___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] GSoC'15 - mentors & ideas

[Nathaniel Smith]

On Feb 25, 2015 12:10 PM, "Charles R Harris" 
wrote:
>
>
>
> On Wed, Feb 25, 2015 at 11:23 AM, Pauli Virtanen  wrote:
>>
>> 25.02.2015, 19:59, Pauli Virtanen kirjoitti:
>> > 25.02.2015, 07:11, Nathaniel Smith kirjoitti:
>> >> Not sure if this is a full GSoC but it would be good to get the
benchmarks
>> >> into the numpy repository, so we can start asking people who submit
>> >> optimizations to submit new benchmarks as part of the PR (just like
other
>> >> changes require tests).
>> >
>> > This may be relevant in this respect:
>> >
>> > https://github.com/scipy/scipy/pull/4501
>>
>> Ok, I didn't read the thread. The vbench benchmarks seem to not be so
>> many and could probably be ported to asv fairly quickly. The bigger job
>> is in setting up and maintaining a host that runs them periodically.
>> Also, asv doesn't (yet) do branches.
>
>
> I would expect a GSOC student to also write some benchmarks. Anyone have
thoughts/ideas on hosting?

One possibility is Rackspace, who seem keen to hand out ~unlimited amounts
of computing resources to FOSS projects. (I think their default is
$10,000/mo/project worth of VMs/storage/etc.) Of course one has to be a bit
careful running benchmarks on virtual hardware...

-n
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] GSoC'15 - mentors & ideas

[Charles R Harris]

On Wed, Feb 25, 2015 at 11:23 AM, Pauli Virtanen  wrote:

> 25.02.2015, 19:59, Pauli Virtanen kirjoitti:
> > 25.02.2015, 07:11, Nathaniel Smith kirjoitti:
> >> Not sure if this is a full GSoC but it would be good to get the
> benchmarks
> >> into the numpy repository, so we can start asking people who submit
> >> optimizations to submit new benchmarks as part of the PR (just like
> other
> >> changes require tests).
> >
> > This may be relevant in this respect:
> >
> > https://github.com/scipy/scipy/pull/4501
>
> Ok, I didn't read the thread. The vbench benchmarks seem to not be so
> many and could probably be ported to asv fairly quickly. The bigger job
> is in setting up and maintaining a host that runs them periodically.
> Also, asv doesn't (yet) do branches.
>

I would expect a GSOC student to also write some benchmarks. Anyone have
thoughts/ideas on hosting?

Chuck
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] GSoC'15 - mentors & ideas

[Pauli Virtanen]

25.02.2015, 19:59, Pauli Virtanen kirjoitti:
> 25.02.2015, 07:11, Nathaniel Smith kirjoitti:
>> Not sure if this is a full GSoC but it would be good to get the benchmarks
>> into the numpy repository, so we can start asking people who submit
>> optimizations to submit new benchmarks as part of the PR (just like other
>> changes require tests).
> 
> This may be relevant in this respect:
> 
> https://github.com/scipy/scipy/pull/4501

Ok, I didn't read the thread. The vbench benchmarks seem to not be so
many and could probably be ported to asv fairly quickly. The bigger job
is in setting up and maintaining a host that runs them periodically.
Also, asv doesn't (yet) do branches.

Pauli

___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] GSoC'15 - mentors & ideas

[Pauli Virtanen]

25.02.2015, 07:11, Nathaniel Smith kirjoitti:
> Not sure if this is a full GSoC but it would be good to get the benchmarks
> into the numpy repository, so we can start asking people who submit
> optimizations to submit new benchmarks as part of the PR (just like other
> changes require tests).

This may be relevant in this respect:

https://github.com/scipy/scipy/pull/4501

___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] GSoC'15 - mentors & ideas

[Nathaniel Smith]

Not sure if this is a full GSoC but it would be good to get the benchmarks
into the numpy repository, so we can start asking people who submit
optimizations to submit new benchmarks as part of the PR (just like other
changes require tests).
On Feb 24, 2015 10:29 AM, "Charles R Harris" 
wrote:

>
>
> On Tue, Feb 24, 2015 at 10:15 AM, Julian Taylor <
> jtaylor.deb...@googlemail.com> wrote:
>
>> On 02/24/2015 05:41 PM, Charles R Harris wrote:
>> >
>> >
>> > On Mon, Feb 23, 2015 at 11:49 PM, Ralf Gommers > > > wrote:
>> >
>> > Hi all,
>> >
>> >
>> > On Fri, Feb 20, 2015 at 10:05 AM, Ralf Gommers
>> > mailto:ralf.gomm...@gmail.com>> wrote:
>> >
>> > Hi all,
>> >
>> > It's time to start preparing for this year's Google Summer of
>> > Code. There is actually one urgent thing to be done (before
>> > 19.00 UTC today), which is to get our ideas page in decent
>> > shape. It doesn't have to be final, but there has to be enough
>> > on there for the organizers to judge it. This page is here:
>> > https://github.com/scipy/scipy/wiki/GSoC-project-ideas. I'll be
>> > reworking it and linking it from the PSF page today, but if you
>> > already have new ideas please add them there. See
>> > https://wiki.python.org/moin/SummerOfCode/OrgIdeasPageTemplate
>> > for this year's template for adding a new idea.
>> >
>> >
>> > The ideas page is now in pretty good shape. More ideas are very
>> > welcome though, especially easy or easy/intermediate ideas. Numpy
>> > right now has zero easy ones and Scipy only one and a half.
>> >
>> >
>> > We could add a benchmark project for numpy that would build off the work
>> > Pauli is doing in Scipy. That would be easy to intermediate I think, as
>> > the programming bits might be easy, but coming up with the benchmarks
>> > would be more difficult.
>> >
>>
>> we already have decent set of benchmarks in yaroslavs setup:
>> http://yarikoptic.github.io/numpy-vbench/
>>
>
> Are you suggesting that we steal copy those (my thought), or
> that we don't need a project? I note that Pauli is using Air Speed Velocity
> instead of vbench.
>
> Chuck
>
>
> ___
> NumPy-Discussion mailing list
> NumPy-Discussion@scipy.org
> http://mail.scipy.org/mailman/listinfo/numpy-discussion
>
>
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] GSoC'15 - mentors & ideas

[Charles R Harris]

On Tue, Feb 24, 2015 at 10:15 AM, Julian Taylor <
jtaylor.deb...@googlemail.com> wrote:

> On 02/24/2015 05:41 PM, Charles R Harris wrote:
> >
> >
> > On Mon, Feb 23, 2015 at 11:49 PM, Ralf Gommers  > > wrote:
> >
> > Hi all,
> >
> >
> > On Fri, Feb 20, 2015 at 10:05 AM, Ralf Gommers
> > mailto:ralf.gomm...@gmail.com>> wrote:
> >
> > Hi all,
> >
> > It's time to start preparing for this year's Google Summer of
> > Code. There is actually one urgent thing to be done (before
> > 19.00 UTC today), which is to get our ideas page in decent
> > shape. It doesn't have to be final, but there has to be enough
> > on there for the organizers to judge it. This page is here:
> > https://github.com/scipy/scipy/wiki/GSoC-project-ideas. I'll be
> > reworking it and linking it from the PSF page today, but if you
> > already have new ideas please add them there. See
> > https://wiki.python.org/moin/SummerOfCode/OrgIdeasPageTemplate
> > for this year's template for adding a new idea.
> >
> >
> > The ideas page is now in pretty good shape. More ideas are very
> > welcome though, especially easy or easy/intermediate ideas. Numpy
> > right now has zero easy ones and Scipy only one and a half.
> >
> >
> > We could add a benchmark project for numpy that would build off the work
> > Pauli is doing in Scipy. That would be easy to intermediate I think, as
> > the programming bits might be easy, but coming up with the benchmarks
> > would be more difficult.
> >
>
> we already have decent set of benchmarks in yaroslavs setup:
> http://yarikoptic.github.io/numpy-vbench/
>

Are you suggesting that we steal copy those (my thought), or
that we don't need a project? I note that Pauli is using Air Speed Velocity
instead of vbench.

Chuck
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] GSoC'15 - mentors & ideas

[Julian Taylor]

On 02/24/2015 05:41 PM, Charles R Harris wrote:
> 
> 
> On Mon, Feb 23, 2015 at 11:49 PM, Ralf Gommers  > wrote:
> 
> Hi all,
> 
> 
> On Fri, Feb 20, 2015 at 10:05 AM, Ralf Gommers
> mailto:ralf.gomm...@gmail.com>> wrote:
> 
> Hi all,
> 
> It's time to start preparing for this year's Google Summer of
> Code. There is actually one urgent thing to be done (before
> 19.00 UTC today), which is to get our ideas page in decent
> shape. It doesn't have to be final, but there has to be enough
> on there for the organizers to judge it. This page is here:
> https://github.com/scipy/scipy/wiki/GSoC-project-ideas. I'll be
> reworking it and linking it from the PSF page today, but if you
> already have new ideas please add them there. See
> https://wiki.python.org/moin/SummerOfCode/OrgIdeasPageTemplate
> for this year's template for adding a new idea.
> 
> 
> The ideas page is now in pretty good shape. More ideas are very
> welcome though, especially easy or easy/intermediate ideas. Numpy
> right now has zero easy ones and Scipy only one and a half.
> 
> 
> We could add a benchmark project for numpy that would build off the work
> Pauli is doing in Scipy. That would be easy to intermediate I think, as
> the programming bits might be easy, but coming up with the benchmarks
> would be more difficult.
> 

we already have decent set of benchmarks in yaroslavs setup:
http://yarikoptic.github.io/numpy-vbench/

___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] GSoC'15 - mentors & ideas

[Charles R Harris]

On Mon, Feb 23, 2015 at 11:49 PM, Ralf Gommers 
wrote:

> Hi all,
>
>
> On Fri, Feb 20, 2015 at 10:05 AM, Ralf Gommers 
> wrote:
>
>> Hi all,
>>
>> It's time to start preparing for this year's Google Summer of Code. There
>> is actually one urgent thing to be done (before 19.00 UTC today), which is
>> to get our ideas page in decent shape. It doesn't have to be final, but
>> there has to be enough on there for the organizers to judge it. This page
>> is here: https://github.com/scipy/scipy/wiki/GSoC-project-ideas. I'll be
>> reworking it and linking it from the PSF page today, but if you already
>> have new ideas please add them there. See
>> https://wiki.python.org/moin/SummerOfCode/OrgIdeasPageTemplate for this
>> year's template for adding a new idea.
>>
>
> The ideas page is now in pretty good shape. More ideas are very welcome
> though, especially easy or easy/intermediate ideas. Numpy right now has
> zero easy ones and Scipy only one and a half.
>

We could add a benchmark project for numpy that would build off the work
Pauli is doing in Scipy. That would be easy to intermediate I think, as the
programming bits might be easy, but coming up with the benchmarks would be
more difficult.



Chuck
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion