Post has attachment
Dear all.

Unfortunately, our application for this year's Summer of Code was rejected.

We realise this is a real disappointment. The SoC is not only a chance to get great students, but also gives us all an opportunity for new collaborations, and get more of an an insight into our respective specializations.

But don't give up now !  Many of the ideas that you (the NESCent mentors) posted on the NESCent GSoC 2014 page could easily fit the remit of one of the organisations that will be participating in this year's SoC.

To that end - I've added some links to the bio/science/math related organisations to help you repurpose your ideas if you'd still like to act as a mentor this year.

http://informatics.nescent.org/wiki/Phyloinformatics_Summer_of_Code_2014

Can anyone point me to the right direction for timings this year? Specifically:

1. When do we hear if NESCent was successful?
2. When are student proposals due? 

Cheers,

Rob

Post has attachment
Today is the last day to get PhyloSoC project ideas up on the wiki - the deadline for the org applications is tomorrow! We have a pretty small list at the moment, so if you have something in mind, please do put it up on the wiki.

http://informatics.nescent.org/wiki/Phyloinformatics_Summer_of_Code_2014#Project_Ideas

Hi All,

I'd like to propose another project on PartitionFinder this year, centred around coding model selection for morphological models. This is something that's rarely (but not never) been considered, and could really usefully build on the successful 2013 project.

Any thoughts very welcome. Particularly if there's anything useful I can do before the mentoring org. deadline on Friday (apologies for the late entry, I've been away at a meeting and unexpectedly out of email).

Cheers,

Rob

Post has attachment
The wiki page is up for PhyloSoC project ideas! Post an outline on the wiki and pitch your idea on the wg-phyloinformatics mailing list. Summer of Code is a great way to build our phyloinformatics developer community. 

http://informatics.nescent.org/wiki/Phyloinformatics_Summer_of_Code_2014

Post has attachment
Would there be interest in a project involving interoperability between museum databases and phylogeny data stores. I have been working a bit on developing an ontology-anchored schema for museum databases that allows for direct interaction with phylogenetic data within the context of the RDBMS by extending Chado to museum data. The system would also provide a mechanism for spinning off RDF triples for use in federated queries. I'd be happy to mentor and interact with folks coming from my current perspective in museum informatics.

Are there guidelines on what kind of projects we should propose?  I'd like to propose some Haskell-related things that affect the core engine of my phylogeny-inference software bali-phy.  (e.g. parser/lexer, typechecking, optimization).  These will assist in adding lots of new phylogenetic models.

Post has attachment
We are starting to gear up for a 2014 GSoC application. Do you develop an open source software package for evolutionary biology? Are there features queued for development that would make a good summer programming project? This is the time to start thinking about project ideas!

https://www.google-melange.com/gsoc/homepage/google/gsoc2014

Post has attachment
This question from +Prasad Mani @ +Dolby Laboratories   may interest budding #GPU implementation #engineers to answer:

"Design and implement a layered depth of field blur based on #Gaussian #Blur. I am particularly interested in GPU accelerated approaches that increase thread-level collaboration and GPU occupancy.

Talk through your design decisions and write out some pseudo code in #OpenCL or #Cuda whatever might be your preference."

Post has attachment
Hello PhyloSoC students,
We are a good way through the GSoC community bonding period (yikes!), and the coding period begins Monday. Here is a summary of the things that you should have done before Monday:

https://docs.google.com/document/d/1c3gZy1fT_oMrWr_yyl2CJVajuN_TFCFaQxMEYoHORac/edit?usp=sharing

More coming next week re: expectations during the coding period. 
Wait while more posts are being loaded