Should I refactor launch functions into single function?

[pbilling]

Current method for adding new bioinformatics (or other) tasks to Trellis is to create a new Cloud Function specifically tailored to launch jobs of that type of task (e.g. "samtools flagstat"). Limitations of generating separate functions for each task include:

• Copying of a lot of boilerplate code across functions
• Potential to differences in boilerplate code across functions
• Changing mechanisms for launching jobs requires changing every launcher function
• Creating a new launcher function is kind of an obtuse process, requiring knowledge of Python and the 'trellisdata' package. If you didn't have an example to look at it, it would be a huge pain.

Can I create a standard function that launches all types of (dsub) jobs, based on a YAML configuration file?

[pbilling]

Yes.

It's worth trying. The amount of work generated by trying to maintain all these different functions is going to keep growing beyond my means and the current model is generally not scalable.