Closed qussai96 closed 6 months ago
Hello @qussai96,
it looks like the slurm job ran out of disk space.
Best, Felix
Thank you @soi for the response. I have an available disk space of 2 terabytes. but it still seems insufficient for Helixer to handle large genomes (exceeding 10 Gb).
best, Qussai
@qussai96 splitting the FASTA into a few parts on chromosome level should be a way to solve the problem.
Best, Felix
Thank you @soi. I am planning to apply this approach and merge the predictions afterwards.
Best, Qussai
Hello @qussai96,
I encountered a similar error once. The disk space in your systems default temporary directory /tmp
is the problem. Helixer creates a few temporary files and a temporary sub-directory in your systems default temporary directory. This default directory has sometimes not enough space for large temporary files. Helixer allows for setting a different temporary directory with --temporary-dir
, if you want to try a different approach without splitting the fasta files.
Best,
Felicitas
Thanks @felicitas215 for the great tip! I will definitely try the --temporary-dir flag.
best, Qussai
Hello @qussai96, I encountered a similar error once. The disk space in your systems default temporary directory
/tmp
is the problem. Helixer creates a few temporary files and a temporary sub-directory in your systems default temporary directory. This default directory has sometimes not enough space for large temporary files. Helixer allows for setting a different temporary directory with--temporary-dir
, if you want to try a different approach without splitting the fasta files. Best, Felicitas
GOAT
Hello,
I am running Helixer on a group of plant genomes. I was able to successfully annotate all of them except three genomes where I had the following error:
The server has plenty of available storage space. Can you please let me know what can cause this issue? And how can I solve it?
Cheers,