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

replace read end and quality trimming to use fastp #120

Open
yannickwurm opened this issue Feb 16, 2024 · 2 comments
Open

replace read end and quality trimming to use fastp #120

yannickwurm opened this issue Feb 16, 2024 · 2 comments

Comments

@yannickwurm
Copy link
Member

see the title...

@Pigrenok
Copy link
Collaborator

But leave cutadapt for cleaning after kmc? I am not sure whether fastp can do the same as the number of reads after kmc is different and fastp does not like it.

@Pigrenok
Copy link
Collaborator

There is an incompatibility between fastp and cutadapt. If fastp is used for end and quality trimming using the following commands

fastp -i input/reads.pe1.fastq.gz -o tmp/reads.pe1.trimmed.fq --cut_front 4 --cut_front_mean_quality 10 -h tmp/reads.pe1.fastp.html
fastp -i input/reads.pe2.fastq.gz -o tmp/reads.pe2.trimmed.fq --cut_front 4 --cut_front_mean_quality 10 -h tmp/reads.pe1.fastp.html

then after kmc run, cutadapt gives an error that the paired reads do not match.

So, unless I am using fastp incorrectly, I would say we should stay with cutadapt at least for now.

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

2 participants