[Perldl] Google Summer of Code Ideas

David Mertens dcmertens.perl at gmail.com
Fri Feb 17 07:02:32 HST 2012


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_mark at 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_mark at yahoo.com
>
>   ------------------------------
> *From:* David Mertens <dcmertens.perl at gmail.com>
> *To:* perldl <perldl at 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.perl at 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 at 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.jach.hawaii.edu/pipermail/perldl/attachments/20120217/649d3b1e/attachment.html>


More information about the Perldl mailing list