Using "parsing" feature for filename syntax requires enhancement for optional filename parts.
For instance :
%(variable)s_%(domain)s_%(driving_model)s_%(experiment)s_%(ensemble)s_%(rcm_model)s_%(rcm_version)s_%(time_frequency)s[_%(period_start)s-%(period_end)s].nc
"period_start" and "period_end" do not occur in each filename. Fixed variables don't have period info.
Another example are the "*-start-end-clim.nc" files which are climatological data.
It could be useful to define pyessv template as "{}_{}_{}_[]-[].nc" where "{}" are mandatory parts and "[]" optional ones. This would also take care of the separators just before.
As in the example, this also requires to support several separator types that can occur in the same template.
Using "parsing" feature for filename syntax requires enhancement for optional filename parts.
For instance :
%(variable)s_%(domain)s_%(driving_model)s_%(experiment)s_%(ensemble)s_%(rcm_model)s_%(rcm_version)s_%(time_frequency)s[_%(period_start)s-%(period_end)s].nc
"period_start" and "period_end" do not occur in each filename. Fixed variables don't have period info.
Another example are the "*-start-end-clim.nc" files which are climatological data.
It could be useful to define pyessv template as "{}_{}_{}_[]-[].nc" where "{}" are mandatory parts and "[]" optional ones. This would also take care of the separators just before.
As in the example, this also requires to support several separator types that can occur in the same template.