-
Notifications
You must be signed in to change notification settings - Fork 1
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
extra-long incorrect prophage calls #6
Comments
Hi Kathryn, Thanks for opening this issue. I just tested the SEQF1065.1.fna file, and I found the problem. Would it be useful to you if I added a flag to force pruning on DTR sequences? I'm planning some small updates and I believe I can implement this. Let me know, Mike |
Hi Mike, Thank you very much for checking this out and for your quick diagnosis. Yes, it would be fantastic if you could add the option to force a prune on DTR seqs. In the case of SEQF1065.1 we expect to have two 30-40kb prophages predicted on that contig and it will be great to see if the force prune recovers them. Do you have a ballpark sense on timeline for your next planned update? Many thanks! Best, |
Kathryn, I'm happy to help. I would anticipate the update to be live in about 1 week. I know that this doesn't help from a pipeline perspective, but if you are just curious about the few cases you mentioned in your earlier post, you can remove the DTR sequence from the beginning or end of your contigs before feeding it to Mike |
Hi Mike, Great about the timing on the update! We are looking forward to reflecting those changes in our pipeline as well. And thank you for mentioning about trimming the DTRs for seeing what's going on in those cases, makes sense. Thank you! Best, |
Hi Kathryn, I've put a new version I've added the flag Please update to
Let me know if this fixes your issue. Mike |
Hi Mike, |
Kathryn, I'm going to close this issue with the assumption that this new function is working for you. Please reopen it if that's not the case. Best, Mike |
Hi Mike,
Thank you for Cenote-Taker3! We liked Cenote-Taker2 and are excited to explore your update. In our early runs we've noticed some examples of extra-long regions (>2,000,000 bases) being incorrectly called as prophages. In general our runs look reasonable and we haven't yet sorted out why this is happening in some cases. Do you have any insight into what might be going on?
We have v3.3.0 and the updated databases, and are running as:
cenotetaker3 -c $inDIR/$1 -r $modified_base -p T --lin_minimum_hallmark_genes 2 --cpu 6 --cenote-dbs $ct3DBpath
Examples of genomes that yield wonky hits:
https://www.homd.org/ftp/genomes/PROKKA/V10.1/fna/SEQF1065.1.fna
https://www.homd.org/ftp/genomes/PROKKA/V10.1/fna/SEQF9972.1.fna
Any feedback or guidance much appreciated, thank you!
-Kathryn (& looping in @AmrutaIdagunji who is working on this)
The text was updated successfully, but these errors were encountered: