famdef and eleredef steps fail when using the docker image on a Mac about tetools HOT 5 CLOSED

Update:

I am now able to make it to round4 of the RepeatModeler phase, but I still receive an exit code of 1024 as it's running RECON (famdef)

from tetools.

Update:

I successfully installed the same docker image on an Ubuntu virtual machine and it seems to be running well so far (currently on round5). Seems to be a problem unique to Mac maybe??

from tetools.

The second time, after re-running with the -recover_Dir option: "eleredef failed. Exit code 11"

This sounds like a similar problem to this one: Dfam-consortium/RepeatModeler#140 (comment). If you can share with us the seed numbers and source genomes, and/or round- directories from some of the failed RECON runs, that may help us to troubleshoot the problem.

Have you encountered this issue with a Mac? Or is it simply a matter of trying it a couple more times to see if it runs to completion?

This one should (hopefully) not be a Mac or Docker-specific problem, since Docker for Mac runs a full Linux virtual machine. I think this one is more likely to be an environment issue (e.g. low on free memory), and/or bad luck with the chosen seed number and genome samples.

from tetools.

Hi :-)

Thank you for the reply and apologies for the delayed response. As we speak, the Ubuntu version is running smoothly despite having the same settings. The only thing I can think of, is that the parallelisation may have failed for the Mac installation. I unfortunately deleted the files you are asking for as I attempted several rounds of re-running and finally settled on using a VM to set up an Ubuntu machine to run the program. I could try to re-run the Mac version once my analysis on the ubuntu machine finishes (currently at the LTR discovery step with no issues since it started running).

Cheers

from tetools.

I took another look at these errors:

famdef failed. Exit code 1024

I found code in famdef.c that would cause this particular error, and it appears to be a bug in RECON. Re-runs would not be expected to reproduce the error unless the same seed number was used.

The second time, after re-running with the -recover_Dir option: "eleredef failed. Exit code 11"

This one is also likely to be a bug in RECON, although (less likely) it can occur in out-of-memory and similar situations.

If you do reproduce the problem, please file the issue to RepeatModeler, including the genome and seed number and/or the contents of the round- dir that failed.

from tetools.