Incorrect exon number in NCBI RefSeq (GRCh38)

25 views
Skip to first unread message

Alexis Praga

unread,
May 8, 2025, 5:12:31 PM5/8/25
to UCSC Genome Browser Public Support
Hi,

In GRCh38, SHANK3 is shown as having 25 exons on NCBI Refseq. Zooming in reveals exon 13 is actually a "micro-exon".

micro-exon.png

However, RefSeq with the same accession number has only 23 exons: https://www.ncbi.nlm.nih.gov/gene/85358. So it does not look like an alignment issues.
On NCBI, only one exon is shown
refseq.png

I'm aware of differences between UCSC and NCBI Refseq for SHANK3 ( https://groups.google.com/a/soe.ucsc.edu/g/genome/c/yMxAt00XVHs/m/I4vamnA7BwAJ ) but this happens on the NCBI Refseq track.
RefSeq helpdesk advised to see with you to get to the bottom of the matter so any pointer would be great

Thanks,

Alexis

ale...@praga.dev

unread,
May 16, 2025, 1:59:56 PM5/16/25
to Alexis Praga, UCSC Genome Browser Public Support
Hi,

After exchanging with Refseq, they told me the transcript is fine but there are alignement issues in GRCh38 with the CDS of SHANK3.
Using a "fix" in the reference genome shows the proper number of exons ( chr22_KQ759762v2_fix:8917-69331 ).
This is actually the first result using the search for SHANK3.

Best,

Alexis

On 2025-05-08T23:12:39.000+02:00, Alexis Praga <alexis...@gmail.com> wrote:
Hi,

In GRCh38, SHANK3 is shown as having 25 exons on NCBI Refseq. Zooming in reveals exon 13 is actually a "micro-exon".

micro-exon.png

However, RefSeq with the same accession number has only 23 exons: https://www.ncbi.nlm.nih.gov/gene/85358. So it does not look like an alignment issues.
On NCBI, only one exon is shown
refseq.png

I'm aware of differences between UCSC and NCBI Refseq for SHANK3 ( https://groups.google.com/a/soe.ucsc.edu/g/genome/c/yMxAt00XVHs/m/I4vamnA7BwAJ ) but this happens on the NCBI Refseq track.
RefSeq helpdesk advised to see with you to get to the bottom of the matter so any pointer would be great

Thanks,

Alexis

--

---
You received this message because you are subscribed to a topic in the Google Groups "UCSC Genome Browser Public Support" group.
To unsubscribe from this topic, visit https://groups.google.com/a/soe.ucsc.edu/d/topic/genome/Ne9k3HxYaI8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to genome+un...@soe.ucsc.edu.
To view this discussion visit https://groups.google.com/a/soe.ucsc.edu/d/msgid/genome/f427c08f-ebf5-429a-9d04-003f8e442da7n%40soe.ucsc.edu.

Gerardo Perez

unread,
May 23, 2025, 5:01:18 AM5/23/25
to ale...@praga.dev, Alexis Praga, UCSC Genome Browser Public Support

Hello, Alexis.

Thank you for your interest in the UCSC Genome Browser and for your question regarding SHANK3.

We appreciate you reaching out to the RefSeq helpdesk and bringing the alignment issue with the SHANK3 CDS in hg38/GRCh38 to our attention. We can confirm that the alignment to the fix patch sequence chr22_KQ759762v2_fix:8,917–69,331 appears in the results and correctly displays 23 exons for SHANK3.

If you have any further questions, please reply to gen...@soe.ucsc.edu. All messages sent to that address are archived on a publicly-accessible Google Groups forum. If your question includes sensitive data, you may send it instead to genom...@soe.ucsc.edu.

Gerardo Perez
UCSC Genomics Institute


You received this message because you are subscribed to the Google Groups "UCSC Genome Browser Public Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to genome+un...@soe.ucsc.edu.
To view this discussion visit https://groups.google.com/a/soe.ucsc.edu/d/msgid/genome/3b671e10-cbc2-4285-b0b6-132f0c331eeb%40mail.infomaniak.com.
Reply all
Reply to author
Forward
0 new messages