You will be presented with the full text of a biomedical research paper. Please write an abstract for this paper. Your response should include the abstract and no additional text.

Paper text:
although they constitute the material with which primary biological databases are made of , nucleotide sequences are rarely used when it comes to analyzing proteins .
the reason is that evolutionary models designed for comparing nucleic acids are often too simplistic and almost never take into account the constraints associated with the coding nature of gene sequences . in practice ,
biologists dealing with proteins are often encouraged to use protein databases and associated tools to build their models . however , the transposition of these results onto the bona fide nucleotide sequences is time consuming .
this limitation can be an issue , especially when reconstructing phylogenetic trees of closely related species or when looking for conserved nucleotide patterns within multiple coding sequences . in theory ,
the task of turning a protein multiple sequence alignment ( msa ) into the associated cds ( coding sequence ) msa is trivial . yet in practice things can prove more complicated for a variety of simple reasons : unknown gene names , msas of domain or partial protein sequence , incomplete database annotation , and the ever faster evolution of genomic resources . of course ,
each of these problems can usually be solved manually , on a case by case basis , but altogether they tend to hamper the establishment of automatic procedures for seamlessly connecting the protein and the nucleotide worlds . when comparing protein and nucleotide sequences , efficient methods exist to either align cdss using their coding potential ( 13 ) or thread cdss onto a pre - established protein sequences ( protal2dna :   and pal2nal ( ) but all these tools require the user to preprocess the data ,
gather the appropriate cdss and make sure these are compatible with any subdomain extracted from the original protein sequence . to the best of our knowledge
, no tool is available online to automatically identify the nucleotide sequence ( genomic or transcript ) associated with a protein partial sequence ( domain or fragment ) and process it to replace that protein with its bona fide cds while retaining the original alignment .
we developed a fully automated program named protogene ( protein to gene ) that when given a protein sequence alignment ( pairwise or multiple ) returns the corresponding cds alignment .
protogene searches refseq ( 4 ) and nr with blast ( 5 ) in order to identify the transcript or genomic sequence(s ) most likely to be associated with the original protein sequences .
the sequences thus identified are processed by exonerate ( 6 ) in order to extract a portion of cds matching perfectly the original protein sequence .
although every attempt is made to identify the genuine protein cds , a conservative post - filtering step is still needed to eliminate any sequence that may not have been correctly processed .
protogene is not a gene finding tool and depends entirely on the pre - established proteomes found in refseq and nr .
we have put the emphasis on robustness and reliability rather than exhaustiveness . in our hands , protogene returns a bona fide cds for 95% of the sequences and fails on 5% . whenever the missed sequences matter , it is up to the user to explore the labyrinth of nucleotide databases and discover the glitch that breaks the information chain between the protein and its cds .
the first step is a blastp ( 5 ) against the refseq ( 4 ) protein database .
matches against refseq are only accepted when associated with an alignment that displays 100% identity and 100% coverage with the query sequence ( i.e. 100% of the query sequence residues aligned with identical residues ) .
if no suitable hit is found in refseq , the query sequence is blasted against the nr non - redundant protein sequence database , with a lowered acceptance threshold ( 95% identity , 95% coverage ) .
ncbi efetch and eutils utilities ( ) are then used to fetch the nucleotide sequences associated with the query sequence .
exonerate is finally used to extract a cds matching perfectly the original protein sequence ( be it a full - length protein or just a fragment ) .
it is up to the user to decide whether these are sequences errors , polymorphisms or identification errors .
the user may also request automatic back - translations using the iuc ambiguity code for unmatched amino acids .
cdss are returned along with some basic annotation including the nucleotide sequence accession number , the source organism and the refseq / nr accession number .
cdss where > 5% of the nucleotides have had to be replaced with ns are considered unreliable and discarded with an explicit mention in the output .
it is important to point out that when several proteins from different organisms have a perfect identity with the original query , each corresponding nucleotide sequence is integrated within the final alignment , leaving it to the user to remove the nucleotide sequences he is not interested in ( see the histone example in the next section ) . to ease this selection ,
nucleotide sequences gathered from the ncbi are kept in cache for 2 weeks , thus insuring faster second runs when reanalyzing a dataset with minor modifications .
it relies on a collection of perl scripts and two external programs : blast and exonerate .
the first step is a blastp ( 5 ) against the refseq ( 4 ) protein database .
matches against refseq are only accepted when associated with an alignment that displays 100% identity and 100% coverage with the query sequence ( i.e. 100% of the query sequence residues aligned with identical residues ) .
if no suitable hit is found in refseq , the query sequence is blasted against the nr non - redundant protein sequence database , with a lowered acceptance threshold ( 95% identity , 95% coverage ) .
ncbi efetch and eutils utilities ( ) are then used to fetch the nucleotide sequences associated with the query sequence .
exonerate is finally used to extract a cds matching perfectly the original protein sequence ( be it a full - length protein or just a fragment ) .
it is up to the user to decide whether these are sequences errors , polymorphisms or identification errors .
the user may also request automatic back - translations using the iuc ambiguity code for unmatched amino acids .
cdss are returned along with some basic annotation including the nucleotide sequence accession number , the source organism and the refseq / nr accession number .
cdss where > 5% of the nucleotides have had to be replaced with ns are considered unreliable and discarded with an explicit mention in the output .
it is important to point out that when several proteins from different organisms have a perfect identity with the original query , each corresponding nucleotide sequence is integrated within the final alignment , leaving it to the user to remove the nucleotide sequences he is not interested in ( see the histone example in the next section ) . to ease this selection ,
nucleotide sequences gathered from the ncbi are kept in cache for 2 weeks , thus insuring faster second runs when reanalyzing a dataset with minor modifications .
it relies on a collection of perl scripts and two external programs : blast and exonerate .
we provide three simple examples of how protogene can be used to rapidly and efficiently ask simple questions regarding protein sequence conservation at the nucleotide level .
serine is the only amino acid coded by two sets of codons ( ucn and agy ) that can not be interconverted by a single point mutation .
class switches , appear however to be very frequent and the question whether they arise from double mutations has been the subject of intense scrutiny and debate ( 7 ) . given a collection of protein sequences , protogene makes it straightforward to analyze the codon conservation of the serine .
figure 2 shows the output obtained after cutting and pasting the pfam ( 8) seed msa of the clp serine protease family ( pf00574 ) .
this alignment is not made of complete proteins but restricted to the serine protease domain .
for each domain , protogene managed to identify at least one corresponding gene and also reported identical protein sequences coming from closely related genomes .
figure 2 represents the portion of this alignment containing the conserved serine that is part of the catalytic triad . in a second test
for that purpose we selected the 209 human trypsin like serine proteases listed in the smart database ( 9 ) ( sm00020 ) .
protogene returned the cdss associated with 253 protein sequences found in refseq and nr ( 157 in refseq and 96 in nr ) . out of the 209 original human sequences ,
4 matched equally well a chimpanzee protein ( thus prompting the return of the associated chimpanzee cdss ) and 66 matched two distinct human entries ( thus prompting the return of 66 extra human cdss ) .
of the original sequences 26 could not be associated with an acceptable cds : 20 did not pass the blast step ( i.e. no suitable match was found in refseq or nr ) and the 6 remaining could not be properly processed by exonerate against the nucleotide sequences indicated by the database annotation .
our third example ( figure 3 ) addresses the question of nucleotide sequence conservation in the histone h2a family .
histones are notoriously conserved proteins and in the present case , launching a protogene analysis on the human h2a sequence ( swissprot p28001 ) returned 5 perfect matches in refseq , resulting in 5 cdss being reported : human , cow , rat , mouse and dog .
such a nucleotide alignment of perfectly conserved protein sequences is ideal for phylogenetic studies or motif discoveries .
it is worth pointing out that although it is identical , the chimpanzee histone was not reported by protogene because it is not included in refseq .
this finding reveals the heavy bias of protogen toward model systems included in refseq . the systematic use of nr rather than
refseq could help solve this problem , but this would come at the cost of a more complex output .
in this paper we describe protogene , a web server that makes it possible to turn a protein msa into the corresponding cds msa , using bona fide genomic or transcriptome data .
its purpose is to rapidly ask simple questions , with an emphasis on accuracy and robustness rather than sensitivity .
nucleotide sequences are fetched from ncbi and processed with exonerate to yield cdss that perfectly match the original protein .
the seed msa of the pfam profile entry ( pfam pf00574 ) was processed by protogene .
the portion of the alignment containing the serine active site classes are indicated in yellow ( ucn ) and green ( agy ) .
we describe protogene , a server that can turn a protein multiple sequence alignment into the equivalent alignment of the original gene coding dna . 
 protogene relies on a pipeline where every initial protein sequence is blasted against refseq or nr . 
 the annotation associated with potential matches is used to identify the gene sequence . 
 this gene sequence is then aligned with the query protein using exonerate in order to extract a coding nucleotide sequence matching the original protein . 
 protogene can handle protein fragments and will return every cds coding for a given protein , even if they occur in different genomes . 
 protogene is available from .