-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EDTA_raw.pl LINE analysis stalls #504
Comments
Hi, I was able to finish the analysis successfully by running RepeatModeler independently, using recovery mode ( |
Thank you for sharing your experience. I am glad it worked out!
Shujun
…On Thu, Sep 26, 2024 at 11:44 AM afurches ***@***.***> wrote:
Hi, I was able to finish the analysis successfully by running
RepeatModeler independently, using recovery mode (-recoverDir) and by
dramatically increasing the threads over the recommended number (-pa 31). Details
here <#252 (comment)>
.
—
Reply to this email directly, view it on GitHub
<#504 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABNX4NEMGVXAPZP5NLNVSALZYQTUPAVCNFSM6AAAAABOOD6BM2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZXGMZTAMJQGI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
I found the step for LINE was so time-consuming too, it took ~ 27 h in a total run of ~35 h, using version 2.2.2 with --anno 1 and --sensitive 1. The task can be completed successfully, but could this step be further optimized? |
Hi,
I am running
EDTA_raw.pl --type line
and the analysis never finishes. It produced around-6
directory with extensive contents, but I can see that the last time any files were written in the/LINE/
directory was over 10 hours ago. I checked thermod.log
and confirmed round 6 never finished. I also logged into the compute node and usedtop
to see that the programeleredef
is continuously running and using about 13% CPU and RepeatModeler is using about 0.2% memory.I found a few similar reports of stalling on the RepeatModeler github, so the error definitely seems to be with that program, but can't find a solution. The contents of my
rmod.log
are not consistent with this example of a successful run posted by RepeatModeler.Have you seen this before or have any suggestions?
Thanks,
Anna
The text was updated successfully, but these errors were encountered: