Difference between revisions of "BIN-PHYLO-Tree analysis"

From "A B C"
Jump to navigation Jump to search
m
m
 
(3 intermediate revisions by the same user not shown)
Line 41: Line 41:
 
<b>Deliverables:</b><br />
 
<b>Deliverables:</b><br />
 
<section begin=deliverables />
 
<section begin=deliverables />
<!-- included from "./data/ABC-unit_components.txt", section: "deliverables-time_management" -->
+
<li><b>Time management</b>: Before you begin, estimate how long it will take you to complete this unit. Then, record in your course journal: the number of hours you estimated, the number of hours you worked on the unit, and the amount of time that passed between start and completion of this unit.</li>
*<b>Time management</b>: Before you begin, estimate how long it will take you to complete this unit. Then, record in your course journal: the number of hours you estimated, the number of hours you worked on the unit, and the amount of time that passed between start and completion of this unit.
+
<li><b>Journal</b>: Document your progress in your [[FND-Journal|Course Journal]]. Some tasks may ask you to include specific items in your journal. Don't overlook these.</li>
<!-- included from "./data/ABC-unit_components.txt", section: "deliverables-journal" -->
+
<li><b>Insights</b>: If you find something particularly noteworthy about this unit, make a note in your [[ABC-Insights|'''insights!''' page]].</li>
*<b>Journal</b>: Document your progress in your [[FND-Journal|Course Journal]]. Some tasks may ask you to include specific items in your journal. Don't overlook these.
 
<!-- included from "./data/ABC-unit_components.txt", section: "deliverables-insights" -->
 
*<b>Insights</b>: If you find something particularly noteworthy about this unit, make a note in your [[ABC-Insights|'''insights!''' page]].
 
 
<section end=deliverables />
 
<section end=deliverables />
 
<!-- ============================  -->
 
<!-- ============================  -->
Line 52: Line 49:
 
<section begin=prerequisites />
 
<section begin=prerequisites />
 
<b>Prerequisites:</b><br />
 
<b>Prerequisites:</b><br />
<!-- included from "./data/ABC-unit_components.txt", section: "notes-prerequisites" -->
+
This unit builds on material covered in the following prerequisite units:<br />
This unit builds on material covered in the following prerequisite units:
 
 
*[[BIN-PHYLO-Tree_building|BIN-PHYLO-Tree_building (Building Phylogenetic Trees)]]
 
*[[BIN-PHYLO-Tree_building|BIN-PHYLO-Tree_building (Building Phylogenetic Trees)]]
 
<section end=prerequisites />
 
<section end=prerequisites />
Line 71: Line 67:
  
  
 +
=== Evaluation ===
 +
<b>Evaluation: NA</b><br />
 +
<div style="margin-left: 2rem;">This unit is not evaluated for course marks.</div>
 
== Contents ==
 
== Contents ==
<!-- included from "./components/BIN-PHYLO-Tree_analysis.components.txt", section: "contents" -->
 
  
  
Line 78: Line 76:
 
*Read the introductory notes on {{ABC-PDF|BIN-PHYLO-Tree_analysis|analysing phylogenetic trees}}.
 
*Read the introductory notes on {{ABC-PDF|BIN-PHYLO-Tree_analysis|analysing phylogenetic trees}}.
 
}}
 
}}
 
 
===Analysis===
 
 
 
  
  
 
==Analysing your tree==
 
==Analysing your tree==
{{Vspace}}
+
{{Smallvspace}}
 
 
In order to analyse your tree, you need a species tree as reference. This really is an absolute prerequisite to make your expectations about the observed tree explicit. Fortunately we have all species nicely documented in our database.
 
 
 
{{Vspace}}
 
 
 
===The reference species tree===
 
 
 
{{Vspace}}
 
 
 
