Closed xinshuaiqi closed 5 years ago
Hi Xinshuai,
Looks like LTR_retriever
was stopped somehow, and the run was not completed. Please rerun it. You may check STDOUT for program status.
Thanks, Shujun
Hi Shujun,
I have a few LAI
jobs always crash. It's hard to track the stdout because I am using AWS cloud. As you may see, my stderr file captured nothing...
I suspect some of the following reasons:
Is it common when you apply LTR-retriever and LAI to many genomes, that many of them will crash?
In cases, when I try to only re-run 'LAI' after 'LTRretriever' fail, I don't see RepeatMasker annotation 'genome.fa.out' in the folder. Is that wired?
Would you mind the explain a little about those Tpases and alluniRefprexp files? I suppose they are temporary process files handling each LTR case. Does that mean in certain specific case, the job encountered some unexpected error, then failed?
In general, I spend 20% time to get 80% jobs done, then have been spending the rest 80% time on debugging the rest 20%...
Your comments are helpful for my debugging. Thanks a lot.
Hi Xinshuai,
This is not common. You may want to check the limit of resource allocation in your AWS nodes. To capture screen output, you can use nohup
, eg. nohup LTR_retriever xxxx > nohup.genome.out
, then you should be able to see what stage the program is stopped. From the files you listed above, the program stopped in stage 2 - identify coding sequences. So you may want to check if hmmsearch
worked properly.
LTR_retriever
will try a couple attempts to fix the long file name issue, and will quit and let you know (stdout
) if it fails to do so. This seems to be not your case.
In some cases, LTR_retriever
do choke and get stuck on the structural analyses, this usually happens when you specify more CPUs than the program can get, or you are running multiple programs that eat up all CPUs, such that LTR_retriever
cannot open new threads because no CPUs are available. In this case, you have to kill and rerun it and make sure you specify the right -t
. In practice, -t 5
works pretty well for the first phase - identification of intact LTR-RT and make a library. But for the second phase, whole-genome LTR annotation, you may want more CPUs for a large genome. You can do this in two steps.
When LTR_retriever
fails, of course you won't be able to run LAI because the dependent files are not generated yet. If you have .LTRlib.fa, you can use it with RepeatMasker
to get the whole genome LTR annotation (.out), then run LAI separately.
Tpases
and alluniRefprexp
are database files for annotation of LTR-RT. They will be deleted after the program finished. Seeing those means your run was not complete.
Thanks, Shujun
hello, I met the same problem. Could you please give me some help. I think my genomic data is not fit for using LAI evaluation, right?
`LAI -genome guatoujing.contig.purged.fa -intact guatoujing.contig.purged.fa.pass.list -all guatoujing.contig.purged.fa.out -q -t 10
######################################
######################################
Developer: Shujun Ou
Please cite:
Ou S., Chen J. and Jiang N. (2018). Assessing genome assembly quality using the LTR Assembly Index (LAI). Nucleic Acids Res. gky730: https://doi.org/10.1093/nar/gky730
Parameters: -genome guatoujing.contig.purged.fa -intact guatoujing.contig.purged.fa.pass.list -all guatoujing.contig.purged.fa.out -q -t 10
Mon Nov 8 10:31:08 EST 2021 Dependency checking: Passed! Mon Nov 8 10:31:08 EST 2021 Calculation of LAI will be based on the whole genome. Please use the -mono parameter if your genome is a recent ployploid, for high identity between homeologues will overcorrect raw LAI scores. Mon Nov 8 10:31:08 EST 2021 Estimate the identity of LTR sequences in the genome: quick mode Mon Nov 8 11:21:33 EST 2021 The identity of LTR sequences: 93.1875177095501% Mon Nov 8 11:21:33 EST 2021 Calculate LAI: 【Error】Intact LTR-RT content (0.09%) is too low for accurate LAI calculation (min 0.1% required) Sorry, LAI is not applicable on the current genome assembly. `
@yuzhenpeng Do you expect lots of LTRs in your genome? If the annotation seems correct, then LAI may not be applicable to your genome. - Shujun
@yuzhenpeng Do you expect lots of LTRs in your genome? If the annotation seems correct, then LAI may not be applicable to your genome. - Shujun
There are some related species have low LTR in their genome,about 4.0~5.5%. Thus, LAI seems not to fit my genome.
Hi Shujun, I have a few runs with normal LTR-retriever.scn outputs, but no LAI report. I noticed there are NO 'out' file from RepeatMasker in the folder. No error message was captured on the std error. Any idea what's the problem?
Below are two examples: