Comments (5)
Hi,
That is a good question. But, this does not necessarily sound like a problem. RepeatModeler processes samples of a particular genome assembly, so it may miss some specific TEs due to "bad luck" or due to limitations in the sequencing or assembly process that make them difficult to recognize. Dfam and RepBase include TE families from ancestral species, which are known from prior research but are too fragmented or mutated to meet RepeatModeler's thresholds. Due to the different limitations of the two approaches, it can be more informative to combine the newly discovered elements into one library as you did.
Does this seem likely to explain the differences in your results?
from tetools.
Hello!
Very happy to receive your reply!
You said that we used the combined collection as the input file. We tried it, and the result was very confusing to me.
We use the combined (cat ) result "the prediction result of RepeatModeler, dfam and repbase" and the result is 44.71% as l said before.
If we first use the prediction result of RepeatModeler to shield the repetitive sequence., and then the shielded sequence again run the set of dfam and repbase the result is 43.64%. We first use the set of dfam and repbase and then run the the prediction result of RepeatModeler, the result is 43.91%.
I would like to ask which method should we use?
The combine is a very confusing place for us. What causes such a deviation?
Looking forward to hearing from you!
from tetools.
The combine is a very confusing place for us. What causes such a deviation?
Running RepeatMasker twice with two different libraries will likely produce different results from running it once with a combined library. For example, the two repeat libraries could include similar but not identical families or fragments of families. In this situation, the first RepeatMasker run might mask most of an element. Then, the second RepeatMasker run might not recognize the leftover part because it is too short. So, each RepeatMasker run can affect the other run depending on the order. If RepeatMasker starts with a combined library instead, it can more effectively discover the elements from both libraries at once.
I would like to ask which method should we use?
The most appropriate method will depend on your goal and how well the RepeatModeler libraries came out for your species. For example, one method might mask more sequence, while another could produce a cleaner annotation with fewer fragments or more well-known names.
I hope this explanation helps you to decide what method to use!
from tetools.
Thank you very much for your valuable advice and patient help.
Your help is really of great significance to our work.
We decided to "combine" it with the method you said.
Maybe this is a more appropriate method.
Sincerely yours
from tetools.
Glad to hear! It seems like this question has been answered, but please re-open this or a new issue if you have more.
from tetools.
Related Issues (20)
- > The combine is a very confusing place for us. What causes such a deviation?
- Feature request: Make the Docker image multi-platform HOT 8
- forksys: Program terminated by a signal 9. HOT 1
- addRepbase.pl: no such file
- reasonaTE "https://github.com/DerKevinRiehl/transposon_annotation_reasonaTE" HOT 1
- hangup error on round5 of RepeatModeler on singularity sif v1.8, v1.85 HOT 1
- Error running repeatmodeler in container HOT 2
- rmblast does not work in new docker image for TETools 1.86. HOT 2
- error of repeatmasker in container HOT 1
- Docker Image Cannot Run LTRStruct pipeline HOT 1
- Customizing RepeatMasker libraries: Absent HOT 2
- Problems configuring RepeatClasifier on docker. HOT 8
- Request: LTR_retriever update from version 2.9.0 HOT 1
- Bump version to 2.0 HOT 1
- Command line fasta file scaffolds_final.fa does not exist! HOT 2
- famdb.py: command not found HOT 2
- Taxonomy::new() needs a path for a famdb directory! HOT 6
- LTRPipeline : Error - could not open clusters.dat! HOT 2
- RepeatModeler BuildDatabase can not open file
- MAFFT failed while running RepeatModeler
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from tetools.