Difference between revisions of "BIO Assignment Week 10"

From "A B C"
Jump to navigation Jump to search
m
m
Line 2: Line 2:
 
<div class="b1">
 
<div class="b1">
 
Assignment for Week 10<br />
 
Assignment for Week 10<br />
<span style="font-size: 70%">Genome Browsers</span>
+
<span style="font-size: 70%">Protein Ligand Complex</span>
 
</div>
 
</div>
  
Line 16: Line 16:
 
==Introduction==
 
==Introduction==
  
Large scale genome sequencing and annotation has made a wealth of information available that is all related to the same biological objects: the DNA. The information however can be of very different types, it includes:
+
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.
* the actual sequence
 
* sequence variants (SNPS and CNVs)
 
* conservation between related species
 
* genes (with introns and exons)
 
* mRNAs
 
* expression levels
 
* regulatory features such as transcription factor bindings sites
 
and much more.
 
  
Since all of this information relates to specific positions or ranges on the chromosome, displaying it alongside the chromosomal coordinates is a useful way to integrate and visualize it. We call such strips of annotation ''tracts'' and display them in '''genome browsers''. Quite a number of such browsers exist, and most work on the same principle: server hosted databases are queried through a Web interface; the resulting data is displayed graphically in a Web browser window. The large data centres each have their own browsers, but arguably the best engineered, most informative and mostly widely used one is provided by the University of California Santa Cruz (UCSC) Genome Browser Project.  
+
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. However, you may remember from the third assignment that the APSES domains in fungi seem to be a relatively small family. And there is no structure available of an APSES domain-DNA complex. How can we find a coordinate set of a structurally similar protein-DNA complex?
  
In this assignment you will explore some of the browsers and we will go through an exercise that relates fungal replication genes to human genes. We have previously focused a lot on Mbp1 homologs, but these have no clear equivalences in "higher" eukaryotes. However one of the key target genes of Mbp1 is the cell cycle protein {{WP|Cdc6}}, and CDC6 is universally conserved in eukaryotes and has a {{WP|CDC6|human homolog}}.
+
This assignment is based on the homology model you built. You will (1) identify similar structures of distantly related domains for which protein-DNA complexes are known, (2) assemble a hypothetical complex structure and (3) consider whether the available evidence allows you to distinguish between different modes of ligand binding,
  
 +
==Modeling a DNA ligand==
  
 +
&nbsp;
  
 
&nbsp;
 
&nbsp;
==GBrowse==
 
  
[http://gmod.org/wiki/GBrowse '''GBrowse'''] - the Generic genome Browser - is the browser developed by the [http://gmod.org/wiki/Main_Page Generic Model Organism Database] project that aims to make industry-strength bioinformatics tools and software available for the model organism community. One of the many databases that uses GMod tools is [http://www.yeastgenome.org/ the Saccharomyces Genome Database].
+
 
 +
===Finding a similar protein-DNA complex===
 +
 
 +
 
 +
&nbsp;<br>
 +
 
 +
Remember that homologous sequences can have diverged to the point where their sequence similarity is no longer recognizable, however their structure may be quite well conserved. Thus if we could find similar structures in the PDB, these might provide us with some plausible hypotheses for how DNA is bound by APSES domains. We thus need a tool similar to BLAST, but not for the purpose of sequence alignment, but for structure alignment. A kind of BLAST for structures. Just like with sequence searches, we might not want to search with the entire protein, if we are interested in is a subdomain that binds to DNA. Attempting to match all structural elements in addition to the ones we are actually interested in is likely to make the search less specific - we would find false positives that are similar to some irrelevant part of our structure. However, defining too small of a subdomain would also lead to a loss of specificity: in the extreme it is easy to imagine that the search for e.g. a single helix would retrieve very many hits that would be quite meaningless.
 +
 
 +
 
 +
 
 +
 
 +
 
 +
At the '''NCBI''', [http://www.ncbi.nlm.nih.gov/Structure/VAST/vast.shtml VAST] is provided as a search tool for structural similarity search.  
  
 
{{task|1=
 
{{task|1=
In this task you will access the SGD GBrowse page for Cdc6 and explore some of the options.
+
# Navigate to the [http://www.ncbi.nlm.nih.gov/Structure/VAST/vast.shtml '''VAST'''] search interface page.
# Navigate to the [http://www.yeastgenome.org/ the Saccharomyces Genome Database], enter Cdc6 into the site search field and on the result page click on the '''GBrowse''' link at the '''Chromosome location''' heading.
+
# Enter <code>1bm8</code> as the PDB ID to search for and click '''Go'''.
# Locate CDC6 (YJL194W) as a red bar in the graph. Note that the triangle at the end points in the direction of transcription.
+
# Follow the link to '''Related Structures'''.
# Note how the shape of the cursor changes over different regions of the window. For example, you can click/hold the graph and slide it left and right (this changes the overview indicator that shows where on the chromosome the currently displayed window of sequence is located). You can click on and follow annotation information. You can also select a stretch of nucleotides and dump it as FASTA (hover over the ruler in the ''Details'' pane).
+
# Study the result.
# Zoom in by selecting '''Show 5 kbp''' at the scroll/zoom controls.
 
# Click on the '''Select Tracks''' tab. This gives you access to a fine-grained selection of all tracks that have been created as genome annotations.
 
# Find the section for '''Transcription Factors'''. Click on the star next to '''TF ChIP chip''' to mark this experiment as a "favorite". Then click on '''Show Favorites Only''' at the top of the page. Finally check '''All on''' for the '''Transcription Factors''' track and '''Back to browser'''.
 
 
}}
 
}}
  
  
This view shows you the ChIP-chip validated TF-binding sites in the upstream regulatory region of Cdc6. Note that Mbp1 is among them. Curiously, Swi6 is also listed there - but you know that [http://www.yeastgenome.org/cgi-bin/locus.fpl?locus=YLR182W Swi6] does not actually bind DNA directly, but forms a complex with the APSES domain transcription factors Mbp1/Swi4 which form the [http://www.yeastgenome.org/cgi-bin/GO/goTerm.pl?goid=0030907 MBF] complex. However, crosslinking of the complex and immunoprecipitation with anti-Swi6 would certainly identify this region. You should be aware that an annotation of a protein in a ChIP-chip experiment is not the same as demonstrating a protein's physical interaction with DNA.
+
You will see that VAST finds more than 3,000 partially similar structures, but it would be almost impossibly tedious to manually search through the list for ''structures of protein DNA complexes'' that are ''similar to the interacting core of the APSES domain''. It turns out that our search is not specific enough in two ways: we have structural elements in our PDB file that are unnecessary for the question at hand, and thus cause the program to find irrelevant matches. But, if we constrain ourselves to just a single helix and strand (i.e. the 50-74 subdomain that has been implicated in DNA binding, the search will become too non-specific. Also we have no good way to retrieve functional information from these hits: which ones are DNA-binding proteins, that bind DNA through residues of this subdomain and for which the structure of a complex has been solved? It seems we need to define our question more precisely.
  
 +
{{task|1=
 +
# Open VMD and load the 1BM8 structure or your YFO homology model.
 +
# Display the backbone as a '''Trace''' (of CA atoms) and color by '''Index'''
 +
# In the sequence viewer, highlight residues 50 to 74.
 +
# In the representations window, find the yellow representation (with Color ID 4) that the sequence viewer has generated. Change the '''Drawing Method''' to '''NewCartoon'''.
 +
# Now (using stereo), study the topology of the region. Focus on the helix at the N-terminus of the highlighted subdomain,  it is preceded by a turn and another helix. This first helix makes interactions with the beta hairpin at the C-terminal end of the subdomain and is thus important for the orientation of these elements. (This is what is referred to as a helix-turn-helix motif, or HtH motif, it is very common in DNA-binding proteins.)
 +
# Holding the shift key in the alignment viewer, extend your selection until you cover all of the first helix, and the residues that contact the beta hairpin. I think that the first residue of interest here is residue 33.
 +
# Again holding the shift key, extend the selection at the C-terminus to include the residues of the beta hairpin to where they contact the helix at the N-terminus. I think that the last residue of interest here is residue 79.
 +
# Study the topology and arrangement of this compact subdomain. It contains the DNA-binding elements and probably most of the interactions that establish its three-dimensional shape. This subdomain even has a name: it is a ''winged helix'' DNA binding motif, a member of a very large family of DNA-binding domains. I have linked a review by Gajiwala and Burley to the end of this page; note that their definition of a canonical winged helix motif is a bit larger than what we have here, with an additional helix at the N-terminus and a second "wing".  )
 +
}}
 +
 +
 +
Armed with this insight, we can attempt again to find meaningfully similar structures.  At the '''EBI''' there are a number of very well designed structure analysis tools linked off the [http://www.ebi.ac.uk/Tools/structural.html '''Structural Analysis''' page]. As part of its MSD Services, [http://www.ebi.ac.uk/msd-srv/ssm/ '''PDBeFold'''] provides a convenient interface for structure searches for our purpose
 +
 +
{{task|1=
 +
# Navigate to the [http://www.ebi.ac.uk/msd-srv/ssm/ '''PDBeFold'''] search interface page.
 +
# Enter <code>1bm8</code> for the '''PDB code''' and choose '''Select range''' from the drop down menu. Select the residues you have defined above<!-- Select Domain would be better but is currently broken :-( Secondary Structure elements 4 to 7 i.e. those elements that span the range you have previously defined.-->.
 +
# Note that you can enter the lowest acceptable match % separately for query and target. This means: what percentage of secondary structure elements would need to be matched in either query or target to produce a hit. Keep that value at 80 for our query, since we would want to find structures with almost all of the elements of the winged helix motif. Set the  match to 10 % for the target, since we are interested in such domains even if they happen to be small subdomains of large proteins.
 +
# Keep the '''Precision''' at '''normal'''. Precision and % query match could be relaxed if we wanted to find more structures.
 +
#  Finally click on: '''Submit your query'''.
 +
# On the results page, click on the index number (in the left-hand column) of the top hit '''that is not one of our familiar Mbp1 structures''' to get a detailed view of the result. Most likely this is <code>1wq2:a</code>, an enzyme. Click on '''View Superposed'''. This will open a window with the structure coordinates superimposed in the Jmol molecular viewer. Control-click anywhere in the window area to open a menu of viewing options. Select '''Style &rarr; Stereographic &rarr; Wall-eyed viewing'''. Select '''Trace''' as the rendering. Then study the superposition. You will note that the secondary structure elements match quite well, but does this mean we have a DNA-binding domain in this sulfite reductase?
 +
}}
  
  
&nbsp;
+
All in all this appears to be well engineered software! It gives you many options to access result details for further processing. I think this can be put to very good use. But for our problem, we would have to search through too many structures because, once again, we can't tell which ones of the hits are DNA binding domains, especially domains for which the structure of a complex has been solved.
 +
 
 +
 
 +
[[Image:A5_Mbp1_subdomain.jpg|frame|none|Stereo-view of a subdomain within the 1MB1 structure that includes residues 36 to 76. The color gradient ramps from blue (36) to green (76) and the "wing" is clearly seen as the green pair of beta-strands, extending to the right of the helix-turn-helix motif.]]
  
==NCBI Map Viewer==
+
&nbsp;<br>
  
 +
APSES domains represent one branch of the tree of helix-turn-helix (HTH) DNA binding modules. (A review on HTH proteins is linked from the resources section at the bottom of this page). Winged Helix domains typically bind their cognate DNA with a "recognition helix" which precedes the beta hairpin and binds into the major groove; additional stabilizing interactions are provided by the edge of a beta-strand binding into the minor groove. This is good news: once we have determined that the APSES domain is actually an example of a larger group of transcription factors, we can compare our model to a structure of a protein-DNA complex. Superfamilies of such structural domains are compiled in the CATH database. Unfortunately CATH itself does not provide information about whether the structures have been determined as complexes. '''But''' we can search the PDB with CATH codes and restrict the results to complexes. Essentially, this should give us a list of all winged helix domains for which the structure of complexes with DNA have been determined. This works as follows:
  
 
{{task|1=
 
{{task|1=
 +
* For reference, access [http://www.cathdb.info/superfamily/1.10.10.10 CATH domain superfamily 1.10.10.10]; this is the CATH classification code we will use to find protein-DNA complexes. Click on '''Superfamily Superposition''' to get a sense of the structural core of the winged helix domain.
  
In this task you will locate and display a map view at the NCBI for the yeast Cdc6 gene.
+
# Navigate to the [http://www.pdb.org/ PDB home page] and follow the link to [http://www.pdb.org/pdb/search/advSearch.do Advanced Search]
 
+
# In the options menu for '''Choose a Query Type''' select '''Structure Features &rarr; CATH Classification Browser'''. A window will open that allows you to navigate down through the CATH tree. You can view the Class/Architecture/Topology names on the CATH page linked above. Click on '''the triangle icons''' (not the text) for '''Mainly Alpha &rarr; Orthogonal Bundle &rarr; ARC repressor mutant, subunit A''' then click on the link to '''winged helix repressor DNA binding domain'''. Or, just enter "winged helix" into the search field. This subquery should match more than 550 coordinate entries.
# Navigate to the [http://www.ncbi.nlm.nih.gov/ '''NCBI''' home page] and follow the link to '''Genomes & maps''' in the left-hand menu.
+
# Click on the '''(+)''' button behind '''Add search criteria''' to add an additional query. Select the option '''Structure Features &rarr; Macromolecule type'''. In the option menus that pop up, select '''Contains Protein&rarr;Yes, Contains DNA&rarr;Yes, Contains RNA&rarr;Ignore, Contains DNA/RNA hybrid&rarr;Ignore'''. This selects files that contain Protein-DNA complexes.
# Click on the '''Tools''' tab and find the link to the [http://www.ncbi.nlm.nih.gov/mapview/ '''Map Viewer''']
+
# Check the box below this subquery to '''Remove Similar Sequences at 90% identity''' and click on '''Submit Query'''. This query should retrieve more than 100 complexes.
# In the '''Fungi''' section, click on the latest "build" of the ''Saccharomycs cerevisiae'' genome. This takes you to an overview page of the status of the Genome project. Each chromosome is linked to its map. If you would not know what chromosome to look for, you would need to search by keyword, or gene name in the nucleotide database. Regarding Cdc6, you remember from the task above that it is located on [http://www.ncbi.nlm.nih.gov/projects/mapview/maps.cgi?taxid=4932&chr=X Chromosome X] (''i.e'' the {{WP|Roman numerals|roman numeral}} ten, not the "X-Chromosome"). You will arrive at the actual mapview of the entire Chromosome with the RefSeq accession number <code>NC_001142.9</code>. This large nucleotide record containing the entire chromosomal sequence underlies the display. 
+
# Scroll down to the beginning of the list of PDB codes and locate the '''Reports''' menu. Under the heading '''View''' select '''Gallery'''. This is a fast way to obtain an overview of the structures that have been returned. Adjust the number of '''Results''' to see all 100 images and choose '''Options&rarr;Resize medium'''.
# Enter '''Cdc6''' into the Search field and click the '''Find in This View''' button. Then zoom in a few levels.
+
# Finally we have a set of winged-helix domain/DNA complexes, for comparison. Scroll through the gallery and study how the protein binds DNA.
 
}}
 
}}
  
  
The [http://www.ncbi.nlm.nih.gov/projects/mapview/maps.cgi?TAXID=4932&CHR=X&MAPS=cntg-r,genes%5B36220.54%3A43678.04%5D&QUERY=Cdc6&zoom=10 resulting view] shows you the location and orientation of the gene on the chromosome. A number of links to various NCBI databases are given for each gene. Note that this is primarily a tool for database crossreferencing, not for integrating and displaying annotations.
+
First of all you may notice that in fact not all of the structures are really different, despite having requested only to retrieve dissimilar sequences, and not all images show DNA. This appears to be a deficiency of the algorithm. But you can also easily recognize how in most of the the structures the '''recognition helix inserts into the major groove of B-DNA''' (eg. 1BC8, 1CF7) and the wing - if clearly visible at all in the image - appears to make accessory interactions with the DNA backbone.. There is one exception: the structure 1DP7 shows how the human RFX1 protein binds DNA in a non-canonical way, through the beta-strands of the "wing". This is interesting since it suggests there is more than one way for winged helix domains to bind to DNA. We can therefore use structural superposition of '''your homology model''' and '''two of the winged-helix proteins''' to decide whether the canonical or the non-canonical mode of DNA binding seems to be more plausible for Mbp1 orthologues.  
  
  
Line 74: Line 103:
 
&nbsp;
 
&nbsp;
  
==Ensembl==
+
===Preparation and superposition of a canonical complex===
  
The EBI offers its own version of genome browsers through the Ensembl project. A large number of genomes have been annotated, cross-referenced and made available for viewing. The EBI has spent a lot of effort on automated curation of their genome offerings. '''The ensemble offerings are therefore more comprehensive and complete than those of other sources'''. In particular, you will find a genome view for YFO.  
+
&nbsp;<br>
 +
 
 +
The structure we shall use as a reference for the '''canonical binding mode''' is the Elk-1 transcription factor.
 +
 
 +
[[Image:A5_canonical_wHTH.jpg|frame|none|Stereo-view of the canonical DNA binding mode of the Winged Helix domain family. Shown here is the Elk-1 transcription factor - an ETS DNA binding domain - in complex with a high-affinity binding site (1DUX). Note how the "recognition helix" inserts into the major groove of the DNA molecule. The color gradient ramps from blue (34) to green (84). Note how the first helix of the "helix-turn-helix" architecture serves only to position the recognition helix and makes few interactions by itself.]]
 +
 
 +
The 1DUX coordinate-file contains two protein domains and two B-DNA dimers in one asymmetric unit. For simplicity, you should delete the second copy of the complex from the PDB file. (Remember that PDB files are simply text files that can be edited.)
  
 
{{task|1=
 
{{task|1=
 +
# Find the 1DUX structure in the image gallery and open the 1DUX structure explorer page in a separate window. Download the coordinates to your computer.
 +
# Open the coordinate file in a text-editor (TextEdit or Notepad - '''NOT''' MS-Word!) and delete the coordinates for chains <code>D</code>,<code>E</code> and <code>F</code>; you may also delete all <code>HETATM</code> records and the <code>MASTER</code> record. Save the file with a different name, e.g. 1DUX_monomer.pdb .
 +
# Open VMD and load your homology model. Turn off the axes, display the model as a Tube representation in stereo, and color it by Index. Then load your edited 1DUX file, display this coordinate set in a tube representation as well, and color it by ColorID in some color you like. It is important that you can distinguish easily which structure is which.
 +
# You could use the Extensions&rarr;Analysis&rarr;RMSD calculator interface to superimpose the two strutcures '''IF''' you would know which residues correspond to each other. Sometimes it is useful to do exactly that: define exact correspondences between residue pairs and superimpose according to these selected pairs. For our purpose it is much simpler to use the Multiseq tool (and the structures are simple and small enough that the STAMP algorithm for structural alignment can define corresponding residue pairs automatically). Open the '''multiseq''' extension window, select the check-boxes next to both protein structures, and open the '''Tools&rarr;Stamp Structural Alignment''' interface.
 +
# In the "'Stamp Alignment Options'" window, check the radio-button for ''Align the following ...'' '''Marked Structures''' and click on '''OK'''.
 +
# In the '''Graphical Representations''' window, double-click on all "NewCartoon" representations for both molecules, to undisplay them.
 +
# You should now see a superimposed tube model of your homology model and the 1DUX protein-DNA complex. You can explore it, display side-chains etc. and study some of the details of how a transcription factor recognizes and binds to its cognate DNA sequence. However, remember that your '''model''''s side-chain orientations have not been determined experimentally but inferred from the '''template''', and that the template's structure was determined in the absence of bound DNA ligand.
 +
 +
# Orient and scale your superimposed structures so that their structural similarity is apparent, and the recognition helix can be clearly seen inserting into the DNA major groove. You may want to keep a copy of the image for future reference. Consider which parts of the structure appear to superimpose best.  Note whether it is plausible that your '''model''' could bind a B-DNA double-helix in this orientation.
 +
}}
 +
 +
&nbsp;<br>
 +
&nbsp;
  
In this task you will review the ensembl view of the YFO ortholog to yeast CDC6.
 
  
# Navigate to the [http://fungi.ensembl.org/index.html '''EnsemblFungi'''] page (easy to find via Google).
+
===Preparation and superposition of a non-canonical complex===
# Select ''Saccharomyces cerevisiae'' from the species list.
 
# '''Search''' for  Cdc6 as a search term in the ''Search Saccharomyces cerevisiae ...'' field.
 
# Click on [http://fungi.ensembl.org/Saccharomyces_cerevisiae/Gene/Summary?g=YJL194W;r=X:69338-70879;t=YJL194W CDC6 (YJL194W)]
 
  
You will be taken to a browser view of the genome. Tracts can be switched on and off through the menu on the left hand side.
 
  
# Find the link to [http://fungi.ensembl.org/Saccharomyces_cerevisiae/Gene/Compara_Ortholog?g=YJL194W;r=X:69338-70879;t=YJL194W '''Orthologues'''] under the '''Fungal Compara''' section in the menu.
+
The structure displaying a non-canonical complex between a winged-helix domain and its cognate DNA binding site is the human Regulatory Factor X.
# In the resulting page, find the YFO orthologue and click on the link in the '''Location''' column.
 
# On the Browser page, click on the cogwheel icon in the bottom left bar of the lower pane to configure tracks.
 
# On the configuration page, click on '''Sequence''' in the left-hand menu and click the (check)-boxes to turn '''Contigs''' off and '''Translated sequence''' on. Click the checkmark in the top-right corner of the configuration window to return to the browser view.
 
# Zoom in until you see the display of the actual nucleotides and the six reading frames.
 
  
}}
+
[[Image:A5_non-canonical_wHTH.jpg|frame|none|Stereo-view of a non-canonical wHTH-DNA complex, discovered in with the stucture of human Regulatory Factor X (hRFX) binding its cognate X-box DNA sequence (1DP7). Note how the helix that coresponds to the recognition helix in the canonical domain lies across the minor groove whereas the beta-"wing" inserts into the major groove. The color gradient ramps from blue (18) to green (68).]]
 +
 
 +
 
 +
Before we can work with this however, we have to fix an annoying problem. If you download and view the <code>1DP7</code> structure in VMD, you will notice that there is only a single strand of DNA! Where is the second strand of the double helix? It is not in the coordinate file, because it happens to be exactly equivalent to the frist starnd, rotated around a two-fold axis of symmetry in the crystal lattice. We need to download and work with the so-called '''Biological Assembly''' instead.  But there is a problem related to the way the PDB stores replicates in biological assemblies. The PDB generates the additional chains as copies of the original and delineates them with <code>MODEL</code> and <code>ENDMDL</code> records, just like in a multi-structure NMR file. The chain IDs and the atom numbers are the same as the original. The PDB file thus contains the '''same molecule in two different orientations''', not '''two independent molecules'''. This is an important difference regarding how such molecules are displayed by VMD. '''If you try to use the biological unit file of the PDB, VMD does not recognize that there is a second molecule present and displays only one chain.''' And that looks exactly like the one we have seen before. We have to edit the file, extract the second DNA molecule, change its chain ID and then append it to the original 1DP7 structure<ref>My apologies if this is tedious. '''But''' in the real world, we encounter such problems a lot and I would be remiss not to use this opportunity to let you practice how to fix the issue that could otherwise be a roadblock in a project of yours.</ref>...
  
 +
{{task|1=
 +
# On the structure explorer page for 1DP7, select the option '''Download Files''' &rarr; '''PDB File'''.
 +
# Also select the option '''Download Files''' &rarr; '''Biological Assembly'''.
 +
# Uncompress the biological assembly file.
 +
# Open the file in a text editor.
 +
# Delete everything except the '''second DNA molecule'''. This comes after the <code>MODEL  2</code> line and has chain ID '''D'''. Keep the <code>TER</code> and <code>END</code> lines. Save this with a new filename (e.g. <code>1DP7_DNAonly.pdb</code>).
 +
# Also delete all <code>HETATM</code> records for <code>HOH</code>, <code>PEG</code> and <code>EDO</code>, as well as the entire second protein chain and the <code>MASTER</code> record. The resulting file should only contain the DNA chain and its copy and one protein chain. Save the file with a new name, eg. <code>1DP7_BDNA.PDB</code>.
 +
# Use a similar procedure as [[BIO_Assignment_Week_8#R code: renumbering the model in the last assignment]] to change the  chain ID.
  
This is a very comprehensive offering in terms of sequences. However, ensemble too offers little in terms of annotations of DNA elements, expression levels and the like. Nevertheless, since it is the only database that has YFO annotated, it would be the tool to go to if you were to compare syntenic regions or genomic context between different species.
+
<source lang="rsplus">
 +
PDBin <- "1DP7_DNAonly.pdb"
 +
PDBout <- "1DP7_DNAnewChain.pdb"
  
 +
pdb  <- read.pdb(PDBin)
 +
pdb$atom[,"chain"] <- "E"
 +
write.pdb(pdb=pdb,file=PDBout)
 +
</source>
  
 +
# Use your text-editor to open both the <code>1DP7.pdb</code> structure file and the  <code>1DP7_DNAnewChain.pdb</code>. Copy the DNA coordinates, paste them into the original file before the <code>END</code> line and save.
 +
# Open the edited coordinate file with VMD. You should see '''one protein chain''' and a '''B-DNA double helix'''. (Actually, the BDNA helix has a gap, because the R-library did not read the BRDU nucleotide as DNA). Switch to stereo viewing and spend some time to see how '''amazingly beautiful''' the complementarity between the protein and the DNA helix is (you might want to display ''protein'' and ''nucleic'' in separate representations and color the DNA chain by ''Position'' &rarr; ''Radial'' for clarity) ... in particular, appreciate how not all positively charged side chains contact the phosphate backbone, but some pnetrate into the helix and make detailed interactions with the nucleobases!
 +
# Then clear all molecules
 +
# In VMD, open '''Extensions&rarr;Analysis&rarr;MultiSeq'''. When you run MultiSeq for the first time, you will be asked for a directory in which to store metadata. You can use the default, or a directory of your choice; you may subsequently skip all steps that ask you to install "required" databases locally since we will not need them for this task.
 +
# Choose '''File&rarr;Import Data''', browse to your directory and load one by one:
 +
:: -Your model;
 +
:: -The 1DUX complex;
 +
:: -The 1DP7 complex.
 +
# Mark all three protein chains by selecting the checkbox next to their name and choose '''Tools&rarr; STAMP structural alignment'''.
 +
# '''Align''' the '''Marked Structures''', choose a '''scanscore''' of '''2''' and '''scanslide''' of '''5'''. Also choose '''Slow scan'''. You may have to play around with the setting to get the molecules to superimpose: but the '''can''' be superimposed quite well - at least the DNA-binding helices and the wings should line up.
 +
# In the graphical representations window, double-click on the cartoon representations that multiseq has generated to undisplay them, also undisplay the Tube representation of 1DUX. Then create a Tube representation for 1DP7, and select a Color by ColorID (a different color that you like). The resulting scene should look similar to the one you have created above, only with 1DP7 in place of 1DUX and colored differently.
 +
# Orient and scale your superimposed structures so that their structural similarity is apparent, and the differences in binding elements is clear. Perhaps visualizing a solvent accessible surface of the DNA will help understand the spatial requirements of the complex formation. You may want to keep a copy of the image for future reference. Note whether it is plausible that your '''model''' could bind a B-DNA double-helix in the "alternative" conformation.
 +
}}
  
  
 
&nbsp;
 
&nbsp;
  
==The UCSC genome browser==
+
<!--
 +
===Coloring by conservation===
  
The University of California Santa Cruz (UCSC) Genome Browser Project has the largest offering of annotation information. However it is strictly model-organism oriented and you will probably not find YFO among its curated genomes. Nevertheless, if you are studying eg. human genes, or yeast, the UCSC browser should be your first choice.
+
With the superimposed coordinates, you can begin to get a sense whether either or both binding modes could be appropriate for a protein-DNA complex in your Mbp1 orthologue. But these are geometrical criteria only, and the protein in your species may be flexible enough to adopt a different conformation in a complex, and different again from your model. A more powerful way to analyze such hypothetical complexes is to look at conservation patterns. With VMD, you can import a sequence alignment into the MultiSeq extension and color residies by conservation. The protocol below assumes
 +
 
 +
*You have prealigned the reference Mbp1 proteins with your species' Mbp1 orthologue;
 +
*You have saved the alignment in a CLUSTAL format.
 +
 
 +
You can use Jalview or any other MSA server to do so. You can even do this by hand - there should be few if any indels and the correct alignment is easy to see.
  
 
{{task|1=
 
{{task|1=
 +
;Load the Mbp1 APSES alignment into MultiSeq.
 +
 +
:(A) 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).
 +
:(B) Open the alignment file, click on '''Ok''' to import the data, it will take a short while to load. If the data can't be loaded, the file may have the wrong extension: .aln is required.
 +
:(C) find the Mbp1_SACCE 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).
  
In this task you will the UCSC genome browser view of the yeast Cdc6 gene and its human orthologue. You will explore some of the very large number of tracks that are available for both and compare transcription factor binding regions.
+
You will see that the 1MB1 sequence and the APSES 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.
  
# Navigate to the [http://genome.ucsc.edu/ '''UCSC''' Genome Bioinformatics entry page] and follow the link to the '''Genome Browser''' in the left-hand menu.
+
;Bring the 1MB1 sequence in register with the APSES alignment.
# From the available menus, access the ''S. cerevisiae'' information ('''group &rarr; other''') and enter Cdc6 as the '''search term'''.
+
:(A)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.
# Click on the link to the [http://genome.ucsc.edu/cgi-bin/hgTracks?position=chrX:69338-70879&hgsid=311433759&sgdGene=pack&hgFind.matches=YJL194W, Cdc6 gene] on chromosome X.
+
:(B) Select '''Edit &rarr; Enable Editing... &rarr; Gaps only''' to allow changing indels.
# Click on the button to zoom out '''3x''' - we want to see the upstream regulatory region.
+
:(C) 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 1MB1: <code>S I M ...</code>
# In the subsection for '''Expression and Regulation''', find the menu for '''Regulatory Code''' and select '''full'''; select '''hide''' for all other expression tracks. Click '''refresh'''.
+
:(D) Now insert as many gaps as you need into the structure sequence, to align it completely with the Mbp1_SACCE 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 the session from a saved state. It is a bit annoying but not mission-critical.)
 +
:(E) When you are done, it may be prudent to save the state of your alignment. Use '''File &rarr; Save Session...'''  
  
Up to now, this looks very similar to the SGD genome browser.
+
;Color by similarity
 +
:(A) 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.
 +
:(B) 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.
 +
:(C) Navigate to the '''Representations''' window and apply the color scheme to your tube-and-sidechain representation: double-click on the NewCartoon representation to hide it and use '''User''' coloring of your ''Tube'' and ''Licorice'' representations to apply the sequence similarity color gradient that MultiSeq has calculated.  
  
# Open a second window, and access the UCSC Genome browser for the '''human genome'''. Search for CDC6 and click the link to the ''Homo sapiens'' cell division cycle 6 homolog (''S. cerevisiae'') (CDC6) on chromosome 17.
+
&nbsp;<br><div style="padding: 5px; background: #DDDDEE;">
# Study the [http://genome.ucsc.edu/cgi-bin/hgTracks?position=chr17:38444146-38459413&hgsid=353080265&knownGene=pack&hgFind.matches=uc002huj.1, Genome Browser view of the CDC6 homolog].
+
* Once you have colored the residues of your model by conservation, create another informative stereo-image and paste it into your assignment.
## In particular, note the extensive functional annotations of DNA and the alignments of vertebrate syntenic regions that allow detailed genomic comparisons.
 
## Distinguish between exon and intron sequence.
 
## Note that the mammal Conservation track has high values for all of the exons, but not only for exons.
 
# Zoom out '''1.5x''' and click/slide the gene to the right to view the upstream regulatory region.
 
# On the page, note the '''large''' number of available tracks that have been integrated into this view. Most of them are switched off. Find the '''Regulation''' section, and click on '''ENCODE Transcription Factor Binding Tracks''' to access the information page on where exactly this data originates from. Note that you can switch individual experiments on or off on this page, as well as setting the display format for all of the results. Leave all of the experiments checked, set the display to '''show''' and click the '''Submit''' button.
 
# Get a sense of the amount of information that is displayed here and note that all experiments agree on a regulatory region that ranges from about 1.5kb upstream to 0.5 kb downstream of the transcription start.
 
# Go back to the '''ENCODE Transcription Factor Binding Tracks''' page uncheck all of the data sources except for the ENCODE/Stanford/Yale/USC/Harvard Chip-seq experiment (SYDH TFBS), set the format to '''full''', '''Display mode: show''' and click '''submit'''.
 
# The resulting tracks are an excellent view of the kind of information that is provided by ChIP-seq experiments in which bound transcription factors are crosslinked to the DNA, immuno-precipitated with transcription factor specific antibodies, and the co-precipitated DNA sequenced with high-throughput sequencing methods. Note that most sequence tags are found in a unimodal distribution close to the transcription start, but some TFs (e.g. Rad21) apparently have more than one binding site.
 
# Now scroll down to the track sections, '''hide''' the '''ENCODE TF binding data''' and show the '''full''' view of the '''TFBS conserved''' track - a consensus of human/mouse and rat annotated TF binding sites. Click on the small vertical bar in the <code>V$E2F_02</code> row, this will take you to a detailed information page on this transcription factor, with cross-references to the databases.
 
 
}}
 
}}
  
 +
&nbsp;
 +
-->
 +
 +
== Interpretation==
 +
<!--
 +
Analysis of the ligand binding site:
  
Based on this kind of information, it should be straightforward to identify human transcription factors that potentially regulate human Cdc6 and determine - via sequence comparisons - whether any of them are homologous to any of the yeast transcription factors. Through a detailed analysis of existing systems, their regulatory components and the conservation of regulation, one can in principle establish functional equivalences across large evolutionary distances.
+
* http://dnasite.limlab.ibms.sinica.edu.tw/
 +
* http://proline.biochem.iisc.ernet.in/pocketannotate/
 +
* http://www.biosolveit.de/PoseView/
 +
 
 +
*Comparison with seq2logo
 +
{{#pmid: 19483101}}
 +
*protedna server PMID: 19483101
 +
* http://serv.csbb.ntu.edu.tw/ProteDNA/
 +
* http://protedna.csie.ntu.edu.tw/
 +
* Multi Harmony
 +
{{#pmid: 20525785}}
 +
 
 +
-->
  
  
The UCSC browser has a sometimes bewildering amount of information available. But its curators are aware of the need for educating users regarding the utility of their tools.
 
  
 
{{task|1=
 
{{task|1=
 
+
# Spend some time studying the complex.
In this task you will access some of the tutorial information that UCSC provides.
+
# Recapitulate in your mind how we have arrived at this comparison, in particular, how this was possible even though the sequence similarity between these proteins is low - none of these winged helix domains came up as a result of our previous BLAST search in the PDB.
# Return to the [http://genome.ucsc.edu/ '''UCSC''' Genome Bioinformatics entry page] and follow the link to '''Training''' in the left-hand menu.
+
# You should clearly think about the following question: considering the position of the two DNA helices relative to the YFO structural model, which binding mode appears to be more plausible for protein-DNA interactions in the YFO Mbp1 APSES domains? Is it the canonical, or the non-canonical binding mode? Is there evidence that allows you to distinguish between the  two modes?
# Follow the link to the [http://www.openhelix.com/ucsc '''OpenHelix UCSC tutorials'''].
+
# Before you quit VMD, save the "state" of your session so you can reload it later. We will look at residue conservation once we have built phylogenetic trees. In the main VMD window, choose '''File&rarr;Save State...'''.
# Download the Hands-on exercise PDF file and work through '''Exercise 2'''
 
 
}}
 
}}
  
This exercise includes a number of interesting options to work with the UCSC data - the BLAT tool for genomic region alignment and the selective display of SNP annotations.
+
<!--
 +
== R code: conservation scores and sequence weighting==
 +
-->
  
; Optional
+
;That is all.
* Work through exercise one and three of the OpenHelix UCSC introduction.
 
* Access the [http://www.openhelix.com/ENCODE2 OpenHelix '''ENCODE''' tutorial], download the '''Hands-on Exercises''' pdf and work through the exercises. Exercise 3 is particularly valuable, as it teaches you how to create results from complex intersections of queries.
 
* Study the ''User's guide to ENCODE'' paper linked below.
 
  
  
Line 159: Line 249:
  
 
== Links and resources ==
 
== Links and resources ==
{{#pmid: 22764121}}
+
{{#pmid: 10679470}}
{{#pmid: 21526222}}
+
{{#pmid: 15808743}}
  
  
<!-- {{#pmid: 19957275}} -->
 
 
<!-- {{WWW|WWW_GMOD}} -->
 
<!-- {{WWW|WWW_GMOD}} -->
 
<!-- <div class="reference-box">[http://www.ncbi.nlm.nih.gov]</div> -->
 
<!-- <div class="reference-box">[http://www.ncbi.nlm.nih.gov]</div> -->

Revision as of 18:37, 18 November 2014

Assignment for Week 10
Protein Ligand Complex

Note! This assignment is currently inactive. Major and minor unannounced changes may be made at any time.

 
 

Concepts and activities (and reading, if applicable) for this assignment will be topics on next week's quiz.



 

Introduction

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[1], 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. However, you may remember from the third assignment that the APSES domains in fungi seem to be a relatively small family. And there is no structure available of an APSES domain-DNA complex. How can we find a coordinate set of a structurally similar protein-DNA complex?

This assignment is based on the homology model you built. You will (1) identify similar structures of distantly related domains for which protein-DNA complexes are known, (2) assemble a hypothetical complex structure and (3) consider whether the available evidence allows you to distinguish between different modes of ligand binding,

Modeling a DNA ligand

 

 


Finding a similar protein-DNA complex

 

Remember that homologous sequences can have diverged to the point where their sequence similarity is no longer recognizable, however their structure may be quite well conserved. Thus if we could find similar structures in the PDB, these might provide us with some plausible hypotheses for how DNA is bound by APSES domains. We thus need a tool similar to BLAST, but not for the purpose of sequence alignment, but for structure alignment. A kind of BLAST for structures. Just like with sequence searches, we might not want to search with the entire protein, if we are interested in is a subdomain that binds to DNA. Attempting to match all structural elements in addition to the ones we are actually interested in is likely to make the search less specific - we would find false positives that are similar to some irrelevant part of our structure. However, defining too small of a subdomain would also lead to a loss of specificity: in the extreme it is easy to imagine that the search for e.g. a single helix would retrieve very many hits that would be quite meaningless.



At the NCBI, VAST is provided as a search tool for structural similarity search.

Task:

  1. Navigate to the VAST search interface page.
  2. Enter 1bm8 as the PDB ID to search for and click Go.
  3. Follow the link to Related Structures.
  4. Study the result.


You will see that VAST finds more than 3,000 partially similar structures, but it would be almost impossibly tedious to manually search through the list for structures of protein DNA complexes that are similar to the interacting core of the APSES domain. It turns out that our search is not specific enough in two ways: we have structural elements in our PDB file that are unnecessary for the question at hand, and thus cause the program to find irrelevant matches. But, if we constrain ourselves to just a single helix and strand (i.e. the 50-74 subdomain that has been implicated in DNA binding, the search will become too non-specific. Also we have no good way to retrieve functional information from these hits: which ones are DNA-binding proteins, that bind DNA through residues of this subdomain and for which the structure of a complex has been solved? It seems we need to define our question more precisely.

Task:

  1. Open VMD and load the 1BM8 structure or your YFO homology model.
  2. Display the backbone as a Trace (of CA atoms) and color by Index
  3. In the sequence viewer, highlight residues 50 to 74.
  4. In the representations window, find the yellow representation (with Color ID 4) that the sequence viewer has generated. Change the Drawing Method to NewCartoon.
  5. Now (using stereo), study the topology of the region. Focus on the helix at the N-terminus of the highlighted subdomain, it is preceded by a turn and another helix. This first helix makes interactions with the beta hairpin at the C-terminal end of the subdomain and is thus important for the orientation of these elements. (This is what is referred to as a helix-turn-helix motif, or HtH motif, it is very common in DNA-binding proteins.)
  6. Holding the shift key in the alignment viewer, extend your selection until you cover all of the first helix, and the residues that contact the beta hairpin. I think that the first residue of interest here is residue 33.
  7. Again holding the shift key, extend the selection at the C-terminus to include the residues of the beta hairpin to where they contact the helix at the N-terminus. I think that the last residue of interest here is residue 79.
  8. Study the topology and arrangement of this compact subdomain. It contains the DNA-binding elements and probably most of the interactions that establish its three-dimensional shape. This subdomain even has a name: it is a winged helix DNA binding motif, a member of a very large family of DNA-binding domains. I have linked a review by Gajiwala and Burley to the end of this page; note that their definition of a canonical winged helix motif is a bit larger than what we have here, with an additional helix at the N-terminus and a second "wing". )


Armed with this insight, we can attempt again to find meaningfully similar structures. At the EBI there are a number of very well designed structure analysis tools linked off the Structural Analysis page. As part of its MSD Services, PDBeFold provides a convenient interface for structure searches for our purpose

Task:

  1. Navigate to the PDBeFold search interface page.
  2. Enter 1bm8 for the PDB code and choose Select range from the drop down menu. Select the residues you have defined above.
  3. Note that you can enter the lowest acceptable match % separately for query and target. This means: what percentage of secondary structure elements would need to be matched in either query or target to produce a hit. Keep that value at 80 for our query, since we would want to find structures with almost all of the elements of the winged helix motif. Set the match to 10 % for the target, since we are interested in such domains even if they happen to be small subdomains of large proteins.
  4. Keep the Precision at normal. Precision and % query match could be relaxed if we wanted to find more structures.
  5. Finally click on: Submit your query.
  6. On the results page, click on the index number (in the left-hand column) of the top hit that is not one of our familiar Mbp1 structures to get a detailed view of the result. Most likely this is 1wq2:a, an enzyme. Click on View Superposed. This will open a window with the structure coordinates superimposed in the Jmol molecular viewer. Control-click anywhere in the window area to open a menu of viewing options. Select Style → Stereographic → Wall-eyed viewing. Select Trace as the rendering. Then study the superposition. You will note that the secondary structure elements match quite well, but does this mean we have a DNA-binding domain in this sulfite reductase?


All in all this appears to be well engineered software! It gives you many options to access result details for further processing. I think this can be put to very good use. But for our problem, we would have to search through too many structures because, once again, we can't tell which ones of the hits are DNA binding domains, especially domains for which the structure of a complex has been solved.


Stereo-view of a subdomain within the 1MB1 structure that includes residues 36 to 76. The color gradient ramps from blue (36) to green (76) and the "wing" is clearly seen as the green pair of beta-strands, extending to the right of the helix-turn-helix motif.

 

APSES domains represent one branch of the tree of helix-turn-helix (HTH) DNA binding modules. (A review on HTH proteins is linked from the resources section at the bottom of this page). Winged Helix domains typically bind their cognate DNA with a "recognition helix" which precedes the beta hairpin and binds into the major groove; additional stabilizing interactions are provided by the edge of a beta-strand binding into the minor groove. This is good news: once we have determined that the APSES domain is actually an example of a larger group of transcription factors, we can compare our model to a structure of a protein-DNA complex. Superfamilies of such structural domains are compiled in the CATH database. Unfortunately CATH itself does not provide information about whether the structures have been determined as complexes. But we can search the PDB with CATH codes and restrict the results to complexes. Essentially, this should give us a list of all winged helix domains for which the structure of complexes with DNA have been determined. This works as follows:

Task:

  • For reference, access CATH domain superfamily 1.10.10.10; this is the CATH classification code we will use to find protein-DNA complexes. Click on Superfamily Superposition to get a sense of the structural core of the winged helix domain.
  1. Navigate to the PDB home page and follow the link to Advanced Search
  2. In the options menu for Choose a Query Type select Structure Features → CATH Classification Browser. A window will open that allows you to navigate down through the CATH tree. You can view the Class/Architecture/Topology names on the CATH page linked above. Click on the triangle icons (not the text) for Mainly Alpha → Orthogonal Bundle → ARC repressor mutant, subunit A then click on the link to winged helix repressor DNA binding domain. Or, just enter "winged helix" into the search field. This subquery should match more than 550 coordinate entries.
  3. Click on the (+) button behind Add search criteria to add an additional query. Select the option Structure Features → Macromolecule type. In the option menus that pop up, select Contains Protein→Yes, Contains DNA→Yes, Contains RNA→Ignore, Contains DNA/RNA hybrid→Ignore. This selects files that contain Protein-DNA complexes.
  4. Check the box below this subquery to Remove Similar Sequences at 90% identity and click on Submit Query. This query should retrieve more than 100 complexes.
  5. Scroll down to the beginning of the list of PDB codes and locate the Reports menu. Under the heading View select Gallery. This is a fast way to obtain an overview of the structures that have been returned. Adjust the number of Results to see all 100 images and choose Options→Resize medium.
  6. Finally we have a set of winged-helix domain/DNA complexes, for comparison. Scroll through the gallery and study how the protein binds DNA.


First of all you may notice that in fact not all of the structures are really different, despite having requested only to retrieve dissimilar sequences, and not all images show DNA. This appears to be a deficiency of the algorithm. But you can also easily recognize how in most of the the structures the recognition helix inserts into the major groove of B-DNA (eg. 1BC8, 1CF7) and the wing - if clearly visible at all in the image - appears to make accessory interactions with the DNA backbone.. There is one exception: the structure 1DP7 shows how the human RFX1 protein binds DNA in a non-canonical way, through the beta-strands of the "wing". This is interesting since it suggests there is more than one way for winged helix domains to bind to DNA. We can therefore use structural superposition of your homology model and two of the winged-helix proteins to decide whether the canonical or the non-canonical mode of DNA binding seems to be more plausible for Mbp1 orthologues.


 

Preparation and superposition of a canonical complex

 

The structure we shall use as a reference for the canonical binding mode is the Elk-1 transcription factor.

Stereo-view of the canonical DNA binding mode of the Winged Helix domain family. Shown here is the Elk-1 transcription factor - an ETS DNA binding domain - in complex with a high-affinity binding site (1DUX). Note how the "recognition helix" inserts into the major groove of the DNA molecule. The color gradient ramps from blue (34) to green (84). Note how the first helix of the "helix-turn-helix" architecture serves only to position the recognition helix and makes few interactions by itself.

The 1DUX coordinate-file contains two protein domains and two B-DNA dimers in one asymmetric unit. For simplicity, you should delete the second copy of the complex from the PDB file. (Remember that PDB files are simply text files that can be edited.)

Task:

  1. Find the 1DUX structure in the image gallery and open the 1DUX structure explorer page in a separate window. Download the coordinates to your computer.
  2. Open the coordinate file in a text-editor (TextEdit or Notepad - NOT MS-Word!) and delete the coordinates for chains D,E and F; you may also delete all HETATM records and the MASTER record. Save the file with a different name, e.g. 1DUX_monomer.pdb .
  3. Open VMD and load your homology model. Turn off the axes, display the model as a Tube representation in stereo, and color it by Index. Then load your edited 1DUX file, display this coordinate set in a tube representation as well, and color it by ColorID in some color you like. It is important that you can distinguish easily which structure is which.
  4. You could use the Extensions→Analysis→RMSD calculator interface to superimpose the two strutcures IF you would know which residues correspond to each other. Sometimes it is useful to do exactly that: define exact correspondences between residue pairs and superimpose according to these selected pairs. For our purpose it is much simpler to use the Multiseq tool (and the structures are simple and small enough that the STAMP algorithm for structural alignment can define corresponding residue pairs automatically). Open the multiseq extension window, select the check-boxes next to both protein structures, and open the Tools→Stamp Structural Alignment interface.
  5. In the "'Stamp Alignment Options'" window, check the radio-button for Align the following ... Marked Structures and click on OK.
  6. In the Graphical Representations window, double-click on all "NewCartoon" representations for both molecules, to undisplay them.
  7. You should now see a superimposed tube model of your homology model and the 1DUX protein-DNA complex. You can explore it, display side-chains etc. and study some of the details of how a transcription factor recognizes and binds to its cognate DNA sequence. However, remember that your model's side-chain orientations have not been determined experimentally but inferred from the template, and that the template's structure was determined in the absence of bound DNA ligand.
  1. Orient and scale your superimposed structures so that their structural similarity is apparent, and the recognition helix can be clearly seen inserting into the DNA major groove. You may want to keep a copy of the image for future reference. Consider which parts of the structure appear to superimpose best. Note whether it is plausible that your model could bind a B-DNA double-helix in this orientation.

 
 


Preparation and superposition of a non-canonical complex

The structure displaying a non-canonical complex between a winged-helix domain and its cognate DNA binding site is the human Regulatory Factor X.

Stereo-view of a non-canonical wHTH-DNA complex, discovered in with the stucture of human Regulatory Factor X (hRFX) binding its cognate X-box DNA sequence (1DP7). Note how the helix that coresponds to the recognition helix in the canonical domain lies across the minor groove whereas the beta-"wing" inserts into the major groove. The color gradient ramps from blue (18) to green (68).


Before we can work with this however, we have to fix an annoying problem. If you download and view the 1DP7 structure in VMD, you will notice that there is only a single strand of DNA! Where is the second strand of the double helix? It is not in the coordinate file, because it happens to be exactly equivalent to the frist starnd, rotated around a two-fold axis of symmetry in the crystal lattice. We need to download and work with the so-called Biological Assembly instead. But there is a problem related to the way the PDB stores replicates in biological assemblies. The PDB generates the additional chains as copies of the original and delineates them with MODEL and ENDMDL records, just like in a multi-structure NMR file. The chain IDs and the atom numbers are the same as the original. The PDB file thus contains the same molecule in two different orientations, not two independent molecules. This is an important difference regarding how such molecules are displayed by VMD. If you try to use the biological unit file of the PDB, VMD does not recognize that there is a second molecule present and displays only one chain. And that looks exactly like the one we have seen before. We have to edit the file, extract the second DNA molecule, change its chain ID and then append it to the original 1DP7 structure[2]...

Task:

  1. On the structure explorer page for 1DP7, select the option Download FilesPDB File.
  2. Also select the option Download FilesBiological Assembly.
  3. Uncompress the biological assembly file.
  4. Open the file in a text editor.
  5. Delete everything except the second DNA molecule. This comes after the MODEL 2 line and has chain ID D. Keep the TER and END lines. Save this with a new filename (e.g. 1DP7_DNAonly.pdb).
  6. Also delete all HETATM records for HOH, PEG and EDO, as well as the entire second protein chain and the MASTER record. The resulting file should only contain the DNA chain and its copy and one protein chain. Save the file with a new name, eg. 1DP7_BDNA.PDB.
  7. Use a similar procedure as BIO_Assignment_Week_8#R code: renumbering the model in the last assignment to change the chain ID.
PDBin <- "1DP7_DNAonly.pdb"
PDBout <- "1DP7_DNAnewChain.pdb"

pdb  <- read.pdb(PDBin)
pdb$atom[,"chain"] <- "E"
write.pdb(pdb=pdb,file=PDBout)
  1. Use your text-editor to open both the 1DP7.pdb structure file and the 1DP7_DNAnewChain.pdb. Copy the DNA coordinates, paste them into the original file before the END line and save.
  2. Open the edited coordinate file with VMD. You should see one protein chain and a B-DNA double helix. (Actually, the BDNA helix has a gap, because the R-library did not read the BRDU nucleotide as DNA). Switch to stereo viewing and spend some time to see how amazingly beautiful the complementarity between the protein and the DNA helix is (you might want to display protein and nucleic in separate representations and color the DNA chain by PositionRadial for clarity) ... in particular, appreciate how not all positively charged side chains contact the phosphate backbone, but some pnetrate into the helix and make detailed interactions with the nucleobases!
  3. Then clear all molecules
  4. In VMD, open Extensions→Analysis→MultiSeq. When you run MultiSeq for the first time, you will be asked for a directory in which to store metadata. You can use the default, or a directory of your choice; you may subsequently skip all steps that ask you to install "required" databases locally since we will not need them for this task.
  5. Choose File→Import Data, browse to your directory and load one by one:
-Your model;
-The 1DUX complex;
-The 1DP7 complex.
  1. Mark all three protein chains by selecting the checkbox next to their name and choose Tools→ STAMP structural alignment.
  2. Align the Marked Structures, choose a scanscore of 2 and scanslide of 5. Also choose Slow scan. You may have to play around with the setting to get the molecules to superimpose: but the can be superimposed quite well - at least the DNA-binding helices and the wings should line up.
  3. In the graphical representations window, double-click on the cartoon representations that multiseq has generated to undisplay them, also undisplay the Tube representation of 1DUX. Then create a Tube representation for 1DP7, and select a Color by ColorID (a different color that you like). The resulting scene should look similar to the one you have created above, only with 1DP7 in place of 1DUX and colored differently.
  4. Orient and scale your superimposed structures so that their structural similarity is apparent, and the differences in binding elements is clear. Perhaps visualizing a solvent accessible surface of the DNA will help understand the spatial requirements of the complex formation. You may want to keep a copy of the image for future reference. Note whether it is plausible that your model could bind a B-DNA double-helix in the "alternative" conformation.


 


Interpretation

Task:

  1. Spend some time studying the complex.
  2. Recapitulate in your mind how we have arrived at this comparison, in particular, how this was possible even though the sequence similarity between these proteins is low - none of these winged helix domains came up as a result of our previous BLAST search in the PDB.
  3. You should clearly think about the following question: considering the position of the two DNA helices relative to the YFO structural model, which binding mode appears to be more plausible for protein-DNA interactions in the YFO Mbp1 APSES domains? Is it the canonical, or the non-canonical binding mode? Is there evidence that allows you to distinguish between the two modes?
  4. Before you quit VMD, save the "state" of your session so you can reload it later. We will look at residue conservation once we have built phylogenetic trees. In the main VMD window, choose File→Save State....


That is all.


 

Links and resources

Gajiwala & Burley (2000) Winged helix proteins. Curr Opin Struct Biol 10:110-6. (pmid: 10679470)

PubMed ] [ DOI ] The winged helix proteins constitute a subfamily within the large ensemble of helix-turn-helix proteins. Since the discovery of the winged helix/fork head motif in 1993, a large number of topologically related proteins with diverse biological functions have been characterized by X-ray crystallography and solution NMR spectroscopy. Recently, a winged helix transcription factor (RFX1) was shown to bind DNA using unprecedented interactions between one of its eponymous wings and the major groove. This surprising observation suggests that the winged helix proteins can be subdivided into at least two classes with radically different modes of DNA recognition.

Aravind et al. (2005) The many faces of the helix-turn-helix domain: transcription regulation and beyond. FEMS Microbiol Rev 29:231-62. (pmid: 15808743)

PubMed ] [ DOI ] The helix-turn-helix (HTH) domain is a common denominator in basal and specific transcription factors from the three super-kingdoms of life. At its core, the domain comprises of an open tri-helical bundle, which typically binds DNA with the 3rd helix. Drawing on the wealth of data that has accumulated over two decades since the discovery of the domain, we present an overview of the natural history of the HTH domain from the viewpoint of structural analysis and comparative genomics. In structural terms, the HTH domains have developed several elaborations on the basic 3-helical core, such as the tetra-helical bundle, the winged-helix and the ribbon-helix-helix type configurations. In functional terms, the HTH domains are present in the most prevalent transcription factors of all prokaryotic genomes and some eukaryotic genomes. They have been recruited to a wide range of functions beyond transcription regulation, which include DNA repair and replication, RNA metabolism and protein-protein interactions in diverse signaling contexts. Beyond their basic role in mediating macromolecular interactions, the HTH domains have also been incorporated into the catalytic domains of diverse enzymes. We discuss the general domain architectural themes that have arisen amongst the HTH domains as a result of their recruitment to these diverse functions. We present a natural classification, higher-order relationships and phyletic pattern analysis of all the major families of HTH domains. This reconstruction suggests that there were at least 6-11 different HTH domains in the last universal common ancestor of all life forms, which covered much of the structural diversity and part of the functional versatility of the extant representatives of this domain. In prokaryotes the total number of HTH domains per genome shows a strong power-equation type scaling with the gene number per genome. However, the HTH domains in two-component signaling pathways show a linear scaling with gene number, in contrast to the non-linear scaling of HTH domains in single-component systems and sigma factors. These observations point to distinct evolutionary forces in the emergence of different signaling systems with HTH transcription factors. The archaea and bacteria share a number of ancient families of specific HTH transcription factors. However, they do not share any orthologous HTH proteins in the basal transcription apparatus. This differential relationship of their basal and specific transcriptional machinery poses an apparent conundrum regarding the origins of their transcription apparatus.



 


Footnotes and references

  1. 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.
  2. My apologies if this is tedious. But in the real world, we encounter such problems a lot and I would be remiss not to use this opportunity to let you practice how to fix the issue that could otherwise be a roadblock in a project of yours.


 

Ask, if things don't work for you!

If anything about the assignment 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.