Phylotastic @iEvoBio

Karen Cranston
Making the tree of life




http://phylotastic.org/
comparative analysis of leaf
                               vein patterns




Acer macrophyllum
Betula lutea
Aesculus glabra
Tilia americana
Ulmus 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.
Cam Webb




•   most cited example of reuse in phylogenetics
•   extracts subtrees from APG plant phylogeny
•   how can we expand to multiple (and larger) trees?
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
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
Making it happen
•   NESCent working group
    o   HIP: Hackathons, Interoperability, Phylogenetics

•   Targeted hackathon
    o   intensive collaborative coding event
OpenSpace                             Targeted

    vague topic, e.g. “database         specific goal, e.g. “generalize
        interoperability”                       Phylomatic”

participants pitch projects at event   projects largely defined a priori

free to select participants via any
                                           particular skills needed
              criteria

      less pre-event planning             more pre-event planning


     disconnected subgroups            subgroups must work together
Invitation + open call for participation
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
Phylotastic @iEvoBio
Some tangible outcomes (evoio.org)
             Description                       Item (link)            Docs (link)


demo galaxy server                     live demo and code on   base class and screencast
                                       github
demo topology server                   live demo and code on   README.pod
                                       github
prototype controller architecture in   github project          [1]
nodeJS
demo service to annotate tree with     http://datelife.org     NA
dates
Reconcile-o-tastic                     live demo               NA

Mesquite-o-tastic demo module          Java code on github     screencast

TNRS API specification                 API                     TNRS

TNRS Demonstration                     Demo                    TNRS

PhyloWS REST wrapper around tree       live demo               NA
store
demos
phylotastic.org/demos.html
galaxy implementation




           http://galaxy.phylotastic.net
         http://youtu.be/kMME658xOu4
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!
Phylotastic @iEvoBio
future hackathons?

•   HIP group planning two additional events;
    topics TBA
•   NESCent hackathon proposals (“informatics
    whitepaper”)
•   Ask us about running your own!
1 of 16

More Related Content

More from Karen Cranston(14)

Open Tree of Life at Evolution 2014Open Tree of Life at Evolution 2014
Open Tree of Life at Evolution 2014
Karen Cranston2.2K views
Carleton Biology talk : March 2014Carleton Biology talk : March 2014
Carleton Biology talk : March 2014
Karen Cranston717 views
Open Tree of Life Phyloseminar 2014Open Tree of Life Phyloseminar 2014
Open Tree of Life Phyloseminar 2014
Karen Cranston1.2K views
WSSSPE: Building communitiesWSSSPE: Building communities
WSSSPE: Building communities
Karen Cranston1.2K views
Cranston Evolution 2013Cranston Evolution 2013
Cranston Evolution 2013
Karen Cranston13.1K views
Open Tree of Life @NSFOpen Tree of Life @NSF
Open Tree of Life @NSF
Karen Cranston672 views
Open Tree at UNCC Jan 2013Open Tree at UNCC Jan 2013
Open Tree at UNCC Jan 2013
Karen Cranston531 views
Freeing scientific data using CC0Freeing scientific data using CC0
Freeing scientific data using CC0
Karen Cranston1K views
Open Tree of Life @Evolution 2012Open Tree of Life @Evolution 2012
Open Tree of Life @Evolution 2012
Karen Cranston2.8K views
OpenTree at NESCent Academy 2012OpenTree at NESCent Academy 2012
OpenTree at NESCent Academy 2012
Karen Cranston397 views
Open Tree of Life at Duke FuturesOpen Tree of Life at Duke Futures
Open Tree of Life at Duke Futures
Karen Cranston899 views

Phylotastic @iEvoBio

  • 1. Making the tree of life http://phylotastic.org/
  • 2. comparative analysis of leaf vein patterns Acer macrophyllum Betula lutea Aesculus glabra Tilia americana Ulmus 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 priori free 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
  • 11. Some tangible outcomes (evoio.org) Description Item (link) Docs (link) demo galaxy server live demo and code on base class and screencast github demo topology server live demo and code on README.pod github prototype controller architecture in github project [1] nodeJS demo service to annotate tree with http://datelife.org NA dates Reconcile-o-tastic live demo NA Mesquite-o-tastic demo module Java code on github screencast TNRS API specification API TNRS TNRS Demonstration Demo TNRS PhyloWS REST wrapper around tree live demo NA store
  • 13. galaxy implementation http://galaxy.phylotastic.net http://youtu.be/kMME658xOu4
  • 14. 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!
  • 16. future hackathons? • HIP group planning two additional events; topics TBA • NESCent hackathon proposals (“informatics whitepaper”) • Ask us about running your own!