-
Notifications
You must be signed in to change notification settings - Fork 441
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
Update shovill tool to accept fastq and fastq.gz #5476
Conversation
Why do you use fastq as format for your data and not fastqsanger or fastqillumina? Fastq is essentially an unspecified fastq which should be used if the underlying tool can work with both phred encodings. Is this the case here? |
The tool failed when we submitted classical fastq or fastq.gz illumina reads (while shovill command line accept this input type). If I force to change data input as fastqsanger it's okay but not good |
Then we should explicitly add
|
But I also have to add that the fact that a tool accepts both types may not be the same as that the tool correctly works with both. Most of the time tools accepting both types either
|
Humm you right, Shovill explicitaly work with |
Ironically I can't agree with this statement. If you check their test data they have fastq files with all quality values being Maybe it's best to just open an issue at their repo and ask if shovill can deal with fastq data of any quality encoding. |
They can for sure deal with fastqsanger. |
I don't have any answer from my issue on shovill repo, so it's better to keep only fastqsanger as previously write on the wrapped. So my PR is not necessary. |
Shovill seem to failed when input is indicated as fast or fastq.gz while it can work with this input.
I just add the fastq as input format