You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems no error or warning during the running stage, but the tmp directory still exists after running metaeuk. Is it correct? Or did I do something wrong ?
Context
Providing context helps us come up with a solution and improve our documentation for the future.
Your Environment
Include as many relevant details about the environment you experienced the bug in.
Git commit used (The string after "MetaEuk Version:" when you execute MetaEuk without any parameters):6.a5d39d9
Which MetaEuk version was used (Statically-compiled, self-compiled, Homebrew, etc.): bioconda
*metaeuk 6.a5d39d9 pl5321h6a68c12_3 bioconda
For self-compiled and Homebrew: Compiler and Cmake versions used and their invocation:
Server specifications (especially CPU support for AVX2/SSE and amount of system memory): 374 GB memory, support AVX2
Operating system and version: CentOS 7
The text was updated successfully, but these errors were encountered:
The log indicates that everything is correct. I think we just don't clean up correctly. You can manually delete the TMP directory until we implement something for better cleanup.
Expected Behavior
I suppose that
tmp
directory should be automatically removed after normally running themetaeuk
.Current Behavior
Now, Some
tmp
directory still exists and the results (proteins.faa, codon.fna, gff, tsv
) are separately created.Steps to Reproduce (for bugs)
Please make sure to execute the reproduction steps with newly recreated and empty tmp folders.
UniRef90
protein database:metaeuk
:MetaEuk Output (for bugs)
Please make sure to also post the complete output of MetaEuk. You can use gist.github.com for large output.
Here is the running results:
Here is the running log:
It seems no
error
orwarning
during the running stage, but thetmp
directory still exists after runningmetaeuk
. Is it correct? Or did I do something wrong ?Context
Providing context helps us come up with a solution and improve our documentation for the future.
Your Environment
Include as many relevant details about the environment you experienced the bug in.
*
metaeuk 6.a5d39d9 pl5321h6a68c12_3 bioconda
The text was updated successfully, but these errors were encountered: