Difference between revisions of "Bioinformatics Introduction Structure"

From "A B C"
Jump to navigation Jump to search
m
 
(2 intermediate revisions by the same user not shown)
Line 13: Line 13:
  
 
{{Vspace}}
 
{{Vspace}}
 
<div class="alert">
 
 
Warning – this page is currently under construction (2016-12-26).
 
 
Do not use before this warning has been removed.
 
 
</div>
 
  
 
{{Vspace}}
 
{{Vspace}}
Line 470: Line 462:
  
 
{{task|1=
 
{{task|1=
* Confirm the MSA for APSES domain sequences in Mbp1 orthologues with the section <code>PART SIX: APSES DOMAIN SEQUENCES OF MBP1 ORTHOLOGUES</code> of the <code>Structure.R<M/code> script.
+
* Confirm the MSA for APSES domain sequences in Mbp1 orthologues with the section <code>PART SIX: APSES DOMAIN SEQUENCES OF MBP1 ORTHOLOGUES</code> of the <code>Structure.R</code> script.
  
 
}}
 
}}
Line 517: Line 509:
  
  
We have spent a significant amount of time to prepare data for the analysis and in practice it usually seems to turn out that way, that the preparation of data occupies the greatest part of our efforts. The actual computational analysis is generally quite fast. And, unfortunately, the '''interpretation of results''' is often somewhat neglected. Don't be that way. Data does not explain itself. The interpreattion of your computational results is the most important part.
+
We have spent a significant amount of time to prepare data for the analysis and in practice it usually seems to turn out that way, that the preparation of data occupies the greatest part of our efforts. The actual computational analysis is generally quite fast. And, unfortunately, the '''interpretation of results''' is often somewhat neglected. Don't be that way. Data does not explain itself. The interpretation of your computational results is the most important part.
  
 
We will look at our homology model with two different questions:
 
We will look at our homology model with two different questions:
Line 524: Line 516:
 
* Can we tell which residues are conserved for functional reasons, rather than for structural reasons?
 
* Can we tell which residues are conserved for functional reasons, rather than for structural reasons?
  
 +
{{Vspace}}
  
&nbsp;
+
=== The PDB file ===
&nbsp;
 
  
=== The PDB file ===
 
&nbsp;<br>
 
  
 
{{task|1=
 
{{task|1=
Line 540: Line 530:
 
}}
 
}}
  
 +
As you have seen above, SwissModel numbers the first residue "1" and does not keep the numbering of the template. We should renumber the model so we can compare the model and the template with the same residue numbers. Carefully doing this by hand should not even take you a whole hour. You just need to edit all the residue numbers in a text editor to give the first residue the number "4" and increment numbers from there.
  
===R code: renumbering the model ===
+
Or we could do this with an '''R''' script.
 
 
As you have seen above, SwissModel numbers the first residue "1" and does not keep the numbering of the template. We should renumber the model so we can compare the model and the template with the same residue numbers. (An alternative renumbering would renumber the model correspond to the sequence it came from. Remember that we have only excised a domain from the full-length sequence.) Carefully doing this by hand will take you a bit less than an hour. Fortunately there is a very useful R package that will help: '''bio3d'''.
 
  
 
{{task|1=
 
{{task|1=
# Navigate to the [http://thegrantlab.org/bio3d/index.php '''bio3D'''] home page to . '''bio3d''' has recently been made available via CRAN - previously it had to be compiled from source.
+
* Renumber your '''model''' PDB file to start with residue number 4 with the code in section <code>PART SEVEN: RENUMBERING THE MODEL</code> of the <code>Structure.R</code> script.
 
 
 
 
 
 
# Explore and execute the following '''R''' script. I am assuming that your model is in your <code>PROJECTDIR</code> folder, change paths and filenames as required.
 
 
 
<source lang="rsplus">
 
 
 
setwd(PROJECTDIR)
 
PDB_INFILE      <- "YFOmodel.pdb"
 
PDB_OUTFILE    <- "YFOmodelRenumbered.pdb"
 
 
 
 
 
# The bio3d package provides functions for working with
 
# protein structures in R
 
if (!require(bio3d, quietly=TRUE)) {
 
install.packages("bio3d")
 
library(bio3d)
 
}
 
 
 
# == Read the YFO pdb file
 
  
iFirst <- 4  # residue number for the first residue
 
 
YFOmodel <- read.pdb(PDB_INFILE) # read the PDB file into a list
 
 
YFOmodel          # examine the information
 
YFOmodel$atom[1,]  # get information for the first atom
 
 
# Explore ?read.pdb and study the examples.
 
 
# == Modify residue numbers for each atom
 
resNum <- as.numeric(YFOmodel $atom[,"resno"])
 
resNum 
 
resNum <- resNum - resNum[1] + iFirst  # add offset
 
YFOmodel $atom[ , "resno"] <- resNum  # replace old numbers with new
 
 
# check result
 
YFOmodel $atom[ , "resno"]
 
YFOmodel $atom[1, ]
 
 
# == Write output to file
 
write.pdb(pdb = YFOmodel, file=PDBout)
 
 
# Done. Open the PDB file you have written in a text editor
 
# and confirm that this has worked.
 
 
 
</source>
 
 
}}
 
}}
  
 
+
{{Vspace}}
&nbsp;
 
 
 
  
 
===First visualization===
 
===First visualization===
 
&nbsp;<br>
 
  
 
Since a homology model inherits its structural details from the '''template''', your model of the YFO sequence should look very similar to the original 1BM8 structure.
 
Since a homology model inherits its structural details from the '''template''', your model of the YFO sequence should look very similar to the original 1BM8 structure.
Line 612: Line 550:
 
# In the '''Favourites''' &rarr; '''Model Panel''' window you can switch between the two molecules.
 
# In the '''Favourites''' &rarr; '''Model Panel''' window you can switch between the two molecules.
 
# Hide the ribbon and choose '''backbone only &rarr; full'''. You will note that the backbone of the two structures is virtually identical.  
 
# Hide the ribbon and choose '''backbone only &rarr; full'''. You will note that the backbone of the two structures is virtually identical.  
# Next, choose '''Actions &rarr; Atoms/Bonds &rarr; show''' to display display the two molecules in a stick style and note how the sidechains have been modeled. Note especially how sidechain coordinates have been guessed, where the template had shorter sidechains than the target. It may be more clear if you hide H-atoms: '''Select &rarr; Chemistry &rarr; Element &rarr; H''' and '''Actions &rarr; Atoms/Bonds &rarr; hide'''
+
# Next, choose '''Actions &rarr; Atoms/Bonds &rarr; show''' to display the two molecules in a stick style and note how the sidechains have been modeled. Note especially how sidechain coordinates have been guessed, where the template had shorter sidechains than the target. It may be more clear if you hide H-atoms: '''Select &rarr; Chemistry &rarr; Element &rarr; H''' and '''Actions &rarr; Atoms/Bonds &rarr; hide'''
 
# Display only residue 50 to 74 to focus on the putative helix-turn-helix domain. You can drag your mouse in the  '''Favourites &rarr; Sequence''', window to select the range then '''Select &rarr; Invert (selected model)''' and '''Actions &rarr; Atoms/Bonds &rarr; hide'''. Or you can use Chimera's commandline: <code>~display</code> to undisplay everything, <code>show #:50-74</code> to show this residue range for all models.  
 
# Display only residue 50 to 74 to focus on the putative helix-turn-helix domain. You can drag your mouse in the  '''Favourites &rarr; Sequence''', window to select the range then '''Select &rarr; Invert (selected model)''' and '''Actions &rarr; Atoms/Bonds &rarr; hide'''. Or you can use Chimera's commandline: <code>~display</code> to undisplay everything, <code>show #:50-74</code> to show this residue range for all models.  
# Study the result: a model of the HTH subdomain of YFO's RBM to Mbp1.
+
# Study the result: a model of the HTH subdomain of Mbp1_SPIPU.
 
}}
 
}}
  
  
&nbsp;
+
{{Vspace}}
  
==Coloring the model by energy ==
+
===Coloring the model by energy ===
  
 
SwissModel calculates energies for each residue of the model with a molecular mechanics forcefield. The SwissModel modeling summary page contains a plot of these energies as a function of sequence number like. The values - between 0.0 and 1.0 - are stored in the PDB file's B-factor field.
 
SwissModel calculates energies for each residue of the model with a molecular mechanics forcefield. The SwissModel modeling summary page contains a plot of these energies as a function of sequence number like. The values - between 0.0 and 1.0 - are stored in the PDB file's B-factor field.
Line 631: Line 569:
 
}}
 
}}
  
Study the options of this window a bit, rendering by attribute is a powerful way to store and depict all manners of information with the molecule. You can simply write a little R script that uses bio3D to replace the B-factor or occupancy values with any value you might be interested in: energies, conservation scores, information ... whatever. Then render this property to map it on the 3D structure of your molecule...
+
{{Vspace}}
  
 
+
{{Vspace}}
&nbsp;
 
 
 
 
 
&nbsp;
 
  
 
==Modelling DNA binding==
 
==Modelling DNA binding==
Line 645: Line 579:
 
Since there is currently no software available that would reliably model such a complex from first principles<ref>''Rosetta'' may get the structure approximately right, ''Autodock'' may get the complex approximately right, but the coordinate changes involved in induced fit makes the result unreliable - and we have no good way to validate whether the predicted complex is correct. </ref>, we will base a model of  a bound complex on homology modelling as well. This means we need to find a similar structure for which the position of bound DNA is known, then superimpose that structure with our model. This places the DNA molecule into the spatial context of the model we are studying. It so happens that early in 2015 an APSES domain structure with bound DNA was published. You probably noticed it as a result of the PDB BLAST search: [http://www.rcsb.org/pdb/explore/explore.do?structureId=4UX5 '''4UX5'''], from the ''Magnaporthe oryzae'' Mbp1 orhologue PCG2<ref>{{#pmid: 25550425}}</ref>.  
 
Since there is currently no software available that would reliably model such a complex from first principles<ref>''Rosetta'' may get the structure approximately right, ''Autodock'' may get the complex approximately right, but the coordinate changes involved in induced fit makes the result unreliable - and we have no good way to validate whether the predicted complex is correct. </ref>, we will base a model of  a bound complex on homology modelling as well. This means we need to find a similar structure for which the position of bound DNA is known, then superimpose that structure with our model. This places the DNA molecule into the spatial context of the model we are studying. It so happens that early in 2015 an APSES domain structure with bound DNA was published. You probably noticed it as a result of the PDB BLAST search: [http://www.rcsb.org/pdb/explore/explore.do?structureId=4UX5 '''4UX5'''], from the ''Magnaporthe oryzae'' Mbp1 orhologue PCG2<ref>{{#pmid: 25550425}}</ref>.  
  
 
+
{{Vspace}}
<!-- But can we also find (and align) distant relatives based purely on '''structural similarity''', ideally a protein-DNA complex? -->
 
 
 
  
 
===A homologous protein/DNA complex structure===
 
===A homologous protein/DNA complex structure===
Line 678: Line 610:
 
}}
 
}}
  
 
+
{{Vspace}}
 
 
&nbsp;
 
  
 
===Superimposing your model===
 
===Superimposing your model===
  
 
Both your homology model and the template structure provide valuable information:
 
Both your homology model and the template structure provide valuable information:
 +
 
* The template structure shows how conserved the structure is at the protein/DNA interface. You have seen what subtle differences can give rise to a sequence specific complex and a non-specific binding mode. For Mbp1 we know that the APSES domain binds to the same cognate DNA sequence as PCG2. Since your model structure is heavily biased towards the template, evaluating the template in the context of a real protein/DNA complex allows you to judge which binding residues appear to be conserved and possibly modelled in an orientation that is productive for binding.
 
* The template structure shows how conserved the structure is at the protein/DNA interface. You have seen what subtle differences can give rise to a sequence specific complex and a non-specific binding mode. For Mbp1 we know that the APSES domain binds to the same cognate DNA sequence as PCG2. Since your model structure is heavily biased towards the template, evaluating the template in the context of a real protein/DNA complex allows you to judge which binding residues appear to be conserved and possibly modelled in an orientation that is productive for binding.
  
Line 694: Line 625:
  
 
* We need to visualize and evaluate differences in binding between different proteins and for me it works well to colour everything by element, and give the carbon atoms some identifying, distinct colour. This is best achieved through the Chimera command line that you can turn on with the little "computer" icon on the left-hand side of the graphics window. Have a look at the [https://www.cgl.ucsf.edu/chimera/docs/UsersGuide/framecommand.html Chimera Users guide], and choose '''select''' to learn how Chimera's selection syntax works.  
 
* We need to visualize and evaluate differences in binding between different proteins and for me it works well to colour everything by element, and give the carbon atoms some identifying, distinct colour. This is best achieved through the Chimera command line that you can turn on with the little "computer" icon on the left-hand side of the graphics window. Have a look at the [https://www.cgl.ucsf.edu/chimera/docs/UsersGuide/framecommand.html Chimera Users guide], and choose '''select''' to learn how Chimera's selection syntax works.  
* Open the Model Panel to check which protein has which Chimera-internal model number. Then you can use the following selection syntax. Instead of the model numbers, I will type <code>&lt;YFO&gt;</code>, <code>&lt;4ux5&gt;</code>, and <code>&lt;1BM8&gt;</code> - you will certainly know by now that these are placeholder labels and you need to replace them with the numbers <code>0</code>, <code>1</code>, and <code>2</code> instead.
+
* Open the Model Panel to check which protein has which Chimera-internal model number. Then you can use the following selection syntax. Instead of the model numbers, I will type <code>&lt;SPIPU&gt;</code>, <code>&lt;4ux5&gt;</code>, and <code>&lt;1BM8&gt;</code> - you will certainly know by now that these are placeholder labels and you need to replace them with the numbers <code>0</code>, <code>1</code>, and <code>2</code> instead.
  
 
:* To colour the DNA carbon atoms white, type:<br />
 
:* To colour the DNA carbon atoms white, type:<br />
Line 705: Line 636:
 
::<code>~display #&lt;4ux5&gt;:.B</code> <small>Note: this is the tilde character, not a hyphen or minus sign.</small>
 
::<code>~display #&lt;4ux5&gt;:.B</code> <small>Note: this is the tilde character, not a hyphen or minus sign.</small>
  
:* To colour the YFO model carbon atoms a pale reddish color, type:<br />
+
:* To colour the SPIPU model carbon atoms a pale reddish color, type:<br />
::<code>color #b06268 #&lt;YFO&gt; & C</code>
+
::<code>color #b06268 #&lt;SPIPU&gt; & C</code>
  
 
:* To colour the 1BM8 structure carbon atoms a pale greenish color, type:<br />
 
:* To colour the 1BM8 structure carbon atoms a pale greenish color, type:<br />
Line 714: Line 645:
 
** Select all models in the Model Panel and click on '''match'''.
 
** Select all models in the Model Panel and click on '''match'''.
 
** Set 4ux5 Chain A as the Reference chain.
 
** Set 4ux5 Chain A as the Reference chain.
** Select YFO as a '''Chain to match''', select the button for specific reference and specific match, and click '''Apply'''.
+
** Select SPIPU as a '''Chain to match''', select the button for specific reference and specific match, and click '''Apply'''.
 
** Repeat this with 1BM8 as the match chain.
 
** Repeat this with 1BM8 as the match chain.
  
* Easy. Now enlarge the binding site. Remember that 4ux5 and 1bm8 are independently determined crystal structures, wheres YFO was modelled on 1bm8 and is expected to be '''very''' similar to it. To give you some guidance what you should focus on, select 4ux5 residue 84 CA atom and display it as '''Ball & Stick'''. You can also repeat the '''Action''' "Set Pivot in case the pivot has shifted.
+
* Easy. Now enlarge the binding site. Remember that 4ux5 and 1bm8 are independently determined crystal structures, wheres SPIPU was modelled on 1bm8 and is expected to be '''very''' similar to it. To give you some guidance what you should focus on, select 4ux5 residue 84 CA atom and display it as '''Ball & Stick'''. You can also repeat the '''Action''' "Set Pivot in case the pivot has shifted.
  
 
* Study the scene. This is where stereo- vision will help '''a lot'''.
 
* Study the scene. This is where stereo- vision will help '''a lot'''.
Line 726: Line 657:
  
 
* Now turn the display of 4ux5 chain B back on and turn chain A off instead. Then superimpose the 1BM8 template and your model on Chain B.  
 
* Now turn the display of 4ux5 chain B back on and turn chain A off instead. Then superimpose the 1BM8 template and your model on Chain B.  
 
  
 
* Again, focus on the binding region. What do you think of that? What would you have expected? Do you see a difference? What does this all mean?
 
* Again, focus on the binding region. What do you think of that? What would you have expected? Do you see a difference? What does this all mean?
Line 733: Line 663:
 
}}
 
}}
  
 +
{{Vspace}}
  
Nb. I haven't seen this before and I am completely intrigued by the results. In fact, I think I understand the protein much, much better now through this exercise. I'm very pleased how this turned out.
+
{{Vspace}}
 
 
  
 
&nbsp;
 
  
 
== Links and resources ==
 
== Links and resources ==
 
:* [http://www.wwpdb.org/documentation/format23/v2.3.html '''PDB file format'''] (see the Coordinate Section if you are unsure about chain identifiers)
 
:* [http://en.wikipedia.org/wiki/Structural_alignment Wikipedia on '''Structural Superposition'''] <small>(although the article is called "Structural Alignment")</small>
 
 
  
 
=== The DNA binding site ===
 
=== The DNA binding site ===
Line 769: Line 693:
  
  
 
===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.
 
 
 
<div class="mw-collapsible mw-collapsed" data-expandtext="Expand" data-collapsetext="Collapse" style="border:#000000 solid 1px; padding: 10px; margin-left:25px; margin-right:25px;">Optional: Load the structure in Chimera, like you did in the last assignment and switch on stereo viewing ... (more) <div  class="mw-collapsible-content">
 
<ol start="7">
 
<li>Display the protein in ribbon style, e.g. with the '''Interactive 1''' preset.
 
<li>Access the '''Interpro''' information page for Mbp1 at the EBI: http://www.ebi.ac.uk/interpro/protein/P39678
 
<li>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.
 
</ol>
 
 
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;
 
*<small>(... in addition &ndash; without following the source here &ndash; the UniProt record for Mbp1 annotates a "HTH APSES-type" domain from residues 5-111)</small>
 
 
... each with its distinct and partially overlapping sequence range. Back to Chimera:
 
 
<!-- For reference:
 
1MB1: 3-100
 
2BM8: 4-102
 
CDD KilA-N: 19-93
 
InterPro KilA-N: 23-88
 
InterPro APSES: 3-133
 
Uniprot HTH/APSES: 5-111
 
-->
 
 
<ol start="10">
 
<li>In the sequence window, select the sequence corresponding to the '''Interpro KilA-N''' annotation and colour this fragment red. <small>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.</small></li>
 
 
<li>Then select the residue range(s) by which the '''CDD KilA-N''' definition is larger, and colour that fragment orange.</li>
 
 
<li>Then select the residue range(s) by which the '''InterPro APSES domain''' definition is larger, and colour that fragment yellow.</li>
 
 
<li>If the structure contains residues outside these ranges, colour these white.</li>
 
 
<li>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.</li>
 
 
<li>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:<br />
 
::(i) '''Select''' &rarr; '''Select all''' <br />
 
::(ii) '''Actions''' &rarr; '''Ribbon''' &rarr; '''hide''' <br />
 
::(iii) '''Select''' &rarr; '''Structure''' &rarr; '''protein''' <br />
 
::(iv) '''Actions''' &rarr; '''Atoms/Bonds''' &rarr; '''show''' <br />
 
::(v)  '''Actions''' &rarr; '''Atoms/Bonds''' &rarr; '''stick''' <br />
 
::(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.<br />
 
</li>
 
 
<li>Then calculate and display the hydrogen bonds:<br />
 
::(vii) '''Tools''' &rarr; '''Surface/Binding Analysis''' &rarr; '''FindHbond''' <br />
 
::(viii) Set the '''Line width''' to 3.0, leave all other parameters with their default values an click '''Apply'''<br />
 
:: Clear the selection.<br />
 
Study this view, especially regarding side chain H-bonds. Are there many? Do side chains interact more with other sidechains, or with the backbone?
 
</li>
 
 
<li>Let's now simplify the scene a bit and focus on backbone/backbone H-bonds:<br />
 
::(ix) '''Select''' &rarr; '''Structure''' &rarr; '''Backbone''' &rarr; '''full'''<br />
 
::(x)  '''Actions''' &rarr; '''Atoms/Bonds''' &rarr; '''show only'''<br /><br />
 
:: Clear the selection.<br />
 
In this way you can appreciate how H-bonds build secondary structure - &alpha;-helices and &beta;-sheets - and how these interact with each other ... in part '''across the KilA N boundary'''.
 
</li>
 
 
 
<li>Save the resulting image as a jpeg no larger than 600px across and upload it to your Lab notebook on the Wiki.</li>
 
<li>When you are done, congratulate yourself on having earned a bonus of 10% on the next quiz.</li>
 
</ol>
 
 
</div>
 
</div>
 
 
 
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&ndash;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<ref>Think of the [http://www.pdb.org/pdb/101/motm.do?momID=121 ribosome] or [http://www.pdb.org/pdb/101/motm.do?momID=3 DNA-polymerase] as extreme examples.</ref>. Each of the individual proteins gets a so-called '''chain ID'''&ndash;a one letter identifier&ndash; 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 '''<code>A</code>'''<ref>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"&ndash;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.</ref>. make sure you understand the concept of protein chains, and chain IDs.
 
 
 
 
 
 
 
 
 
&nbsp;
 
 
=== Chimera "sequence": implicit or explicit ? ===
 
 
We discussed the distinction between implicit and explicit sequence. But which one does the Chimera sequence window display? Let's find out.
 
 
{{task|1=
 
# Open Chimera and load the 1BM8 structure from the PDB.
 
# Save the ccordinate file with '''File''' &rarr; '''Save PDB ...''', use a filename of <code>test.pdb</code>.
 
# Open this file in a '''plain text''' editor: notepad, TextEdit, nano or the like, but not MS Word! Make sure you view the file in a '''fixed-width font''', not proportionally spaced, i.e. Courier, not Arial. Otherwise the columns in the file won't line up.
 
# Find the records that begin with <code>SEQRES  ...</code> and confirm that the first amino acid is <code>GLN</code>.
 
# Now scroll down to the <code>ATOM  </code> section of the file. Identify the records for the first residue in the structure. Delete all lines for side-chain atoms except for the <code>CB</code> atom. This changes the coordinates for glutamine to those of alanine.
 
# Replace the <code>GLN</code> residue name with <code>ALA</code> (uppercase). This relabels the residue as Alanine in the coordinate section. Therefore you have changed the '''implicit''' sequence. Implicit and explicit sequence are now different. The second atom record should now look like this:<br />
 
:<code>ATOM      2  CA  ALA A  4      -0.575  5.127  16.398  1.00 51.22          C</code>
 
<ol start="7">
 
<li>Save the file and load it in Chimera.
 
<li>Open the sequence window: does it display <code>Q</code> or <code>A</code> as the first reside?
 
</ol>
 
 
Therefore, does Chimera use the '''implicit''' or '''explicit''' sequence in the sequence window?
 
 
}}
 
 
==Coloring by conservation==
 
 
With VMD, you can import a sequence alignment into the MultiSeq extension and color residues by conservation. The protocol below assumes that an MSA exists - you could have produced it in many different ways, for convenience, I have precalculated one for you. This may not contain the sequences from YFO, if you are curious about these you are welcome to add them and realign.
 
 
{{task|1=
 
;Load the Mbp1 APSES alignment into MultiSeq.
 
 
# Access [[Reference alignment for APSES domains (MUSCLE, reference species)|the set of MUSCLE aligned and edited fungal APSES domains]].
 
# Copy the alignment and save it into a convenient directory on your computer as a plain text file. Give it the extension <code>.aln</code> .
 
# Open VMD and load the <code>1BM8</code> structure.
 
# As usual, turn the axes off and display your structure in side-by-side stereo.
 
# Visualize the structure as '''New Cartoon''' with '''Index''' coloring to re-orient yourself. Identify the recognition helix and the "wing".
 
# Open '''Extensions &rarr; Analysis &rarr; Multiseq'''.
 
# You can answer '''No''' to download metadata databases, we won't need them here.
 
# In the MultiSeq Window, navigate to '''File &rarr; Import Data...'''; Choose "From Files" and '''Browse''' to the location of the alignment you have saved. The File navigation window gives you options which files to enable: choose to '''Enable <code>ALN</code>''' files (these are CLUSTAL formatted multiple sequence alignments).
 
# Open the alignment file, click on '''Ok''' to import the data. If the data can't be loaded, the file may have the wrong extension: .aln is required.
 
# find the <code>Mbp1_SACCE</code> sequence in the list, click on it and move it to the top of the Sequences list with your mouse (the list is not static, you can re-order the sequences in any way you like).
 
}}
 
 
 
You will see that the <code>1BM8</code> sequence and the <code>Mbp1_SACCA APSES</code> domain sequence do not match: at the N-terminus the sequence that corresponds to the PDB structure has extra residues, and in the middle the APSES sequences may have gaps inserted.
 
 
{{task|1=
 
;Bring the 1MB1 sequence in register with the APSES alignment.
 
 
# MultiSeq supports typical text-editor selection mechanisms. Clicking on a residue selects it, clicking on a row selects the whole sequence. Dragging with the mouse selects several residues, shift-clicking selects ranges, and option-clicking toggles the selection on or off for individual residues. Using the mouse and/or the shift key as required, select the '''entire first column''' of the '''Sequences''' you have imported.  Note: don't include the 1BM8 sequence - this is just for the aligned sequences.
 
# Select '''Edit &rarr; Enable Editing... &rarr; Gaps only''' to allow changing indels.
 
# Pressing the spacebar once should insert a gap character before the '''selected column''' in all sequences. Insert as many gaps as you need to align the beginning of sequences with the corresponding residues of 1BM8: <code>S I M ...</code> . Note: Have patience - the program's response can be a bit sluggish.
 
# Now insert as many gaps as you need into the <code>1BM8</code> structure sequence, to align it completely with the <code>Mbp1_SACCE</code> APSES domain sequence. (Simply select residues in the sequence and use the space bar to insert gaps. (Note: I have noticed a bug that sometimes prevents slider or keyboard input to the MultiSeq window; it fails to regain focus after operations in a different window. I don't know whether this is a Mac related problem or a more general bug in MultiSeq. When this happens I quit VMD and restore a saved session. It is a bit annoying but not mission-critical. But to be able to do that, you might want to save your session every now and then.)
 
# When you are done, it may be prudent to save the state of your alignment. Use '''File &rarr; Save Session...'''
 
}}
 
 
 
{{task|1=
 
;Color by similarity
 
 
# Use the '''View &rarr; Coloring &rarr; Sequence similarity &rarr; BLOSUM30''' option to color the residues in the alignment and structure. This clearly shows you where conserved and variable residues are located and allows to analyze their structural context.
 
# Navigate to the '''Representations''' window and create a '''Tube''' representation of the structure's backbone. Use '''User''' coloring to color it according to the conservation score that the Multiseq extension has calculated.
 
# Create a new representation, choose '''Licorice''' as the drawing method, '''User''' as the coloring method and select <code>(sidechain or name CA) and not element H</code> (note: <code>CA</code>, the C-alpha atom must be capitalized.)
 
# Double-click on the NewCartoon representation to hide it.
 
# You can adjust the color scale in the usual way by navigating to '''VMD main &rarr; Graphics &rarr; Colors...''', choosing the Color Scale tab and adjusting the scale midpoint.
 
 
}}
 
 
 
Study this structure in some detail. If you wish, you could load and superimpose the DNA complexes to determine which conserved residues are in the vicinity of the double helix strands and potentially able to interact with backbone or bases. Note that the most highly conserved residues in the family alignment are all structurally conserved elements of the core. Solvent exposed residues that comprise the surface of the recognition helix are quite variable, especially at the binding site. You may also find - if you load the DNA molecules, that residues that contact the phosphate backbone in general tend to be more highly conserved than residues that contact bases.
 
 
 
 
&nbsp;
 
 
==Modelling the Ankyrin Domain Section==
 
 
===Creating an Ankyrin domain alignment===
 
 
 
APSES domains are relatively easy to identify and annotate but we have had problems with the ankyrin domains in Mbp1 homologues. Both CDD as well as SMART have identified such domains, but while the domain model was based on the same Pfam profile for both, and both annotated approximately the same regions, the details of the alignments and the extent of the predicted region was different.
 
 
[http://www.yeastgenome.org/cgi-bin/locus.fpl?locus=mbp1 Mbp1] forms heterodimeric complexes with a homologue, [http://www.yeastgenome.org/cgi-bin/locus.fpl?locus=swi6 Swi6]. Swi6 does not have an APSES domain, thus it does not bind DNA. But it is similar to Mbp1 in the region spanning the ankyrin domains and in 1999 [http://www.ncbi.nlm.nih.gov/pubmed/10048928 Foord ''et al.''] published its crystal structure ([http://www.rcsb.org/pdb/cgi/explore.cgi?pdbId=1SW6 1SW6]). This structure is a good model for Ankyrin repeats in Mbp1. For details, please refer to the consolidated [[Reference annotation yeast Mbp1|Mbp1 annotation page]] I have prepared.
 
 
In what follows, we will use the program JALVIEW - a Java based multiple sequence alignment editor to load and align sequences and to consider structural similarity between yeast Mbp1 and its closest homologue in your organism.
 
 
In this part of the assignment,
 
 
#You will load sequences that are most similar to Mbp1 into an MSA editor;
 
#You will add sequences of ankyrin domain models;
 
#You will perform a multiple sequence alignment;
 
#You will try to improve the alignment manually;
 
<!-- Finally you will consider if the Mbp1 APSES domains could extend beyond the section of homology with Swi6 -->
 
  
  
Line 960: Line 707:
 
{{#pmid: 10747782}}
 
{{#pmid: 10747782}}
  
 
+
:* [http://www.wwpdb.org/documentation/format23/v2.3.html '''PDB file format'''] (see the Coordinate Section if you are unsure about chain identifiers)
 
+
:* [http://en.wikipedia.org/wiki/Structural_alignment Wikipedia on '''Structural Superposition'''] <small>(although the article is called "Structural Alignment")</small>
 
 
 
 
  
  

Latest revision as of 03:25, 8 January 2017

Structure

Data Sequence Structure Phylogeny Function


 


 


 


 


The Structure Unit

This Unit is part of a brief introduction to bioinformatics. The material is more or less interleaved with the Structure.R Project File which is part of the RStudio project associated with this material. Refer to the course/workshop page for installation instructions.

In the previous units we have discovered homologues of APSES domain containing proteins in all fungal species. This makes the domain an ancient protein family that had already duplicated to several paralogues at the time when the cenancestor of all fungi lived, more than 600,000,000 years ago, in the Vendian period of the Proterozoic era of Precambrian times.

In this unit we will explore the domain's 3-dimensional structure, learn how to compute features from structures, and how to map features computed elsewhere onto structures.


 


 

Molecular graphics: UCSF Chimera

To view molecular structures, we need a tool to visualize the three dimensional relationships of atoms. A molecular viewer is a program that takes 3D structure data and allows you to display and explore it. For a number of reasons, I use the UCSF Chimera viewer for this course:

  1. Chimera is free and open;
  2. It creates very appealing graphics;
  3. It is under ongoing development and is well maintained;
  4. It provides an array of useful utilities for structure analysis; and,
  5. besides an intuitive, menu driven interface, Chimera can be scripted via its command line, or even programmed via its in-built python interpreter.


Task:

  1. Access the Chimera homepage and navigate to the Download section.
  2. Find the the newest version for your platform in the table and click on the file to download it.
  3. Follow the instructions to install Chimera.


Let's explore Chimera functions first with a simple small molecule:


 

Modeling small molecules

"Small" molecules are solvent, ligands, substrates, products, prosthetic groups, drugs - in short, essentially everything that is not made by DNA-, RNA-polymerases or the ribosome. Whereas the biopolymers are still front and centre in our quest to understand molecular biology, small molecules are crucial for our quest to interact with the inventory of the cell, create useful products, or advance medicine.

A number of public repositories make small-molecule information available, such as PubChem at the NCBI, the ligand collection at the PDB, the ChEBI database at the European Bioinformatics Institute, the Canadian DrugBank, or the NCI database browser at the US National Cancer Institute. One general way to export topology information from these services is to use SMILES strings—a shorthand notation for the composition and topology of chemical compounds.


Task:

  1. Access PubChem.
  2. Enter "caffeine" as a search term in the Compound tab. A number of matches to this keyword search are returned.
  3. Click on the top hit - 1,3,7-Trimethylxanthine, the Caffeine molecule. Note that the page contains among other items:
    1. A 2D structural sketch;
    2. An idealized 3D structural conformer, for which you can download coordinates in several formats;
    3. The IUPAC name: 1,3,7-trimethylpurine-2,6-dione;
    4. The CAS identifier 58-08-2 which is a unique identifier and can be used as a cross-reference ID;
    5. The SMILES strings CN1C=NC2=C1C(=O)N(C(=O)N2C)C;
    6. ... and much more.


That's great, but let's sketch our own version of caffeine. Several versions of Peter Ertl's Java Molecular Editor (JME) are offered online, PubChem offers this functionality via its Sketcher tool.

Task:

  1. Return to the PubChem homepage.
  2. Follow the link to Structure search (in the right hand menu).
  3. Click on the 3D conformer tab and on the Launch button to launch the molecular editor in its own window.
  4. Sketch the structure of caffeine. I find the editor quite intuitive but clicking on the Help button will give you a quick, structured overview. Make sure you define your double-bonds correctly.
  5. Export the SMILES string of your compound to your computer.


 

Translating SMILES to structure

Chimera can translate SMILES strings to coordinates[1].

Task:

  1. Open Chimera.
  2. Select ToolsStructure EditingBuild Structure.
  3. In the Build Structure window, select the SMILES string button, paste the string from your file, and click Apply.
  4. The caffeine molecule will be generated and visualized in the graphics window. This is a "stick" representation.
  5. You can rotate it with your mouse, <command> drag to scale, <shift> drag to translate.
  6. Use the ActionsAtoms/Bondsball & stick or sphere menu items to change appearance.
  7. Use the ActionsColorby element menu to change colors.
  8. Change the display back to stick and use ActionsSurfaceshow to add a solvent accessible surface. Choosing this command triggers the calculation of the surface, which is then available as an individually selectable object. However, with default parameters the surface appears a bit rough for this small molecule.
  9. Change the parameters of this solvent accessible surface:
    1. Select the surface with <control><click> (<control><left mouse button> on windows). A green contour line appears around selected items – it surrounds the surface in this case.
    2. Open the selection inspector by clicking on the tiny green icon in the lower-right corner of the window (It has a magnifying glass symbol which means "inspect" for Chimera, not "search").
    3. Select Inspect ...MSMS surface and change the Vertex density value to 50.0 - hit return.
  10. By default, the surface inherits the colour of the atoms it envelopes. To change the colour of the surface, use the ActionsColorall options menu. Click the surfaces button to indicate that the color choice should be applied to the surface object (note what else you can apply color to...), then choose cornflower blue.
  11. Use the ActionsSurfacetransparency50% menu to see atoms and bonds that are covered by the surface.
  12. To begin working with molecules in "true" 3D, choose ToolsViewing ControlsCamera and select camera modewall-eye stereo. Also, use the Effects tab of the Viewing window, and check shadows off.
  13. Your structure should look about like what you see below. Save your session with the FileSave Session dialogue so you can easily recreate the scene.


Caffeine stereo.jpg

Wall-eye stereo view of the caffeine structure, surrounded by a transparent molecular surface. The image for the left eye is on the left side. For instructions on stereo-viewing, see the next section.



 

Stereo vision

A simple molecular scene like the caffeine molecule is a great way to practice viewing structures in stereo. This is a learnable skill, but it takes practice.

Task:

Access the Stereo Vision tutorial and practice viewing molecular structures in stereo.

Practice at least ...

  • two times daily,
  • for 3-5 minutes each session,

Keep up your practice. It is a wonderful skill that will greatly support your understanding of structural molecular biology. Practice with different molecules and try out different colours and renderings.

Note: do not go through your practice sessions mechanically. If you are not making any progress with stereo vision, contact me so I can help you on the right track.


 


 

Protein structure features

In this series of tasks we will showcase some of the globally applied tools that help us study molecular structure. Our first task is to find a structure for the sequence we are interested in, to work with.


Structure search

The search options in the PDB structure database are as sophisticated as those at the NCBI. At its simplest, we will try a simple keyword search to get us started.


Task:

  • Visit the RCSB PDB website at http://www.rcsb.org/
  • Briefly orient yourself regarding the database contents and its information offerings and services.
  • Enter Mbp1 into the search field.

Keyword searches are notorious for being imprecise. In our case we retrieve maltose binding proteins, a homologous transcription factor from Magnaporthe oryzae (4UX5), and three Saccharomyces cerevisiae Mbp1 transcription factor structures (1L3G, 1BM8, and 1MB1) – only these contain (partial) sequence of the protein we are interested in. These three are APSES domain structures: an NMR ensemble and two crystal structures of different resolution.

  • Click on the 1BM8 entry[2] and explore the information and services linked from that page.


 

Next we will load this molecule in Chimera, work with the sequence interface, use it to select specific parts of a molecule, and colour specific regions (or residues) of a molecule separately.


 

Task:

  1. Open Chimera.
  2. One of the three yeast Mbp1 fragment structures has the PDB ID 1BM8. Load it in Chimera (simply enter the ID into the appropriate field of the FileFetch by ID... window).
  3. Display the protein in PresetsInteractive 1 mode and familiarize yourself with its topology of helices and strands.
  4. Open the sequence tool: ToolsSequenceSequence. You will see the sequence for each chain - here there is only one chain. By default, coloured rectangles overlay the secondary structure elements of the sequence.
  5. Hover the mouse over some residues and note that the sequence number and chain is shown at the bottom of the window.
  6. Click/drag one residue to select it. (Simply a click wont work, you need to drag a little bit for the selection to catch on.) Note that the residue gets a green overlay in the sequence window, as it also gets selected with a green border in the graphics window.
  7. In the bottom of the sequence window, there are instructions how to select (multiple) regions. Try this: colour the protein white (SelectSelect All; ActionsColorlight gray). Clear the selection. Now select all the helical regions (pale yellow boxes) by click/dragging and using the shift key. Color them red. Then select all the strands by clicking into any of the pale green boxes and color them green.

Next, display the DNA binding subdomain.

  1. In the bottom of the sequence window, there are instructions how to select (multiple) regions. Clear the selection by <control> clicking into an empty spot of the viewer. Now select the region that encompasses the residues that have been reported to form the DNA binding subdomain, residues 50 to 74: KRTRILEKEVLKETHEKVQGGFGKYQ (Taylor 2000). Show the side chains of these residues by clicking on the little green inspector icon on the viewer window, inspecting Atom and choosing displayed: true, and inspecting Bond and setting the stick radius to 0.4.
  2. Undisplay the Hydrogen atoms by selecting the element H in the Chemistry option of the Selection Menu, and use the Action menu to hide them. Then use the effects pane of the Depiction menu to add a contour.
  3. Finally, give the scene a gradient grey background grey via the ActionsColorall options... menu.


1BM8 DNAbindingRegion stereo.jpg

The DNA binding region of Mbp1 according to NMR measurements of DNA contact by Taylor et al. (2000). The backbone of 1BM8 is shown with a colour ramp from blue (N-terminus) to red (C-terminus). The side chains of the region 50-74 are shown coloured by element.



  1. Finally, generate a stereo-view that shows the molecule well, in which the domain is coloured dark grey, and the DNA binding domain residues (as defined above) are coloured with a colour ramp (ToolsDepictionRainbow)[3]
  2. Show the first and last residue's CA atom[4] as a sphere and colour the first one blue (to mark the N-terminus) and the last one red. E.g.:
    1. SelectAtom specifier:4@CA
    2. ActionsRibbonhide
    3. ActionsAtoms/bondsshow
    4. ActionsAtoms/bondssphere
    5. ActionsColorcornflower blue
    6. Then click on the selection inspector (the green button with the magnifying glass at the lower right of the graphics window) and set the sphere radius to 1.0Å.



 

A Ramachandran plot

Task:

  1. Choose PresetsInteractive 2 (all atoms) for a detailed view of the 1BM8 structure.
  2. Choose FavoritesModel Panel
  3. Look for the Option Ramachandran plot... in the choices on the right.
  4. Click the button and study the result. The dots in thisRamachandran Plot represent the phi-psi angle combinations for residue backbones. We see that they are well distributed, this is a high-resolution structure essentially without outliers. Clicking on a dot selects a residue in the structure viewer (selected residues have a green contour), conversely, already selected residues appear as red dots in the Ramachandran plot.
  5. Choose FileFetch by ID and fetch 1L3G, an NMR structure of the Mbp1 APSES domain. Chimera loads the 19 models that comprise this structure dataset.
  6. In the FavoritesModel Panel, select 1BM8 and click on hide.
  7. Then select 1LG3 and click group/ungroup to be able to address the models individually. Select any of the models individually and click again on Ramachandran plot. You will see that the points are much more dispersed, and there are a number of outliers that have comparatively high-energy conformations.


 

B-factors

Task:

  1. Choose FavoritesModel Panel, click/drag over the 1LG3 models and click close to remove them again.
  2. To explore B-Factors in the 1BM8 model, click show to view it again.
  3. Choose ToolsStructure AnalysisRender byAttribute.
  4. Select Attributes of atoms, Model 1BM8 and Attribute: bfactor. A histogram appears with sliders that allow you to render the distribution of values found in the structure for this attribute.
  5. Let's colour the atoms by B-Factor. Click on the colours tab. A standard colouring scheme is blue - white - red, but you can move the sliders, add new thresholds, and colour them individually by clicking on the colour patch to create your own colour spectrum, e.g. from black via red to white, in a black-body spectrum. Click Apply.
  6. Choose ActionsAtoms/Bondsstick to give the bonds more volume. You will find that the core of the protein has low temperature factors, and the surface has a number of highly mobile sidechains and loops.

1BM8 thermal stereo.jpg

Structure of the yeast transcription factor Mbp1 DNA binding domain (1BM8) coloured by B-factor (thermal factor). The protein bonds are shown in a "stick" model, coloured with a spectrum that emulates black-body radiation. Note that the interior of the protein is less mobile, some of the surface loops are highly mobile (or statically disordered, X-ray structures can't distinguish that) and the discretely bound water molecules that are visible in this high-resolution structure are generally more mobile than the residues they bind to.


 

Electrostatics

Task:

  1. To visualize the electrostatic potential of the protein, mapped on the surface, first select PresetsInteractive 2... and ActionsColorcyan for a vividly contrasting color.
  2. To apply potential coloring to a surface, we need to calculate a solvent accessible surface first: select ActionsSurfaceshow.
  3. A simple electrostatic potential calculation just assumes Coulomb charges. A more accurate calculation of full Poisson-Boltzmann potentials is also available. Select ToolsSurface/Binding AnalysisCoulombic Surface Coloring.
  4. Make sure the surface object is selected in the form (it should be selected by default since there is only one surface), keep the default parameters and click Apply.
  5. Use ActionsSurfaceTransparency30% to make the protein backbone somewhat visible. Select ActionsAtoms/Bondshide to turn off the detailed view of coordinates, then ActionsRibbonshow to display the fold of the domain.
  6. Open the ToolsViewing ControlsLighting window → and set Intensity from two-point to ambient. This reduces shadowing and reflections on the surface and thus emphasizes the color values - here our focus is not on shape, but on property.
  7. Use the Effects tab to turn shadows off and depth-cueing and silhouettes on. This recreates visual cues of depth which compensate for the loss of shape information by using a flat lighting model.
  8. Back at the sequence window, use the mouse to select the "DNA recognition domain" (residues 50-74). Then select ActionsColorall options ... to open the color menu window. Find the control buttons for "Coloring applies to:" and select ribbons only. This is important, otherwise you will overwrite the coloring of your surface. Then choose "red" as the color for the selection.
  9. Study the resulting structure carefully: what do you expect regarding the electrostic potential of the surface of a DNA binding molecule? What do you find? If there is anything remarkable - how does it relate to the annotated "DNA binding" region? How do you interpret this relationship? Note down your answers, I may ask you to hand them in for credit at a later time in the course.

1BM8 coulomb stereo.jpg

Coulomb (electrostatic) potential mapped to the solvent accessible surface of the yeast transcription factor Mbp1 DNA binding domain (1BM8). The protein backbone is visible through the transparent surface as a cartoon model, note the helix at the bottom of the structure. This helix has been suggested to play a role in forming the domain's DNA binding site and the positive (blue) electrostatic potential of the region is consistent with binding the negatively charged phosphate backbone of DNA. The other side of the domain has a negative (red) charge excess, which balances the molecule's electric charge overall, but also guides the protein-ligand interaction and supports faster on-rates.



 

Hydrogen bonds

Task:

  1. Hydrogen bonds encode the basic folding patterns of the protein. To visualize H-bonds select PresetsPublication 1... and ActionsColorby element.
  2. Turn the surface and ribbons off with ActionsSurfacehide and ActionsRobbonhide. Use ActionsAtoms/Bondsshow.
  3. Use ToolsStructure AnalysisFindHBond and Apply default parameters.
  4. To emphasize the role of H-bonds in determining the architecture of the protein, select SelectStructurebackbonefull and then SelectInvert (all models). Now ActionsAtoms/bondshide will show only the backbone with its H-bonds.


1BM8 hbond stereo.jpg

Hydrogen bonds shown for the peptide backbone of the yeast transcription factor Mbp1 DNA binding domain (1BM8). This view emphasizes the interactions of secondary structure elements that govern the folding topology of the domain.


 


 

Compute with structures

 

To practice actual computations with structures we'll use the Grant lab's bio3d package in R.

Task:

  • Open an RStudio session, load the project file from the File → Recent projects ... menu.
  • Bring code and data resources up to date:
    • pull the most recent version of the project from GitHub
    • type init() to load the most recent files and functions.
    • load() the latest version of myDB.
  • Study and work through the code in the Structure.R script:
    • PART ONE: INTRODUCTION TO bio3d;
    • PART TWO: A RAMACHANDRAN PLOT;
    • PART THREE: H-BOND LENGTH DISTRIBUTIONS; and
    • PART FOUR: MAPPING CALCULATED VALUES TO STRUCTURE.
  • There are a number of questions in the code, don't gloss over them but try to answer them for yourself.


 


 

Homology Modeling

In order to understand how specific residues in the sequence contribute to the putative function of the protein, and why and how they are conserved throughout evolution, we would need to study an explicit molecular model of an APSES domain protein, bound to its cognate DNA sequence. Explanations of a protein's observed properties and functions can't rely on the general fact that it binds DNA, we need to consider details in terms of specific residues and their spatial arrangement. In particular, it would be interesting to correlate the conservation patterns of key residues with their potential to make specific DNA binding interactions. Unfortunately, the experimental evidence we have considered in Assignment 2 (Taylor et al., 2000) is not sufficient to unambiguously define the details of how a DNA double helix might be bound. Moreover, at least two distinct modes of DNA binding are known for proteins of the winged-helix superfamily, of which the APSES domain is a member.

In this section you will (1) construct a molecular model of the APSES domain from the MBP1_SPIPU sequence.

For the following, please remember the following terminology:

Target
The protein that you are planning to model.
Template
The protein whose structure you are using as a guide to build the model.
Model
The structure that results from the modelling process. It has the Target sequence and is similar to the Template structure.

 

A brief overview article on the construction and use of homology models is linked to the resource section at the bottom of this page. That section also contains links to other sites and resources you might find useful or interesting.


 

A Point Mutation

To illustrate how homology modelling works in principle, let's consider changing the sequence of a single amino acid, based on a structural template.

Such minimal changes to structure models can be done directly in Chimera. Let us consider the residue A 42 of the 1BM8 structure. It is oriented towards the core of the protein, but most other Mbp1 orthologs have a larger amino acid in this position, V, or even I.

Task:

  1. Open 1BM8 in Chimera, hide the ribbons and show all atoms as a stick model.
  2. Color the protein white.
  3. Open the sequence window and select A 42. Color it red. Choose Actions → Set pivot. Then study how nicely the alanine side chain fits into the cavity formed by its surrounding residues.
  4. To emphasize this better, hide the solvent molecules and select only the protein atoms. Display them as a sphere model to better appreciate the packing, i.e. the Van der Waals contacts we discussed in class. Use the Favorites → Side view panel to move the clipping plane and see a section through the protein. Study the packing, in particular, note that the additional methyl groups of a valine or isoleucine would not have enough space in the structure. Then restore the clipping planes so you can see the whole molecule.
  5. Lets simplify the view: choose Actions → Atoms/Bonds → backbone only → chain trace. Then select A 42 again in the sequence window and choose Actions → Atoms/Bonds → show.
  6. Add the surrounding residues: choose Select → Zone.... In the window, see that the box is checked that selects all atoms at a distance of less then 5Å to the current selection, and check the lower box to select the whole residue of any atom that matches the distance cutoff criterion. Click OK and choose Actions → Atoms/Bonds → show.
  7. Select A 42 again: left-click (control click) on any atom of the alanine to select the atom, then up-arrow to select the entire residue. Now let's mutate this residue to isoleucine.
  8. Choose Tools → Structure Editing → Rotamers and select ILE as the rotamer type. Click OK, a window will pop up that shows you the possible rotamers for isoleucine together with their database-derived probabilities; you can select them in the window and cycle through them with your arrow keys. But note that the probabilities are very different - and thus show you high-energy and low-energy rotamers to choose from. Therefore, unless you have compelling reasons to do otherwise, try to find the highest-probability rotamer that may fit. This is where your stereo viewing practice becomes important, if not essential. It is really, really hard to do this reasonably in a 2D image! It becomes quite obvious in 3D. Btw: I find such "quantitative" work - where the real distances are important - easier in orthographic than in perspective view (cf. the Camera panel).
  9. I find that the first rotamer is actually not such a bad fit. The CD atom comes close to the sidechains of I 25 and L 96. But we can assume that these are somewhat mobile and can accommodate a denser packing, because - as you can easily verify in your MSA - it is NOT the case that sequences that have I 42, have a smaller residue in position 25 and/or 96. So let's accept the most frequent ILE rotamer by selecting it in the rotamer window and clicking OK (while existing side chain(s): replace is selected).
  10. Done.

If you want to go over this in more detail, check the video tutorial on YouTube published by the NIAID bioinformatics group here. I would also encourage you to go over Part 2 of the video tutorial that discusses how to check for and resolve (by energy minimization) steric clashes. But note that it is not clear whether energy minimization will make your structure more correct in the sense of a smaller overall RMSD with the real, mutated protein.

What we have done here with one residue is exactly the way homology modeling works with entire sequences. The homology modelling program simply changes all amino acids to the residues of the target sequence, based on the template structure. Let's now build a homology model for MBP1_SPIPU.


 

Preparation

  • We need to define our Target sequence;
  • find a suitable structural Template; and
  • build a Model.


 

Target sequence

We have encountered the PDB 1BM8 structure before, the APSES domain of saccharomyces cerevisiae Mbp1. This is a useful template to model the DNA binding domain of your RBM match. But what exactly is the aligned region of the APSES domain? We could use several approaches to define the APSES domain:

  • we could use the biostrings package to calculate a pairwise sequence alignment with the 1BM8 sequence, like we did previously for the full-length sequences. This would give us the domain boundaries.
  • we could calculate a multiple sequence alignment, while including the 1BM8 sequence. This would also allow us to infer domain boundaries, actually in all sequences in our database at once. But we have found previously that such multiple sequence alignments are quite sensitive to un-alignable regions of which we have quite a few in the full length sequences. We do need an MSA, but we do need to restrict the length of the sequences we align to a reasonable region.
  • we could access the domain annotations at CDD or at the SMART Database, but both have interfaces that are difficult to use computationally, and have other issues: NCBI does not recognize APSES domains, only the smaller KilA-N domain, and SMART sometimes does not find APSES domains in our sequences.
  • the most straightforward approach of course is to use the annotation that we already have produced for the APSES domain in MBP1_SPIPU. You should be able to simply take the MBP1_SACCE sequence and the one for S. punctatus from the the multiple sequence aligment you have produced with the msa package.


 

Template choice and template sequence

The SWISS-MODEL server provides several different options for constructing homology models. The easiest option requires only a target sequence as input. In this mode the program will automatically choose suitable templates and create an input alignment. I would argue however that that is not the best way to use such a service: template choice and alignment both may be significantly influenced by biochemical reasoning, and an automated algorithm cannot make the necessary decisions. Should you use a structure of reduced resolution that however has a ligand bound? Should you move an indel from an active site to a loop region even though the sequence similarity score might be less? Questions like that may yield answers that are different from the best choices an automated algorithm could make. But Swiss Model is flexible and allows us to upload an explicit alignment between target and template. Please note: the model you will produce is "easy" - the sequence similarity is high and there are no indels to consider, the automated mode would have done just as well. But the strategy we pursue here is suitable also for much more difficult problems. The automated strategy probably is not.

Template choice is the first step. Often more than one related structure can be found in the PDB. The degree of sequence identity is the most important criterion, but there are many other factors to consider. Please refer to the template choice principles page on this Wiki where I discuss more details and alternatives. To find related structures, you can search the PDB itself through its Advanced Search interface; for example one can search for sequence similarity with a BLAST search, or search for structural similarity by accessing structures according to their CATH or SCOP classification. But the BLAST search is probably the method of choice: after all, the most important measure of the probability of success for homology modelling is sequence similarity.


Defining a template means finding a PDB coordinate set that has sufficient sequence similarity to your target that you can build a model based on that template. To find suitable PDB structures, we will perform a BLAST search at the PDB.




Task:

  1. Retrieve the aligned Mbp1 S. punctatus RBM APSES domain sequence from the apsesMat matrix as explained in

PART FIVE: PREPARE APSES DOMAIN SEQUENCES FOR HOMOLOGY MODELING of the Structure.R script. This is your target sequence.

  1. Navigate to the PDB.
  2. Click on Advanced to enter the advanced search interface.
  3. Open the menu to Choose a Query Type:
  4. Find the Sequence features section and choose Sequence (BLAST...)
  5. Paste your target sequence into the Sequence field, select not to mask low-complexity regions and Submit Query. Since the E-value is set rather high by default, you will get a number of low-confidence hits as well as the actual homologs, these have very low E-values.

All hits that are homologs are potentially suitable templates, but some are more suitable than others. Consider how the coordinate sets differ and which features would make each more or less suitable for creating a homology model: you should consider ...

  • sequence similarity to your target
  • size of expected model (= length of alignment)
  • presence or absence of ligands
  • experimental method and quality of the data set

Sequence similarity is the most important, but we can have the PDB tabulate the other features concisely for this task.

  1. There is a menu to create Reports: - select customizable table.
  2. Select (at least) the following information items:
Structure Summary
  • Experimental Method
Sequence
  • Chain Length
Ligands
  • Ligand Name
Biological details
  • Macromolecule Name
refinement Details
  • Resolution
  • R Work
  • R free
  1. click: Create report.

Unfortunately you don't get the E-values into the report, and those should strongly influence your final decision. However in our case the sequences and therefore the E-values of the top three hits are all the same. And there is a new structure from January 2015, with a lower resolution. Some of the sequences have a longer chain-length ... but those are only disordered residues (otherwise these would be better suited templates; regrettably, you'd need to check that in the real world, there is no automatic tool to evaluate disorder and its effects on template choice). In my opinion that leaves pretty much only one unambiguous choice for our template: 1BM8.

Finally
Click on the 1BM8 ID to navigate to the structure page for the template and save the FASTA sequence to your computer. This is the template sequence.


 

Sequence numbering

It is not straightforward at all how to number sequence in such a project. A "natural" numbering starts with the start-codon of the full length protein and goes sequentially from there. However, this does not map exactly to other numbering schemes we have encountered. As you know the first residue of the APSES domain (as defined by CDD) is not Residue 1 of the Mbp1 protein. The first residue of the 1BM8 FASTA file (one of the related PDB structures) is the fourth residue of the Mbp1 protein. The first residue in the structure is GLN 3, therefore Q is the first residue in a FASTA sequence derived from the coordinate section of the PDB file (the ATOM records. In the 1MB1 structure, the original N-terminal amino acids are present in the molecule, therefore they are present in the FASTA file which starts with MSNQIY..., but they are disordered in the structure and no coordinates are present for M and S. A sequence derived explicitly from the coordinates is therefore different from the reported FASTA sequence, which is really bad because that is what the modelling program has to work with ... and so on. It can get complicated. You need to remember: a sequence number is not absolute, but assigned in a particular context and you need to be careful how to do this.

Fortunately, the numbering for the residues in the coordinate section of our target structure corresponds not to its FASTA sequence, but to the numbering of the gene. Otherwise we would need to renumber the sequence (e.g. by using the bio3D R package). If we would not do this, the sequence numbers in the model might not correspond to the sequence numbers of our target.


 

The input alignment

The sequence alignment between target and template is the single most important factor that determines the quality of your model. No comparative modelilng process will repair an incorrect alignment; it is useful to consider a homology model rather like a three-dimensional map of a sequence alignment rather than a structure in its own right. In a homology modelling project, typically the largest amount of time should be spent on preparing the best possible alignment. Even though automated servers like the SwissModel server will align sequences and select template structures for you, it would be unwise to use these just because they are convenient. You should take advantage of the much more sophisticated alignment methods available. Analysis of wrong models can't be expected to produce right results.

The best possible alignment is usually constructed from a multiple sequence alignment that includes at least the target and template sequence and other related sequences as well. The additional sequences are an important aid in identifying the correct placement of insertions and deletions. Your alignment should have been carefully reviewed by you and wherever required, manually adjusted to move insertions or deletions between target and template out of the secondary structure elements of the template structure.

In most of the Mbp1 orthologues, we do not observe indels in the APSES domain regions. Evolutionary pressure on the APSES domains has selected against indels in the more than 600 million years these sequences have evolved independently in their respective species.


Task:

  • Confirm the MSA for APSES domain sequences in Mbp1 orthologues with the section PART SIX: APSES DOMAIN SEQUENCES OF MBP1 ORTHOLOGUES of the Structure.R script.


Of course, this one-to-one correspondence is the simplest possible case but the principle of working from a good MSA to recover the best-informed alignment between target and template sequence applies in all cases.


 


 

Homology model

The alignment defines the residue by residue relationship between target and template sequence. All we need to do now is to change every residue of the template to the target sequence


SwissModel

Access the Swissmodel server at http://swissmodel.expasy.org and click on the Start Modelling button. Under the Supported Inputs, choose Target-Template Alignment.

Task:

  • Paste the aligned sequences of the S. punctatus target and the 1BM8 template into the form field. SwissModel will analyse the sequences and ask you to identify target and template. The MBP1_SPIPU sequence is your target. The 1BM8 sequence is the template.
  • Click Validate Target Template Alignment and check that the returned alignment is correct. All non-identical residues are shown in light-grey.
  • Click Build Model to start the modelling process. This will take about a minute or so.
  • The resulting page returns information about the resulting model and its quality. You can rotate the model in the window on the right with the mouse. Regions that have a reddish hue have lower quality scores, i.e. they were harder to model or could not be modelled well with good geometry. Hovering the mouse over parts of the structure highlights the respective region of the sequence alignment.
  • Mouse over the Model 01 dropdown menu (under the icon of the template structure), and choose the PDB file. Note that the B-factor column of the coordinate section contains the QMEAN scores (between 0 and 1) that the server has calculated. Higher is better. Save the PDB file on your computer.
  • Open the SwissModel documentation in a new tab. Read about the modelling process. there are a number of important technical details that help to understand what the computed coordinates of your model mean, you should pay special attention to the GQME and QMEAN quality scores.
  • Also save:
    • The output page as pdf (for reference)
    • The modeling report (as pdf)


 

Model interpretation

We have spent a significant amount of time to prepare data for the analysis and in practice it usually seems to turn out that way, that the preparation of data occupies the greatest part of our efforts. The actual computational analysis is generally quite fast. And, unfortunately, the interpretation of results is often somewhat neglected. Don't be that way. Data does not explain itself. The interpretation of your computational results is the most important part.

We will look at our homology model with two different questions:

  • Can we define the DNA binding residues?
  • Can we tell which residues are conserved for functional reasons, rather than for structural reasons?


 

The PDB file

Task:
Open your model coordinates in a text-editor (make sure you view the PDB file in a fixed-width font (like "courier") so all the columns line up correctly) and consider the following questions:

  • What is the residue number of the first residue in the model? What should it be, based on the alignment? If the putative DNA binding region was reported to be residues 50-74 in the Mbp1 protein, which residues of your model correspond to that region?

That's not easy to tell. But it should be.

As you have seen above, SwissModel numbers the first residue "1" and does not keep the numbering of the template. We should renumber the model so we can compare the model and the template with the same residue numbers. Carefully doing this by hand should not even take you a whole hour. You just need to edit all the residue numbers in a text editor to give the first residue the number "4" and increment numbers from there.

Or we could do this with an R script.

Task:

  • Renumber your model PDB file to start with residue number 4 with the code in section PART SEVEN: RENUMBERING THE MODEL of the Structure.R script.


 

First visualization

Since a homology model inherits its structural details from the template, your model of the YFO sequence should look very similar to the original 1BM8 structure.

Task:

  1. Start Chimera and load the model coordinates that you have just renumbered.
  2. From the PDB, also load the template structure. (Use File → Fetch by ID ...)
  3. In the FavouritesModel Panel window you can switch between the two molecules.
  4. Hide the ribbon and choose backbone only → full. You will note that the backbone of the two structures is virtually identical.
  5. Next, choose Actions → Atoms/Bonds → show to display the two molecules in a stick style and note how the sidechains have been modeled. Note especially how sidechain coordinates have been guessed, where the template had shorter sidechains than the target. It may be more clear if you hide H-atoms: Select → Chemistry → Element → H and Actions → Atoms/Bonds → hide
  6. Display only residue 50 to 74 to focus on the putative helix-turn-helix domain. You can drag your mouse in the Favourites → Sequence, window to select the range then Select → Invert (selected model) and Actions → Atoms/Bonds → hide. Or you can use Chimera's commandline: ~display to undisplay everything, show #:50-74 to show this residue range for all models.
  7. Study the result: a model of the HTH subdomain of Mbp1_SPIPU.


 

Coloring the model by energy

SwissModel calculates energies for each residue of the model with a molecular mechanics forcefield. The SwissModel modeling summary page contains a plot of these energies as a function of sequence number like. The values - between 0.0 and 1.0 - are stored in the PDB file's B-factor field.


Task:

  1. Back in Chimera, use the model panel to close the 1BM8 structure. Select all and show Atoms, bonds to view the entire model structure.
  2. Choose Tools → Depiction → Render by attribute and select attributes of atoms, Attribute: bfactor, check color atoms and click OK.
  3. Study the result: It seems that residues in the core of the protein have better energies (higher values) than residues at the surface. Why could that be the case?


 


 

Modelling DNA binding

One of the really interesting questions we can discuss with reference to our homology model is how sequence variation might result in changed DNA recognition sites, and then lead to changed cognate DNA binding sequences. In order to address this, we would need to generate a plausible structural model for how DNA is bound to APSES domains.

Since there is currently no software available that would reliably model such a complex from first principles[5], we will base a model of a bound complex on homology modelling as well. This means we need to find a similar structure for which the position of bound DNA is known, then superimpose that structure with our model. This places the DNA molecule into the spatial context of the model we are studying. It so happens that early in 2015 an APSES domain structure with bound DNA was published. You probably noticed it as a result of the PDB BLAST search: 4UX5, from the Magnaporthe oryzae Mbp1 orhologue PCG2[6].


 

A homologous protein/DNA complex structure

Task:

The PCG2 / DNA complex
  • Open Chimera and load the 4UX5 structure. Spend some time exploring it. There are two domains of identical sequence bound to one DNA molecule. The first question I would have is whether the two molecules bind to the same DNA motif - the CGCG core of the "MCB-box", and whether the observed protein:DNA interfaces are actually with the cognate sequence, or whether one (or both) proteins are non-specific complexes. The conditions under which proteins crystallize can be harsh, and physiological function under these conditions is not guaranteed.[7] Indeed, Liu et al. (2015) report that at low concentrations a 1:1 complex is formed and the 2:1 Protein:DNA complex only forms at high concentrations. Figure 3. of their paper shows that the detailed contacts between protein and DNA are in fact not identical.
  • Without taking this question too far, let's get a quick view of the comparison by duplicating one domain of the structure and superimposing it on the other. The authors feel that chain A represents the tighter, more specific mode of interaction; so we will duplicate chain B and superpose the copy on A.
  • In Chimera, open the FavoritesModel Panel and use the copy/combine button to create a copy of the 4UX5 model. Call it test.
  • Select chain B of the test model, then use SelectInvert (selected models) to apply the selection to everything in the test model except chain B.
  • Use ActionsAtoms/Bondsdelete to remove everything but Chain B.
  • Select and colour the chain red.
  • Back on the Model Panel, select both models and use the match... dialogue to open a MatchMaker dialogue window. Choose the radio button two match two specific chains and select 4UX5 chain A as the Reference chain, test chain B as the Chain to match. Click Apply.

You will see that the superimposed structures are very similar, that the main difference is in the orientation of the disordered C-terminus, but also that there is a structural difference between the two structures around Gly 84 which inserts into the minor groove of the double helix.

  • Select one of the residues of that loop in chain A by <control>-clicking on it and use ActionSet pivot to set the centre of rotation to that residue: this makes it easier to visualize the binding situation when you make the molecules larger.
  • Select residues 81 to 87 and the corresponding (sequence VQGGYGKY) and in both chains turn their ribbon display off and display this range as "sticks".
  • Select nucleic acid in the structure submenu and turn ribbons and nucleotide objects off to display the DNA as sticks as well. Colour the DNA by element.
  • Study the situation. Focus on Gly 84.A, especially the interaction of its carbonyl oxygen, which hydrogen bonds to the N2 atom of G8.D chain. Gln 89.A hydrogen bonds to the N2 atom of G8.C chain. Gly 84 and Gln 82 thus recognize a G:C C:G pair. In the B chain, Gly 84.B does not contact the DNA well, since it contacts residues of chain A, especially Gln 82.A. The carbonyl atom of Gly 84.B hydrogen bonds to Gln 89.B. and therefore Gln89.B is not available to contact nucleotide bases. What do you think[8]? It seems to me that a crucial interaction for the cognate sequence is contributed by Guanine 8,
  • Finally, use the Model Panel to select test and close it.


 

Superimposing your model

Both your homology model and the template structure provide valuable information:

  • The template structure shows how conserved the structure is at the protein/DNA interface. You have seen what subtle differences can give rise to a sequence specific complex and a non-specific binding mode. For Mbp1 we know that the APSES domain binds to the same cognate DNA sequence as PCG2. Since your model structure is heavily biased towards the template, evaluating the template in the context of a real protein/DNA complex allows you to judge which binding residues appear to be conserved and possibly modelled in an orientation that is productive for binding.
  • The model structure maps sequence variation into that context: are the crucial residues for sequence specific binding conserved?

Task:

  • Start by loading your model and the 1BM8 structure into your chimera session. Select all, turn all ribbons off, and set all atoms to stick representation. Then select H atoms by element and hide them.
  • We need to visualize and evaluate differences in binding between different proteins and for me it works well to colour everything by element, and give the carbon atoms some identifying, distinct colour. This is best achieved through the Chimera command line that you can turn on with the little "computer" icon on the left-hand side of the graphics window. Have a look at the Chimera Users guide, and choose select to learn how Chimera's selection syntax works.
  • Open the Model Panel to check which protein has which Chimera-internal model number. Then you can use the following selection syntax. Instead of the model numbers, I will type <SPIPU>, <4ux5>, and <1BM8> - you will certainly know by now that these are placeholder labels and you need to replace them with the numbers 0, 1, and 2 instead.
  • To colour the DNA carbon atoms white, type:
color white #<4ux5>:.C,.D & C
  • To colour the 4ux5 A chain carbon atoms grey, type:
color #878795 #<4ux5>:.A & C Note: the color values after the first hash are rgb triplets in the hexadecimal numbering systems - exactly like in R.
  • To undisplay the 4ux5 B chain, type:
~display #<4ux5>:.B Note: this is the tilde character, not a hyphen or minus sign.
  • To colour the SPIPU model carbon atoms a pale reddish color, type:
color #b06268 #<SPIPU> & C
  • To colour the 1BM8 structure carbon atoms a pale greenish color, type:
color #92b098 #<1BM8> & C
  • Ready? Let's superimpose the chains.
    • Select all models in the Model Panel and click on match.
    • Set 4ux5 Chain A as the Reference chain.
    • Select SPIPU as a Chain to match, select the button for specific reference and specific match, and click Apply.
    • Repeat this with 1BM8 as the match chain.
  • Easy. Now enlarge the binding site. Remember that 4ux5 and 1bm8 are independently determined crystal structures, wheres SPIPU was modelled on 1bm8 and is expected to be very similar to it. To give you some guidance what you should focus on, select 4ux5 residue 84 CA atom and display it as Ball & Stick. You can also repeat the Action "Set Pivot in case the pivot has shifted.
  • Study the scene. This is where stereo- vision will help a lot.
  • What do you think? Is this what you expected? Can you explain what you see? Was the modelling process succesful?


  • Now turn the display of 4ux5 chain B back on and turn chain A off instead. Then superimpose the 1BM8 template and your model on Chain B.
  • Again, focus on the binding region. What do you think of that? What would you have expected? Do you see a difference? What does this all mean?


 


 


Links and resources

The DNA binding site

Now, that you know how YFO Mbp1 aligns with yeast Mbp1, you can evaluate functional conservation in these homologous proteins. You probably already downloaded the two Biochemistry papers by Taylor et al. (2000) and by Deleeuw et al. (2008) that we encountered in Assignment 2. These discuss the residues involved in DNA binding[9]. In particular the residues between 50-74 have been proposed to comprise the DNA recognition domain.

Task:

  1. Using the APSES domain alignment you have just constructed, find the YFO Mbp1 residues that correspond to the range 50-74 in yeast.
  2. Note whether the sequences are especially highly conserved in this region.
  3. Using Chimera, look at the region. Use the sequence window to make sure that the sequence numbering between the paper and the PDB file are the same (they are often not identical!). Then select the residues - the proposed recognition domain - and color them differently for emphasis. Study this in stereo to get a sense of the spatial relationships. Check where the conserved residues are.
  4. A good representation is stick - but other representations that include sidechains will also serve well.
  5. Calculate a solvent accessible surface of the protein in a separate representation and make it transparent.
  6. You could combine three representations: (1) the backbone (in ribbon view), (2) the sidechains of residues that presumably contact DNA, distinctly colored, and (3) a transparent surface of the entire protein. This image should show whether residues annotated as DNA binding form a contiguous binding interface.


DNA binding interfaces are expected to comprise a number of positively charged amino acids, that might form salt-bridges with the phosphate backbone.


Task:

  • Study and consider whether this is the case here and which residues might be included.



Links and resources


Taylor et al. (2000) Characterization of the DNA-binding domains from the yeast cell-cycle transcription factors Mbp1 and Swi4. Biochemistry 39:3943-54. (pmid: 10747782)

PubMed ] [ DOI ] The minimal DNA-binding domains of the Saccharomyces cerevisiae transcription factors Mbp1 and Swi4 have been identified and their DNA binding properties have been investigated by a combination of methods. An approximately 100 residue region of sequence homology at the N-termini of Mbp1 and Swi4 is necessary but not sufficient for full DNA binding activity. Unexpectedly, nonconserved residues C-terminal to the core domain are essential for DNA binding. Proteolysis of Mbp1 and Swi4 DNA-protein complexes has revealed the extent of these sequences, and C-terminally extended molecules with substantially enhanced DNA binding activity compared to the core domains alone have been produced. The extended Mbp1 and Swi4 proteins bind to their cognate sites with similar affinity [K(A) approximately (1-4) x 10(6) M(-)(1)] and with a 1:1 stoichiometry. However, alanine substitution of two lysine residues (116 and 122) within the C-terminal extension (tail) of Mbp1 considerably reduces the apparent affinity for an MCB (MluI cell-cycle box) containing oligonucleotide. Both Mbp1 and Swi4 are specific for their cognate sites with respect to nonspecific DNA but exhibit similar affinities for the SCB (Swi4/Swi6 cell-cycle box) and MCB consensus elements. Circular dichroism and (1)H NMR spectroscopy reveal that complex formation results in substantial perturbations of base stacking interactions upon DNA binding. These are localized to a central 5'-d(C-A/G-CG)-3' region common to both MCB and SCB sequences consistent with the observed pattern of specificity. Changes in the backbone amide proton and nitrogen chemical shifts upon DNA binding have enabled us to experimentally define a DNA-binding surface on the core N-terminal domain of Mbp1 that is associated with a putative winged helix-turn-helix motif. Furthermore, significant chemical shift differences occur within the C-terminal tail of Mbp1, supporting the notion of two structurally distinct DNA-binding regions within these proteins.



Footnotes and references

  1. There also exist several online servers that translate SMILES strings to idealized structures, see e.g. the online SMILES translation service at the NCI.
  2. Xu et al. (1997) Crystal structure of the DNA-binding domain of Mbp1, a transcription factor important in cell-cycle control of DNA synthesis. Structure 5:349-58. (pmid: 9083114)

    PubMed ] [ DOI ] BACKGROUND: During the cell cycle, cells progress through four distinct phases, G1, S, G2 and M; transcriptional controls play an important role at the transition between these phases. MCB-binding factor (MBF), a transcription factor from budding yeast, binds to the so-called MCB (MluI cell-cycle box) elements found in the promoters of many DNA synthesis genes, and activates the transcription of those at the G1-->S phase transition. MBF is comprised of two proteins, Mbp1 and Swi6. RESULTS: The three-dimensional structure of the N-terminal DNA-binding domain of Mbp1 has been determined by multiwavelength anomalous diffraction from crystals of the selenomethionyl variant of the protein. The structure is composed of a six-stranded beta sheet interspersed with two pairs of alpha helices. The most conserved core region among Mbp1-related transcription factors folds into a central helix-turn-helix motif with a short N-terminal beta strand and a C-terminal beta hairpin. CONCLUSIONS: Despite little sequence similarity, the structure within the core region of the Mbp1 N-terminal domain exhibits a similar fold to that of the DNA-binding domains of other proteins, such as hepatocyte nuclear factor-3gamma and histone H5 from eukaryotes, and the prokaryotic catabolite gene activator. However, the structure outside the core region defines Mbp1 as a larger entity with substructures that stabilize and display the helix-turn-helix motif.

  3. The Rainbow tool can only create color ramps for an entire molecule. In order to achieve this effect: color the molecule with a color ramp, then select the target domain, then invert the selection and color the new selection dark grey.
  4. See here for details of the specification syntax.
  5. Rosetta may get the structure approximately right, Autodock may get the complex approximately right, but the coordinate changes involved in induced fit makes the result unreliable - and we have no good way to validate whether the predicted complex is correct.
  6. Liu et al. (2015) Structural basis of DNA recognition by PCG2 reveals a novel DNA binding mode for winged helix-turn-helix domains. Nucleic Acids Res 43:1231-40. (pmid: 25550425)

    PubMed ] [ DOI ] The MBP1 family proteins are the DNA binding subunits of MBF cell-cycle transcription factor complexes and contain an N terminal winged helix-turn-helix (wHTH) DNA binding domain (DBD). Although the DNA binding mechanism of MBP1 from Saccharomyces cerevisiae has been extensively studied, the structural framework and the DNA binding mode of other MBP1 family proteins remains to be disclosed. Here, we determined the crystal structure of the DBD of PCG2, the Magnaporthe oryzae orthologue of MBP1, bound to MCB-DNA. The structure revealed that the wing, the 20-loop, helix A and helix B in PCG2-DBD are important elements for DNA binding. Unlike previously characterized wHTH proteins, PCG2-DBD utilizes the wing and helix-B to bind the minor groove and the major groove of the MCB-DNA whilst the 20-loop and helix A interact non-specifically with DNA. Notably, two glutamines Q89 and Q82 within the wing were found to recognize the MCB core CGCG sequence through making hydrogen bond interactions. Further in vitro assays confirmed essential roles of Q89 and Q82 in the DNA binding. These data together indicate that the MBP1 homologue PCG2 employs an unusual mode of binding to target DNA and demonstrate the versatility of wHTH domains.

  7. This particular crystal structure however was crystallized from a Tris-buffer with 50mM NaCl at pH 8.0 - comparatively gentle conditions actually.
  8. Besides the coordinate difference between the chains, if indeed chain B would be representative of a DNA "scanning" conformation, perhaps one should expect that the local DNA structure that chain B binds to is structurally closer to canonical B-DNA than the DNA binding interface of chain A...
  9. (Taylor et al. (2000) Biochemistry 39: 3943-3954 and Deleeuw et al. (2008) Biochemistry. 47:6378-6385)


 

Ask, if things don't work for you!

If anything about this page is not clear to you, please ask on the mailing list. You can be certain that others will have had similar problems. Success comes from joining the conversation.




 


Data Sequence Structure Phylogeny Function