-
Notifications
You must be signed in to change notification settings - Fork 0
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
very few coresynteny region #14
Comments
Hi Zhigui, nice to see msyd didn't crash on so many genomes :D how long did it run BTW? Weird that msyd seems to find quite some coresynteny in Chr5 but little in Chr1. How does it look in the other chrs? More generally, SyRI/msyd does find synteny even with indels/snps in them (e.g. CORESYN456 in the output above) – in our experience, playing around with minimap2 parameters can help to find somewhat more consistent synteny. LMK if that helps! |
I confirmed with miniprot alignment that at least Chr1 could find many shared core genes. So I think some weird thing happened. It only finds 11Mb sequences across 5 chromosomes. If you take genomes from NCBI public genomes, may could be enough to catch this. I could share you with a link |
Hi, @lrauschning
I tried
msyd
with 279 A.thaliana genomes, but the core synteny region is small. For example, Chr1 only has several regions beginning only in the Chr1:1-200000 and Chr1:2700000-32000000. Would it be possible to lower the threshold? Like any region have SNPs and InDels less than 50 bp still could be coresynteny?By the way, why msyd generate lots of duplicated region with different synID?
The text was updated successfully, but these errors were encountered: