-
Notifications
You must be signed in to change notification settings - Fork 75
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
Add support back in for GEO IDs #155
Conversation
|
We'll need to update the test-datasets for fetchngs to include a GSM ID (maybe GSE ID aswell?) for a small dataset |
This is the GEO id I was using previously for testing |
Added GSM4907283 back in nf-core/test-datasets@45bdee9 But as I mentioned in the previous comment, be nice to find another small GEO id that is composed of multiple runs for a given experiment. |
Made a PR to add GSE214215 for a series/experiment that is composed of 2 SRA runs, see nf-core/test-datasets#887. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Gorgeous!
Closes #104
Adding support for GEO IDs back in by:
GSM*
(GEO sample accessions) andGSE*
(GEO series/experiment IDs which contain multiple GSM IDs) IDs differentlyesearch
) and resolve to SRA IDs directlyesummary
to resolve GSE IDs -> GDS UIDs (withdb: gds
) thenesearch
to resolve GDS UIDs -> GSM UIDs -> SRAHas been tested on the following GEO IDs:
GSM4907283
GSM465244
GSM465247
GSE215376
GSE18729
PR checklist
nf-core lint
).nextflow run . -profile test,docker --outdir <OUTDIR>
).docs/usage.md
is updated.docs/output.md
is updated.CHANGELOG.md
is updated.README.md
is updated (including new tool citations and authors/contributors).