Re: [Perldl] Google Summer of Code
On Sat, Feb 14, 2015 at 07:18:52PM -0600, Zakariyya Mughal wrote: On 2015-02-14 at 19:17:43 -0500, Paul Johnson wrote: Hello PDLers, Some of you may well be aware of the Google Summer of Code programme. We would like to get Perl involved in it again this year. And personally I would love to have a PDL project in the mix. If you think you can suggest a project or would like to volunteer as a mentor, please take a look at http://blogs.perl.org/users/shadowcat_mdk/2015/02/gsoc-i-need-your-ideas.html Our application goes in within a few days so timely help is much appreciated. Hey all! Just a reminder that some ideas from 2012 are in the wiki https://github.com/PDLPorters/pdl/wiki/GSoC-2012-Ideas. Thanks very much for the pointer. Which of these ideas are still appropriate for projects this year? Do we have anyone who would like to be a mentor? To be honest, mentors are always harder to find than projects, so if anyone would like to get involved, as either a primary or backup mentor, please raise your hand! Then we can see about listing potential projects. Thanks! -- Paul Johnson - p...@pjcj.net http://www.pjcj.net ___ Perldl mailing list Perldl@jach.hawaii.edu http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
Re: [Perldl] Google Summer of Code Ideas
I would be willing to help with mentoring. Maybe we should have a list on the wiki as a number of the ideas sound good and it would be useful to have a way to keep things sorted out. The wiki would also allow for more detail on the items. Different folks have looked at implementing a number of these and may have a better understanding of the tasks and scope involved. --Chris On 2/17/2012 11:21 AM, David Mertens wrote: Hello all - Nobody jumped up to help mentor. I'll assume that's because nobody is excited about the possibilities, so let's do what I initially didn't want to do: let's brainstorm some ideas for what could be implemented. The student(s) would spend their summer, which is supposed to be three to four months, on these projects, so they can be fairly large in their scope. Here are my ideas: 1) Expand and enhance PDL's help database API so that other PDL modules can add to it it at install time and other projects can tap into it more easily (pure-perl, may be too small) 2) Finally get PDL::Expt designed and implemented (should be all Perl) 3) Build a PDL equivalent of Matlab's Signal Processing Toolkit (some Perl, some PDL::PP) 4) Design and implement PDL::Pointer, PDL::SV, and PDL::Struct (mostly PDL core hacking, some PDL::PP and Perl) 5) Make PDL capable of handling2G elements (PDL core hacking) 6) Make PDL thread-safe (PDL core hacking) What else would we like to see implemented? In particular, are there any Toolkits that you would like to see implemented? We have no guarantee that a student will take us up on these, but we stand to improve our chances if we have some cool ideas. One last thing: please mention if you will be able to mentor the student on your proposed ideas. Mentoring is mostly over email or instant messaging, and you'll have the rest of us around, so it's not necessarily a huge commitment. If you know something about a topic and simply haven't had the time to write the code for it, you would be a *perfect* mentor, so speak up! David ___ Perldl mailing list Perldl@jach.hawaii.edu http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
Re: [Perldl] Google Summer of Code Ideas
More ideas: 1) Update FFTW for FFTW3 (PDL::PP and XS) 2) Full GSL support (PDL::PP and XS) 3) memory maping support for Windows (PDL core hacking, working with PDL magic) David On Fri, Feb 17, 2012 at 10:21 AM, David Mertens dcmertens.p...@gmail.comwrote: Hello all - Nobody jumped up to help mentor. I'll assume that's because nobody is excited about the possibilities, so let's do what I initially didn't want to do: let's brainstorm some ideas for what could be implemented. The student(s) would spend their summer, which is supposed to be three to four months, on these projects, so they can be fairly large in their scope. Here are my ideas: 1) Expand and enhance PDL's help database API so that other PDL modules can add to it it at install time and other projects can tap into it more easily (pure-perl, may be too small) 2) Finally get PDL::Expt designed and implemented (should be all Perl) 3) Build a PDL equivalent of Matlab's Signal Processing Toolkit (some Perl, some PDL::PP) 4) Design and implement PDL::Pointer, PDL::SV, and PDL::Struct (mostly PDL core hacking, some PDL::PP and Perl) 5) Make PDL capable of handling 2G elements (PDL core hacking) 6) Make PDL thread-safe (PDL core hacking) What else would we like to see implemented? In particular, are there any Toolkits that you would like to see implemented? We have no guarantee that a student will take us up on these, but we stand to improve our chances if we have some cool ideas. One last thing: please mention if you will be able to mentor the student on your proposed ideas. Mentoring is mostly over email or instant messaging, and you'll have the rest of us around, so it's not necessarily a huge commitment. If you know something about a topic and simply haven't had the time to write the code for it, you would be a *perfect* mentor, so speak up! David -- Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -- Brian Kernighan -- Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -- Brian Kernighan ___ Perldl mailing list Perldl@jach.hawaii.edu http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
Re: [Perldl] Google Summer of Code Ideas
Yet another idea, though not for the faint-of-heart: 1) Python/Numpy + Perl/PDL David On Fri, Feb 17, 2012 at 10:30 AM, David Mertens dcmertens.p...@gmail.comwrote: More ideas: 1) Update FFTW for FFTW3 (PDL::PP and XS) 2) Full GSL support (PDL::PP and XS) 3) memory maping support for Windows (PDL core hacking, working with PDL magic) David On Fri, Feb 17, 2012 at 10:21 AM, David Mertens dcmertens.p...@gmail.comwrote: Hello all - Nobody jumped up to help mentor. I'll assume that's because nobody is excited about the possibilities, so let's do what I initially didn't want to do: let's brainstorm some ideas for what could be implemented. The student(s) would spend their summer, which is supposed to be three to four months, on these projects, so they can be fairly large in their scope. Here are my ideas: 1) Expand and enhance PDL's help database API so that other PDL modules can add to it it at install time and other projects can tap into it more easily (pure-perl, may be too small) 2) Finally get PDL::Expt designed and implemented (should be all Perl) 3) Build a PDL equivalent of Matlab's Signal Processing Toolkit (some Perl, some PDL::PP) 4) Design and implement PDL::Pointer, PDL::SV, and PDL::Struct (mostly PDL core hacking, some PDL::PP and Perl) 5) Make PDL capable of handling 2G elements (PDL core hacking) 6) Make PDL thread-safe (PDL core hacking) What else would we like to see implemented? In particular, are there any Toolkits that you would like to see implemented? We have no guarantee that a student will take us up on these, but we stand to improve our chances if we have some cool ideas. One last thing: please mention if you will be able to mentor the student on your proposed ideas. Mentoring is mostly over email or instant messaging, and you'll have the rest of us around, so it's not necessarily a huge commitment. If you know something about a topic and simply haven't had the time to write the code for it, you would be a *perfect* mentor, so speak up! David -- Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -- Brian Kernighan -- Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -- Brian Kernighan -- Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -- Brian Kernighan ___ Perldl mailing list Perldl@jach.hawaii.edu http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
Re: [Perldl] Google Summer of Code Ideas
Hey David I would like to work on number 5 there.. and any thing else getting PDL to handle 2 Gigabyte elements send me a email outlining in a list what we need to do to get this on Google summer of code ! What about integration with OpenCL I think that would be really cool I know it sounds like the lazy thing to say, But I think Google would fund that ! I would like to volunteer as a student but I will Mentor if everyone says its ok; so while I look like I'm a expert, I'm really just Innovative... --Mark R baker mrbaker_m...@yahoo.com From: David Mertens dcmertens.p...@gmail.com To: perldl perldl@jach.hawaii.edu Sent: Friday, February 17, 2012 8:30 AM Subject: Re: [Perldl] Google Summer of Code Ideas More ideas: 1) Update FFTW for FFTW3 (PDL::PP and XS) 2) Full GSL support (PDL::PP and XS) 3) memory maping support for Windows (PDL core hacking, working with PDL magic) David On Fri, Feb 17, 2012 at 10:21 AM, David Mertens dcmertens.p...@gmail.com wrote: Hello all - Nobody jumped up to help mentor. I'll assume that's because nobody is excited about the possibilities, so let's do what I initially didn't want to do: let's brainstorm some ideas for what could be implemented. The student(s) would spend their summer, which is supposed to be three to four months, on these projects, so they can be fairly large in their scope. Here are my ideas: 1) Expand and enhance PDL's help database API so that other PDL modules can add to it it at install time and other projects can tap into it more easily (pure-perl, may be too small) 2) Finally get PDL::Expt designed and implemented (should be all Perl) 3) Build a PDL equivalent of Matlab's Signal Processing Toolkit (some Perl, some PDL::PP) 4) Design and implement PDL::Pointer, PDL::SV, and PDL::Struct (mostly PDL core hacking, some PDL::PP and Perl) 5) Make PDL capable of handling 2G elements (PDL core hacking) 6) Make PDL thread-safe (PDL core hacking) What else would we like to see implemented? In particular, are there any Toolkits that you would like to see implemented? We have no guarantee that a student will take us up on these, but we stand to improve our chances if we have some cool ideas. One last thing: please mention if you will be able to mentor the student on your proposed ideas. Mentoring is mostly over email or instant messaging, and you'll have the rest of us around, so it's not necessarily a huge commitment. If you know something about a topic and simply haven't had the time to write the code for it, you would be a perfect mentor, so speak up! David -- Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -- Brian Kernighan -- Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -- Brian Kernighan ___ Perldl mailing list Perldl@jach.hawaii.edu http://mailman.jach.hawaii.edu/mailman/listinfo/perldl___ Perldl mailing list Perldl@jach.hawaii.edu http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
Re: [Perldl] Google Summer of Code Ideas
Mark - As you're still a student, you could certainly apply to Google with that project in mind: http://code.google.com/soc/ And that goes for any students, graduate or undergraduate, who might be interested in applying. David On Fri, Feb 17, 2012 at 10:49 AM, MARK BAKER mrbaker_m...@yahoo.com wrote: Hey David I would like to work on number 5 there.. and any thing else getting PDL to handle 2 Gigabyte elements send me a email outlining in a list what we need to do to get this on Google summer of code ! What about integration with OpenCL I think that would be really cool I know it sounds like the lazy thing to say, But I think Google would fund that ! I would like to volunteer as a student but I will Mentor if everyone says its ok; so while I look like I'm a expert, I'm really just Innovative... --Mark R baker mrbaker_m...@yahoo.com -- *From:* David Mertens dcmertens.p...@gmail.com *To:* perldl perldl@jach.hawaii.edu *Sent:* Friday, February 17, 2012 8:30 AM *Subject:* Re: [Perldl] Google Summer of Code Ideas More ideas: 1) Update FFTW for FFTW3 (PDL::PP and XS) 2) Full GSL support (PDL::PP and XS) 3) memory maping support for Windows (PDL core hacking, working with PDL magic) David On Fri, Feb 17, 2012 at 10:21 AM, David Mertens dcmertens.p...@gmail.comwrote: Hello all - Nobody jumped up to help mentor. I'll assume that's because nobody is excited about the possibilities, so let's do what I initially didn't want to do: let's brainstorm some ideas for what could be implemented. The student(s) would spend their summer, which is supposed to be three to four months, on these projects, so they can be fairly large in their scope. Here are my ideas: 1) Expand and enhance PDL's help database API so that other PDL modules can add to it it at install time and other projects can tap into it more easily (pure-perl, may be too small) 2) Finally get PDL::Expt designed and implemented (should be all Perl) 3) Build a PDL equivalent of Matlab's Signal Processing Toolkit (some Perl, some PDL::PP) 4) Design and implement PDL::Pointer, PDL::SV, and PDL::Struct (mostly PDL core hacking, some PDL::PP and Perl) 5) Make PDL capable of handling 2G elements (PDL core hacking) 6) Make PDL thread-safe (PDL core hacking) What else would we like to see implemented? In particular, are there any Toolkits that you would like to see implemented? We have no guarantee that a student will take us up on these, but we stand to improve our chances if we have some cool ideas. One last thing: please mention if you will be able to mentor the student on your proposed ideas. Mentoring is mostly over email or instant messaging, and you'll have the rest of us around, so it's not necessarily a huge commitment. If you know something about a topic and simply haven't had the time to write the code for it, you would be a *perfect* mentor, so speak up! David -- Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -- Brian Kernighan -- Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -- Brian Kernighan ___ Perldl mailing list Perldl@jach.hawaii.edu http://mailman.jach.hawaii.edu/mailman/listinfo/perldl -- Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -- Brian Kernighan ___ Perldl mailing list Perldl@jach.hawaii.edu http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
Re: [Perldl] Google Summer of Code Ideas
My first post. I'm still learning PDL, excuse me if I suggest something that is already maturely implemented in PDL! PDL interfaces to sparse eigensolvers such as ARPACK or BLZPACK would be really awesome. All us biophysical folks love diagonalizing huge sparse matrices. Date: Fri, 17 Feb 2012 10:21:56 -0600 From: David Mertens dcmertens.p...@gmail.com To: perldl perldl@jach.hawaii.edu Subject: [Perldl] Google Summer of Code Ideas Message-ID: ca+4ieywk+tdjofqpqexs9+grjjwywc4e8nccdv_6se-e4dq...@mail.gmail.com Content-Type: text/plain; charset=iso-8859-1 Hello all - Nobody jumped up to help mentor. I'll assume that's because nobody is excited about the possibilities, so let's do what I initially didn't want to do: let's brainstorm some ideas for what could be implemented. The student(s) would spend their summer, which is supposed to be three to four months, on these projects, so they can be fairly large in their scope. Here are my ideas: 1) Expand and enhance PDL's help database API so that other PDL modules can add to it it at install time and other projects can tap into it more easily (pure-perl, may be too small) 2) Finally get PDL::Expt designed and implemented (should be all Perl) 3) Build a PDL equivalent of Matlab's Signal Processing Toolkit (some Perl, some PDL::PP) 4) Design and implement PDL::Pointer, PDL::SV, and PDL::Struct (mostly PDL core hacking, some PDL::PP and Perl) 5) Make PDL capable of handling 2G elements (PDL core hacking) 6) Make PDL thread-safe (PDL core hacking) What else would we like to see implemented? In particular, are there any Toolkits that you would like to see implemented? We have no guarantee that a student will take us up on these, but we stand to improve our chances if we have some cool ideas. One last thing: please mention if you will be able to mentor the student on your proposed ideas. Mentoring is mostly over email or instant messaging, and you'll have the rest of us around, so it's not necessarily a huge commitment. If you know something about a topic and simply haven't had the time to write the code for it, you would be a *perfect* mentor, so speak up! David -- Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -- Brian Kernighan ___ Perldl mailing list Perldl@jach.hawaii.edu http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
Re: [Perldl] Google Summer of Code
On Tue, Feb 14, 2012 at 9:05 AM, David Mertens dcmertens.p...@gmail.comwrote: PDL People - The Google Summer of Code is starting to get rolling [1] and Perl will once again apply to be a mentoring organization [2]. At this time, we need to organize ourselves regarding the following: * Discuss and add some fun PDL ideas to the Perl Project Ideas page [3] * Find mentors among our ranks to oversee projects * Look for students (any student in college is eligible, including Ph. D. students) I only just started reading about this today so I am uncertain about a few things. In particular, I am not certain if there are deadlines for getting project ideas onto Perl's idea list [3]. I'm looking into that now and will send an update once I find out. If you have ideas, please make a note of them, but do not send them to the mailing list. I expect that we will want to build a wiki page for our GSoC ideas, and then either summarize and link to it from Perl's Ideas Page, or copy to Perl's Ideas page verbatim. Please reply if you are interested in mentoring, or if you are a student who would be interested in applying! David [1] http://google-melange.appspot.com/gsoc/homepage/google/gsoc2012 [2] http://wiki.enlightenedperl.org/gsoc2012 [3] http://wiki.enlightenedperl.org/gsoc2012/ideas -- Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -- Brian Kernighan More details: Perl's efforts are discussed on #soc-help at irc.perl.org, so feel free to sign-on there to join the discussion. After chatting with rafl on irc, I intend to flesh out our ideas on our own wiki page, but submit a decent per-project summary, including mentor, to the Perl idea page. The deadline for that (i.e. when rafl will submit the proposal to Google) is February 27. We have just under two weeks. So, if you have ideas, please reply! David -- Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -- Brian Kernighan ___ Perldl mailing list Perldl@jach.hawaii.edu http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
