Pass annotation files to last-dotplot

[charles-plessy]

This adds the capacity to overlay annotations to the dot plots. In the pairgenomealign pipeline, we will use it to indicate genomic regions containing N stretches that typically mark contig boundaries in scaffold assemblies, like the pink lines in the following example:

Details

The annotation of the target (plotted horizontally) genome is passed as a new channel.

The annotation of the query (plotted vertically) genome is passed as a new component of the first channel.

This is because this module typically loops on a list of alignments of various query genomes (from samplesheet) to a single target genome.

The annotation files are called annot_a and annot_b because they are passed to the -a and -b arguments of last-dotplot.

PR checklist

Closes #XXX

• [x] This comment contains a description of changes (with reason).
• [x] If you've fixed a bug or added code that should be tested, add tests!
• [x] If you've added a new tool - have you followed the module conventions in the contribution docs
• [x] If necessary, include test data in your PR.
• [x] Remove all TODO statements.
• [x] Emit the versions.yml file.
• [x] Follow the naming conventions.
• [x] Follow the parameters requirements.
• [x] Follow the input/output options guidelines.
• [x] Add a resource label
• [ x] Use BioConda and BioContainers if possible to fulfil software requirements.
• Ensure that the test works with either Docker / Singularity. Conda CI tests can be quite flaky:
  • For modules:
  • [x] nf-core modules test <MODULE> --profile docker
  • [x] nf-core modules test <MODULE> --profile singularity
  • [x] nf-core modules test <MODULE> --profile conda
  • For subworkflows:
  • [x] nf-core subworkflows test <SUBWORKFLOW> --profile docker
  • [x] nf-core subworkflows test <SUBWORKFLOW> --profile singularity
  • [x] nf-core subworkflows test <SUBWORKFLOW> --profile conda

[charles-plessy]

Good to know, thank you. Do I need to mark the discussion resolved or is it enough that the file was changed in a newer commit ?

[SPPearce]

Good to know, thank you. Do I need to mark the discussion resolved or is it enough that the file was changed in a newer commit ?

As an author, I generally mark the discussions as resolved once I have addressed them, assuming that they are just minor fixes like these. If I want to continue the discussion then I don't.