|
|
| (59 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| − | <!-- {{Template:Inactive}} --> | + | <div id="APB"> |
| − | {{Template:Active}}
| |
| | | | |
| | + | <table width="40%"><tr><td class="l1"> </td><td> |
| | | | |
| − | __TOC__
| + | ===Hardware=== |
| − | | + | <table width="100%"> |
| − |
| + | <tr class="s1"><td class="l1">High performance computing <!-- (... at the bench: GPUs, FPGAs, Clusters) --></td></tr> |
| | + | <tr class="s2"><td class="l1">Cloud computing</td></tr> |
| | + | <tr><td class="sp"> </td></tr> |
| | + | </table> |
| | | | |
| − | <div style="padding: 5px; background: #A6AFD0; border:solid 1px #AAAAAA; font-size:200%;font-weight:bold;"> | + | ===Systems and Tools=== |
| − | Assignment 5 - Homology modeling
| + | <table width="100%"> |
| − | </div>
| |
| | | | |
| − | <div style="padding: 15px; background: #F0F1F7; border:solid 1px #AAAAAA; font-size:125%;color:#444444"> | + | <tr class="s1"><td class="l1 mw-collapsible mw-collapsed" data-expandtext="Expand subtopics" data-collapsetext="Collapse">[[Unix]] |
| − | ;How could the search for ultimate truth have revealed so hideous and visceral-looking an object?
| + | <div class="mw-collapsible-content"> |
| − | ::''<small>Max Perutz (on his first glimpse of the Hemoglobin structure)</small>''
| + | <table width="100%"><tr class="s2"><td class="l2">[[Unix system administration]]</td></tr></table> |
| | + | <table width="100%"><tr class="s1"><td class="l2">[[Unix automation]]</td></tr></table> |
| | + | <table width="100%"><tr class="s2"><td class="l2">[[Program installation]]</td></tr></table> |
| | + | <table width="100%"><tr class="s1"><td class="l2">[[wget]]</td></tr></table> |
| | </div> | | </div> |
| − |
| + | </td></tr> |
| − |
| |
| | | | |
| − | Where is the hidden beauty in structure, and where, the "ultimate truth"? In the previous assignments we have studied sequence conservation in APSES family domains and we have discovered homologues in all fungal species. This is an ancient protein family that had already duplicated to several paralogues at the time the cenancestor of all fungi lived, more than 600,000,000 years ago, in the [http://www.ucmp.berkeley.edu/fungi/fungifr.html Vendian period] of the Proterozoic era of Precambrian times.
| + | <tr class="s2"><td class="l1">[[Network Configuration]]</td></tr> |
| | + | <tr class="s1"><td class="l1">[[Apache]]</td></tr> |
| | + | <tr class="s2"><td class="l1">[[MySQL]]</td></tr> |
| | + | <tr class="s1"><td class="l1">[[Tools for the bioinformatics lab]]</td></tr> |
| | + | <tr class="s2"><td class="l1">[[GBrowse|GBrowse and LDAS]]</td></tr> |
| | + | <tr><td class="sp"> </td></tr> |
| | + | </table> |
| | | | |
| − | 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, no APSES domain structures in complex with bound DNA has been solved up to now, and the experimental evidence we have considered in Assignment 2 ([http://www.ncbi.nlm.nih.gov/entrez/query.fcgi?cmd=Retrieve&db=pubmed&dopt=Abstract&list_uids=10747782 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.
| + | ===Programming=== |
| | + | <table width="100%" > |
| | + | <tr class="s1"><td class="l1">[[IDE|IDE (Integrated Development Environment)]]</td></tr> |
| | + | <tr class="s2"><td class="l1">[[Regular Expressions]]</td></tr> |
| | + | <tr class="s1"><td class="l1">[[Screenscraping]]</td></tr> |
| | | | |
| − | ''In this assignment you will (1) construct a molecular model of the APSES domain from the Mbp1 orthologue in your assigned species, (2) identify similar structures of distantly related domains for which protein-DNA complexes are known, (3) assemble a hypothetical complex structure and(4) discuss whether the available evidence allows you to distinguish between different modes of ligand binding, ''
| + | <tr class="s2"><td class="l1 mw-collapsible mw-collapsed" data-expandtext="Expand subtopics" data-collapsetext="Collapse">[[Perl]] |
| − | | + | <div class="mw-collapsible-content"> |
| − | For the following, please remember the following terminology:
| + | <table width="100%"><tr class="s1"><td class="l2">[[Perl basic programming]]</td></tr></table> |
| − | | + | <table width="100%"><tr class="s2"><td class="l2">[[Perl hash example]]</td></tr></table> |
| − | ;Target
| + | <table width="100%"><tr class="s1"><td class="l2">[[Perl LWP example]]</td></tr></table> |
| − | :The protein that you are planning to model.
| + | <table width="100%"><tr class="s2"><td class="l2">[[Perl MySQL introduction]]</td></tr></table> |
| − | ;Template
| + | <table width="100%"><tr class="s1"><td class="l2">[[Perl OBO parser]]</td></tr></table> |
| − | :The protein whose structure you are using as a guide to build the model.
| + | <table width="100%"><tr class="s2"><td class="l2">[[Perl basic programming]]</td></tr></table> |
| − | ;Model
| + | <table width="100%"><tr class="s1"><td class="l2">[[Perl programming exercises 1]]</td></tr></table> |
| − | :The structure that results from the modeling process. It has the '''Target sequence''' and is similar to the '''Template structure'''.
| + | <table width="100%"><tr class="s2"><td class="l2">[[Perl programming exercises 2]]</td></tr></table> |
| − |
| + | <table width="100%"><tr class="s1"><td class="l2">[[Perl programming Data Structures]]</td></tr></table> |
| − | | + | <table width="100%"><tr class="s2"><td class="l2">[[Perl references]]</td></tr></table> |
| − | 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.
| + | <table width="100%"><tr class="s1"><td class="l2">[[Perl simulation]]</td></tr></table> |
| − | | + | <table width="100%"><tr class="s2"><td class="l2">[[Perl: Object oriented programming]]</td></tr></table> |
| − | {{Template:Preparation|
| + | <table width="100%"><tr class="s1"><td class="l2">[[Perl: Ugly programming]]</td></tr></table> |
| − | care=Be sure you have understood all parts of the assignment and cover all questions in your answers! Sadly, we see too many assignments which, arduously effected, nevertheless intimate nescience of elementary tenets of molecular biology. If the sentence above did not trigger an urge to open a dictionary, you are trying to guess, rather than confirm possibly important information.|
| |
| − | num=5|
| |
| − | ord=fifth|
| |
| − | due = Monday, December 5. at 12:00 noon}}
| |
| − | | |
| − |
| |
| − | | |
| − | ;Your documentation for the procedures you follow in this assignment will be worth 2 marks - 1 mark for generating the model and 1 mark for the selection/superposition and visualization of protein/DNA complexes.
| |
| − | | |
| − |
| |
| − | | |
| − | | |
| − | <div style="padding: 5px; background: #BDC3DC; border:solid 1px #AAAAAA;"> | |
| − | ==(1) Preparation== | |
| | </div> | | </div> |
| | + | </td></tr> |
| | | | |
| | + | <tr class="s1"><td class="l1">[[BioPerl]]</td></tr> |
| | + | <tr class="s2"><td class="l1">[[PHP]]</td></tr> |
| | + | <tr class="s1"><td class="l1">[[Data modelling]]</td></tr> |
| | + | <tr class="s2"><td class="l1">BioPython <!-- (scope, highlights, installation, use, support) --></td></tr> |
| | + | <tr class="s1"><td class="l1">Graphical output <!-- (PNG and SVG) --></td></tr> |
| | + | <tr class="s2"><td class="l1">[[Autonomous agents]]</td></tr> |
| | + | </table> |
| | | | |
| − | <div style="padding: 5px; background: #E9EBF3; border:solid 1px #AAAAAA;"> | + | ===Algorithms=== |
| − | ===(1.1) Template choice and template sequence=== | + | <table width="100%" > |
| − | </div> | + | <tr class="sh"><td class="l1">Algorithms on Sequences</td></tr> |
| − | The [http://swissmodel.expasy.org/ SWISS-MODEL] server provides several different options for constructing homology models. The easiest is probably the '''Automated Mode''' that requires only a target sequence as input, in this mode the program will automatically choose suitable templates and create an input alignment. I disagree however that that is the best way to use such a service: the reason is that 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 counter to the best choices an automated algorithm could make. Therefore we will use the '''Alignment Mode''' of Swiss-Model in this assignment, choose our own template and upload our own alignment.
| + | <tr class="s1"><td class="l2">[[Dynamic Programming]]</td></tr> |
| | + | <tr class="s2"><td class="l2">[[Multiple Sequence Alignment]]</td></tr> |
| | + | <tr class="s1"><td class="l2">[[Genome Assembly]]</td></tr> |
| | | | |
| − | Template choice is the first step. Often more than one related structure can be found in the PDB. We have touched on principles of selecting template structures in the lecture and I have posted a short summary of [[Template_choice_principles|template choice principles]] on this Wiki. One can either 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 one can always also use the BLAST interface at the NCBI, since the sequences contained in PDB files are accessible as a database subsection on the BLAST menu.
| + | <tr><td class="sp"> </td></tr> |
| | | | |
| | + | <tr class="sh"><td class="l1">Algorithms on Structures</td></tr> |
| | + | <tr class="s1"><td class="l2">[[Docking]]</td></tr> |
| | + | <tr class="s2"><td class="l2">Protein Structure Prediction <!-- ''ab initio'' --></td></tr> |
| | | | |
| − | <div style="padding: 5px; background: #DDDDEE;"> | + | <tr><td class="sp"> </td></tr> |
| − | In assignment 2 you have already searched for structures of APSES domains in the PDB. If you need to repeat this:
| |
| − | *Use the NCBI BLAST interface to identify all PDB files that are clearly homologous to your target APSES domain.
| |
| − | *In Assignment 2, you have defined the extent of the APSES domain in yeast Mbp1. In Assignment 3, you have aligned reference APSES domains with those you found in your species. In assignment 4 you have confirmed by phylogenetic analysis and ''Recoprocal Best Match'' which of these APSES domain sequences is the closest related orthologue to yeast Mbp1. This sequence is the best candidate for having a conserved function similar to yeast Mbp1. Therefore, this sequence is the '''target''' for the homology modeling procedure.
| |
| − | *Defining a ''template''' means finding a PDB coordinate set that has sufficient sequence similarity to your '''target'' that you can huild a model based on theat '''template'''. To find suitable PDB structures, use your '''target''' sequence as input for a BLAST search, and select Protein Data Bank proteins(pdb) as the '''Database''' you search in. Hits that are homologues are all suitable '''templates''' in principle, 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; comment briefly on
| |
| − | :*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
| |
| − | Then choose the '''template''' you consider the most suitable and note why you have decided to use this template.
| |
| − | </div> | |
| | | | |
| | + | <tr class="sh"><td class="l1">Algorithms on Trees</td></tr> |
| | + | <tr class="s1"><td class="l2">Computing with trees <!-- Bayesian approaches for phylogenetic trees, tree comparison) --></td></tr> |
| | | | |
| − | It is not straightforward at all how to number sequence in such a project. The "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 1MB1 FASTA file <small>(one of the related PDB strcuctures)</small> '''is''' the first residue of Mbp1 protein, but the last five residues are an artifical His tag. Is H125 of 1MB1 thus equivalent to R125 in MBP1_SACCE? The N-terminus of the Mbp1 crystal structure is disordered. The first residue in the structure is ASN 3, therefore N is the first residue in a FASTA sequence derived from the cordinate section of the PDB file (the <code>ATOM </code> records; whereas the SEQRES records start with MET ... and so on. You need to remember: a sequence number is not absolute, but assigned in a particular context.
| + | <tr><td class="sp"> </td></tr> |
| | | | |
| − | The homology '''model''' will be based on an alignment of '''target''' and '''template'''. Thus we have to define the target sequence. As discussed in class, PDB files have an explicit and an implied sequence and these do not necessarily have to be the same. To compare the implied and the explicit sequence for the template, you need to extract sequence information from coordinates. One way to do this is via the Web interface for [http://swift.cmbi.ru.nl/servers/html/index.html '''WhatIf'''], a crystallography and molecular modeling package that offers many useful tools for coordinate manipulation tasks.
| + | <tr class="sh"><td class="l1">Algorithms on Networks</td></tr> |
| | + | <tr class="s1"><td class="l2">Network metrics <!-- (Degree distributions, Centrality metrics, other metrics on topology, small-world- vs. random-geometric controversy) --></td></tr> |
| | + | <tr class="s2"><td class="l3">[[Dijkstras Algorithm]]</td></tr> |
| | + | <tr class="s1"><td class="l3">[[Floyd Warshall Algorithm]]</td></tr> |
| | + | </table> |
| | | | |
| − | <div style="padding: 5px; background: #DDDDEE;">
| |
| − | *Navigate to the '''Administration''' sub-menu of the [http://swift.cmbi.ru.nl/servers/html/index.html WhatIf Web server]. Follow the link to '''Make sequence file from PDB file'''. Enter the PDB-ID of your template into the form field and '''Send''' the request to the server. The server accesses the PDB file and extracts sequence information directly from the <code>ATOM </code> records of the file. The results will be returned in PIR format. Copy the results, edit them to FASTA format and save them in a text-only file. Make sure you create a valid FASTA formatted file! Use this '''implied''' sequence to check if and how it differs from the sequence ...
| |
| | | | |
| − | :*... listed in the <code>SEQRES</code> records of the coordinate file;
| + | ===Communication and collaboration=== |
| − | :*... given in the FASTA sequence for the template, which is provided by the PDB;
| + | <table width="100%" > |
| − | :*... stored in the protein database of the NCBI.
| + | <tr class="s1"><td class="l1">[[MediaWiki]]</td></tr> |
| − | : and record your results.
| + | <tr class="s2"><td class="l1">[[HTML essentials]]</td></tr> |
| | + | <tr class="s1"><td class="l1">[[HTML 5]]</td></tr> |
| | + | <tr class="s2"><td class="l1">[[SADI|SADI Semantic Automated Discovery and Integration]]</td></tr> |
| | + | <tr class="s1"><td class="l1">[[CGI]]</td></tr> |
| | + | <tr><td class="sp"> </td></tr> |
| | + | </table> |
| | | | |
| − | * Establish how the sequence numbers in the coordinate section of your template(*) correspond to your target sequence numbering.
| + | ===Statistics=== |
| | + | <table width="100%" > |
| | + | <tr class="s1"><td class="l1">[[Pattern discovery]]</td></tr> |
| | + | <tr class="s2"><td class="l1">Correlation <!-- (Covariance matrices and their interpretation, application to large problems, collaborative filtering, MIC and MINE) --></td></tr> |
| | + | <tr class="s1"><td class="l1">Clustering methods <!-- (Algorithms and choice (including: hierarchical, model-based and partition clustering, graphical methods (MCL), flow based methods (RRW) and spectral methods). Implementation in R if possible) --></td></tr> |
| | + | <tr class="s2"><td class="l1">Cluster metrics <!-- (Cluster quality metrics (Akaike, BIC)–when and how) --></td></tr> |
| | + | <tr class="s1"><td class="l1">[[Map equation|The Map Equation]] </td></tr> |
| | + | <tr class="s2"><td class="l1">Machine learning <!-- (Classification problems: Neural Networks, HMMs, SVM..) --></td></tr> |
| | | | |
| | + | <tr class="s1"><td class="l1 mw-collapsible mw-collapsed" data-expandtext="Expand subtopics" data-collapsetext="Collapse">[[R]] |
| | + | <div class="mw-collapsible-content"> |
| | + | <table width="100%"><tr class="s2"><td class="l2">R plotting</td></tr></table> |
| | + | <table width="100%"><tr class="s1"><td class="l2">[[R programming]]</td></tr></table> |
| | + | <table width="100%"><tr class="s2"><td class="l2">R EDA</td></tr></table> |
| | + | <table width="100%"><tr class="s1"><td class="l2">R regression</td></tr></table> |
| | + | <table width="100%"><tr class="s2"><td class="l2">R PCA</td></tr></table> |
| | + | <table width="100%"><tr class="s1"><td class="l2">R Clustering</td></tr></table> |
| | + | <table width="100%"><tr class="s2"><td class="l2">R Classification <!-- Phrasing inquiry as a classification problem, dealing with noisy data, machine learning approaches to classification, implementation in R) --></td></tr></table> |
| | + | <table width="100%"><tr class="s1"><td class="l2">R hypothesis testing</td></tr></table> |
| | + | <table width="100%"><tr class="s2"><td class="l2">[[Bioconductor]]</td></tr></table> |
| | </div> | | </div> |
| | + | </td></tr> |
| | | | |
| − | :(*) <small>These residue numbers are important, since they are referenced e.g. by VMD when you visualize the structure. The easiest way to list them is via the ''Sequence Viewer'' extension of VMD.</small>.
| + | <tr><td class="sp"> </td></tr> |
| − | :<small>Don't do this for every residue individually but define ranges. Look at the correspondence of the first and last residue of target and template sequence and take indels into account. Establishing sequence correspondence precisely is crucially important! For example, when a publication refers to a residue by its sequence number, you have to be able to relate that number to the residue numbers of the model as well as your target sequence.</small>.
| + | </table> |
| − |
| |
| − |
| |
| | | | |
| − | <div style="padding: 5px; background: #E9EBF3; border:solid 1px #AAAAAA;"> | + | ===Applications=== |
| | + | <table width="100%" > |
| | + | <tr class="s1"><td class="l1">[[Data integration]] <!-- Add BioMart: Biodata integration, and data-mining of complex, related, descriptive data --></td></tr> |
| | + | <tr class="s2"><td class="l1">Text mining <!-- (Use cases, tasks and metrics, taggers, vocabulary mapping, Practicals: R-support, Python/Perl support, others...) --></td></tr> |
| | + | <tr class="s1"><td class="l1">[[HMMER]]</td></tr> |
| | + | <tr class="s2"><td class="l1">High-throughput sequencing</td></tr> |
| | + | <tr class="s1"><td class="l1">Functional annotation <!-- GFF --></td></tr> |
| | + | <tr class="s2"><td class="l1">Microarray analysis <!-- (... in R: differential expression and multiple testing; Loading and normalizing data, calculating differential expression, LOWESS, the question of significance, FWERs: Bonferroni and FDR; SAM and LIMMA) --></td></tr> |
| | + | <tr><td class="sp"> </td></tr> |
| | + | </table> |
| | + | </td></tr></table> |
| | | | |
| − | ===(1.2) The input alignment===
| |
| | </div> | | </div> |
| − | <br>
| |
| − |
| |
| − | The sequence alignment between target and template is the single most important factor that determines the quality of your model. No comparative modeling 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 modeling 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 only 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 - (and for the ones in which we do see indels, we might suspect that these are actually gene-model errors). 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. To obtain an alignment between the '''template sequence''' and the '''target sequence''' from your species, proceed as follows.
| |
| − |
| |
| − | <div style="padding: 5px; background: #DDDDEE;">
| |
| − | ;In Jalview...
| |
| − | * Load your Jalview project with aligned APSES domain sequences or recreate it from the Mbp1 orthologue in your species and the APSES domains from the [[Reference APSES domains|'''Reference APSES domain page''']] that I prepared for Assignment 4. Include the sequence of your '''template protein''' and re-align.
| |
| − | * Delete all sequence you no longer need, i.e. keep only the APSES domains of the '''target''' (from your species) and the '''template''' (from the PDB) and choose '''Edit → Remove empty columns'''. This is your '''input alignment'''.
| |
| − | * Choose '''File→Output to textbox→FASTA''' to obtain the aligned sequences. They should both have exactly the same length, i.e. N- or C- termini have to be padded by hyphens if the original sequences had different length. Save the sequences in a text-file.
| |
| − |
| |
| − |
| |
| − | ;Using a different MSA program
| |
| − | * Copy the FASTA formatted sequences of the Mbp1 proteins in the reference species from the [[Reference APSES domains|'''Reference APSES domain page''']].
| |
| − | * Access e.g. the MSA tools page at the EBI.
| |
| − | * Paste the Mbp1 sequence set, your '''target''' sequence and the '''template''' sequence into the input form.
| |
| − | *Run the alignment and save the output.
| |
| − |
| |
| − |
| |
| − | ;By hand
| |
| − | APSES domains are strongly conserved and have few if any indels. You could also simply align by hand.
| |
| − |
| |
| − | * Copy the CLUSTAL formatted reference alignment of the Mbp1 proteins in the reference species from the [[Reference APSES domains|'''Reference APSES domain page''']].
| |
| − | * Open a new file in a text editor.
| |
| − | * Paste the Mbp1 sequence set, your '''target''' sequence and the '''template''' sequence into the file.
| |
| − | *Align by hand, replace all spaces with hyphens and save the output.
| |
| − | </div>
| |
| − |
| |
| − |
| |
| − | Whatever method you use: the result should be a multiple sequence alignment in '''multi-FASTA''' format, that was constructed from a number of supporting sequences and that contains your aligned '''target''' and '''template''' sequence. This is your '''input alignment''' for the homology modeling server.
| |
| − |
| |
| − |
| |
| − | <div style="padding: 5px; background: #BDC3DC; border:solid 1px #AAAAAA;">
| |
| − |
| |
| − | ==(2) Homology model==
| |
| − | </div>
| |
| − |
| |
| − |
| |
| − |
| |
| − | <div style="padding: 5px; background: #E9EBF3; border:solid 1px #AAAAAA;">
| |
| − | === (2.1) SwissModel===
| |
| − | </div>
| |
| − | <br>
| |
| − |
| |
| − | Access the Swissmodel server at '''http://swissmodel.expasy.org''' . Navigate to the '''Alignment Mode''' page.
| |
| − |
| |
| − | <br><div style="padding: 5px; background: #DDDDEE;">
| |
| − | *Paste your alignment for target and model into the form field. Refer to the [[Homology_modeling_fallback_data|'''Fallback Data file''']] if you are not sure about the format. Make sure to select the correct option (FASTA) for the alignment input format on the form.
| |
| − |
| |
| − | * Click '''submit alignment ''' and on the returned page define your '''target''' and '''template''' sequence. For the '''template sequence''' define the PDB ID of the coordinate file it came from. Enter the correct Chain-ID <small>(usually "A", note: upper-case)</small>.
| |
| − | :<small>If you run into problems, compare your input to the fallback data. It has worked for me, it will work for you. In particular we have seen problems that arise from "special" characters in the FASTA header like the pipe "<code>|</code>" character that the NCBI uses to separate IDs - keep the header short and remove all non-alphanumeric characters to be safe.</small>
| |
| − |
| |
| − | *Click '''submit alignment''' and review the alignment on the returned page. Make sure it has been interpreted correctly by the server. '''The conserved residues have to be lined up and matching'''. Then click '''submit alignment''' again, to start the modeling process.
| |
| − |
| |
| − | * The resulting page returns information about the resulting model. Save the '''model coordinates''' on your computer. Read the information on what is being returned by the server (click on the red questionmark icon). Paste the Anolea profile into your assignment.
| |
| − | :<small>Do not paste a screenshot of the result, but copy and paste the image from the Web-page! You do not need to submit the actual coordinate files with your assignment.</small>
| |
| − | </div>
| |
| − |
| |
| − |
| |
| − |
| |
| − | <div style="padding: 5px; background: #BDC3DC; border:solid 1px #AAAAAA;">
| |
| − |
| |
| − | ==(3) Model analysis==
| |
| − | </div>
| |
| − |
| |
| − |
| |
| − |
| |
| − | <div style="padding: 5px; background: #E9EBF3; border:solid 1px #AAAAAA;">
| |
| − | === (3.1) The PDB file ===
| |
| − | </div>
| |
| − | <br>
| |
| − |
| |
| − | Open your '''model''' coordinates in a text-editor (make sure you view the PDB file in a fixed-width font) and consider the following questions:
| |
| − |
| |
| − |
| |
| − | <br><div style="padding: 5px; background: #DDDDEE;">
| |
| − | *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?
| |
| − | </div>
| |
| − | <!-- discuss flagging of loops - setting of B-factor to 99.0 phps. ANOLEA vs. Gromos ... packing vs. energy? -->
| |
| − |
| |
| − |
| |
| − | <div style="padding: 5px; background: #E9EBF3; border:solid 1px #AAAAAA;">
| |
| − | ===(3.2) First visualization===
| |
| − | </div>
| |
| − | <br>
| |
| − |
| |
| − | In assignment 2 you have already studied a Mbp1 structure and compared it with your organism's Mbp1 APSES domain, Since a homology model inherits its structural details from the '''template''', the model should look very similar to the original structure but contain the sequence of the '''target'''.
| |
| − |
| |
| − | <br><div style="padding: 5px; background: #DDDDEE;">
| |
| − | *Save your '''model''' coordinates to your computer and visualize the structure in VMD. Make an informative (parallel, not cross-eyed!) stereo view that shows the general orientation of the helix-turn-helix motif and the "wing", and paste it into your assignment.
| |
| − |
| |
| − | </div>
| |
| − | <br>
| |
| − | <br>
| |
| − |
| |
| − | <div style="padding: 5px; background: #BDC3DC; border:solid 1px #AAAAAA;">
| |
| − |
| |
| − | ==(4) The DNA ligand==
| |
| − | </div>
| |
| − |
| |
| − |
| |
| − |
| |
| − | <div style="padding: 5px; background: #E9EBF3; border:solid 1px #AAAAAA;">
| |
| − |
| |
| − | ===(4.1) Finding a similar protein-DNA complex===
| |
| − | </div>
| |
| − | <br>
| |
| − |
| |
| − | One of the really interesting questions we can discuss with reference to our 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 accurately model such a complex from first principles, we will base a model of a bound complex on homology modeling 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?
| |
| − |
| |
| − | 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.
| |
| − |
| |
| − | 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.
| |
| − |
| |
| − | However we have also read previously that the APSES domains are members of a much larger superfamily, the "winged helix" DNA binding domains , of which hundreds of structures have been solved.
| |
| − |
| |
| − | <br>
| |
| − |
| |
| − | [[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.]]
| |
| − |
| |
| − | <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:
| |
| − |
| |
| − | * For reference, access [http://cathwww.biochem.ucl.ac.uk/cgi-bin/cath/GotoCath.pl?cath=1.10.10.10 CATH domain 1.10.10.10]; this is the domain you will use to find protein-DNA complexes.
| |
| − | * 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 → 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 500 coordinate entries.
| |
| − | * 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.
| |
| − | * Check the box below this subquery to "Remove Similar Sequences at 90% identity" and click on "Submit Query". This query should retrieve more than 90 complexes.
| |
| − | * Scroll down to the beginning of the list of PDB codes and locate the "Generate reports" menu. Under the heading '''Custom reports''' select '''Image collage'''. This is a fast way to obtain an overview of the structures that have been returned. First of all you may notice that in fact not all of the structures are really different, despite selecting only to retrieve dissimilar sequences. 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). 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.
| |
| − |
| |
| − | <br><div style="padding: 5px; background: #DDDDEE;">
| |
| − | * Follow the procedure outlined above, from a CATH entry page up to viewing a Collage (or alternatively a tabular view) of the retrieved coordinate files. You can be maximally concise in your documentation for the procedure I have defined above, but I expect you to have spent enough time on this process to understand the key elements of the PDB's advanced search interface.
| |
| − | </div>
| |
| − |
| |
| − |
| |
| − | <div style="padding: 5px; background: #E9EBF3; border:solid 1px #AAAAAA;">
| |
| − |
| |
| − | ===(4.2) Preparation and superposition of a canonical complex===
| |
| − | </div>
| |
| − | <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.)
| |
| − |
| |
| − | * Access the PDB and navigate to the 1DUX structure explorer page. Download the coordinates to your computer.
| |
| − | * Open the coordinate file in a text-editor 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→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.
| |
| − | * 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.
| |
| − |
| |
| − | <br><div style="padding: 5px; background: #DDDDEE;">
| |
| − | * 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. Paste a copy of your image into your assignment. Remark briefly on which parts of the structure appear to superimpose best. Note whether this orientation of a B-DNA double-helix is a plausible model for DNA binding of your Mbp1 orthologue.
| |
| − |
| |
| − | </div>
| |
| − | <br>
| |
| − |
| |
| − |
| |
| − |
| |
| − | <div style="padding: 5px; background: #E9EBF3; border:solid 1px #AAAAAA;">
| |
| − |
| |
| − | ===(4.2) Preparation and superposition of a non-canonical complex===
| |
| − | </div>
| |
| − |
| |
| − |
| |
| − | The structure displaying a non-canonical complex between a winged-helix domain and its cognate DNA binding site is the human Regulatory Factor X.
| |
| − |
| |
| − | [[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 caused by the way the PDB stores replicates in biological assemblies. The PDB generates 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 were to use the biological unit file of the PDB, VMD does not recognize that there is a second molecule present and displays only one. We have to edit the file to merge the two molecules by removing the MODEL and ENDMDL records - and while we're editing the file we'll also remove unneeded heteroatoms and the second copy of the protein chain (which we don't need, we need only the second B-DNA strand). But then we end up with residues that have '''exactly the same residue number''' in the same file. That won't work for visualization, since the program expects residue numbers to be unique, therefore we have to renumber the residues. Here's how:
| |
| − |
| |
| − | * On the structure explorer page for 1DP7, select the option '''Download Files''' → '''Biological Assembly'''.
| |
| − | * Dowload, save and uncompress the file.
| |
| − | * Open the file in a text editor.
| |
| − | * Delete both <code>MODEL</code> and both <code>ENDMDL</code> records.
| |
| − | * 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.
| |
| − | * Access the [http://swift.cmbi.ru.nl/servers/html/index.html '''Whatif Web interface'''] and click on '''Administration''' and '''Renumber a PDB File from 1'''. Upload your edited file, access the results and save the file.
| |
| − | * Open the renumbered file with VMD. You should see '''one protein chain''' and a '''B-DNA double helix'''. 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 ''chain P'' and ''chain D'' in separate representations and color the DNA chain by ''Position'' → ''Radial'' for clarity) ... in particular, appreciate how Arginine 76 interacts with the base of Guanine 92!
| |
| − | * Then clear all molecules
| |
| − | * 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.
| |
| − | * A window will appear - the MultiSeq window - it contains the sequence of the APSES domain you are visualizing. MultiSeq will also generate an additional cartoon representation of the structure. Choose '''File→Import Data''', browse to your directory and load:
| |
| − | ** Your model;
| |
| − | ** The 1DUX complex;
| |
| − | ** The 1DP7 complex.
| |
| − | * Mark all three protein chains by selecting the checkbox next to their name and run the STAMP structural alignment.
| |
| − | * 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.
| |
| − |
| |
| − | <br><div style="padding: 5px; background: #DDDDEE;">
| |
| − | * Orient and scale your superimposed structures so that their structural similarity is apparent, the orientation is similar to the scene generated above and the 1DP7 "wing" can be clearly seen inserting into the DNA major groove. Paste a copy of your image into your assignment. Remark briefly on which parts of the structure appear to superimpose best. Note whether this orientation of a B-DNA double-helix is a plausible model for DNA binding of your Mbp1 orthologue.
| |
| − | </div>
| |
| − |
| |
| − |
| |
| − | <div style="padding: 5px; background: #E9EBF3; border:solid 1px #AAAAAA;">
| |
| − |
| |
| − | ===(4.3) Coloring by conservation===
| |
| − | </div>
| |
| − |
| |
| − | 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.
| |
| − |
| |
| − |
| |
| − | ;Load the Mbp1 APSES alignment into MultiSeq.
| |
| − |
| |
| − | :(A) In the MultiSeq Window, navigate to '''File → 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).
| |
| − |
| |
| − | 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.
| |
| − |
| |
| − | ;Bring the 1MB1 sequence in register with the APSES alignment.
| |
| − | :(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.
| |
| − | :(B) Select '''Edit → Enable Editing... → Gaps only''' to allow changing indels.
| |
| − | :(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>
| |
| − | :(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 → Save Session...'''
| |
| − |
| |
| − | ;Color by similarity
| |
| − | :(A) Use the '''View → Coloring → Sequence similarity → 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 → Graphics → 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.
| |
| − |
| |
| − | <br><div style="padding: 5px; background: #DDDDEE;">
| |
| − | * Once you have colored the residues of your model by conservation, create another informative stereo-image and paste it into your assignment.
| |
| − | </div>
| |
| − |
| |
| − |
| |
| − |
| |
| − | <div style="padding: 5px; background: #E9EBF3; border:solid 1px #AAAAAA;">
| |
| − |
| |
| − | ===(4.4) Interpretation===
| |
| − | </div>
| |
| − |
| |
| − |
| |
| − | <div style="padding: 5px; background: #FFCC99;">
| |
| − | ;Analysis (2 marks)
| |
| − | * Considering the conservation patterns for Mbp1 orthologues, and assuming that all these orthologues bind DNA in a similar way, which model appears to be more plausible for protein-DNA interactions in APSES domains? Is it the canonical, or the non-canonical binding mode? Discuss briefly what you would expect to find and how this relates to your observations. Distinguish clearly between experimental evidence, computational inference and empirical hypothesis. You are welcome to upload detail views (stereo !) of particular sidechains, or surfaces etc. if this helps your arguments. Sometimes a picture is worth many words. But this is not a requirement, we are more interested in evidence-based reasoning than in the form of the presentation.
| |
| − | </div>
| |
| − |
| |
| − |
| |
| − | <div style="padding: 5px; background: #BDC3DC; border:solid 1px #AAAAAA;">
| |
| − |
| |
| − | ==(5) Summary of Resources==
| |
| − | </div>
| |
| − | <br>
| |
| − |
| |
| − | ;Links and background reading
| |
| − |
| |
| − | :* [http://biochemistry.utoronto.ca/undergraduates/courses/BCH441H/restricted/Peitsch_2002_UseOfModels.pdf '''Review (PDF, restricted)''' Manuel Peitsch on Homology Modeling]
| |
| − | :* [http://biochemistry.utoronto.ca/undergraduates/courses/BCH441H/restricted/Aravind_2005_HTHdomains.pdf '''Review (PDF, restricted)''' Aravind ''et al.'' Helix-turn-helix domains]
| |
| − | :* [http://biochemistry.utoronto.ca/undergraduates/courses/BCH441H/restricted/2000_Gajiwala_WingedHelixDomains.pdf '''Review (PDF, restricted)''' Gajiwala & Burley, winged-Helix domains]
| |
| − | :* [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>
| |
| − |
| |
| − | ;[[Assignment_4_fallback_data|'''Fallback Data page''']]
| |
| − |
| |
| − | ;Alignments
| |
| − | :* [[APSES_domains_MUSCLE|APSES domains MUSCLE aligned]]
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − | {{Template:Assignment_Footer}}
| |
