Frequency field cannot be reliably inferred from filename

[aidanheerdegen]

The frequency encoded in the filename of ACCESS-OM3 outputs can be reliably mapped to the relevant schema

ACCESS-NRI/access-om3-configs#374 (comment)

But the same is not true for ACCESS-OM2, and by extension ACCESS-ESM1.5 and ACCESS-ESM1.6, which use 1daily, 1monthly, 1yearly

https://github.com/ACCESS-NRI/access-esm1.6-configs/blob/dev-preindustrial%2Bconcentrations/ocean/diagnostic_profiles/source_yaml_files/diag_table_standard_source.yaml#L80-L88

This means addmeta will need to have a mapping from the filename encoded frequency to the correct schema value.

[aidanheerdegen]

This means addmeta will need to have a mapping from the filename encoded frequency to the correct schema value.

Or ... modify the output filenames to be compliant

[aidanheerdegen]

Or break the processing up into separate steps for each frequency (which is what I decided to do for expediency)