[Numpy-discussion] GSoC?

[Chris Barker]

ANyone interested in Google Summer of Code this year?

I think the real challenge is having folks with the time to really put into
mentoring, but if folks want to do it -- numpy could really benefit.

Maybe as a python.org sub-project?

https://wiki.python.org/moin/SummerOfCode/2016

Deadlines are approaching -- so I thought I'd ping the list and see if
folks are interested.

-Chris
--
Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R [phone] voice
7600 Sand Point Way NE [phone] fax
Seattle, WA 98115 [phone] main reception

***@noaa.gov

[SMRUTI RANJAN SAHOO]

sir actually i am interested very much . so can you help me about this or
suggest some , so that i can contribute .




Thanks & Regards,
Smruti Ranjan Sahoo

Post by Chris Barker
ANyone interested in Google Summer of Code this year?
I think the real challenge is having folks with the time to really put
into mentoring, but if folks want to do it -- numpy could really benefit.
Maybe as a python.org sub-project?
https://wiki.python.org/moin/SummerOfCode/2016
Deadlines are approaching -- so I thought I'd ping the list and see if
folks are interested.
-Chris
--
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R [phone] voice
7600 Sand Point Way NE [phone] fax
Seattle, WA 98115 [phone] main reception
_______________________________________________
NumPy-Discussion mailing list
https://mail.scipy.org/mailman/listinfo/numpy-discussion

[Chris Barker]

As you can see in the timeline:

https://developers.google.com/open-source/gsoc/timeline

We are now in the stage where mentoring organizations are getting their act
together. So the question now is -- are there folks that want to mentor for
numpy projects? It can be rewarding, but it's a pretty big commitment as
well, and, I suppose depending on the project, would require some good
knowledge of the innards of numpy -- there are not a lot of those folks out
there that have that background.

So to students, I suggest you keep an eye out, and engage a little later on
in the process.

That being said, if you have a idea for a numpy improvement you'd like to
work on , by all means propose it and maybe you'll get a mentor or two
excited.

-CHB

Post by SMRUTI RANJAN SAHOO
sir actually i am interested very much . so can you help me about this or
suggest some , so that i can contribute .
Thanks & Regards,
Smruti Ranjan Sahoo

Post by Chris Barker
ANyone interested in Google Summer of Code this year?
I think the real challenge is having folks with the time to really put
into mentoring, but if folks want to do it -- numpy could really benefit.
Maybe as a python.org sub-project?
https://wiki.python.org/moin/SummerOfCode/2016
Deadlines are approaching -- so I thought I'd ping the list and see if
folks are interested.
-Chris
--
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R [phone] voice
7600 Sand Point Way NE [phone] fax
Seattle, WA 98115 [phone] main reception
_______________________________________________
NumPy-Discussion mailing list
https://mail.scipy.org/mailman/listinfo/numpy-discussion

_______________________________________________
NumPy-Discussion mailing list
https://mail.scipy.org/mailman/listinfo/numpy-discussion

--
Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R [phone] voice
7600 Sand Point Way NE [phone] fax
Seattle, WA 98115 [phone] main reception

***@noaa.gov

[Elliot Hallmark]

Is there a clean way of importing existing C code as a vectorized numpy
func? Like, it would be awesome to use gdal in a vectorized way just with
ctypes or something.

Just something I've dreamed of that I thought I'd ask about in regards to
the GSoC.

Elliot

Post by Chris Barker
https://developers.google.com/open-source/gsoc/timeline
We are now in the stage where mentoring organizations are getting their
act together. So the question now is -- are there folks that want to mentor
for numpy projects? It can be rewarding, but it's a pretty big commitment
as well, and, I suppose depending on the project, would require some good
knowledge of the innards of numpy -- there are not a lot of those folks out
there that have that background.
So to students, I suggest you keep an eye out, and engage a little later
on in the process.
That being said, if you have a idea for a numpy improvement you'd like to
work on , by all means propose it and maybe you'll get a mentor or two
excited.
-CHB

