You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@MartinDix I am having a look at where using mule in perturbIC specifically would fail and the error could be caught for if someone doesn't remove the timeseries, with the goal to try to catch the error if someone attempts to use this code with out stripping the timeseries data.
ifile is the rstart file ff = mule.FieldsFile.from_file(args.ifile) for ifield, field in enumerate(ff.fields):
#Find surface temp if field.lbuser4 == 24: print(field.get_data())
The warning is
Incorrect dataset_type (found 1, should be one of (3,))
warnings.warn(msg)
I see that this warning traces back to the same error that Martin got in Issue #8
Currently is producing a validation error attached to Issue #7#8 I have implemented mule here with the intention of adding a pre-step to strip out the time series
When run with /g/data/vk83/configurations/inputs/access-esm1p5/modern/pre-industrial/restart/atmosphere/PI-02.astart-01010101 it removes the timeseries ok but writing the new file fails because of validation of the river fields #8
Mule has problems reading timeseries in fieldsfiles. Would be better to have a separate function to remove these?
Something similar to
um_fields_subset.py
or something mule_based (if the read error can be trapped and handled).The text was updated successfully, but these errors were encountered: