The current implementation of GetBaseCountsMultiSample in the workflow runs one instance for all supplied bam files
To future-proof this against large numbers of input bam files, need to convert this to a scatter step and run each bam fillout individually then merge the results together in a CLI-arg-length safe manner (using pre-exising CWL steps)
Closing this because we are currently utilizing the multi-sample output from the current implementation so maybe we should not change it to a scatter step
The current implementation of
GetBaseCountsMultiSample
in the workflow runs one instance for all supplied bam filesTo future-proof this against large numbers of input bam files, need to convert this to a
scatter
step and run each bam fillout individually then merge the results together in a CLI-arg-length safe manner (using pre-exising CWL steps)