Skip to content
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

Incorrect fastq paths in scRNA-seq sample sheet #326

Open
huldash opened this issue Nov 29, 2024 · 0 comments
Open

Incorrect fastq paths in scRNA-seq sample sheet #326

huldash opened this issue Nov 29, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@huldash
Copy link

huldash commented Nov 29, 2024

Description of the bug

I am trying to use fetchngs to download scRNA-seq data from SRP348981 and prepare a sample sheet for input to the nf-core/scrnaseq pipeline. The scrnaseq pipeline requires columns sample, fastq_1, and fastq_2 in the sample sheet. The SRA records show three reads per spot: an index read (not required), read 1 (fastq_1), and read 2 (fastq_2). Read 2 is tagged as a biological read while the index and read 1 are tagged as technical reads. fetchngs with default options only downloads the fastq file for read 2. The path is added to the fastq_1 column of the sample sheet which is incorrect. Setting --download_method sratools results in successful download of all three fastq files but the sample sheet is still incorrect. The index read is added to the fastq_1 column and the fastq_2 column is still empty.

Is there a way to include both the read 1 and read 2 fastqs in the correct columns of the sample sheet with the current fetchngs version?

I have encountered this issue and others with several scRNA-seq datasets in SRA. Are there plans for future fetchngs releases to explicitly support --pipeline scrnaseq?

Command used and terminal output

nextflow run nf-core/fetchngs --input ./SRP348981_accession_list.csv --download_method sratools -profile docker

Relevant files

SRP348981_accession_list.csv
samplesheet.csv

System information

nf-core/fetchngs version 1.12.0

@huldash huldash added the bug Something isn't working label Nov 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant