You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently QC is a separate module.
All assemblies are completed and then the user kicks off QC.
In a DToL pipeline scenario you would likely have some very large genomes mixed in with small ones.
We don't realistically need to wait on the large genomes completing to kick off QC on the small ones.
All we need to do is import the QC module to the Snakemake of the Assembly Module and then there can be a switch which conditionally adds all the targets to the rule all of the assembly module.
This would mean Assembly + QC can be run as if they were one module (by providing a command line flag like --straight-to-qc)
The text was updated successfully, but these errors were encountered:
Currently QC is a separate module.
All assemblies are completed and then the user kicks off QC.
In a DToL pipeline scenario you would likely have some very large genomes mixed in with small ones.
We don't realistically need to wait on the large genomes completing to kick off QC on the small ones.
All we need to do is import the QC module to the Snakemake of the Assembly Module and then there can be a switch which conditionally adds all the targets to the rule all of the assembly module.
This would mean Assembly + QC can be run as if they were one module (by providing a command line flag like --straight-to-qc)
The text was updated successfully, but these errors were encountered: