PubMed Nucleotide Protein Genome Structure Taxonomy

Macaca mulatta - rhesus macaque genome data and search tips Revised 2 May 2007

The Map Viewer help document describes how to use the Map Viewer software. This page describes the data available for Macaca mulatta, and the search tips specific to that organism. Upon familiarization, return to the Macaca mulatta genome overview page or stop by the Map Viewer home page, where you can search the genome data of any organism represented in Map Viewer.

  1. Scope of Data
  2. Available Maps
  3. Constructing queries
  4. Constructing URLs


Scope of Data back to top

The Map Viewer provides a view of rhesus data from sequence and radiation hybrid maps, described below.
Separate documents provide an introduction to the information infrastructure developed at NCBI to integrate the various types of data generated by the Rhesus Macaque Genome Project, including statistics for the current build.

Rhesus Macaque Genomic Sequence Data back to top

The current rhesus macaque genome build is the assembly produced by the Macaque Genome Sequencing Consortium which was led by the Baylor College of Medicine Genome Sequencing Center in collaboration with the J. Craig Venter Joint Technology Center and the Genome Sequencing Center at Washington University in St. Louis. The genome was derived from a female rhesus macaque at the Southwest Foundation for Biomedical Research in San Antonio, Texas. The sequencing strategy produced a 5.1-fold whole-genome shotgun (WGS) assembly.

Rhesus BLAST Databases back to top

The complete set of rhesus macaque sequence databases available for BLAST searching are shown on the Rhesus macaque BLAST page, which includes a link to the database descriptions.

Additional Rhesus Genome Resources back to top

In addition to the Macaca mulatta data available in the Map Viewer and through BLAST, links to NCBI resources and external sites are available from the Rhesus Genome Resource Guide.

Available Maps back to top

Sequence-Based Maps back to top

Ab initio

Shows models generated by Gnomon. mRNA alignments were used to segment the genomic sequence by putative gene boundaries, and Gnomon was executed on these segments to predict genes. Gnomon uses protein alignments in addition to transcript alignments and, in order to capture as much coding information in the genome as possible in this assembly, Gnomon models may represent partial as well as complete coding sequences. Models with a completely supported CDS are blue, models with a partially supported CDS are green, and the pure ab initio predictions are brown. Those ab initio predictions with e values <0.0001 are indicated as dark brown on the map and all other ab initio predictions are shown in light brown. Pure ab initio status indicates that the model was built without the support of mRNA or protein alignments, either through failure to align the sequence to the genome or an alignment ignored by Gnomon due to a score falling below a pre-determined threshold.

Component The component map provides the tiling path of GenBank accessions from the Rhesus macaque whole genome shotgun project used to build the WGS contigs, which are described below.

Contig Shows the chromosomal placement of NW_xxxxxx contigs on the rhesus macaque assembly of whole genome shotgun (WGS) data. The individual GenBank records used to assemble the contigs are shown on the Component map, described above.

CpG Island Shows regions of high G + C content on the assembled genome sequence. Two sets of criteria were used for finding CpG islands: "strict" and "relaxed," described below. The algorithm (and cutoffs) were taken from Takai and Jones, 2002.
  • relaxed (shown with light blue shading on the map)
    • 200 bp min length
    • 50% or higher G + C content
    • 0.60 or higher observed CpG / expected CpG
    • post-processing:  merge islands that are <= 100 bp apart
  • strict (shown with dark blue shading on the map)
    • 500 bp min length
    • 50% or higher GC content
    • 0.60 or higher observed CpG / expected CpG
GenBank_DNA

Shows the placement of rhesus macaque genomic DNA sequences from GenBank that were not used in the assembly of contigs. The placement is based on the alignment of the sequences to the components of the contigs. It includes rhesus macaque genomic sequences longer than 500 bp that have at least 97% identity to the components for at least 98 base pairs. If a sequence extends beyond a contig, that portion of sequence is not shown. The 'hits' link leads to a tabular display that shows the matching regions (base spans) of the assembly component and the GenBank genomic DNA record that has been aligned to it.

Orange lines represent unfinished (phase 1 and 2) HTGs sequences that have been aligned to the assembled genome. Blue lines represent other rhesus macaque genomic DNA records that have been aligned to the assembled genome.

The length of a line represents the upper and lower-most points on the genome assembly to which sequence fragments from a single GenBank record were aligned.

Thick parts of a line represent fragments of sequence from a GenBank record that have been aligned to the assembled genomic sequence, and the thin parts of a line connect the fragment that come from a single GenBank record.

When the GenBank_DNA map is displayed as the master map, in the default verbose mode, the descriptive text includes a bases column, which shows the total number of bases in the GenBank record that was aligned to the genome, and a status column, which shows the total number of bases from that record that were aligned to the genome, how many separate pieces of sequence from that record were aligned, and whether those pieces were shuffled to make the alignment.
Genes_Sequence Genes that have been annotated on the genomic contigs. This includes known and putative genes placed as a result of alignments of mRNAs to the contigs. If multiple models exist for a single gene, corresponding to splicing variants, the Genes Sequence map presents a flattened view of all the exons that can be spliced together in various ways. For example, if one splice variant uses exons 1, 3, 4, and another splice variant uses exons 2, 3, 4, the Genes Sequence map shows exons 1, 2, 3, 4. Genes shown on the left of the grey line are transcribed in the - orientation (from bottom up), and those on the right in the + orientation (from top down).

When Genes Sequence is selected as the Master map, the verbose display (detailed labeling, shown by default) includes arrows to the right of each gene name indicate its direction of transcription as well as links to:

  • sv - sequence viewer
  • pr - protein
  • dl - view/download sequence data
  • ev - evidence viewer
  • mm - Model Maker
  • hm - HomoloGene

Gene models are shown in five colors, depending on the type of evidence that was used to construct the models. The one or two letter code shown in the evidence column (that is displayed when Gene_Sequence is the master map) also indicates the type of evidence.

 
Gene Color Evidence Code Type of evidence used to construct gene model
Blue C Confirmed gene model - model based on alignment of mRNA, or mRNAs plus ESTs, to the genomic sequence (see additional notes, below)
Light Green E EST only - model based on EST evidence only
Dark Brown PE Predicted+EST - model predicted by Gnomon and EST evidence
Light Brown P Predicted only - model predicted by Gnomon
Orange ? Conflict - there is some discrepancy between the mRNA sequence and the gene model (see additional notes, below)
  I Interim LocusID - model based alignment of mRNAs, or mRNAs plus ESTs, to the genome, in which the aligning transcripts could not be unambiguously assigned to a preexisting LocusID (see additional notes, below)

  Additional Notes:

In general, a gene model is shown in blue if there is a clean alignment between a RefSeq or GenBank mRNA sequence and the genomic sequence, and if there is an exact match between the protein product that was annotated in the mRNA sequence record and the conceptual translation of the genomic sequence gene model.

A gene model is shown in orange if there is some discrepancy between the mRNA sequence and the gene model, either in the alignment of the two and/or in their protein products. Examples of the former can include gaps, or the alignment of an mRNA to two or more genomic regions. Examples of the latter can include differences between the amino acid sequence given in an mRNA sequence record and the conceptual translation of the corresponding gene model, or premature termination of a coding region in the genomic sequence. Both of those can be caused by base pair mismatches between the mRNA and genomic sequence.

Models with Interim LocusIDs (evidence code I) may be paralogs, genes not yet curated, duplications because of assembly errors, or pseudogenes. The genome assembly and annotation pipeline assigns interim IDs when there is no unambiguous solution to what they should be. Interim LocusIDs are always associated with a RefSeq XM_* accessions (model mRNAs), although supporting alignments may (or may not) include RefSeq NM_* accessions (known mRNAs). More about RefSeq and RefSeq accessions...

RefSeq RNA Diagrams of the RNAs that are predicted on the genomic contigs. The RefSeq RNA map and Genes_Sequence map are built in the same way, using the same types of evidence, described above. However, the Genes_Sequence map shows a view of all the exons in a gene, while the RefSeq RNA map shows the combinations of exons (i.e., splice variants) that are valid, based on mRNA sequences.

Repeats Position of repetitive elements.

The RepeatMasker was used to illustrate areas within the genome that contain interspersed repeats and low complexity DNA sequences.


RNA Maps

The RNA maps show mRNA and EST sequences from a given organism aligned to the assembled rhesus macaque genomic sequence that has been repeat-masked and dusted. Only ESTs supplied with orientation are used. Each alignment is the single best placement for that sequence in the current build of the rhesus macaque genome. It can be queried by sequence accession.

The RNA maps include:
  • Hs_RNAs - individual Homo sapiens (human) mRNAs and ESTs aligned to the rhesus macaque genome.
  • Macaca_RNAs - individual mRNAs and ESTs from species of the genus macaca aligned to the rhesus macaque genome.
  • Mmu_RNAs - individual Macaca mulatta (rhesus macaque) mRNAs and ESTs aligned to the rhesus macaque genome.

The display for RNA maps differs from those labeled as Xx_UniGene in that what are displayed here are the alignments [thicker lines] and putative introns [thinner lines] of ESTs and longer mRNAs best placed at that position. Green lines indicate ESTs; blue indicates cDNAs. In contrast, the "UniGene" map is a summary of probable splicing events, with connections to UniGene for the clusters that contain those sequences.

STS Placement of STSs from a variety of sources onto the assembled genomic sequence (the NW_xxxxxx contigs, described above) using Electronic-PCR (e-PCR).


Unigene Maps

The UniGene maps show EST sequences from a given organism aligned to the assembled genomic sequence that has been repeat-masked and dusted. Only ESTs supplied with orientation are used. Each alignment is the single best placement for that sequence in the current build of the genome. ESTs are clustered based on shared introns and alignment to a common position on the genome. Those ESTs can come from one or more UniGene clusters, whose IDs are noted by the EST cluster. (UniGene clusters are made with a different build procedure, so there is not necessarily a one-to-one correspondence between EST clusters on the UniGene map and clusters in the UniGene resource.)

The display of the UniGene map varies according to the span of sequence being displayed.

For large spans of sequence (greater than 10 million bases), the Map Viewer displays histograms that show the density of ESTs and mRNAs aligned to a region, the UniGene clusters to which they belong, and the number of sequences from each UniGene cluster.

For smaller spans of sequence (i.e., higher resolutions, showing less than 10 million bases), the Map Viewer displays the above information plus blue lines that indicate exon/intron structure:

  • thick blue lines indicate aligned regions (putative exons)
  • thin blue lines indicate connections between aligned regions (putative introns). Regions are connected if they come from a single transcript, or from a set of 'chained' transcripts that share at least one common intron/exon splice junction. (For example, if transcript B shares one intron/exon splice junction with transcript A, and a different splice junction with transcript C, then A, B, and C will be chained together into one transcript.)
  • a light grey bar shades the region that encompasses all the alignments consistent with a given set of evidence (putative mRNA), and therefore indicates the span of a model

Alignments are grouped by common structure. If two or more transcripts share at least one intron/exon splice junction, the alignments of those transcripts are merged into a single model. If two or more transcripts do not share any intron/exon splice junction, they are shown as separate models.

The UniGene maps include:
  • Hs_UniGene - Human EST clusters aligned to the assembled rhesus macaque genome.
  • Macaca_UniGene - Macaque species, excluding Macaca mulatta, EST clusters aligned to the assembled rhesus macaque genome.
  • Mmu_UniGene - Rhesus macaque EST clusters aligned to the assembled rhesus macaque genome.
Variation Alignment of genetic variation data from dbSNP onto the assembled genomic sequence (the NW_xxxxxx contigs, described above).

Radiation Hybrid Maps back to top

RH This comprehensive radiation hybrid (RH) map was created using a 5000 rad RH panel as described by Murphy et al. 2005 and Murphy et al. 2001. It has an average resolution of 3.5 Mb and contains 802 markers covering all 20 autosomes and the X and Y chromosomes. Most of the computations for the map were done with rh_tsp_map (retrieve software). The Murphy et al. publications follow the human-based chromosome naming system proposed by Wienberg et al. The mapviewer RH map follows the size-based naming system proposed by Rogers et al.

The Rogers et al. chromosome naming system compared to the human chromosome and Wienberg et al. chromosome names can be reviewed in this table

Constructing queries back to top

Searchable Terms back to top

The Map Viewer supports searching on any term that describes an element on any map, including:
  • GenBank accession number
  • marker name
  • marker alias
    Sometimes two or more marker names refer to the same primer pair, and are therefore considered synonyms or "aliases." In such cases, any one of the terms will retrieve the marker.
  • text words
    For example, a search for actin will retrieve all map objects containing that word in their description. If multiple terms are entered, they will automatically be combined with the 'AND' Boolean operator. Adjacency searches are not supported at present. For example, a query entered as "cell adhesion" will be processed as cell AND adhesion and will retrieve records with descriptions that contain cell matrix adhesion as well as cell adhesion.
Search terms can also be truncated at the right end only, using an asterisk (*) as a wild card to represent zero to many characters. See the truncation section of the general Map Viewer Help document for more details.

Map Positions back to top

As noted in the Search By Position section of the Entrez Map Viewer general help document, there are three main ways to search by map position from the Map View of a chromosome:
  1. enter a range of interest in the Region text boxes in side bar
  2. click on the region of interest in the chromosome thumbnail graphic in the sidebar
  3. click on a region of interest in the enlarged Map View of the chromosome
The following types of map positions can be entered in option 1:
  • symbols - you can enter marker names or alternate marker names (aliases) to display a region of the chromosome between those mapped elements. Note that both mapped elements must be present on the maps that share the same coordinate system in order for the range search to work properly.

  • numerical positions - can be used if the master map is a genetic map, radiation hybrid map, YAC map, or sequence map. It is not necessary to specify units. The Map Viewer will interpret the range in the units of the master map (centiMorgans, centiRays, ordinal units, or bases, respectively). Note that for a sequence map, base pair positions may be entered in any of the following formats: 1000000 or 1,000,000 or 1M or 100K.

It is not necessary to enter a value in both Region text boxes. If you enter a value only in the upper box, the Map Viewer will display the region of the chromosome starting from that point and ending at the lower end of the chromosome. If you enter a value only in the lower box, the Map Viewer will display the region of the chromosome starting at the upper end of the chromosome and ending at the value entered.

General Tips back to top

As mentioned in the Searchable Terms section of the Map Viewer Help Document, any term entered in the query box will be treated as an independent entity to be joined by the 'AND' Boolean operator. It is also possible to construct more complex queries by using explicit Boolean operators (AND, OR, NOT), field restriction, or limiting retrieval to records that have certain properties.

The Advanced Search page allows you to use a number of query options by simply checking boxes or radio buttons that represent various search fields, properties, and object types. It also allows you to limit your query to one or more chromosomes. The Advanced Search page is accessible from the header region of the genome view page.

Constructing URLs that link to Map Viewer back to top

If you would like to create WWW links to the Map Viewer, the instructions for constructing URLs are given in the general Map Viewer Help document. You can construct URLs that either perform a search or display a specific mapped object or chromosomal region.