-
Notifications
You must be signed in to change notification settings - Fork 192
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
RefGenie - add assets currently used from AWS-iGenomes #1086
Comments
Checking which assets currently available in iGenomes have corresponding recipes available in refgenie.
|
@KevinMenden, I can help put together the refgenie asset recipes for the missing asset types. Where can I find commands used to create these? |
Needs more data than that for Sarek (cf: https://github.com/nf-core/sarek/blob/05194ed421d7fef6b7cef05fe267a95d8ceb4d6c/conf/igenomes.config#L36-L57) |
TODO: Still to add: These can be added as attributes to eg. the Fast file rather than dedicated uploads:
Readme can probably be skipped, as RefGenie hopefully already has enough provenance for assets. |
Split from #592, related directly to #1084
We want to transition away from using AWS-iGenomes to using the central RefGenie server(s) to host reference genome assets for the nf-core pipelines. To do this, we need to make sure that everything we currently have is available on a AWS refgenie server somewhere. Once all assets are mirrored we can do a clean swap in the config.
Going from
igenomes.config
, here is a check-list:Summary of genomes
Detailed version with asset types
From @nsheff:
See also:
The text was updated successfully, but these errors were encountered: