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

https://github.com/schneebergerlab/plotsr #77

Closed
GallVp opened this issue Nov 30, 2023 · 6 comments · Fixed by #89
Closed

https://github.com/schneebergerlab/plotsr #77

GallVp opened this issue Nov 30, 2023 · 6 comments · Fixed by #89
Milestone

Comments

@GallVp
Copy link
Member

GallVp commented Nov 30, 2023

No description provided.

@GallVp
Copy link
Member Author

GallVp commented Nov 30, 2023

[4:20 pm] Ross Crowhurst
I wouldn't rush to add it since it requires all chromosomes in both genomes to be exact same orientation (and that is never guaranteed so has to be fixed before use in nucmer - most tools do not care - this one doses). It also requires each genome to have same number of chromosomes and not include any contigs. It also requires names to be same eg 'Chr01' as name in both. It also only handles a single genome sequence from each genome and not haplotypes. If haplotypes than each one has to be done pairwise vs all others - so a checker board. So it might be more trouble to add to pipelines than its worth

@GallVp
Copy link
Member Author

GallVp commented Nov 30, 2023

@rosscrowhurst

@rosscrowhurst
Copy link
Collaborator

See https://github.com/schneebergerlab/plotsr for multi-genome (but pairwise) workflow

@GallVp GallVp added this to the 2.0.0 milestone May 3, 2024
@GallVp
Copy link
Member Author

GallVp commented May 3, 2024

Hi @rosscrowhurst

Is this needed after the addition of the linear synteny plot in addition to the circos plot? As you have mentioned in your previous message, it also requires stringent naming convention among other issues.

@rosscrowhurst
Copy link
Collaborator

plotsr has recently been used by others now - for example Sarah Bailey recently used it. IT does a nicer job of displaying inversions, duplications, deletions etc. so it has two foci - one is during assembly to check haplotype assemblies against each other (for example) and one at the end of the assembly to see the differences better between your genome and another. But I am wondering if it needs to be part of assemblyqc automatically as you could not use it unless you had a second genome (say 2 haplotypes) so it would be an optional module at most

@GallVp
Copy link
Member Author

GallVp commented May 27, 2024

Hi @rosscrowhurst

I have added PLOTSR to the dev branch. I'll be testing the pipeline before creating a release. In case you need early access to it, please download the dev branch and try it.

@GallVp GallVp mentioned this issue May 30, 2024
10 tasks
@GallVp GallVp closed this as completed in #89 Jun 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants