Ngs With Sanger
4
1
Entering edit mode
12.1 years ago
User 9166 ▴ 10

Hello all,

Our Sanger sequencing finds one homologous SNPs on chr7 for a patient with heart disease, but NGS data from three platforms (PGM, MiSeq and HiSeq) all show that site only has homologous of reference allele, how to explain this?

Many thanks

sequencing • 2.4k views
ADD COMMENT
3
Entering edit mode

Can you provide more information about the Sanger sequencing? How many sample repeats were performed? What does the chromatogram trace look like for the Sanger read?

ADD REPLY
3
Entering edit mode

You probably mean homozygous, not homologous? In addition to looking at the sanger trace, I would also want to see the coverage for NGS that you have at this position.

ADD REPLY
0
Entering edit mode
12.1 years ago
Darked89 4.6k

Back in the past some cloning kits introduced mutations in cloned PCR fragments. Also "mutation calling" on Sanger PCR-fragment data can be nonsensical if there is high amplification background. show/send trace files to some old hats experienced with mutation screening.

ADD COMMENT
0
Entering edit mode
12.1 years ago
Swbarnes2 ★ 1.6k

What are the odds that it's a sample mix-up? These things do happen.

ADD COMMENT
0
Entering edit mode
12.1 years ago
Wen.Huang ★ 1.2k

could it be misalignment? NGS reads are short and if there was a short stretch of sequence somewhere else in the genome that looked like your target region except that it was homo for the reference, the situation you described could have happened.

ADD COMMENT
0
Entering edit mode
12.1 years ago
Bair • 0

Thank you all.

Several Sanger samples repeat the mutation, it's NGS coverages are high (>300) by each of the three platforms.

The length of reads is as long as 300bp, (100 in HiSeq, 150 in MiSeq and 20-300 in PGM), so it might be a sample mix-up problem.

Will let you informed ASAP.

ADD COMMENT

Login before adding your answer.

Traffic: 2733 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6