-
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
FIX: Remove use_annotation_cache_keys params #1298
Conversation
|
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.
Unfortunately, still doesn't work for me, see posts on Slack:
The following cmd fails because of the hardcoding of the Sarek version number to 3.3.0 I get However, I get the same error when running the command from the docs on your latest commit:
The command in the docs should probably also include |
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/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.
removed that bit
In
where the version of Sarek is hardcoded to 3.3.0. Could one instead specify There is another command there with By the way, I needed to add |
Good point about the version, I'll update that. For the profile, I'd say it's implied given the previous instructions that you have to use one |
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. but why remove -profile
?
@@ -962,7 +962,7 @@ aws s3 --no-sign-request ls s3://annotation-cache/vep_cache/ | |||
|
|||
Since both Snpeff and VEP are internally figuring the path towards the specific cache version / species, `annotation-cache` is using an extra set of keys to specify the species and genome build. | |||
|
|||
So if you are using this resource, please either set `--use_annotation_cache_keys` to use the AWS annotation cache, or point towards your own cache folder structure matching the expected structure. | |||
Which is handled internally by Sarek. |
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.
music to my user-ears. But what is Which
pointing to?
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.
annotation-cache
is using an extra set of keys to specify the species and genome build.
I felt it was a mess because we have that in some command but not others, so I'd rather remove it everywhere and tell people to use the profile they need |
No description provided.