Difference between revisions of "BIN-SX-Domains"
m |
m |
||
Line 27: | Line 27: | ||
<div id="ABC-unit-framework"> | <div id="ABC-unit-framework"> | ||
== Abstract == | == Abstract == | ||
+ | <section begin=abstract /> | ||
<!-- included from "../components/BIN-SX-Domains.components.wtxt", section: "abstract" --> | <!-- included from "../components/BIN-SX-Domains.components.wtxt", section: "abstract" --> | ||
... | ... | ||
+ | <section end=abstract /> | ||
{{Vspace}} | {{Vspace}} | ||
Line 62: | Line 64: | ||
*<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. | *<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. | ||
<!-- included from "ABC-unit_components.wtxt", section: "deliverables-journal" --> | <!-- included from "ABC-unit_components.wtxt", section: "deliverables-journal" --> | ||
− | *<b>Journal</b>: Document your progress in your [[FND-Journal| | + | *<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 "ABC-unit_components.wtxt", section: "deliverables-insights" --> | <!-- included from "ABC-unit_components.wtxt", section: "deliverables-insights" --> | ||
− | *<b>Insights</b>: If you find something particularly noteworthy about this unit, make a note in your [[ABC-Insights|insights! page]]. | + | *<b>Insights</b>: If you find something particularly noteworthy about this unit, make a note in your [[ABC-Insights|'''insights!''' page]]. |
{{Vspace}} | {{Vspace}} |
Revision as of 17:32, 7 September 2017
Structure domains
Keywords: Structural domains, domain databases - CATH, SCOP, cDART
Contents
This unit is under development. There is some contents here but it is incomplete and/or may change significantly: links may lead to nowhere, the contents is likely going to be rearranged, and objectives, deliverables etc. may be incomplete or missing. Do not work with this material until it is updated to "live" status.
Abstract
...
This unit ...
Prerequisites
You need to complete the following units before beginning this one:
Objectives
...
Outcomes
...
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.
Evaluation
Evaluation: NA
- This unit is not evaluated for course marks.
Contents
Task:
- Read the introductory notes on protein domains defined by 3D structure analysis.
APSES domains in Chimera (from A4)
What precisely constitutes an APSES domain however is a matter of definition, as you can explore in the following (optional) task.
- Display the protein in ribbon style, e.g. with the Interactive 1 preset.
- Access the Interpro information page for Mbp1 at the EBI: http://www.ebi.ac.uk/interpro/protein/P39678
- In the section Domains and repeats, mouse over the red annotations and note down the residue numbers for the annotated domains. Also follow the links to the respective Interpro domain definition pages.
At this point we have definitions for the following regions on the Mbp1 protein ...
- The KilA-N (pfam 04383) domain definition as applied to the Mbp1 protein sequence by CDD;
- The InterPro KilA, N-terminal/APSES-type HTH, DNA-binding (IPR018004) definition annotated on the Mbp1 sequence;
- The InterPro Transcription regulator HTH, APSES-type DNA-binding domain (IPR003163) definition annotated on the Mbp1 sequence;
- (... in addition – without following the source here – the UniProt record for Mbp1 annotates a "HTH APSES-type" domain from residues 5-111)
... each with its distinct and partially overlapping sequence range. Back to Chimera:
- In the sequence window, select the sequence corresponding to the Interpro KilA-N annotation and colour this fragment red. Remember that you can get the sequence numbers of a residue in the sequence window when you hover the pointer over it - but do confirm that the sequence numbering that Chimera displays matches the numbering of the Interpro domain definition.
- Then select the residue range(s) by which the CDD KilA-N definition is larger, and colour that fragment orange.
- Then select the residue range(s) by which the InterPro APSES domain definition is larger, and colour that fragment yellow.
- If the structure contains residues outside these ranges, colour these white.
- Study this in a side-by-side stereo view and get a sense for how the extra sequence beyond the Kil-A N domain(s) is part of the structure, and how the integrity of the folded structure would be affected if these fragments were missing.
- Display Hydrogen bonds, to get a sense of interactions between residues from the differently colored parts. First show the protein as a stick model, with sticks that are thicker than the default to give a better sense of sidechain packing:
- (i) Select → Select all
- (ii) Actions → Ribbon → hide
- (iii) Select → Structure → protein
- (iv) Actions → Atoms/Bonds → show
- (v) Actions → Atoms/Bonds → stick
- (vi) click on the looking glass icon at the bottom right of the graphics window to bring up the inspector window and choose Inspect ... Bond. Change the radius to 0.4.
- (i) Select → Select all
- Then calculate and display the hydrogen bonds:
- (vii) Tools → Surface/Binding Analysis → FindHbond
- (viii) Set the Line width to 3.0, leave all other parameters with their default values an click Apply
- Clear the selection.
- (vii) Tools → Surface/Binding Analysis → FindHbond
- Let's now simplify the scene a bit and focus on backbone/backbone H-bonds:
- (ix) Select → Structure → Backbone → full
- (x) Actions → Atoms/Bonds → show only
- Clear the selection.
- (ix) Select → Structure → Backbone → full
- Save the resulting image as a jpeg no larger than 600px across and upload it to your Lab notebook on the Wiki.
- When you are done, congratulate yourself on having earned a bonus of 10% on the next quiz.
There is a rather important lesson in this: domain definitions may be fluid, and their boundaries may be computationally derived from sequence comparisons across many families, and do not necessarily correspond to individual structures. Make sure you understand this well.
}}
Given this, it seems appropriate to search the sequence database with the sequence of an Mbp1 structure–this being a structured, stable, subdomain of the whole that presumably contains the protein's most unique and specific function. Let us retrieve this sequence. All PDB structures have their sequences stored in the NCBI protein database. They can be accessed simply via the PDB-ID, which serves as an identifier both for the NCBI and the PDB databases. However there is a small catch (isn't there always?). PDB files can contain more than one protein, e.g. if the crystal structure contains a complex[1]. Each of the individual proteins gets a so-called chain ID–a one letter identifier– to identify them uniquely. To find their unique sequence in the database, you need to know the PDB ID as well as the chain ID. If the file contains only a single protein (as in our case), the chain ID is always A
[2]. make sure you understand the concept of protein chains, and chain IDs.
Further reading, links and resources
Notes
- ↑ Think of the ribosome or DNA-polymerase as extreme examples.
- ↑ Otherwise, you need to study the PDB Web page for the structure, or the text in the PDB file itself, to identify which part of the complex is labeled with which chain ID. For example, immunoglobulin structures some time label the light- and heavy chain fragments as "L" and "H", and sometimes as "A" and "B"–there are no fixed rules. You can also load the structure in VMD, color "by chain" and use the mouse to click on residues in each chain to identify it.
Self-evaluation
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-08-05
Version:
- 0.1
Version history:
- 0.1 First stub
This copyrighted material is licensed under a Creative Commons Attribution 4.0 International License. Follow the link to learn more.