Open BioWu opened 6 years ago
Hi there, Thanks for the report. Unfortunately this a database problem and not a RepeatMasker problem. RepeatMasker is designed to merge significantly overlapping fragments of two repeats from the same Class and Subfamily to resolve noisy alignment artifacts. The correct call is highly dependent on the quality of the species database. In this example neither annotation is appears to be correct. The high divergence and the likelihood that this falls within the conserved reverse- transcriptase region of the LINE suggests that this is a bit of an uncharacterized lineage-specific subfamily of the Jockey element. Is the genome you are analyzing perhaps not D_virilis or D_grimshawi ( the species in which these two elements are derived )?
-R
Yes, I applied it in D_melanogaster. But, the question is that the TE reference and aligned regions (in TE) reported in the *.out file were not properly paired. eg. Jockey-3_DGri LINE/Jockey 2774 2863 (12236)
, according to two alignment records the TE fragment aligned was 3207 3426 (1287)
. And this makes me confused. Besides, you said bith of these two alignments were wrong, I think I did not understand this. Did you mean these two alignments (TE fragment annotaions) were not right? I checked and found aligned regions in TART_DV and Jockey-3_DGri consisted of lots of poly CAG/CAA, did you mean that these tandem repeats might lead wrong alignment?
Thanks
Oh yes, that does appear strange. Do you have the *.cat file from this run? I could use that to track down why it used the TART_DV coordinates for the Jockey-3_DGri annotation. Email me at rhubley@systemsbiology.org.
These are both purported to be lineage specific versions of a Jockey in _virilis or _grimshawi. Since they overlap significantly and they are low scoring (but not low enough to be considered a false positive) it leads me to suspect that this is a bit of a Jockey subfamily that doesn't have a good representation (consensus sequence) in the repeat libraries yet. And of course as you point out there is always the chance that this tiny hit is a higher scoring false positive that got through.
-R
Details:
And the corrsponding line out file
As this example illustrates, TE reference and positions of these two closed alignment records were wrongly commbined. I found this bug in both v4.0.6 and this current version. I tried to fix it by myself, but I did found functions as RepeatMasker is one huge project with plenty of scripts.
Hope you could fix it.
Thanks!