-
Notifications
You must be signed in to change notification settings - Fork 6
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
why doesn't output directory genbank_genomes
get written to config-specified outdir
#79
Comments
Shouldn't dir `genbank_genomes` be written to `out`?
my naive idea was that they'd probably be things that could be shared
between runs that had different output dirs.
|
hmm I see that logic, but for me, I would make a project dir that I would cd into, then run genome-girst there, with the outdir as |
:) fair. I was thinking of making a cache dir, see #8, that could be shared across projects and/or users... |
vaguely relevant - #9 - we need a way to specify a list of already existing genomes, from genbank and potentially from a private collection, too. |
oooh I love cache dir idea, optionally available by a flag in the config file? like:
or something, and if not set, no cache dir and put everything in |
have run into issue in my snakefile where not having a config-specifiable output dir is causing issues:
I get that its wasteful that this genome would be downloaded twice on the hard drive, but if I could specify the output dir I could work around the above issue |
Fixing in #130 with new config parameter |
using conf file:
Shouldn't dir
genbank_genomes
be written toout
?The text was updated successfully, but these errors were encountered: