I was trying to run this cmd inside my (slurm) script
trf genome.fasta 2 7 7 80 10 50 500 -d -m -h
It was running fine producing output files until it got to the end. It aborted silently without saying what caused the error.
I already asked the sysadmins and they say that do not report any kill signal by the scheduler on that job AND that it must have been the tool itself that generated that exit code and then quit execution.
This genome is giving us trouble. It is an insect. The BUSCOS for the genome are above 95%; however, the BUSCOS for the (BRAKER2) proteins is under 5%. We cannot figure out what is causing this discrepancy. That why we are exploring the possibility of tandem repeats confounding the genome annotation tool.
I was trying to run this cmd inside my (slurm) script
trf genome.fasta 2 7 7 80 10 50 500 -d -m -hIt was running fine producing output files until it got to the end. It aborted silently without saying what caused the error.
I already asked the sysadmins and they say that do not report any kill signal by the scheduler on that job AND that it must have been the tool itself that generated that exit code and then quit execution.
I am attaching the log file of the execution progress slurm-7224411.out.txt
A little bit of background:
This genome is giving us trouble. It is an insect. The BUSCOS for the genome are above 95%; however, the BUSCOS for the (BRAKER2) proteins is under 5%. We cannot figure out what is causing this discrepancy. That why we are exploring the possibility of tandem repeats confounding the genome annotation tool.