-
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
Debug lines found in EDTA.pl #2
Comments
Hi @hsiaopei , Thanks for testing Best, |
Dear @hsiaopei, @gabyrech, and @philippbayer, Thank you for using EDTA. I just finished a major upgrade for the program including fixing the Please kindly let me know if you encounter any other errors. Thank you! Best, |
Thanks for the heads-up Shujun - I just pulled it and turned it on, it's currently running and will probably run for a few days (plant genome) :) |
I've now have had it running for about 24 hours:
currently it's hanging at this step:
and is not consuming memory or CPU, and it hasn't written output in about 12 hours. The last file written was Last output in ragoo.fasta.defalse: Chr0_RaGOO:14387060..14401218 false motif:TGAA TSD:TCAG 14387056..14387059 14401219..14401222 IN:14387558..14400719 0.9779 ? unknown NA 862315 Adjust: NO lLTR: 498 rLTR: 499 Alignment regions: 1, 498, 13661, 14158 LTR coordinates: 14387060, 14387557, 14400720, 14401218 TSD-LTR overlap: 0 Boundary missing: 0 |
Hi Philipp,
This sounds not right for me. If the defalse step was finished, you should
be seeing a pass.list file, otherwise the LTR_retriever program is stuck in
the defalse step. This could happen when the specified cpus are not made
exclusive to the job (other jobs taking a lot of cpu resources), such that
the multithreading module couldn't allocate new threads to tasks. If this
is the case, the only way is to restart LTR_retriever or EDTA.
Best,
Shujun
…On Thu, Jun 20, 2019, 1:52 AM Philipp Bayer ***@***.***> wrote:
I've now have had it running for about 24 hours:
perl EDTA/EDTA.pl -genome ragoo.fasta -threads 15
currently it's hanging at this step:
perl <snip>/EDTA/bin/LTR_retriever/bin/LTR.identifier.pl ragoo.fasta -list ragoo.fasta.retriever.scn -seq ragoo.fasta.retriever.scn.extend.fa -anno ragoo.fasta.retriever.scn.extend.fa.aa.anno -flanksim 60 -flankmiss 25 -flankaln 0.6 -minlen 100 -u 1.3e-8 -threads 15 -blastplus /ws/00089503/anaconda/envs/EDTA/bin/ -motif TCCA TGCT TACA TACT TGGA TATA TGTA TGCA > ragoo.fasta.defalse
and is not consuming memory or CPU, and it hasn't written output in about
12 hours. The last file written was ragoo.fasta.defalse (my input is
ragoo.fasta). Have you observed this before?
Last output in ragoo.fasta.defalse:
Chr0_RaGOO:14387060..14401218 false motif:TGAA TSD:TCAG 14387056..14387059 14401219..14401222 IN:14387558..14400719 0.9779 ? unknown NA 862315
Adjust: NO lLTR: 498 rLTR: 499
Alignment regions: 1, 498, 13661, 14158
LTR coordinates: 14387060, 14387557, 14400720, 14401218
TSD-LTR overlap: 0
Boundary missing: 0
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#2?email_source=notifications&email_token=ABNX4NGVFWHZZQTE55AHIYDP3MSLBA5CNFSM4HS4XUM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYEOUYQ#issuecomment-503900770>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABNX4NCYWK4MNAKDJOQVPQ3P3MSLBANCNFSM4HS4XUMQ>
.
|
Dear All, Sorry for the delay of response. I just push a bulk update to EDTA and have tested it in different servers - it seems to work now. But I have not tested it in macOS, so some tiny differences could cause problems. For testing purposes, please use a small file, ie. 20 Mb, for faster turn around. Please let me know if there are any issues. Best, |
I consider this issue is fixed. Please reopen it if the problem is persistent, or open new issues if you found new problems. Best, |
We tried to run the pipeline using our genome assembly fasta file, xxx.fa. Unfortunately,
the error message showed up "xxx.fa.masked does not contain any sequences!"
What's going on?
Apparently, at line 48 of the code of EDTA.pl , "if (0){", should be changed to "if (1){".
The text was updated successfully, but these errors were encountered: