Difference between revisions of "BIN-ALI-Optimal sequence alignment"
m |
m |
||
Line 1: | Line 1: | ||
<div id="ABC"> | <div id="ABC"> | ||
− | <div style="padding:5px; border:1px solid #000000; background-color:# | + | <div style="padding:5px; border:1px solid #000000; background-color:#b3dbce; font-size:300%; font-weight:400; color: #000000; width:100%;"> |
Optimal global and local sequence alignment | Optimal global and local sequence alignment | ||
− | <div style="padding:5px; margin-top:20px; margin-bottom:10px; background-color:# | + | <div style="padding:5px; margin-top:20px; margin-bottom:10px; background-color:#b3dbce; font-size:30%; font-weight:200; color: #000000; "> |
(NWS (optimal global) and SW (optimal local) algorithms, alignment via EMBOSS tools in practice, interpretation of alignments) | (NWS (optimal global) and SW (optimal local) algorithms, alignment via EMBOSS tools in practice, interpretation of alignments) | ||
</div> | </div> | ||
Line 10: | Line 10: | ||
− | <div style="padding:5px; border:1px solid #000000; background-color:# | + | <div style="padding:5px; border:1px solid #000000; background-color:#b3dbce33; font-size:85%;"> |
<div style="font-size:118%;"> | <div style="font-size:118%;"> | ||
<b>Abstract:</b><br /> | <b>Abstract:</b><br /> | ||
Line 60: | Line 60: | ||
− | |||
{{Smallvspace}} | {{Smallvspace}} | ||
Line 80: | Line 79: | ||
{{Task|1= | {{Task|1= | ||
− | *Read the introductory notes on {{ABC-PDF|BIN-ALI-Optimal_sequence_alignment| | + | *Read the introductory notes on {{ABC-PDF|BIN-ALI-Optimal_sequence_alignment|concepts of optimal sequence alignment}}. |
}} | }} | ||
Line 99: | Line 98: | ||
* Fetch the sequences for <code>MBP1_SACCE</code> and <code>MBP1_MYSPE</code> from your database that you have prepared in the [[BIN-Storing_data]] unit. Open the RStudio project and enter the code below - substituting the proper name for MYSPE where appropriate. | * Fetch the sequences for <code>MBP1_SACCE</code> and <code>MBP1_MYSPE</code> from your database that you have prepared in the [[BIN-Storing_data]] unit. Open the RStudio project and enter the code below - substituting the proper name for MYSPE where appropriate. | ||
− | < | + | <pre> |
source("makeProteinDB.R") | source("makeProteinDB.R") | ||
Line 110: | Line 109: | ||
myDB$protein$RefSeqID[sel] | myDB$protein$RefSeqID[sel] | ||
− | </ | + | </pre> |
− | (If this didn't work, fix | + | (If this didn't work, fix the problem. Did you give your sequence the right '''name''' in your database?) |
# Access the [https://www.ebi.ac.uk/Tools/emboss/ EMBOSS tools page] at the EBI. | # Access the [https://www.ebi.ac.uk/Tools/emboss/ EMBOSS tools page] at the EBI. | ||
Line 128: | Line 127: | ||
# Study the results. You will find that the alignment extends over the entire protein, likely with significant ''indels'' at the termini. | # Study the results. You will find that the alignment extends over the entire protein, likely with significant ''indels'' at the termini. | ||
}} | }} | ||
− | |||
Line 147: | Line 145: | ||
{{Vspace}} | {{Vspace}} | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
== Further reading, links and resources == | == Further reading, links and resources == | ||
{{#pmid: 10782117}} | {{#pmid: 10782117}} | ||
Line 183: | Line 164: | ||
:2017-08-05 | :2017-08-05 | ||
<b>Modified:</b><br /> | <b>Modified:</b><br /> | ||
− | : | + | :2020-09-24 |
<b>Version:</b><br /> | <b>Version:</b><br /> | ||
− | :1. | + | :1.1 |
<b>Version history:</b><br /> | <b>Version history:</b><br /> | ||
+ | *1.1 2020 Updates | ||
*1.0 First live | *1.0 First live | ||
*0.1 First stub | *0.1 First stub | ||
Line 195: | Line 177: | ||
[[Category:ABC-units]] | [[Category:ABC-units]] | ||
{{UNIT}} | {{UNIT}} | ||
− | {{ | + | {{LIVE}} |
</div> | </div> | ||
<!-- [END] --> | <!-- [END] --> |
Latest revision as of 11:28, 25 September 2020
Optimal global and local sequence alignment
(NWS (optimal global) and SW (optimal local) algorithms, alignment via EMBOSS tools in practice, interpretation of alignments)
Abstract:
This unit covers the concepts and algorithms for optimal pairwise sequence alignments.
Objectives:
|
Outcomes:
|
Deliverables:
- Your protein database
- Add APSES domain annotations for MBP1_MYSPE proteins to your database.
Prerequisites:
This unit builds on material covered in the following prerequisite units:
Contents
Evaluation
Evaluation: NA
Contents
Pairwise Alignments: Optimal
Task:
- Read the introductory notes on concepts of optimal sequence alignment.
Optimal pairwise sequence alignment is the mainstay of sequence comparison. To try our first alignments in practice, we will start with aligning Mbp1 and its MYSPE relative. For simplicity, I will call the two proteins MBP1_SACCE
and MBP1_MYSPE
through the remainder of the unit.
Optimal Sequence Alignment: EMBOSS online tools
EMBOSS tools are a collection of standard sequence analysis programs. The most important ones are hosted at the EBI, but the EMBOSS explorer site hosts many more. They offer Needlman-Wunsch and Smith-Waterman alignments.
Task:
- Fetch the sequences for
MBP1_SACCE
andMBP1_MYSPE
from your database that you have prepared in the BIN-Storing_data unit. Open the RStudio project and enter the code below - substituting the proper name for MYSPE where appropriate.
source("makeProteinDB.R") # Print the MBP1_SACCE sequence sel <- myDB$protein$name == "MBP1_SACCE" myDB$protein$sequence[sel] # Print the MBP1_MYSPE sequence sel <- myDB$protein$name == paste0("MBP1_", biCode(MYSPE)) myDB$protein$RefSeqID[sel]
(If this didn't work, fix the problem. Did you give your sequence the right name in your database?)
- Access the EMBOSS tools page at the EBI.
- Look for Water, click on protein, paste your sequences and run the program with default parameters.
- Study the results. You will probably find that the alignment extends over most of the protein, but does not include the termini.
- Considering the sequence identity cutoff we discussed in class (25% over the length of a domain), do you believe that the N-terminal domains (the APSES domains) are homologous?
- Change the Gap opening and Gap extension parameters to high values (e.g. 25 and 5). Then run the alignment again.
- Note what is different.
Global optimal sequence alignment using "needle"
Task:
- Look for Needle, click on protein, paste the
MBP1_SACCE
andMBP1_MYSPE
sequences again and run the program with default parameters. - Study the results. You will find that the alignment extends over the entire protein, likely with significant indels at the termini.
Optimal Sequence Alignment with R: Biostrings
Biostrings has extensive functions for sequence alignments. They are generally well written and tightly integrated with the rest of Bioconductor's functions. There are a few quirks however: for example alignments won't work with lower-case sequences[1].
Task:
- Open RStudio and load the
ABC-units
R project. If you have loaded it before, choose File → Recent projects → ABC-Units. If you have not loaded it before, follow the instructions in the RPR-Introduction unit. - Choose Tools → Version Control → Pull 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-ALI-Optimal_sequence_alignment.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
Fitch (2000) Homology a personal view on some of the problems. Trends Genet 16:227-31. (pmid: 10782117) |
[ PubMed ] [ DOI ] There are many problems relating to defining the terminology used to describe various biological relationships and getting agreement on which definitions are best. Here, I examine 15 terminological problems, all of which are current, and all of which relate to the usage of homology and its associated terms. I suggest a set of definitions that are intended to be totally consistent among themselves and also as consistent as possible with most current usage. |
Notes
- ↑ While this seems like an unnecessary limitation, given that we could easily write such code to transform to-upper when looking up values in the MDM, perhaps it is meant as an additional sanity check that we haven't inadvertently included text in the sequence that does not belong there, such as the FASTA header line.
About ...
Author:
- Boris Steipe <boris.steipe@utoronto.ca>
Created:
- 2017-08-05
Modified:
- 2020-09-24
Version:
- 1.1
Version history:
- 1.1 2020 Updates
- 1.0 First live
- 0.1 First stub
This copyrighted material is licensed under a Creative Commons Attribution 4.0 International License. Follow the link to learn more.