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

Feature request: Support circular=Y for detecting circularized contigs #151

Open
dfornika opened this issue Sep 11, 2023 · 0 comments
Open

Comments

@dfornika
Copy link
Contributor

dfornika commented Sep 11, 2023

We've been using dragonflye for some hybrid assemblies recently and have noticed a few unexpected results when running mob-recon on the assemblies. In one example, mob-recon included a small (~2kb) contig into the chromosome, despite the assembly including a large circular contig that appeared to be a complete chromosome. It seemed that mob-recon should have recognized the chromosome as being complete/circularized, so it wouldn't make sense to include other contigs into the chromosome reconstruction.

I suspect the reason this is happening is that mob-recon looks for a unicycler-style circularization tag in the fasta headers, which looks like: circular=true. But dragonflye (and presumably flye itself, though I haven't confirmed) add a tag that looks like: circular=Y.

Am I understanding how mob-recon detects circular contigs correctly? Would it be straightforward to support both circular=true and circular=Y? If this isn't straightforward to do in mob-recon then we could make a little sed command that converts circular=Y to circular=true. But other users would need to do the same thing in all of their codebases too, so it seems like a less efficient solution.

@dfornika dfornika changed the title Support circular=Y for detecting circularized contigs Feature request: Support circular=Y for detecting circularized contigs Sep 11, 2023
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