Phylotastic/Participants

From Evolutionary Interoperability and Outreach
Revision as of 16:51, 10 June 2012 by Hilmar (talk | contribs)
Jump to navigation Jump to search

To add your photo, upload an image and give it the "destination" file name of "firstname_lastname_face.jpg"-- if you keep this file name, your image will appear automatically in the gallery below. If you have a personal web page, click the "edit" button above this section, then find the fake URL that has your name (it will be firstname_lastname.com) and replace this with the real URL. You can also create a user page on this wiki (see Karen and Hilmar for examples). To see participant's skills (declared in applications) refer to the skills table below.

Participant gallery


Event photos

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
Jim Balhoff Comments:
Chris Baron viz flow grft NeX mash WS
Christopher Baron Comments: I'm a web developer with little background in evolutionary biology, I can do front end and back end. Currently, I've developing a web application that allows users to upload source trees, as well as prune, replace, and graft together larger trees from these source trees using a graphical interface rather than sophisticated algorithms.
Holly Bik viz flow doc graft use other
Holly Bik Comments:
Helena Deus prov viz flow doc mash tnrs WS other
Helena Deus Comments:
Jamie Estill tree graft NeX
Jamie Estill Comments:
Tracy Heath scale doc graft tnrs
Tracy Heath Comments:
Mark Holder flow graft NeX WS
Mark Holder Comments:
Hilmar Lapp tree viz flow NeX mash WS
Participant Picture 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
Naim Matasci Comments:
Emily Jane McTavish tree prov scale doc graft tnrs use other
Emily Jane McTavish 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
Peter Midford Comments:
Siavash Mirarab scale flow graft tnrs WS
Siavash Mirarab 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
Megan Pirrung Comments:
Rick Ree tree prov scale viz flow doc graft tnrs use WS
Rick Ree Comments:
Aaron Steele tree prov viz flow doc mash tnrs WS
Aaron Steele Comments:
Arlin Stoltzfus tree prov viz flow doc NeX use other
Arlin Stoltzfus Comments: I have experience (as a developer or project manager or scientist) with viz (Nexplorer); a toolbox with tree operations (Bio::NEXUS); fossil-based calibrations (Norris & Stoltzfus, in review); automated workflow for gene-family trees (De Kee, et al. 2007); documentation (NeXML; Bio::NEXUS; Nexplorer); an ontology (CDAO). I am familiar with a variety of phylotastic-relevant use-cases (Stoltzfus, et al., in review).
Jeet Sukumaran tree prov scale flow NeX mash
Jeet Sukumaran Comments:
Gaurav Vaidya flow mash tnrs WS other
Gaurav Vaidya Comments:
Ben Vandervalk flow mash WS
Ben Vandervalk Comments:
Cam Webb tree scale viz flow doc graft NeX mash tnrs use WS
Cam Webb Comments:
Christian Zmasek tree viz flow graft mash tnrs
Christian Zmasek Comments: I am using phylogenetic trees (gene trees) as tools for comparative and functional genomics.
Rutger A. Vos tree prov scale viz flow doc graft NeX mash tnrs WS
Rutger A. Vos Comments: I am guilty of developing NeXML, which might become one of the output formats because it allows for semantic annotation of trees, nodes, taxa, etc. I've also implemented PhyloWS services for TreeBASE, and wrapper PhyloWS services for ToLWeb, uBio, TimeTree.
Participant Name doc NeX WS other
Participant Picture Comments: