First, thanks for giving us all an avenue beyond the web interface for KO annotations :)
I wanted to suggested adding a check to see if the default ./tmp directory exists before launching a run. This was very much me not paying enough attention and making a silly mistake, but I've been running kofamscan simultaneously for several assemblies called from the same directory for a couple days, and just realized now they were all constantly overwriting the same files in the ./tmp directory, making it all meaningless 😬
It might save someone else from being as silly as I was if when the command is executed the program checked to see if the temporary directory that will be used (whether default or specified by the user) already exists, and if it does, exit and tell the user.
That's a great idea. Is it also possible to add a --force-overwrite option to this? It could be useful to have this start where it left off and also restart if selected.
Hiya!
First, thanks for giving us all an avenue beyond the web interface for KO annotations :)
I wanted to suggested adding a check to see if the default
./tmp
directory exists before launching a run. This was very much me not paying enough attention and making a silly mistake, but I've been running kofamscan simultaneously for several assemblies called from the same directory for a couple days, and just realized now they were all constantly overwriting the same files in the./tmp
directory, making it all meaningless 😬It might save someone else from being as silly as I was if when the command is executed the program checked to see if the temporary directory that will be used (whether default or specified by the user) already exists, and if it does, exit and tell the user.
Just a suggestion, thanks again!