Open mortunco opened 1 month ago
Hi @mortunco
I think you might have found a fun bug. Do you know if the values existed for --outdir
in each of these situations?
Also, can you try running the second command with --only-download-metadata
? I'm also going to replicate on my end to see why one works and the other doesn't.
Cheers, Robert
$ fastq-dl -a ERX5847526 --outdir case_1/ --only-provider --verbose --cpus 2 --only-download-metadata
2024-06-05 20:45:53 DEBUG 2024-06-05 20:45:53:root:DEBUG - Querying for metadata (Attempt 1 of 10) fastq_dl.py:473
DEBUG 2024-06-05 20:45:53:root:DEBUG - --only-provider supplied, limiting queries to ena fastq_dl.py:476
DEBUG 2024-06-05 20:45:53:urllib3.connectionpool:DEBUG - Starting new HTTPS connection (1): www.ebi.ac.uk:443 connectionpool.py:1055
2024-06-05 20:45:55 DEBUG 2024-06-05 20:45:55:urllib3.connectionpool:DEBUG - https://www.ebi.ac.uk:443 "GET /ena/portal/api/search?result=read_run&format=tsv&query=%22experiment_accession=ERX5847526%22&fields=all connectionpool.py:549
HTTP/1.1" 200 None
INFO 2024-06-05 20:45:55:root:INFO - Query: ERX5847526 fastq_dl.py:723
INFO 2024-06-05 20:45:55:root:INFO - Archive: ena fastq_dl.py:724
INFO 2024-06-05 20:45:55:root:INFO - Total Runs Found: 2 fastq_dl.py:726
DEBUG 2024-06-05 20:45:55:root:DEBUG - --only-download-metadata used, skipping FASTQ downloads fastq_dl.py:727
INFO 2024-06-05 20:45:55:root:INFO - Writing metadata to case_1//fastq-run-info.tsv
$ fastq-dl -a SRX12493302 --outdir case_2/ --only-provider --verbose --cpus 2 --only-download-metadata
2024-06-05 20:46:15 DEBUG 2024-06-05 20:46:15:root:DEBUG - Querying for metadata (Attempt 1 of 10) fastq_dl.py:473
DEBUG 2024-06-05 20:46:15:root:DEBUG - --only-provider supplied, limiting queries to ena fastq_dl.py:476
DEBUG 2024-06-05 20:46:15:urllib3.connectionpool:DEBUG - Starting new HTTPS connection (1): www.ebi.ac.uk:443 connectionpool.py:1055
2024-06-05 20:46:17 DEBUG 2024-06-05 20:46:17:urllib3.connectionpool:DEBUG - https://www.ebi.ac.uk:443 "GET connectionpool.py:549
/ena/portal/api/search?result=read_run&format=tsv&query=%22experiment_accession=SRX12493302%22&fields=all HTTP/1.1" 200 7559
INFO 2024-06-05 20:46:17:root:INFO - Query: SRX12493302 fastq_dl.py:723
INFO 2024-06-05 20:46:17:root:INFO - Archive: ena fastq_dl.py:724
INFO 2024-06-05 20:46:17:root:INFO - Total Runs Found: 1 fastq_dl.py:726
DEBUG 2024-06-05 20:46:17:root:DEBUG - --only-download-metadata used, skipping FASTQ downloads fastq_dl.py:727
INFO 2024-06-05 20:46:17:root:INFO - Writing metadata to case_2//fastq-run-info.tsv fastq_dl.py:736
I shared the output fastq-run-info.tsv
My ignorant idea is maybe --only-provider is causing one to fail and other one fail ?
Hello,
Great tool. Super useful. Especially one SRX deal with all SRRs is a life saver. Many thanks.
I have two scRNAseq datasets. I shared the examples below. I am strictly running my fastq-dl with --only-provider to get fastq.gz . These two samples dont have fastq.gz therefore technically both runs should exit with 1. But one finishes with exist status 0 (the top case) and the other exits with 1. I am just curious how these two samples are different so they are giving different outputs.
Any idea what could be different?
Thanks in advance, Best, T.