Post by SMRUTI RANJAN SAHOO
sir actually i am interested very much . so can you help me about this
or suggest some , so that i can contribute .
Thanks & Regards,
Smruti Ranjan Sahoo

Post by Chris Barker
ANyone interested in Google Summer of Code this year?
I think the real challenge is having folks with the time to really put
into mentoring, but if folks want to do it -- numpy could really benefit.
Maybe as a python.org sub-project?
https://wiki.python.org/moin/SummerOfCode/2016
Deadlines are approaching -- so I thought I'd ping the list and see if
folks are interested.
-Chris
--
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R [phone] voice
7600 Sand Point Way NE [phone] fax
Seattle, WA 98115 [phone] main reception
_______________________________________________
NumPy-Discussion mailing list
https://mail.scipy.org/mailman/listinfo/numpy-discussion

_______________________________________________
NumPy-Discussion mailing list
https://mail.scipy.org/mailman/listinfo/numpy-discussion

--
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R [phone] voice
7600 Sand Point Way NE [phone] fax
Seattle, WA 98115 [phone] main reception
_______________________________________________
NumPy-Discussion mailing list
https://mail.scipy.org/mailman/listinfo/numpy-discussion

[Ralf Gommers]

Post by Chris Barker
https://developers.google.com/open-source/gsoc/timeline
We are now in the stage where mentoring organizations are getting their
act together. So the question now is -- are there folks that want to mentor
for numpy projects? It can be rewarding, but it's a pretty big commitment
as well, and, I suppose depending on the project, would require some good
knowledge of the innards of numpy -- there are not a lot of those folks out
there that have that background.

Note that we have always done a combined numpy/scipy ideas page and
submission. For really good students numpy may be the right challenge, but
in general scipy is easier to get started on. So we have difficult project
ideas for both, but easy/intermediate ones will most likely be for scipy.

Post by Chris Barker
So to students, I suggest you keep an eye out, and engage a little later
on in the process.
That being said, if you have a idea for a numpy improvement you'd like to
work on , by all means propose it and maybe you'll get a mentor or two
excited.
-CHB

Post by SMRUTI RANJAN SAHOO
sir actually i am interested very much . so can you help me about this
or suggest some , so that i can contribute .

Hi Smruti, I suggest you look at the numpy or scipy issues on Github, and
start with one labeled "easy-fix".

Post by Chris Barker

Post by SMRUTI RANJAN SAHOO
Thanks & Regards,
Smruti Ranjan Sahoo

Post by Chris Barker
I think the real challenge is having folks with the time to really put
into mentoring, but if folks want to do it -- numpy could really benefit.
Maybe as a python.org sub-project?

Under the PSF umbrella has always worked very well, both in terms of
communication quality and of getting the amount of slots we wanted, so yes.

Post by Chris Barker

Post by SMRUTI RANJAN SAHOO

Post by Chris Barker
https://wiki.python.org/moin/SummerOfCode/2016
Deadlines are approaching -- so I thought I'd ping the list and see if
folks are interested.
ANyone interested in Google Summer of Code this year?

Yes, last year we had quite a productive GSoC, so I had planned to organize
it along the same lines again (with an updated ideas page of course).

Are you maybe interested in co-organizing or mentoring Chris? Updating the
ideas page, proposal reviewing and interviewing students via video calls
can be time-consuming, and mentoring definitely is, so the more the merrier.

Cheers,
Ralf

[Chris Barker]

Thanks Ralf,

Note that we have always done a combined numpy/scipy ideas page and

Post by Ralf Gommers
submission. For really good students numpy may be the right challenge, but
in general scipy is easier to get started on.

yup -- good idea. Is there a page ready to go, or do we need to get one up?
(I don't even know where to put it...)

Post by Ralf Gommers
Under the PSF umbrella has always worked very well, both in terms of
communication quality and of getting the amount of slots we wanted, so yes.

hmm, looking here:

https://wiki.python.org/moin/SummerOfCode/2016#Sub-orgs

it seems it's time to get started. and I _think_ our ideas page can go on
that Wiki.

Post by Ralf Gommers
Are you maybe interested in co-organizing or mentoring Chris? Updating the
ideas page, proposal reviewing and interviewing students via video calls
can be time-consuming, and mentoring definitely is, so the more the merrier.

I would love to help -- though I don't think I can commit to being a
full-on mentor.

If we get a couple people to agree to mentor, then we can get ourselves
setup up with the PSF.

-Chris
--
Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R [phone] voice
7600 Sand Point Way NE [phone] fax
Seattle, WA 98115 [phone] main reception

***@noaa.gov

[Ralf Gommers]

Post by Chris Barker
Thanks Ralf,
Note that we have always done a combined numpy/scipy ideas page and

Post by Ralf Gommers
submission. For really good students numpy may be the right challenge, but
in general scipy is easier to get started on.

yup -- good idea. Is there a page ready to go, or do we need to get one
up? (I don't even know where to put it...)

This is last year's page:
https://github.com/scipy/scipy/wiki/GSoC-2015-project-ideas

Some ideas have been worked on, others are still relevant. Let's copy this
page to -2016- and start editing it and adding new ideas. I'll start right
now actually.

Post by Chris Barker

Post by Ralf Gommers
Under the PSF umbrella has always worked very well, both in terms of
communication quality and of getting the amount of slots we wanted, so yes.

https://wiki.python.org/moin/SummerOfCode/2016#Sub-orgs
it seems it's time to get started. and I _think_ our ideas page can go on
that Wiki.

Post by Ralf Gommers
Are you maybe interested in co-organizing or mentoring Chris? Updating
the ideas page, proposal reviewing and interviewing students via video
calls can be time-consuming, and mentoring definitely is, so the more the
merrier.

I would love to help -- though I don't think I can commit to being a
full-on mentor.
If we get a couple people to agree to mentor,

That's always the tricky part. We normally let people indicate whether
they're interested in mentoring for specific project ideas on the ideas
page.

Post by Chris Barker
then we can get ourselves setup up with the PSF.
<https://mail.scipy.org/mailman/listinfo/numpy-discussion>

That's the easiest part, takes one email and one wiki page edit:)

Ralf

[Ralf Gommers]

Post by Ralf Gommers

Post by Chris Barker
Thanks Ralf,
Note that we have always done a combined numpy/scipy ideas page and

Post by Ralf Gommers
submission. For really good students numpy may be the right challenge, but
in general scipy is easier to get started on.

yup -- good idea. Is there a page ready to go, or do we need to get one
up? (I don't even know where to put it...)

https://github.com/scipy/scipy/wiki/GSoC-2015-project-ideas
Some ideas have been worked on, others are still relevant. Let's copy this
page to -2016- and start editing it and adding new ideas. I'll start right
now actually.

OK first version:
https://github.com/scipy/scipy/wiki/GSoC-2016-project-ideas
I kept some of the ideas from last year, but removed all potential mentors
as the same people may not be available this year - please re-add
yourselves where needed.

And to everyone who has a good idea, and preferably is willing to mentor
for that idea: please add it to that page.

Ralf

Post by Ralf Gommers

Post by Chris Barker

Post by Ralf Gommers
Under the PSF umbrella has always worked very well, both in terms of
communication quality and of getting the amount of slots we wanted, so yes.

https://wiki.python.org/moin/SummerOfCode/2016#Sub-orgs
it seems it's time to get started. and I _think_ our ideas page can go on
that Wiki.

Post by Ralf Gommers
Are you maybe interested in co-organizing or mentoring Chris? Updating
the ideas page, proposal reviewing and interviewing students via video
calls can be time-consuming, and mentoring definitely is, so the more the
merrier.

I would love to help -- though I don't think I can commit to being a
full-on mentor.
If we get a couple people to agree to mentor,

That's always the tricky part. We normally let people indicate whether
they're interested in mentoring for specific project ideas on the ideas
page.

Post by Chris Barker
then we can get ourselves setup up with the PSF.
<https://mail.scipy.org/mailman/listinfo/numpy-discussion>

That's the easiest part, takes one email and one wiki page edit:)
Ralf

[Stephan Hoyer]

Post by Ralf Gommers
https://github.com/scipy/scipy/wiki/GSoC-2016-project-ideas
I kept some of the ideas from last year, but removed all potential mentors
as the same people may not be available this year - please re-add
yourselves where needed.
And to everyone who has a good idea, and preferably is willing to mentor
for that idea: please add it to that page.
Ralf

I removed the "Improve Numpy datetime functionality" project, since the
relevant improvements have mostly already made it into NumPy 1.11.

We might consider adding "improve duck typing for numpy arrays" if any GSOC
students are true masochists ;). I could potentially be a mentor for this
one, though of course Nathaniel is the obvious choice.

Stephan

[Chris Barker]

Post by Stephan Hoyer
We might consider adding "improve duck typing for numpy arrays"

care to elaborate on that one?

I know it come up on here that it would be good to have some code in numpy
itself that made it easier to make array-like objects (I.e. do indexing the
same way) Is that what you mean?

-CHB
--
Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R [phone] voice
7600 Sand Point Way NE [phone] fax
Seattle, WA 98115 [phone] main reception

***@noaa.gov

[Stephan Hoyer]

Post by Stephan Hoyer
We might consider adding "improve duck typing for numpy arrays"
care to elaborate on that one?
I know it come up on here that it would be good to have some code in numpy
itself that made it easier to make array-like objects (I.e. do indexing the
same way) Is that what you mean?

I was thinking particularly of improving the compatibility of numpy
functions (e.g., concatenate) with non-numpy array-like objects, but now
that you mention it utilities to make it easier to make array-like objects
could also be a good thing.

In any case, I've now elaborated on my thought into a full project idea on
the Wiki:
https://github.com/scipy/scipy/wiki/GSoC-2016-project-ideas#improved-duck-typing-support-for-n-dimensional-arrays

Arguably, this might be too difficult for most GSoC students -- the API
design questions here are quite contentious. But given that "Pythonic
dtypes" is up there as a GSoC proposal still it's in good company.

Cheers,
Stephan

[Bryan Van de Ven]

[This is a complete tangent, and so I apologize in advance.]

We are considering applying to GSOC for Bokeh. However, I have zero experience with GSOC, but non-zero questions (e.g. go it alone, vs apply through PSF... I think?) If anyone with experience from the mentoring organization side of things wouldn't mind a quick chat (or a few emails) to answer questions, share your experience, or offer advice, please drop me a line directly.

Thanks,

Bryan

Post by Stephan Hoyer
We might consider adding "improve duck typing for numpy arrays"
care to elaborate on that one?
I know it come up on here that it would be good to have some code in numpy itself that made it easier to make array-like objects (I.e. do indexing the same way) Is that what you mean?
I was thinking particularly of improving the compatibility of numpy functions (e.g., concatenate) with non-numpy array-like objects, but now that you mention it utilities to make it easier to make array-like objects could also be a good thing.
https://github.com/scipy/scipy/wiki/GSoC-2016-project-ideas#improved-duck-typing-support-for-n-dimensional-arrays
Arguably, this might be too difficult for most GSoC students -- the API design questions here are quite contentious. But given that "Pythonic dtypes" is up there as a GSoC proposal still it's in good company.
Cheers,
Stephan
_______________________________________________
NumPy-Discussion mailing list
https://mail.scipy.org/mailman/listinfo/numpy-discussion

[Chris Barker]

Apparetnly, NumFocus is applyign to be a GSoC Umbrella org as well:

https://github.com/numfocus/gsoc

Not sure why one might choose NumFocus vs PSF...

-Chris

Post by Bryan Van de Ven
[This is a complete tangent, and so I apologize in advance.]
We are considering applying to GSOC for Bokeh. However, I have zero
experience with GSOC, but non-zero questions (e.g. go it alone, vs apply
through PSF... I think?) If anyone with experience from the mentoring
organization side of things wouldn't mind a quick chat (or a few emails) to
answer questions, share your experience, or offer advice, please drop me a
line directly.
Thanks,
Bryan

Post by Stephan Hoyer
We might consider adding "improve duck typing for numpy arrays"
care to elaborate on that one?
I know it come up on here that it would be good to have some code in

numpy itself that made it easier to make array-like objects (I.e. do
indexing the same way) Is that what you mean?

Post by Stephan Hoyer
I was thinking particularly of improving the compatibility of numpy

functions (e.g., concatenate) with non-numpy array-like objects, but now
that you mention it utilities to make it easier to make array-like objects
could also be a good thing.

Post by Stephan Hoyer
In any case, I've now elaborated on my thought into a full project idea

https://github.com/scipy/scipy/wiki/GSoC-2016-project-ideas#improved-duck-typing-support-for-n-dimensional-arrays

Post by Stephan Hoyer
Arguably, this might be too difficult for most GSoC students -- the API

design questions here are quite contentious. But given that "Pythonic
dtypes" is up there as a GSoC proposal still it's in good company.

Post by Stephan Hoyer
Cheers,
Stephan
_______________________________________________
NumPy-Discussion mailing list
https://mail.scipy.org/mailman/listinfo/numpy-discussion

_______________________________________________
NumPy-Discussion mailing list
https://mail.scipy.org/mailman/listinfo/numpy-discussion

--
Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R [phone] voice
7600 Sand Point Way NE [phone] fax
Seattle, WA 98115 [phone] main reception

***@noaa.gov

[Andy Ray Terrel]

Post by Chris Barker
https://github.com/numfocus/gsoc
Not sure why one might choose NumFocus vs PSF...

No reason to choose, you can get students from both orgs.

Post by Chris Barker
-Chris

Post by Bryan Van de Ven
[This is a complete tangent, and so I apologize in advance.]
We are considering applying to GSOC for Bokeh. However, I have zero
experience with GSOC, but non-zero questions (e.g. go it alone, vs apply
through PSF... I think?) If anyone with experience from the mentoring
organization side of things wouldn't mind a quick chat (or a few emails) to
answer questions, share your experience, or offer advice, please drop me a
line directly.
Thanks,
Bryan

Post by Stephan Hoyer
We might consider adding "improve duck typing for numpy arrays"
care to elaborate on that one?
I know it come up on here that it would be good to have some code in

numpy itself that made it easier to make array-like objects (I.e. do
indexing the same way) Is that what you mean?

Post by Stephan Hoyer
I was thinking particularly of improving the compatibility of numpy

functions (e.g., concatenate) with non-numpy array-like objects, but now
that you mention it utilities to make it easier to make array-like objects
could also be a good thing.

Post by Stephan Hoyer
In any case, I've now elaborated on my thought into a full project idea

https://github.com/scipy/scipy/wiki/GSoC-2016-project-ideas#improved-duck-typing-support-for-n-dimensional-arrays

Post by Stephan Hoyer
Arguably, this might be too difficult for most GSoC students -- the API

design questions here are quite contentious. But given that "Pythonic
dtypes" is up there as a GSoC proposal still it's in good company.

Post by Stephan Hoyer
Cheers,
Stephan
_______________________________________________
NumPy-Discussion mailing list
https://mail.scipy.org/mailman/listinfo/numpy-discussion

_______________________________________________
NumPy-Discussion mailing list
https://mail.scipy.org/mailman/listinfo/numpy-discussion

--
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R [phone] voice
7600 Sand Point Way NE [phone] fax
Seattle, WA 98115 [phone] main reception
_______________________________________________
NumPy-Discussion mailing list
https://mail.scipy.org/mailman/listinfo/numpy-discussion

[Evgeni Burovski]

<snip>

Post by Ralf Gommers

Post by Ralf Gommers
https://github.com/scipy/scipy/wiki/GSoC-2015-project-ideas
Some ideas have been worked on, others are still relevant. Let's copy this
page to -2016- and start editing it and adding new ideas. I'll start right
now actually.

https://github.com/scipy/scipy/wiki/GSoC-2016-project-ideas
I kept some of the ideas from last year, but removed all potential mentors
as the same people may not be available this year - please re-add yourselves
where needed.

Thanks Ralf for doing it!

Just a quick note on de-listed projects. While I do not disagree with
removing the projects on splines and special functions, this IMO does
not mean we won't consider proposals on either of these topics if
someone wants to write one. For instance, if Josh or Ted want to frame
their work on hypergeometric functions as a GSoC project, I'm sure
we're going to at least consider these.

Evgeni

[Pauli Virtanen]

Thu, 11 Feb 2016 00:02:52 +0100, Ralf Gommers kirjoitti:
[clip]

https://github.com/scipy/scipy/wiki/GSoC-2016-project-ideas I kept some
of the ideas from last year, but removed all potential mentors as the
same people may not be available this year - please re-add yourselves
where needed.
And to everyone who has a good idea, and preferably is willing to mentor
for that idea: please add it to that page.

I probably don't have bandwidth for mentoring, but as the Numpy
suggestions seem to be mostly "hard" problems, we can add another
one:

## Dealing with overlapping input/output data

Numpy operations where output arrays overlap with
input arrays can produce unexpected results.
A simple example is
```
x = np.arange(100*100).reshape(100,100)
x += x.T # <- undefined result!
```
The task is to change Numpy so that the results
here become similar to as if the input arrays
overlapping with output were separate (here: `x += x.T.copy()`).
The challenge here lies in doing this without sacrificing
too much performance or memory efficiency.

Initial steps toward solving this problem were taken in
https://github.com/numpy/numpy/pull/6166
where a simplest available algorithm for detecting
if arrays overlap was added. However, this is not yet
utilized in ufuncs. An initial attempt to sketch what
should be done is at https://github.com/numpy/numpy/issues/6272
and issues referenced therein.

[Sebastian Berg]

Post by Pauli Virtanen
[clip]

https://github.com/scipy/scipy/wiki/GSoC-2016-project-ideas I kept some
of the ideas from last year, but removed all potential mentors as the
same people may not be available this year - please re-add
yourselves
where needed.
And to everyone who has a good idea, and preferably is willing to mentor
for that idea: please add it to that page.

I probably don't have bandwidth for mentoring, but as the Numpy
suggestions seem to be mostly "hard" problems, we can add another
## Dealing with overlapping input/output data
Numpy operations where output arrays overlap with
input arrays can produce unexpected results.
A simple example is
```
x = np.arange(100*100).reshape(100,100)
x += x.T # <- undefined result!
```
The task is to change Numpy so that the results
here become similar to as if the input arrays
overlapping with output were separate (here: `x += x.T.copy()`).
The challenge here lies in doing this without sacrificing
too much performance or memory efficiency.
Initial steps toward solving this problem were taken in
https://github.com/numpy/numpy/pull/6166
where a simplest available algorithm for detecting
if arrays overlap was added. However, this is not yet
utilized in ufuncs. An initial attempt to sketch what
should be done is at https://github.com/numpy/numpy/issues/6272
and issues referenced therein.

Since I like the idea, I copy pasted it into the GSoC project ideas
wiki.

- Sebastian

Post by Pauli Virtanen
_______________________________________________
NumPy-Discussion mailing list
https://mail.scipy.org/mailman/listinfo/numpy-discussion