Phylotastic/Skills table
For column descriptions hover over them (or see end of the page). For more info about participants, refer to this page.
Participant | tree | prov | scale | viz | flow | doc | grft | NeX | mash | tnrs | use | WS | other | Describe Other |
Jim Balhoff | prov | flow | NeX | mash | WS | |||||||||
Comments: | ||||||||||||||
Holly Bik | viz | flow | doc | graft | use | other | ||||||||
Comments: | ||||||||||||||
Mark Holder | flow | graft | NeX | WS | ||||||||||
Comments: | ||||||||||||||
Hilmar Lapp | tree | viz | flow | NeX | mash | WS | ||||||||
Comments: I am interested in interoperability and reuse of software and data, and have considerable experience in data and metadata modeling, software architecture, and API design for reuse. | ||||||||||||||
Naim Matasci | tree | viz | flow | doc | graft | tnrs | ||||||||
Comments: | ||||||||||||||
Siavash Mirarab | scale | flow | graft | tnrs | WS | |||||||||
Comments: I am interested in TNRS, but have little experience with it. I am familiar with gene duplication concepts, so I can help with the reconciliation use case (if included). I work on meta-genomics, so I can help with a meta-genomic use case. | ||||||||||||||
Megan Pirrung | viz | flow | WS | other | ||||||||||
Comments: | ||||||||||||||
Rick Ree | tree | prov | scale | viz | flow | doc | graft | tnrs | use | WS | ||||
Comments: | ||||||||||||||
Aaron Steele | tree | prov | viz | flow | doc | mash | tnrs | WS | ||||||
Comments: | ||||||||||||||
Jeet Sukumaran | tree | prov | scale | flow | NeX | mash | ||||||||
Comments: | ||||||||||||||
Gaurav Vaidya | flow | mash | tnrs | WS | other | |||||||||
Comments: | ||||||||||||||
Jamie Estill | tree | graft | NeX | |||||||||||
Comments: | ||||||||||||||
Helena Deus | prov | viz | flow | doc | mash | tnrs | WS | other | ||||||
Comments: | ||||||||||||||
Emily Jane McTavish | tree | prov | scale | doc | graft | tnrs | use | other | ||||||
Comments: My background is phylogenetics, and some bioinformatics. I'm most comfortable with python, fine with SQL, knew C++ and could probably remember if pressed. I'm particularly interested in how to incorporate uncertainty from source trees into phylotastic output, and make it handy without being dangerously blackboxy. | ||||||||||||||
Peter Midford | graft | NeX | tnrs | other | ||||||||||
Comments: | ||||||||||||||
Tracy Heath | scale | doc | graft | tnrs | ||||||||||
Comments: | ||||||||||||||
Ben Vandervalk | flow | mash | WS | |||||||||||
Comments: | ||||||||||||||
Cam Webb | tree | scale | viz | flow | doc | graft | NeX | mash | tnrs | use | WS | |||
Comments: | ||||||||||||||
Christian M. Zmasek | tree | viz | flow | graft | mash | tnrs | ||||||||
Comments: | ||||||||||||||
Participant Name | tree | prov | scale | viz | flow | doc | graft | NeX | mash | tnrs | use | WS | other | |
Participant Picture | Comments: | |||||||||||||
Column Names and Descriptions
- tree (back-end trees): you know where to get large trees (>1K species) and make them available via some data store
- prov (provenance annotation): you can use metadata to keep track of where results came from
- scale (branch length): estimation: you can adapt tools that estimate missing branch lengths on species trees
- viz (visualization): you can adapt an existing phylogeny visualization tool for new inputs and capabilities
- flow (workflows): you can assemble web services (or other resources) into an executable workflow
- doc (documentation): you can make screencasts and write clear how-to documents
- grft (grafting & pruning): you can implement algorithms for grafting and pruning input trees to create a synthetic tree
- Nex (NeXML spec): you can help expand the NeXML spec to cover the Phylotastic use-case
- mash (semantic integration, mashups): you can write tools to discover, collect and integrate online data
- TNRS (taxonomic name resolution): you can use and adapt tools to map one set of names to another
- use (use-case expert): you know a real pruning-grafting-integration problem that can be used to test Phylotastic
- WS (web service interfaces): you can design and implement interfaces to wrap existing tools
- other (something else): you can contribute to this project in ways we haven't imagined yet