You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I used HGTector2 to predict HGTs in my genome, and it classified my genome as "phylum Proteobacteria". The prediction results showed that 318 genes were identified as HGTs, but only 40 of them had a 'TaxID' and were eukaryotes and archaea. The 'TaxID' for 278 genes was 0. Can you help me understand the meaning of this result and the impact on the analysis?
The text was updated successfully, but these errors were encountered:
Hello @chenhuag Thanks for your interest in this program! 318 genes being identified as HGT-derived means that they have an atypical homology search pattern which is likely attributed to HGT. 278 genes having the potential donor identified as TaxID 0 meaning that the potential donor cannot be identified. Since you were examining a very deep taxonomic level (phylum), it could be that the donor information was already lost or attenuated throughout the history of evolution. Hope it helps!
Thank you for your answer. I check the log file and I get a warning message "WARNING: Cannot cluster distal group using KDE. Use fixed threshold 25 instead". Is this related to this result?
Hi,I have a question:when I set up the self- and close- taxa, I found a large number of HGT events were annotated with the source as N/A. Can I assume that a significant portion of these HGT events are very similar to the close- or self- groups we defined, making it difficult to determine their origin?
I used HGTector2 to predict HGTs in my genome, and it classified my genome as "phylum Proteobacteria". The prediction results showed that 318 genes were identified as HGTs, but only 40 of them had a 'TaxID' and were eukaryotes and archaea. The 'TaxID' for 278 genes was 0. Can you help me understand the meaning of this result and the impact on the analysis?
The text was updated successfully, but these errors were encountered: