Closed seandavi closed 3 years ago
This looks related to: https://github.com/ncbi/sra-tools/issues/318#issuecomment-661121843
If the expected fix is to not use fasterq-dump
with PacBio runs loaded with pacbio-load
, is there not a way to fall back to fastq-dump
when this error arises rather than requiring the user to catch the error by hand (note that there is no way to computationally catch this error, specifically) and then troubleshoot?
Now fasterq-dump SRR5219188
prints the following message:
2020-12-18T20:11:06 fasterq-dump.2.10.9 err: accession 'SRR5219188' is PACBIO, please use fastq-dump instead
Unfortunately fasterq-dump
does not support PacBio runs.
Use fastq-dump
instead.
I am trying to unpack some pacbio SRA files using fastq-dump 3.0.1 and it throws this error
fastq-dump SRR10130136.sra
2023-02-14T20:46:42 fastq-dump.3.0.1 err: accession 'SRR10130136' is PACBIO, please use fastq-dump instead
Results in:
These all look to be PacBio runs, so I suspect there is a systematic issue here somewhere. Any suggestions?