Closed dchackett closed 6 years ago
This issue is resolved with the generalized ConfigGenerator and ConfigMeasurement tasks in combination with the scheme of taxis importing the run-specification script. Subclassing is easy, and if a runner is specified in the run-specification script, it will be available to the taxis.
Frequently, one modifies a binary so that it takes slightly different input than usual. Adapting taxi to run such modified binaries is remarkably difficult, and should be much easier for ease of adaptability for different applications. The Task classes do not subclass particularly gracefully.
In particular: adding additional command line arguments requires unpleasantly ad-hoc modifications. Modifying the file naming convention (related to another issue) is remarkably finnicky and more ad-hoc still (although this relates to the larger issue of modularizing file naming conventions).
How can we make it easier to make small adjustments to tasks?
Having Task subclasses inside runner scripts might naturally alleviate the worst of this issue.