what can cause high(> 80%) spike-ins and low read count (<100 reads) in low complexity ampseq run
1
0
Entering edit mode
20 months ago
eli_bayat ▴ 90

Hello, I have data output from low complexity ampseq run. The read counts are very low (<100 reads per well) and the spike-ins% is very high (>80%) across all of the samples. We checked QC for the run and have not observed any issue with the run. I am not sure what could go wrong during experiment or library prep that contribute to this. Lab scientists repeated the library prep. and we got the same result. Any suggestion or idea on What might be the reason for such a high spike-ins and low read count appreciated.

amplicon_sequencing NGS_reads low_complexity spike-ins ampseq • 417 views
ADD COMMENT
2
Entering edit mode
20 months ago
LChart 3.9k

My first instinct is DNAse contamination, which would impact both the input material and the spike-in. If the spike-in reads are very high, and amplicon reads very low; then the contamination occurred prior to spike-in; of reads are low across the board then the contamination happened during library prep.

However, unless equipment was heavily contaminated, or there's contamination in some reagent, this typically impacts a single library prep, and should not be repeatable.

Another possibility is that the primers did not anneal; and sometimes this can happen if there are multiple batches of primers being used for different experiments, and something was mislabeled. Alternatively the thermocycler could be broken; but it typically issues an error or warning if it thinks something is wrong with the temperature.

ADD COMMENT

Login before adding your answer.

Traffic: 3223 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