-
Notifications
You must be signed in to change notification settings - Fork 160
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
rmdup: dup-num-file not created if no duplicated reads #436
Comments
Oh, yes, it's designed to act like this. https://github.com/shenwei356/seqkit/blob/master/seqkit/cmd/rmdup.go#L181 |
I can see the logic of not creating the file if there are no duplicated reads but, when using |
Well, I can change the behaviour. But it should be easy to detect if a file exists in |
Changed. Try this. |
Nice! It seems to work! |
Please check the items below before submitting an issue.
They help to improve the communication efficiency between us.
Thanks!
Prerequisites
For Mac users, Please download
seqkit_darwin_amd64.tar.gz
for Mac with Intel CPUs.seqkit_darwin_arm64.tar.gz
for Mac with M series CPUs.seqkit version -u
.Describe your issue in detail
file xxx
andls -lh xxx
.head -n 5 xxx
orzcat xxx.gz | head -n 5
.I am running
seqkit
on a RedHat server:But
seqkit rmdup
does not create thedup-num-file
(dup.tsv
) file if there are no duplicated reads in the input file.Input file is a FASTQ:
The text was updated successfully, but these errors were encountered: