-
Notifications
You must be signed in to change notification settings - Fork 7
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
fail to predict inserted contamination #11
Comments
We currently predict contamination just for shore sequences of length < 20kb. The 20kb can be in scaffolds or just single sequences. I assume you have just one long sequence? |
@martin-steinegger Is there a way to indicate that contamination should be reported for longer sequences? I'm trying to reproduce the example between C. elegans and E. coli in your ms. |
The
|
There are indeed expected hits in the |
Yes, I agree. I had this on my todo list for quite some time. :( |
Hello!
I did a synthetic genome to check the outputs and the conterminator failed to predict inserted contaminants.
Infos:
Version: 1.c74b5
Organisms in this synthetic genome: Saccharum hybrid cultivar SP80-3280, Klebsiella pneumoniae and Acinetobacter baumannii.
History
I inserted the complete A.baumanii and K.pneumoniae genome into the sugarcane genome and created a kraken mapping file (when I checked the mapping file, I could see the ID taxonomy of the inserted items - A.baumani ID = 470, K.pneumoniae ID = 573 and SP80-3280 ID = 193079).
Then, I ran the conterminator with the following command:
conterminator dna synthetic_genome.fasta kraken_mapping_file.txt synthetic_genome_conterminator tmp
Results
The synthetic_genome_conterminator_conterm_prediction is empty.
The synthetic_genome_conterminator_all don't have informations of the inserted contaminants.
Data
synthetic_genome_conterminator_all.txt
kraken_mapping_file.txt
Genome file is too big and the conterm_prediction is empty.
Problem
My objective is to observe contamination in the sugarcane genome. I'm using the conterminator incorrectly or is the conterminator failing to predict contamination?
The text was updated successfully, but these errors were encountered: