NCBI Bookshelf. A service of the National Library of Medicine, National Institutes of Health.
SNP FAQ Archive [Internet]. Bethesda (MD): National Center for Biotechnology Information (US); 2005-.
This publication is provided for historical reference only and the information may be out of date.
Ensembl shows rs3210531 on chromosome 11 strand +1, however, NCBI shows it on chromosome 6 strand -1. Why?
We conduct two different mapping procedures for each SNP. First one places the SNP on contigs, and according to our database, rs3210531 hits chromosome 11 across all assemblies:
snp_id pos chr assembly 3210531 46406925 11 reference 3210531 46598418 11 Celera 3210531 46157042 11 HuRef An additional hit to chr6 was rejected due to our "absolute hit" strategy. This strategy states that if the mapping process finds a 100% identity hit, then the process will reject hits with lower scores as irrelevant.
Mapping to underlying sequences is a separate process and it produced the following hits for rs3210531:
We are working now on a synchronization mechanism for two these processes. (09/29/08)
The data for rs13306584 is not the same in the UCSC Genome Browser, Ensembl, or dbSNP. Why is this?
The UCSC Genome Browser and Ensembl haven't yet updated to build 128, which is the current dbSNP build. USCS is updated only to build 126, while Ensembl is updated to build 127. Since the data for rs13306584 has changed between these three builds, the data for the three databases will not be the same until the UCSC Genome Browser and Ensembl update to dbSNP build 128. (11/23/07)
- Discrepancies between Cluster Report data and Other Genome Resources - SNP FAQ A...Discrepancies between Cluster Report data and Other Genome Resources - SNP FAQ Archive
Your browsing activity is empty.
Activity recording is turned off.
See more...