-
Notifications
You must be signed in to change notification settings - Fork 417
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
FEAT: Use annotation-cache and update VEP to v110 #1122
Conversation
|
"use_annotation_cache_keys": { | ||
"type": "boolean", | ||
"fa_icon": "fas fa-toolbox", | ||
"description": "Use annotation cache keys for snpeff_cache and vep_cache.", |
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.
can we get a help text with a bit more explanation
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.
like i am unsure now, if this referes to the new s3 bucket or if I want to define some cache locally or so
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.
yeah, basically that's because of how snpeff and vep store data, they're made for HPC, and I'm storing on cloud.
Plan would be to extrapolate that in the docs.
But I need to build a website for that.
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.
ok awesome :)
@@ -128,6 +128,10 @@ if (params.tools && (params.tools.split(',').contains('ascat') || params.tools.s | |||
} | |||
} | |||
|
|||
if ((params.download_cache) && (params.snpeff_cache || params.vep_cache)) { | |||
error("Please specify either `--download_cache` or `--snpeff_cache`, `--vep_cache`.\nhttps://nf-co.re/sarek/dev/usage#how-to-customise-snpeff-and-vep-annotation") |
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.
did you update these docs already? Quick question how does this work for a cluster wide setup? I am thinking it would make sense to instruct users to predownload this, same as for igenomes and then supply the cache location (maybe sarek specific config specific config, to keep download costs low in terms of time and storage space for users)
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.
yeah, for a regular HPC, that depends if you build yourself or if you copy annotation_cache.
If you build locally, then no issue, just set up use_annotation_cache_keys
to false.
If just basic mirror of annotation_cache then use_annotation_cache_keys
should be set to true.
But for now, no other options.
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.
❤️ really nice. I think a few more docs, and the changelog
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.
looks good, just some minor things about the versio
Co-authored-by: Friederike Hanssen <Friederike.hanssen@qbic.uni-tuebingen.de>
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).