Description
Is your feature request related to a problem? Please describe.
I am currently using CUPiD for timeseries generation. The flexibility and ease-of-use is awesome, but I can only process a single history file type from a model component at a time (e.g. not both monthly and daily CAM outputs).
Describe the solution you'd like
I have made some minor changes to cupid/run.py that allow users to specify multiple history file strings and data variable lists for each model component (in a config.yml file). I wasn't sure if these changes were compatible with other CUPiD functionality that I haven't used and wanted to check.
Describe alternatives you've considered
It is less convenient but still totally functional to create a config.yml file for each history file type to post-process (e.g. h0, h1, etc).
Additional context
N/A