Question: WXS kmer over-representation post trimming.
0
gravatar for dr.dimo
2.4 years ago by
dr.dimo0
dr.dimo0 wrote:

Greetings and salutations, I am attempting to analyse some human Illumina WXS data and am getting some unfamiliar kmer over-representation. Usually post trimming (trimmomatic) I get quite good removal of kmers but with this latest data I can't seem to get rid of the 3-primer kmers. My question is in two parts.

1) Should I worry about this or just continue alignment/variant calling.

2) If I should worry about, how can I trim these successfully?

My trimmomatic parameters and pre/post trimming images are below, but I am probably missing something super obvious.

Thanks in advance.

 trimmomatic-0.36.jar  -phred33 1_ATGCCTAA_L001_R1.fastq.gz 1_ATGCCTAA_L001_R2.fastq.gz output_forward_paired.fq.gz output_forward_unpaired.fq.gz output_reverse_paired.fq.gz output_reverse_unpaired.fq.gz ILLUMINACLIP:adapters/TruSeq3-PE.fa:2:30:10 LEADING:3 TRAILING:3 SLIDINGWINDOW:4:15 MINLEN:75

pre trim post trim

next-gen • 764 views
ADD COMMENTlink written 2.4 years ago by dr.dimo0

I have no experience in sequencing, but have seen this in our data due to the use of hexamers in the fragmentation or shearing step... You might not have to worry about this in variant-calling if you have good-enough coverage and are looking into major allele fractions

ADD REPLYlink written 2.4 years ago by Rohit1.3k

Great, appreciate the response.

ADD REPLYlink written 2.4 years ago by dr.dimo0

Fragmentation bias tends to be on the left end of the read, rather than the right end.

ADD REPLYlink written 2.3 years ago by Brian Bushnell16k
Please log in to add an answer.

Help
Access

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 2.3.0
Traffic: 1762 users visited in the last hour