[WIP] new db download with alpha, ksize considerations #20
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
database info is in
conf/databases.csv
additional configuration info has been added to
conf/defaults.conf
andconf/system.conf
. At some point we should decide which needs to contain db info - really doesn't need to be in both.get_databases.snakefile
has some rules for downloading or linking these files.We can:
a) add
include: get_databases.snakefile
into the mainSnakefile
, to use those rulesb) use new shiny module stuff to import the rules:
b) move all of
get_databases.snakefile
intoSnakefile
.I'd say unless you want to split other things out, maybe we should just do
c
for simplicity. Thoughts @taylorreiter?Also, this is a rather complex way to do it, so the alternative is to just hardcode one database for each alpha/ksize/scaled and call it a day. 🤷🏻♀️