Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an experimental stub for an "all vs all" PAF adapter. It is similar to the normal PAF adapter, except it assumes all refNames are prefixed with a assembly name
All-vs-all PAF can be produced by concatenating multiple genome assemblies into a single FASTA file, and running
A command similar to the above is run by the PGGB workflow as a step (https://github.com/pangenome/pggb)
It is often advisable to include the assembly name in the FASTA file, so there is the PanSN spec that recommends prepending the assembly name (and haplotype number), example tool https://github.com/ekg/fastix
I ran this with about 14 different c.elegans assemblies and results look like this
Potentially this type of workflow can be leveraged to produce multi-way synteny visualizations in a more intuitive way. Instead of a user having to configure A vs B and B vs C manually, it is just known that all comparisons exist, so it can be automatically prepared.
Not all situations have all vs all, but for those that do, this can work