Open aaraney opened 3 weeks ago
@hellkite500, what are your thoughts on this?
I think this is reasonable. We would probably want to pass the pattern down to the output hook and let it decide how to handle it, especially the case when the pattern matches more than one file.
https://github.com/NOAA-OWP/ngen-cal/blob/f22302070668bac823b731bd2e05eace32f8f41d/python/ngen_cal/src/ngen/cal/ngen.py#L86
Its not uncommon that software that creates model outputs (e.g.
ngen
ort-route
) names their output files based on factors like the associated nexus or catchmentid
, the current time, or the simulation start time. Often a prefix or suffix is used (e.g.troute_output_{{start_time}}.csv
) with the output format. It would be convenient if a glob star could be provided in the name of therouting_output
field so that you don't have to know a priori the full name of therouting_output
file. For examplerouting_output: troute_output_*.csv
.