Skip to content
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

Understanding no secondary cluster in output reports #174

Open
cizydorczyk opened this issue Oct 24, 2024 · 0 comments
Open

Understanding no secondary cluster in output reports #174

cizydorczyk opened this issue Oct 24, 2024 · 0 comments

Comments

@cizydorczyk
Copy link

When running mob-recon with a custom plasmid database, I often get no secondary cluster reported for contigs that are assigned to a primary cluster. In the database (constructed using ~50K plasmids), all plasmid sequences are assigned both a primary and secondary cluster.

This makes me think that this is not an issue with my database.

So, when a contig has only a primary cluster designation, does this mean it is insufficiently similar to any secondary clusters to belong to those clusters? What if I want to know whether two such plasmids are similar to each other (e.g., a new secondary cluster group absent in my database)?

Does mob-recon handle new secondary clusters, assigning them new IDs etc.? Or does it simply ignore them and would require a better db to incorporate them?

Any help in understanding is greatly appreciated.

Thank you,
Conrad

@cizydorczyk cizydorczyk changed the title No secondary cluster reported? Understanding no secondary cluster in output reports Oct 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant