Difference between revisions of "ABC-INT-Phylogeny"
Jump to navigation
Jump to search
m |
m |
||
| Line 56: | Line 56: | ||
* Document your results in a short report on a subpage of your User page on the Student Wiki. Describe your methods (R-code!) in an appendix; | * Document your results in a short report on a subpage of your User page on the Student Wiki. Describe your methods (R-code!) in an appendix; | ||
* When you are done with everything, add the following category tag '''to the end of page''': | * When you are done with everything, add the following category tag '''to the end of page''': | ||
| − | + | ::<code><nowiki>[[Category:EVAL-INT-Phylogeny]]</nowiki></code>. | |
Once the page has been saved with this tag, it is considered "submitted". | Once the page has been saved with this tag, it is considered "submitted". | ||
| Line 72: | Line 72: | ||
:* make sure that you have included important literature references. | :* make sure that you have included important literature references. | ||
:* When you are done with everything, add the following category tag '''to the end of page''': | :* When you are done with everything, add the following category tag '''to the end of page''': | ||
| − | + | ::<code><nowiki>[[Category:EVAL-INT-Phylogeny]]</nowiki></code>. | |
Once the page has been saved with this tag, it is considered "submitted". | Once the page has been saved with this tag, it is considered "submitted". | ||
| Line 84: | Line 84: | ||
:* make sure that you have included all references and citations. | :* make sure that you have included all references and citations. | ||
:* When you are done with everything, add the following category tag '''to the end of page''': | :* When you are done with everything, add the following category tag '''to the end of page''': | ||
| − | + | ::<code><nowiki>[[Category:EVAL-INT-Phylogeny]]</nowiki></code>. | |
Once the page has been saved with this tag, it is considered "submitted". | Once the page has been saved with this tag, it is considered "submitted". | ||
| Line 99: | Line 99: | ||
* Put your code on a subpage of your User page on the Student Wiki; | * Put your code on a subpage of your User page on the Student Wiki; | ||
* When you are done with everything, add the following category tag '''to the end of page''': | * When you are done with everything, add the following category tag '''to the end of page''': | ||
| − | + | ::<code><nowiki>[[Category:EVAL-INT-Phylogeny]]</nowiki></code>. | |
Once the page has been saved with this tag, it is considered "submitted". | Once the page has been saved with this tag, it is considered "submitted". | ||
Revision as of 03:21, 3 November 2018
Integrator Unit: Phylogeny
(Integrator unit: calculate and analyse a phylogenetic tree)
Abstract:
This page integrates material from the learning units for working with multiple sequence alignments, and building and analysing phylogenetic trees, in a task for evaluation.
Deliverables:
- Integrator unit: Deliverables can be submitted for course marks. See below for details.
Prerequisites:
This unit builds on material covered in the following prerequisite units:
Contents
Evaluation
This "Integrator Unit" should be submitted for evaluation for a maximum of 8 marks if one of the written deliverables is chosen, resp. 16 marks for the oral exam[1].
- Please note the evaluation types that are available as options for this unit. Choose one evaluation type that you have not chosen for another Integrator Unit. (Each submitted Integrator Unit must be evaluated in a different way and one of your evaluations - but not your first one - must be an oral exam).
- Report option
- Work through the tasks described in the scenario.
- Document your results in a short report on a subpage of your User page on the Student Wiki. Describe your methods (R-code!) in an appendix;
- When you are done with everything, add the following category tag to the end of page:
[[Category:EVAL-INT-Phylogeny]].
Once the page has been saved with this tag, it is considered "submitted". Do not change your submission after this tag has been added. The page will be marked and the category tag will be removed by the instructor.
- Interview option
- Identify a laboratory whose work includes constructing and evaluating phylogenetic trees. Get in touch with the PI, a postdoc or senior graduate student in the laboratory and interview them in person or by eMail. Find out
- why this work is important;
- how they approach it methodologically;
- in particular, how they quantify the severity of an effect (get technical on that point);
- what they have recently learned;
- what the major challenges, current discussions, or controversies are.
- write up your interview on a subpage of your User page of the Student Wiki;
- add information that may be required to understand the methodology;
- make sure that you have included important literature references.
- When you are done with everything, add the following category tag to the end of page:
[[Category:EVAL-INT-Phylogeny]].
Once the page has been saved with this tag, it is considered "submitted". Do not change your submission after this tag has been added. The page will be marked and the category tag will be removed by the instructor.
- Literature research option
- Navigate to the Phylogeny Literature Research Topics page on the Student Wiki.
- Pick a topic and enter your name in the table to claim it.
- Write a report on your research. Note: this is not a review, but a report. Think of a "whitepaper", not a publication. Write to a specialist technical audience and be specific to provide actionable information.
- write your report on a subpage of your User page of the Student Wiki;
- make sure that you have included all references and citations.
- When you are done with everything, add the following category tag to the end of page:
[[Category:EVAL-INT-Phylogeny]].
Once the page has been saved with this tag, it is considered "submitted". Do not change your submission after this tag has been added. The page will be marked and the category tag will be removed by the instructor.
- Oral exam option
- Work through the tasks described in the scenario. Remember to document your work in your journal.
- Part of your task will involve writing an R script, place that code in a subpage of your User page on the Student Wiki and link to it from your Journal. (Do not add an evaluation category tag to that code).
- Your work must be complete before 21:00 on the day before your exam.
- Schedule an oral exam by editing the signup page on the Student Wiki. Enter the unit that you are signing up for, and your name. You must have signed-up for an exam slot before 21:00 on the day before your exam.
- R code option
- Work through the tasks described in the scenario and develop code as required.
- Put your code on a subpage of your User page on the Student Wiki;
- When you are done with everything, add the following category tag to the end of page:
[[Category:EVAL-INT-Phylogeny]].
Once the page has been saved with this tag, it is considered "submitted". Do not change your submission after this tag has been added. The page will be marked and the category tag will be removed by the instructor.
Contents
For the Report Option ...
Choose one of the two tasks below:
- Does masking improve the tree?
Task:
- Produce a phylogenetic tree from full-length Mbp1 orthologues for the reference species and MYSPE. Do not apply masking.
- Produce a second phylogenetic tree from full-length Mbp1 orthologues for the reference species and MYSPE. Apply masking to delete all columns that have more then 2/3 gap-characters.
- Determine which tree is "more correct" by calculating tree distances to the species tree.
- Report your findings.
- Does adding characters improve the tree?
Task:
- Produce a phylogenetic tree from full-length Mbp1 orthologues for the reference species and MYSPE. Do not apply masking.
- Produce a second phylogenetic tree only from APSES domains of Mbp1 orthologues for the reference species and MYSPE. Again, do not apply masking.
- Determine which tree is "more correct" by calculating tree distances to the species tree.
- Report your findings.
For the Oral Exam Option ...
Interpret the full APSES tree.
Task:
- Produce a phylogenetic tree from APSES domains of all proteins in myDB. This includes all APSES domain proteins from MYSPE that you have found with PSI-BLAST. (Caution: the proml program may take quite long to compute this tree. Several hours.) You will find this bit of code useful to get you started:
library(msa)
# Align all sequences in the database + KILA_ESSCO
mySeq <- myDB$protein$sequence
names(mySeq) <- myDB$protein$name
mySeq <- c(mySeq,
"IDGEIIHLRAKDGYINATSMCRTAGKLLSDYTRLKTTQEFFDELSRDMGIPISELIQSFKGGRPENQGTWVHPDIAINLAQ")
names(mySeq)[length(mySeq)] <- "KILA_ESCCO"
mySeqMSA <- msaClustalOmega(AAStringSet(mySeq)) # too many sequences for MUSCLE
# get the sequence of the SACCE APSES domain
sel <- myDB$protein$name == "MBP1_SACCE"
proID <- myDB$protein$ID[sel]
sel <- myDB$feature$ID[myDB$feature$name == "APSES fold"]
fanID <- myDB$annotation$ID[myDB$annotation$proteinID == proID &
myDB$annotation$featureID == sel]
start <- myDB$annotation$start[fanID]
end <- myDB$annotation$end[fanID]
SACCEapses <- substring(myDB$protein$sequence[proID], start, end)
# extract the APSES domains from the MSA
APSESmsa <- fetchMSAmotif(mySeqMSA, SACCEapses)
# Produce the phylogenetic tree ...- Interpret the tree with two objectives.
- (A) how many APSES domain proteins did the last common ancestor (LCA) of all fungi have?
- (B) what is the evolutionary history of the APSES domain proteins in MYSPE? Were genes lost? Did duplications occur?
- Print your tree and annotate it. Bring it to the exam and be prepared to discuss your interpretation.
For the R-code option ...
- Does adding species improve the tree?
Task:
- Produce a MSA from APSES domains of all proteins in myDB.
library(msa)
# Align all sequences in the database + KILA_ESSCO
mySeq <- myDB$protein$sequence
names(mySeq) <- myDB$protein$name
mySeq <- c(mySeq,
"IDGEIIHLRAKDGYINATSMCRTAGKLLSDYTRLKTTQEFFDELSRDMGIPISELIQSFKGGRPENQGTWVHPDIAINLAQ")
names(mySeq)[length(mySeq)] <- "KILA_ESCCO"
mySeqMSA <- msaClustalOmega(AAStringSet(mySeq)) # too many sequences for MUSCLE
# get the sequence of the SACCE APSES domain
sel <- myDB$protein$name == "MBP1_SACCE"
proID <- myDB$protein$ID[sel]
sel <- myDB$feature$ID[myDB$feature$name == "APSES fold"]
fanID <- myDB$annotation$ID[myDB$annotation$proteinID == proID &
myDB$annotation$featureID == sel]
start <- myDB$annotation$start[fanID]
end <- myDB$annotation$end[fanID]
SACCEapses <- substring(myDB$protein$sequence[proID], start, end)
# extract the APSES domains from the MSA
APSESmsa <- fetchMSAmotif(mySeqMSA, SACCEapses)- Write an R-script that does the following:
- pick ten random sequences plus the Mbp1 orthologues plus KILA_ESCCO
- remove all other sequences from the alignment
- mask all columns that have more then 80% gap characters
- produce a phylogenetic tree from this input data
- drop all tips from your tree that are not Mbp1 orthologues and not KILA_ESCCO. This code will be useful:
# assuming your new tree is called "allApsTree"
sel <- ! (allApsTree$tip.label %in% fungiTree$tip.label)
newTree <- drop.tip(allApsTree, allApsTree$tip.label[sel])- Is this tree more similar to fungiTree than apsTree was?
- Submit your script, significant data, and the results.
Notes
- ↑ Note: the oral exam will focus on the unit content but will also cover other material that leads up to it
Further reading, links and resources
If in doubt, ask! 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.
About ...
Author:
- Boris Steipe <boris.steipe@utoronto.ca>
Created:
- 2017-08-05
Modified:
- 2017-11-01
Version:
- 1.1
Version history:
- 1.1 Corrected posted marks, which were not consistent with the description in the syllabus.
- 1.0 First live version
- 0.1 First stub
This copyrighted material is licensed under a Creative Commons Attribution 4.0 International License. Follow the link to learn more.
