Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Paired-end mode : Read1 quality revision #39

Open
hubert93 opened this issue Dec 28, 2016 · 0 comments
Open

Paired-end mode : Read1 quality revision #39

hubert93 opened this issue Dec 28, 2016 · 0 comments

Comments

@hubert93
Copy link

hubert93 commented Dec 28, 2016

I've trimmed nexteraXT adapter for paired-end illumina data, using this command.

skewer -x CTGTCTCTTATACACATCT sample_1.fastq.gz sample_2.fastq.gz

And i realized that the quality of trimmed read1 is revised to better score.
For example,

Raw read1)
@Miseq:70:000000000-AWLU0:1:1101:14472:1001 1:N:0:TAGGCATGAAGGAGTA
NTGG ... ACCAGACGGTGAGTAACGAAAGCCAGGGGCGCGAACCGGATTAGAAACCCTTGTAGTCCCTGTCTCT
+
#8AC ... 3:C=>5ACGGG>GGFF>7=DGB47CCF7CC@>BD))9ED<C=<6@7CF6C#################

Trimmed read1)
@Miseq:70:000000000-AWLU0:1:1101:14472:1001 1:N:0:TAGGCATGAAGGAGTA
NTGG ... ACCAGACGGTGAGTAACGAAAGCCAGGGGCGCGAACCGGATTAGAAACCCTTGTAGTCC
+
#8AC ... GGGGGFGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGFFGGGGGGGCCCCC

I assume that quality of read1 is corrected by being trimmed adapter sequence using paired-end information. I wonder it is true, and whether there is any way to prevent it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant