-
Notifications
You must be signed in to change notification settings - Fork 76
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
Automatic retrieval of input id.csv from test-datasets for test profile #293
Comments
The csv file is actually part of the release, you can see it at https://github.com/nf-core/fetchngs/blob/1.11.0/tests/sra_ids_test.csv and it does get fetched:
When I launch the pipeline with test profile, it reports: [...] So, projectDir is set to the expected path, but is not expanded properly. This is on nextflow version 23.04.1.5866 |
I realized it can be solved with a simple fix: However, version 1.12.0 of fetchngs is supposed to come out very soon, and there it is set to fetch input from test-datasets: |
yeah, sorry about that, this issue has been fixed in |
it was a simple why did I use single quotes instead of double quotes error |
Oh, I see! Thanks for the info! Closing this issue then! |
Description of feature
I'd like to change the test.config profile so that it points to an
ids.csv
file hosted in the test-datasets repository, instead of requiring the user to first manually create one.I realize that the documentation explains that you need to create an
ids.csv
file yourself, but when I first tried the pipeline, I just tried adding-profile test,apptainer
and expected it to work (like it does for the other pipelines I've used, e.g., https://github.com/nf-core/rnaseq/blob/b89fac32650aacc86fcda9ee77e00612a1d77066/conf/test.config#L24). Instead I was greeted by the following error:and was left trying to figure if something was wrong on my end, with the latest release or if the test profile simply didn't work the way I was expecting.
I'm happy to fix this myself, but wanted to first check if you'd rather have me:
or
(Thanks for the amazing tool by the way, it's made fastq retrieval so much easier for me.)
The text was updated successfully, but these errors were encountered: