Opsin evolution: annotation tricks

From genomewiki
Revision as of 16:18, 23 March 2010 by Tomemerald (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

See also: Curated Sequences | Informative Indels | Ancestral Introns | Update Blog

Quick Tricks to Annotating Remotely Related Opsins

Managing Hundreds of Opsin Sequences

As the number of opsin reference sequences increases, their management becomes more difficult. For example, aligning all 238 opsins at once is highly desirable but the result will spread out inconveniently over many dozens of jumbo computer screens. It turns out that certain opsin classes are significantly expanded in length at either or both termini. To the extent these are conserved within that opsin class over long total branch lengths, these extensions are important functionally (but in some unknown way). While that interest is narrowly defined, the offending residues cannot simply be discarded because it is primary data.

Consequently it is helpful to reversibly trim off these ends as needed, indeed trim down to the maximal conserved core. Sequences need to be identical in lengths for certain comparative genomic web tools, ie gapped out to all match in length. That can't be done just once because the reference sequence set is constantly growing (or shrinking).

Another common task is to compare variation just in a restricted subset of residues, perhaps in an adjacent patch but perhaps co-evolving residues scattered along the entire linear length, say all the counterion residues associated with the retinal Schiff base. Intervening extraneous residues are a major distraction in this situation. To understand covariance in the output, it may be necessary to sort and categorize the resultant classes.

All this and much more could be managed in a custom-programmed relational database such as open source MySQL. However an ever-shifting research agenda requires endless reprogramming of database capabilities and interface, with no server support within genomeWiki. That development could be justified for universal gene family data management software. However every gene family raises issues with no counterpart elsewhere and opsins are no exception. There has to be something simpler.

Because opsins are easily alignable even in remotely related homologs due to their many conserved and dispersed internal anchors, it doesn't matter which of ClustalW, T-Coffee, MultAlin, Blast, etc is used to align them. These tools do differ extensively in the ability of the user to control output. It turns out that MultAlin web tool by Florence Corpet has just the properties we need to trim and manage dispersed covariant residues, among them a fast and stable server very tolerant of extraneous characters in fasta sequences -- nothing to buy, nothing needing download and installation.

To trim off extraneous residues C-terminally, simply paste in all or any subset of the Opsin Classifier reference set. Run Multalin at default settings and note the position number in the alignment where trimming should occur. Re-run the sequences, now with the 'maximum line length' parameter set to the position number. This will cause the alignment output to be in two blocks, the second of which is throwaway.

Next, recover trimmed sequences in fasta format so a similar process can be applied N-terminally to trim that. At the bottom of the page, click on the 'results as an html page' option to get paste the initial alignment graphic to text that can be copied. In any text editor, install the first fasta header symbol '>" by replacing carriage returns with 'carriage return >'. Then replace double spaces (which only occur after the sequence names with carriage return.

Resubmit the resulting carboxy-trimmed fasta sequences, now specifying where the N-terminal trim should occur. The top block will be trim but the rest the desired double-trim. That may be a satisfactory stopping point. However to recover doubly trimmed fasta sequences for other web tools, the second and later blocks must be consolidated by pasting side by side and discarding redundant name columns in spreadsheet or 1xn html table.

To isolate small blocks or individual residues of interest, simply set the 'graduation step' to create the appropriate flanking single spaces. Replace those with tabs, put in any desktop spreadsheet and delete unwanted columns. This leaves a column with the original sequence name tags (first word only -- note the Opsin Classifier has looked way ahead on this) and columns of desired residues. The graduation step can even be set to 1, which places every residue in its own column. Any combination of non-adjacent residues can be brought side by side using a simple custom row to direct horizontal sorts (and a second to allow restores). Comparative genomics then consists of various vertical sort orders, as illustrated in the section on counterions to the Schiff base lysine.

This whole process takes 2-3 minutes to perform -- it's not a hack because it uses Multalin features more or less as intended. You're back to biology in minutes instead of spending months writing MySQL code.

Using the Opsin Classifier to determine ancestral introns in ciliary opsins

Here we begin with a tunicate opsin (blue) of somewhat uncertain affinities within the Opsin Classifier. Three of its introns (orange) correspond exactly in position and phase to those of the full range of opsins -- from cone to pineal to encephalopsin (but not melanopsin, RGR, or protostomal opsins: not shown). Another 3 introns (magenta) have no counterparts in other opsin genes; these are tunicate-specific. (Intron gain and loss are unusually common in Ciona generally.)

Using the Opsin Classifier to align the tunicate opsin to a full spectrum of (representative) frog opsins, residues homologous to tunicate exon ends can be reliably located. These are shown in the same color scheme. However some of these latter opsins have intron gains of their own (phases shown in teal). The data fit very parsimoniously with 3 introns in the ancestral protein, the first of phase 2 and the others phase 0. These 3 introns were already established at the time of amphioxus and tunicate encephalopsin divergences, indeed sea urchin and even ragworm.

Opsin ancient introns.png

Using the Opsin Classifier to compare introns across Lophotrochozoa and Vertebrates

The snapshot of a colored alignment makes clear how to compare intron position and phase in melanopsins from widely diverged species. The magenta coloring in the query sequence from Schistostoma shows 3 exon ends followed by numbering 0,1,2 to indicate phase (basepairs extending beyond the last coding triplet). The Schmidtea ortholog is colored similarly.

Next, the query sequence is run against the full set of opsins in the classifier. The alignment to stickleback is important because the genome project there has reliably established where and how the exon breaks occur. Using the Schistosoma exon termini in a web browser text search locates the homologous peptides in stickleback. These are colored red in the alignment and also where located in the intronated sequence. It turns out exon breaks and phasing exactly match those of Schistosoma (for the 3 exons considered but not all).

However the peptides transfered homologously to tick and bee (and vertebrate ciliary opsins, not shown) fail to correspond to exon breaks. This establishes some specificity -- the matching introns are not some generic property of all GPCR nor all rhodopsin-class receptors

Opsin loph mel introns.png

Using the Opsin Classifier to annotate a new opsin in hemichordate

Below is a step-by-step example showing how the Opsin Classifier is used within an overall annotation strategy for recovering intronated opsin homologs in an unstudied species, here the hemichordate Saccoglossus kowalevskii. It's best to follow along actively replicating the steps on actual live web tools.

Here we expect to find minimally an opsin that underlies epidermal photoreception. The best initial queries (for detecting diverged sequences) are likely fellow Ambulacraria (ie sea urchin) opsins. The best initial target is Trace Archives Saccoglossus 'other' because these are transcripts which give longer blastn matches than dispersed exons. However this draws a blank, possibly because cell types with opsin transcripts are exceedingly rare. Hence we move to the "wgs" division.

A flawed but long sea urchin dna query, XM_778236, a GNOMON pipeline product labeled "similar to Go-coupled rhodopsin" elicits a significant hit provided the "Somewhat similar sequences (blastn)" trace query option has been selected. This option is critical for queries across diverged species or diverged opsin classes.

The key feature of this match is length. The rule of thumb is anything exceeding 40 bp will prove informative; here we have 71 bp. The percent identity is quite respectable at 76% given the time elapsed since sea urchin and acornworm divergence -- and this may be even be a match of paralogs. Note however the two gaps. The second can be written off as a slight gap misplacement by blastn. The first cannot. It represents an apparent inactivating frameshift (change in reading frame). However traces contain many artifactual indels and most likely this is sequencing error. We cannot rule out a recent processed pseudogene at this point -- indeed they give better initial hits than a multi-exonic gene.

The trace blast graphic shows five stacked hits. I selected one of these because its length was good at 917 bp and sufficient material was left over on both flanks, that is 754 bp upstream and 94 bp downstream.

>gnl|ti|1695985935 Length=917 Score = 41.0 bits Expect = 9.0 Identities = 54/71 (76%), Gaps = 3/71 (4%) Strand=Plus/Minus

            |||| |||||| | || |  ||| | |||||||||||||||||  | ||| ||||||   || || |||||

Next, the retrieved full length trace is back-blastxed against the Opsin Classifier collection. This gives three immediate benefits: properly translating the trace irrespective of its frameshifts (which surface as exon breaks with breaks too short for an intron in the numbering), finding the best available gene model (the initial query choice may have been sub-optimal), and extending match length over what Trace Archive blastn could do.

Here we see that the top 15 matches for trace ti|1695985935 are consistently opsins previously classified as peropsins and neuropsins. There appear to be two disjoint segments to the blastx match to PERa_braFlo Branchiostoma floridae but the numbering shows they really reflect a single extended match encompassing a frameshift. Here the trace was on the minus strand which means larger numbers are earlier in the coding sequence. The two fragments can then be joined into a single polypeptide, likely with a one amino acid glitch at the frameshift join. Blast often extends its matches too far into bogus territory and this must be trimmed.

PERa_braFlo     Branchiostoma floridae (amphioxus) ?? ... -1   182  3.6e-28   2
PERa_braBel     Branchiostoma belcheri (amphioxus) ?? ... -1   174  5.7e-27   2
PER_xenTro      Xenopus tropicalis (frog) ?? -1   195  4.8e-26   2
NEUR_calMil     Callorhinchus milii (elephantfish) ?? ... -2   151  1.9e-24   2
PER_gasAcu      Gasterosteus aculeatus (stickleback) ?... -1   174  4.2e-23   2

Score = 167 (58.8 bits), Expect = 3.6e-28, Sum P(2) = 3.6e-28 Identities = 28/60 (46%), Positives = 41/60 (68%), Frame = -2

             G+ IFG   S  SS    WLFG  GC ++GF GM FG+ +IG LT +++DRY++ C+++L

Score = 182 (64.1 bits), Expect = 3.6e-28, Sum P(2) = 3.6e-28 Identities = 35/82 (42%), Positives = 50/82 (60%), Frame = -1

             Y+  C Q+   K++      Y  Y  + A+ W  A FW+ +PL GW+ Y+LEP GT+CTI+W  ND+ YISYV+    +CFI

The two fragments can then be joined into a single polypeptide, likely with a one amino acid glitch at the frameshift join. This 133 residue peptide is blastped against Opsin Classifier. Here the Expect = 5.4e-33 is highly encouraging but the two small insertions raise questions for an opsin. Perhaps extraneous residues have been incorporated into our gene model, currently a fragment corresponding to residues 83-197 of the 361 residue peropsin in amphioxus.

Switching to a six-frame translation view in a second browser tab, we see GLTI is preceded by a stop codons without good opportunities for a GT-AG splice site that does not sacrifice regions of apparent alignment. This could reflect additional frameshifts but without any guidance from blastp output, we have no idea what frame might contain further good upstream sequence. Next we look for exon boundary guidance from the best gene model amphioxus PERa_braFlo. Here we see GLTI is towards the end of an exon. If we look to GRWL as the valid start of the alignment, it lacks a supporting phase 0 intron of PERa_braFlo

Downstream there is a GT splice option for a phase 2 intron at YISYV (which would eliminate the insert) or an option for adding IRSKTDTTFVDT followed by a phase 0 splice start (and a stop codon). However that extension has no support in any known opsin. Further, there is no support from PERa_braFlo exon boundaries.

The information in this trace has not yet been exhausted because we can re-blastn against the trace archives, perhaps finding a trace that stayed on task. Indeed this picks up two high-identity trace with clear multiple exons, ti|1723199539 and ti|1705099698, supporting the notion that the original trace reflects a processed pseudogene. By recursively using the Opsin Classifier with further rounds of trace archive searching (to tile out ends), we eventually arrive at a 246 residue fragmentary gene model with consistent top matches to peropsins and neuropsins, sharing two appropriate introns with correct phasing but also two fused introns with respect to later deuterostomes. This fragment is a good candidate for ortholog as these genes are single copy in all studied species.

The fragmentary gene is best further studied after release of acornworm contig assembly.

>PER_sacKol Saccoglossus kowalevskii Expect = 2.0e-49 PERa_braFlo Identities = 97/246 (39%)

PERa_braFlo     Branchiostoma floridae (amphioxus) ?? 0.2...   484  2.0e-49   1
PERa_braBel     Branchiostoma belcheri (amphioxus) ?? 0.2...   472  3.8e-48   1
PER_monDom      Monodelphis domestica (opossum) ?? 0.2.0....   443  4.5e-45   1
PER_xenTro      Xenopus tropicalis (frog) ??   442  5.7e-45   1
PER_gasAcu      Gasterosteus aculeatus (stickleback) ?? 0...   436  2.5e-44   1
PER_homSap      Homo sapiens (human) ?? ind...   435  3.2e-44   1
PER_galGal      Gallus gallus (chicken) ?? ...   418  2.0e-42   1
NEUR_gasAcu     Gasterosteus aculeatus (stickleback) ?? 0...   304  3.9e-41   2
NEUR_ornAna     Ornithorhynchus anatinus (platypus) ?? 0....   396  4.3e-40   1
NEUR_monDom     Monodelphis domestica (opossum) ?? 0.2.2....   390  1.9e-39   1
NEUR_homSap     Homo sapiens (human) ?? indel...   383  1.0e-38   1
NEUR_galGal     Gallus gallus (chicken) ?? in...   383  1.0e-38   1
NEUR_xenTro     Xenopus tropicalis (frog) ?? ...   370  2.4e-37   1
NEUR_anoCar     Anolis carolinensis (lizard) ??   365  8.3e-37   1

genomeWiki display experiments

GenomeWiki code resists displaying colors within preformatted (ie monospaced Courier) html text, but by indenting each line with a space, standard color markups can be used to indicate sequence features such as intron phases or occurrences of selenocysteines while retaining the equal letter spacing needed.

red  magenta  blue  green  brown
#FF0000  #996633
#990099 #00CC66
#990000  #0066CC


* To get pop-up image of a seq alignment:
<balloon hover="load:myImage1" title="load:myImage2" click="1">
Hover for temporary, click for persistent. Can be same or different images</balloon>

* To get mouse-over to provide a 15 second popup of plain text: use balloon title="" syntax:

<balloon title="message">popup of title content</balloon>
* To get mouse-over to provide formatted text, use balloon title=load:"content" followed by span id="content" style="color:"

<balloon title="load:myContent" style="color:magenta">colored balloon text</balloon> 

* To float position of mouse-over or highlight text:
<balloon title="load:myContent2" style="float:left;background:yellow">Mouse over</balloon>

* Mouse-over an image:
<balloon title="I chase squirrels"><img width=75 src="http://mckay.cshl.edu/wiki/images/8/85/Ginger.png"></balloon>
* To get both mouse-over hover and mouse-click:

<balloon hover="Hover gives different outcome than click" title="sticky or persistent balloon" click="1" style="float:middle;color:green">Click vs hover</balloon>

<balloon link="http://www.google.com/search?q=Generic%20popup%20balloons" title="Click image for Google search"> <img src="http://mckay.cshl.edu/wiki/images/5/51/Google.png"> </balloon>

<balloon link="http://www.google.com/search?q=Generic%20popup%20balloons" title="Click this link text for a Google search"> Or click on this text to launch google search </balloon>

More on this extension at mediawiki:Extension:Balloons

Crosslinking genomewiki articles

This small database can be assigned numbers to indicate inclusion and listing order. Then the relevent links can be pulled up and grepped into a single line for inclusion in header and footer of each article as appropriate. Note wiki software does not allow self-referential links to be displayed as links.

Update Blog
LWS | 
Encephalopsins | 
Melanopsins | 
Neuropsins | 
Peropsins | 
RGR phyloSNPs | 
Alignment | 
Ancestral Introns | 
Informative Indels | 
Ancestral Sequences | 
Curated Sequences | 
Cytoplasmic face | 
RBP3 (IRBP) | 
RPE65 | 
Annotation Tricks | 
Cnidaria | 
Deuterostomes | 
Ecdysozoa | 
Lophotrochozoa | 
Opsin Origins | 
Transducins | 
Tetrachromatic Ancestral Mammal | 
Usher: USH2A | 
Usher: CDH23 | 

See also: Update Blog LWS | Encephalopsins | Melanopsins | Neuropsins | Peropsins | RGR phyloSNPs | Alignment | Ancestral Introns | Informative Indels | Ancestral Sequences | Curated Sequences | Cytoplasmic face | RBP3 (IRBP) | RPE65 | Annotation Tricks | Cnidaria | Deuterostomes | Ecdysozoa | Lophotrochozoa | Opsin Origins | Transducins | Tetrachromatic Ancestral Mammal | Usher: USH2A | Usher: CDH23 | LOXHD1 |

See also: Curated Sequences | Informative Indels | Ancestral Introns | Update Blog