{{task|1=
 
 
 
To get a species tree, we make use of the smart and useful PhyloT service:
 
 
 
* Navigate to the [http://phylot.biobyte.de/index.html '''PhyloT''']
 
 
 
* Execute the following '''R''' command to create a list of all taxonomy records for the species in your database (plus E. coli):
 
<source lang="R">
 
cat(paste(c(myDB$taxonomy$ID, "83333"), collapse=", "))
 
</source>
 
 
 
<!-- 227321, 930090, 367110, 559292, 284812, 240176, 214684, 418459, 237631, 671144, 83333 -->
 
 
 
* Copy this list and paste it into the search field of the PhyloT page. Select: '''Scientific names'''; Internal Nodes '''collapsed'''; polytomy '''no'''; Format '''newick'''; Filename '''<tt>fungiTree.txt</tt>'''. Click on '''Generate tree'''. The file <tt>fungiTree.txt</tt> will be downloaded to your computer into your default download directory. Move it to your project directory. Then click on '''Visualize in iTOL''' and confirm the tree: the resulting tree should have twelve species names listed - ten "reference" fungi, ''E. coli'' (as the outgroup), and MYSPE. Make sure MYSPE is included! If it's not there, you did something wrong that needs to be fixed.
 
 
 
*Open <tt>fungiTree.txt</tt> in RStudio. This is a tree, specified in the so-called {{WP|Newick_format|'''"Newick format"'''}}. The topology of the tree is defined through the brackets, and the branch-lengths are all the same: this is a cladogram, not a phylogram.
 
 
 
Let's continue the analysis in R.
 
  
 
{{ABC-unit|BIN-PHYLO-Tree_analysis.R}}
 
{{ABC-unit|BIN-PHYLO-Tree_analysis.R}}
  
 
}}
 
  
 
{{Vspace}}
 
{{Vspace}}
 
I have constructed a cladogram for many of the species we are analysing, based on data published for 1551 fungal ribosomal sequences. The six reference species are included. Such reference trees from rRNA data are a standard method of phylogenetic analysis, supported by the assumption that rRNA sequences are monophyletic and have evolved under comparable selective pressure in all species.
 
 
{{vspace}}
 
<div class="reference-box">
 
[[Image:FungiCladogram.jpg|600px|none]]
 
 
 
<small>'''Cladogram of the "reference" fungi''' studied in the assignments. This cladogram is based on a tree returned by the NCBI Common Tree. It is thus a digest of cladistic relationships, not a representation of a specific molecular phylogeny.</small>
 
</div>
 
 
Alternatively, you can look up your species in the latest version of the species tree for the fungi and add it to the tree by hand while resolving the trifurcations. See:
 
{{#pmid: 22114356}}
 
 
{{Vspace}}
 
 
 
{{task|1=
 
 
* Return to the RStudio project and continue with the script to its end. Note the deliverable at the end: to print out your trees and bring them to class.
 
 
}}
 
 
 
  
 
<!--
 
<!--
Line 179: Line 119:
 
* Now use Rproml to calculate a mixed gene tree based on '''all'' APSES domains. You saved it as <code>APSES.mfa</code>. For the fifty or so domains, each run will take about an hour. Thus run as many <code>random.addition</code> cycles as reasonable during a study break, or overnight. Thus the command will be something like:
 
* Now use Rproml to calculate a mixed gene tree based on '''all'' APSES domains. You saved it as <code>APSES.mfa</code>. For the fifty or so domains, each run will take about an hour. Thus run as many <code>random.addition</code> cycles as reasonable during a study break, or overnight. Thus the command will be something like:
  
<source lang="R">
+
<pre>
 
allApsIn <- read.protein("APSES.mfa")
 
allApsIn <- read.protein("APSES.mfa")
 
fullApsTree <- Rproml(allApsIn, path=PROMLPATH, random.addition=3)
 
fullApsTree <- Rproml(allApsIn, path=PROMLPATH, random.addition=3)
Line 185: Line 125:
 
#... and don't forget:
 
#... and don't forget:
 
save(fullApsTree, file="fullApsTree.rda")
 
save(fullApsTree, file="fullApsTree.rda")
</source>
+
</pre>
  
 
}}
 
}}
 
{{Vspace}}
 
 
 
 
 
 
 
 
  
 
{{Vspace}}
 
{{Vspace}}
Line 348: Line 279:
  
 
-->
 
-->
== Notes ==
 
<!-- included from "./components/BIN-PHYLO-Tree_analysis.components.txt", section: "notes" -->
 
<!-- included from "./data/ABC-unit_components.txt", section: "notes" -->
 
<references />
 
 
== Further reading, links and resources ==
 
== Further reading, links and resources ==
  
Line 360: Line 287:
 
Also: [http://www.nature.com/scitable/topicpage/reading-a-phylogenetic-tree-the-meaning-of-41956 Nature-Scitable (2008): '''Reading a Phylogenetic Tree: The Meaning of Monophyletic Groups''']
 
Also: [http://www.nature.com/scitable/topicpage/reading-a-phylogenetic-tree-the-meaning-of-41956 Nature-Scitable (2008): '''Reading a Phylogenetic Tree: The Meaning of Monophyletic Groups''']
  
 +
== Notes ==
 +
<references />
  
 
{{Vspace}}
 
{{Vspace}}
  
 
<!-- included from "./data/ABC-unit_components.txt", section: "ABC-unit_ask" -->
 
 
----
 
 
{{Vspace}}
 
 
<b>If in doubt, ask!</b> If anything about this learning unit is not clear to you, do not proceed blindly but ask for clarification. Post your question on the course mailing list: others are likely to have similar problems. Or send an email to your instructor.
 
 
----
 
 
{{Vspace}}
 
  
 
<div class="about">
 
<div class="about">
Line 384: Line 301:
 
:2017-08-05
 
:2017-08-05
 
<b>Modified:</b><br />
 
<b>Modified:</b><br />
:2017-10-31
+
:2020-09-25
 
<b>Version:</b><br />
 
<b>Version:</b><br />
:1.0
+
:1.1
 
<b>Version history:</b><br />
 
<b>Version history:</b><br />
 +
*1.1 2020 updates; remove iTOL (now using taxize::)
 
*1.0 First live version.
 
*1.0 First live version.
 
*0.1 First stub
 
*0.1 First stub
 
</div>
 
</div>
[[Category:ABC-units]]
 
<!-- included from "./data/ABC-unit_components.txt", section: "ABC-unit_footer" -->
 
  
 
{{CC-BY}}
 
{{CC-BY}}
  
 +
[[Category:ABC-units]]
 +
{{UNIT}}
 +
{{LIVE}}
 
</div>
 
</div>
 
<!-- [END] -->
 
<!-- [END] -->

Latest revision as of 11:42, 26 September 2020

Analysing Phylogenetic Trees

(Species trees, gene trees and the importance of naming, Speciation and duplication signatures)


 


Abstract:

The analysis of mixed gene trees.


Objectives:
This unit will ...

  • ... introduce ;
  • ... demonstrate ;
  • ... teach how to fetch a species tree from the NCBI taxonomy page;

Outcomes:
After working through this unit you ...

  • ... can ;
  • ... are familar with ;
  • ... have begun to.

Deliverables:

  • Time management: Before you begin, estimate how long it will take you to complete this unit. Then, record in your course journal: the number of hours you estimated, the number of hours you worked on the unit, and the amount of time that passed between start and completion of this unit.
  • Journal: Document your progress in your Course Journal. Some tasks may ask you to include specific items in your journal. Don't overlook these.
  • Insights: If you find something particularly noteworthy about this unit, make a note in your insights! page.

  • Prerequisites:
    This unit builds on material covered in the following prerequisite units:


     



     



     


    Evaluation

    Evaluation: NA

    This unit is not evaluated for course marks.

    Contents

    Task:


    Analysing your tree

     

    Task:

     
    • Open RStudio and load the ABC-units R project. If you have loaded it before, choose FileRecent projectsABC-Units. If you have not loaded it before, follow the instructions in the RPR-Introduction unit.
    • Choose ToolsVersion ControlPull Branches to fetch the most recent version of the project from its GitHub repository with all changes and bug fixes included.
    • Type init() if requested.
    • Open the file BIN-PHYLO-Tree_analysis.R and follow the instructions.


     

    Note: take care that you understand all of the code in the script. Evaluation in this course is cumulative and you may be asked to explain any part of code.


     


     

    Further reading, links and resources

    Szöllősi et al. (2015) Genome-scale phylogenetic analysis finds extensive gene transfer among fungi. Philos Trans R Soc Lond., B, Biol Sci 370:20140335. (pmid: 26323765)

    PubMed ] [ DOI ]

    Ebersberger et al. (2012) A consistent phylogenetic backbone for the fungi. Mol Biol Evol 29:1319-34. (pmid: 22114356)

    PubMed ] [ DOI ]

    Marcet-Houben & Gabaldón (2009) The tree versus the forest: the fungal tree of life and the topological diversity within the yeast phylome. PLoS ONE 4:e4357. (pmid: 19190756)

    PubMed ] [ DOI ]

    Also: Nature-Scitable (2008): Reading a Phylogenetic Tree: The Meaning of Monophyletic Groups

    Notes


     


    About ...
     
    Author:

    Boris Steipe <boris.steipe@utoronto.ca>

    Created:

    2017-08-05

    Modified:

    2020-09-25

    Version:

    1.1

    Version history:

    • 1.1 2020 updates; remove iTOL (now using taxize::)
    • 1.0 First live version.
    • 0.1 First stub

    CreativeCommonsBy.png This copyrighted material is licensed under a Creative Commons Attribution 4.0 International License. Follow the link to learn more.