Open mahesh-panchal opened 4 years ago
The include
statement can be included in config files rather than hard coded into the code. This potentially allows for profile specific include
statements. This needs to be tested.
An alternative would be to use a workflow parameter to provide the module path.
Marcs (IKMB) cleaned up code -> DSL2: https://github.com/ikmb/esga
Just to clarify what's in Marc's modules:
If some one with a bit more knowledge could also annotate the new module suggestions with what could be reused from here, it would be appreciated.
nf-core has a #denovohybrid channel where they are building a de novo genome assembly and annotation workflow.
It would be helpful if all stages of genome annotation could be run in a single workflow.
@Juke34 Provided this diagram of how the single workflow might look like.
With the introduction of Nextflow modules, each stage can be built as independent workflows and then imported into a single workflow.
e.g. (note: modules must be locally available).
Part of the suggested workflow proposes to include a part from another workflow: https://github.com/ikmb-denbi/genome-annotation
A collaboration has been suggested, such that we just need to include the proposed part(s) into the single workflow. This requires the ikmb-denbi workflow to be converted to DSL2 and modularized. Together, we need to ensure interoperability between modules. The NBIS annotation workflows are almost complete to be used as modules.
Tasks:
Should training genemark be included into the Abinitio training pipeline?
Which pipeline should the
agat_sp_complement_annotations
process go into?Trinity will be added to the transcript assembly pipeline.