You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some SRA files are incorrect (either due to submitter not supplying correct files, or SRA not having correct annotation). For example, this file: SRR18972600 (GSM6077643). This marked as PE, but fastq-dump only gets one fastq file.
To Reproduce
RNA-seq workflow, with the following samples.tsv:
sample assembly
GSM6077643 GRCh38
Expected behavior
I don't know! Either an informative error message (i.e. two fastq files should be there, there's only one, this can be checked) or the file being treated as single-end. The second option may not be correct, and I assume this may also be hard to implement. I would guess an error message would already be good, because the error is not easily identifiable from the log, but only when you manually repeat the steps.
One thing I noticed that these are not sequenced with Illumina, but with DNBSEQ-G400.
Low priority bug I would say, but something to be aware of.
The text was updated successfully, but these errors were encountered:
Describe the bug
Some SRA files are incorrect (either due to submitter not supplying correct files, or SRA not having correct annotation). For example, this file:
SRR18972600 (GSM6077643). This marked as PE, but
fastq-dump
only gets one fastq file.To Reproduce
RNA-seq workflow, with the following
samples.tsv
:Expected behavior
I don't know! Either an informative error message (i.e. two fastq files should be there, there's only one, this can be checked) or the file being treated as single-end. The second option may not be correct, and I assume this may also be hard to implement. I would guess an error message would already be good, because the error is not easily identifiable from the log, but only when you manually repeat the steps.
One thing I noticed that these are not sequenced with Illumina, but with DNBSEQ-G400.
Low priority bug I would say, but something to be aware of.
The text was updated successfully, but these errors were encountered: