Currently, the assembly workflow presents a "skip_depletion" boolean option to the depletion step that can be a little hard to find for new users (it defaults to false) and incurs some unnecessary wall clock cost anyway (waiting for an instance that simply exits).
Would it be possible to just have the automated build process create a viral-ngs-assembly_Generic_nodeplete workflow as well, that simply starts from filter?
Currently, the assembly workflow presents a "skip_depletion" boolean option to the depletion step that can be a little hard to find for new users (it defaults to false) and incurs some unnecessary wall clock cost anyway (waiting for an instance that simply exits).
Would it be possible to just have the automated build process create a viral-ngs-assembly_Generic_nodeplete workflow as well, that simply starts from
filter?