Closed andersgs closed 5 years ago
This is a case I hadn't considered - I'll get this implemented in the near future. The downside to this is that the way ConFindr works now you only ever have to set up a genus-specific database once, but if using a temporary file as the genus-specific database it'll have to get recalculated every time.
Now implemented - ConFindr 0.4.6 has a -tmp
option which allows you to specify a directory to write genus-specific databases to and will get cleaned up at the end of a run (unless you specify the -k
option to keep files). PyPi release has been updated, bioconda recipe will get updated later today.
Thank you @lowandrew. Yes, I was trying to think about how to best get around that issue of recreating it every time. I suppose if the user specifies a directory of their choosing and use the -k
option it could be re-used.
Hi.
I am just trying out
confindr
. In our server setup, we have alinuxbrew
user where we keep all tools for general use by all users (including the DBs). I have installed confindr as that user, and have setup the DB as that user and made sure everyone "knows" where it is by using the CONFINDR_DB env variable.However, when trying to run confindr as myself, I get the following error:
sample_database = os.path.join(databases_folder, '{}_db.fasta'.format(genus))
db_folder = databases_folder if tmpdir is None else tmpdir sample_database = os.path.join(db_folder, '{}_db.fasta'.format(genus))