-
Notifications
You must be signed in to change notification settings - Fork 112
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
Pangenome from draft assemblies #1552
Comments
And one quick additional comment. My understanding of progressive is that it works well even when lower quality assemblies are included in the dataset. But, I'm cautious to interpret this as meaning that a dataset comprised entirely of 'fragmented' assemblies will render a good result. The vcf output with minigraph is also useful because it's easy to weed out any SVs that don't have high alignment scores. Curious of your thoughts. Thanks again, Maggs |
I think you've outlined all the points
In both cases, the alignment quality will only be as good as the input data. I guess you can try the |
Thanks Glenn. If you’re curious, I’ll let you know how it turns out .
Maggs X
they/them
…________________________________
From: Glenn Hickey ***@***.***>
Sent: Tuesday, December 3, 2024 1:39:10 AM
To: ComparativeGenomicsToolkit/cactus ***@***.***>
Cc: maggs-x ***@***.***>; Author ***@***.***>
Subject: Re: [ComparativeGenomicsToolkit/cactus] Pangenome from draft assemblies (Issue #1552)
I think you've outlined all the points
* progressive cactus doesn't require a reference-quality assembly, but you can't use it for genotyping downstream
* minigraph-cactus does require a reference assembly, and you can use the results for genotyping.
In both cases, the alignment quality will only be as good as the input data. I guess you can try the --noSplit option of cactus-pangenome with your data, but I can't guarantee the results will be useful.
—
Reply to this email directly, view it on GitHub<#1552 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A7HSYLWWM6Z54MTNBH2HLVD2DRWI5AVCNFSM6AAAAABS2TXXTSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJRG4YTQOBUGM>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Hi is either progressive cactus or cactus minigraph pangenome appropriate to create a pangenome graph for assemblies that are just short of chromosome level? We'd like to generate a pangenome graph that can be used later to genotype structural variants across more individuals.
I'm inclined to use cactus minigraph instead of progressive because I imagine relying on the highest quality assembly as a reference would be helpful. We do not have a chromosome level reference in this case. Based on the paper and the GitHub, it sounds like sufficiently long scaffolds will still render accurate results. If you have any feedback on how best to troubleshoot let me know. I've debated going with standard read mapping approaches to call structural variants, but this wouldn't be as beneficial downstream.
Thanks for your help,
Maggs
The text was updated successfully, but these errors were encountered: