-
Notifications
You must be signed in to change notification settings - Fork 259
fasterq-dump fails due to output file naming error #865
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
Comments
the executed command was this
|
It looks like the tool is confused about the output-file. |
Thanks for the swift response and the workaround. I'll try to modify the code of the pipeline I am using. However, to me it looks like the path gets split at the |
by the way... what is the version of fasteq-dump you are using? |
the version is 3.0.8 |
Just to let you know. This does not occur in version 2.11.0 |
Thanks for reporting @dmalzl ! And thanks for investigating @wraetz 🙏🏽 I have managed to reproduce the issue and the problem is indeed the fact that a
name: sra-tools-3.0.8
channels:
- conda-forge
- bioconda
- defaults
dependencies:
- conda-forge::pigz=2.6
- bioconda::sra-tools=3.0.8
|
The problem is this function here, which splits on any period found and creates a new filename. It should split on the final period only, or even better use some form of path handling (not 100% familiar with code). sra-tools/tools/external/fasterq-dump/sbuffer.c Lines 146 to 172 in 8575947
|
Please try release 3.2.1. |
I am currently trying to download a couple of raw sequencing data files using sra-tools prefetch and fasterq-dump. Prefetch works fine but I get a weird error when trying to convert the generated *.sra file to fastq with fasterq-dump. The data is paired-end and the actual path should be
/scratch/daniel.malzl/work/aa/7ab6e5d29db7a0352a1f1cd4af2af3/SRX10737613_SRR14385311
but judging by the error message there seems to be some bug in the renaming code because it says the following:so it seems to insert the read1, read2 suffixes into the path causing the path to be invalid.
The version I am using is 3.0.8.
The text was updated successfully, but these errors were encountered: