An olfactory receptor pseudogene whose function emerged in humans: A case study in the evolution of structure-function in GPCRs

Peter C. Lai, Gautam Bahl, Maryse Gremigni, Valery Matarazzo, Olivier Clot-Faybesse, Catherine Ronin, Chiquito J. Crasto

Research output: Contribution to journalArticle

13 Scopus citations

Abstract

Human olfactory receptor, hOR17-210, is identified as a pseudogene in the human genome. Experimental data has shown however, that the gene product of frame-shifted, cloned hOR17-210 cDNA was able to bind an odorant-binding protein and is narrowly tuned for excitation by cyclic ketones. Supported by experimental results, we used the bioinformatics methods of sequence analysis (genome-wide and pair-wise), computational protein modeling and docking, to show that functionality in this receptor is retained due to sequence-structure features not previously observed in mammalian ORs. This receptor does not possess the first two transmembrane helical domains (of seven typically seen in GPCRs). It however, possesses an additional TM that has not been observed in other human olfactory receptors. By incorporating these novel structural features, we created two putative models for this receptor. We also docked odor ligands that were experimentally shown to bind hOR17-210. We show how and why structural modifications of OR17-210 do not hinder this receptor's functionality. Our studies reveal that novel gene rearrangements that result in sequence and structural diversity may have a bearing on OR and GPCR function and evolution.

Original languageEnglish
Pages (from-to)29-40
Number of pages12
JournalJournal of Structural and Functional Genomics
Volume9
Issue number1-4
DOIs
StatePublished - Dec 2008

Keywords

  • Computational modeling
  • Docking
  • Functional pseudogene
  • Olfactory receptors

Fingerprint Dive into the research topics of 'An olfactory receptor pseudogene whose function emerged in humans: A case study in the evolution of structure-function in GPCRs'. Together they form a unique fingerprint.

  • Cite this