| Workflow-wide node categories | no | *yes* | | | Node priorities on sub-workflows | *yes* | no | | | Reduce memory footprint of large workflows | *yes?* | no | If used properly | -| Per-sub-workflow file final nodes | yes | no | | -| Abort sub-workflows individually | yes | no | | -| Variables associated with sub-workflows | yes | no | | +| Per-sub-workflow file final nodes | *yes* | no | | +| Abort sub-workflows individually | *yes* | no | | +| Variables associated with sub-workflows | *yes* | no | | | Separate configuration for sub-workflows | yes | no | Can be good or bad | -| One node status file, etc., for entire workflow | no | yes | | +| One node status file, etc., for entire workflow | no | *yes* | | *When should I use one of these features?* @@ -40,3 +40,7 @@ The simple answer is that, unless you need one of the features that's available with external sub-DAGs but not with splices, you should use splices. Splices are generally simpler... (add more stuff here) + +*How to use external sub-DAGs to reduce workflow memory footprint* + +(add stuff here)
