Consider using a class or decorators to manage the workflow of each operation (function)

[agstephens]

We can see from clisops.ops.subset::subset that most of the workflow will be independent of the actual operation:

clisops/clisops/ops/subset.py

Line 53 in ffeb599

def subset(

The differences are:

• input arguments
• mapping those arguments
• calling the actual operation(s) - from clisops.core.*

Would it make sense to create a class that worked through the stages?

1. validate/parse inputs
2. map args
3. call operation
4. get outputs

The latter, get_outputs could, in turn, be a class that brings together:

• file-naming
• format management
• time-splitting
• output file/object generation

The clisops.ops.subset could then be a class or function with dectorators:

@validate_ds
def subset(ds, .....):
      mapped_args = utils.map_params(...)
      ds = clisops.core.subset(ds, ...)
      
      output_handler = OutputHandler(ds, ...)
      return output_handler.get_outputs()

NOTE: we also need to simplify, or find a way to remove: clisops.ops.subset::_subset

[agstephens]

Implemented with op_average branch.