Your SlideShare is downloading. ×

Phylotastic @iEvoBio

700

Published on

Phylotastic hackathon report from 2012 iEvoBio meting

Phylotastic hackathon report from 2012 iEvoBio meting

Published in: Technology, Business
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
700
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
3
Comments
0
Likes
3
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Making the tree of lifehttp://phylotastic.org/
  • 2. comparative analysis of leaf vein patternsAcer macrophyllumBetula luteaAesculus glabraTilia americanaUlmus rubra Leaf patterns image from Walls RL: Angiosperm leaf vein patterns are linked to leaf functions in a global-scale data set. American Journal of Botany 2011, 98(2):244-253.
  • 3. Cam Webb• most cited example of reuse in phylogenetics• extracts subtrees from APG plant phylogeny• how can we expand to multiple (and larger) trees?
  • 4. Species list? Acer macrophyllum Betula lutea TNRS Aesculus glabra Tilia americana Ulmus rubra Phylotastic! A. macrophyllum available mega-trees B. alleghaniensis A. glabra T. americana U. rubra
  • 5. Components{ cat, dog, squirrel, human } • name resolution - fix typos, use preferred synonyms, resolve taxonomy • tree storage - store megatrees with metadata • pruning & grafting - remove & add branches • scaling - add branch lengths • controllers - manage workflow
  • 6. Making it happen• NESCent working group o HIP: Hackathons, Interoperability, Phylogenetics• Targeted hackathon o intensive collaborative coding event
  • 7. OpenSpace Targeted vague topic, e.g. “database specific goal, e.g. “generalize interoperability” Phylomatic”participants pitch projects at event projects largely defined a priorifree to select participants via any particular skills needed criteria less pre-event planning more pre-event planning disconnected subgroups subgroups must work together
  • 8. Invitation + open call for participation
  • 9. The event: June 4-8@NESCent• 25 local + 5 remote participants• 5 Subgroups: • TNRS - taxonomic name resolution • TreeStore - triple store with REST API • Architecture* - flow control, interoperability (*and pruning services) • DateLife - scaling trees using chronograms • Shiny - other demos and cool front-end stuff
  • 10. Some tangible outcomes (evoio.org) Description Item (link) Docs (link)demo galaxy server live demo and code on base class and screencast githubdemo topology server live demo and code on README.pod githubprototype controller architecture in github project [1]nodeJSdemo service to annotate tree with http://datelife.org NAdatesReconcile-o-tastic live demo NAMesquite-o-tastic demo module Java code on github screencastTNRS API specification API TNRSTNRS Demonstration Demo TNRSPhyloWS REST wrapper around tree live demo NAstore
  • 11. demosphylotastic.org/demos.html
  • 12. galaxy implementation http://galaxy.phylotastic.net http://youtu.be/kMME658xOu4
  • 13. what did we learn? • lots of enthusiasm and hard work at the event o but pre-event planning & post-event follow-up more difficult• important to scope carefully for targetted event• remote participation via Google hangouts added value o needs dedicated on and off-site participants• getting diverse participation required active invitation• spent way too much time on taxonomic name reconciliation for a phylogeny event!
  • 14. future hackathons?• HIP group planning two additional events; topics TBA• NESCent hackathon proposals (“informatics whitepaper”)• Ask us about running your own!

×