With a CM2 restart file mule gives warnings about river fields only if it can't find the STASHmaster file. E.g.
% mule-pumf /g/data/p73/archive/CMIP6/ACCESS-CM2/bi889/restart/atm/bi889a.da10000101_00 > out
/g/data/hh5/public/apps/miniconda3/envs/analysis3-24.04/lib/python3.10/site-packages/mule/stashmaster.py:259: UserWarning:
Unable to load STASHmaster from version string, path does not exist
Path: $UMDIR/vn10.6/ctldata/STASHmaster/STASHmaster_A
Please check that the value of mule.stashmaster.STASHMASTER_PATH_PATTERN is correct for your site/configuration
warnings.warn(msg)
/g/data/hh5/public/apps/miniconda3/envs/analysis3-24.04/lib/python3.10/site-packages/mule/validators.py:198: UserWarning:
File: /g/data/p73/archive/CMIP6/ACCESS-CM2/bi889/restart/atm/bi889a.da10000101_00
Field validation failures:
Fields (731,732,733)
Field grid longitudes inconsistent
File grid : 0.0 to 358.125, spacing 1.875
Field grid: 0.5 to 359.5, spacing 1.0
Extents should be within 1 field grid-spacing
warnings.warn(msg)
After setting UMDIR, export UMDIR=~access/umdir there are no warnings.
However with ESM1.5 these problems persist
% mule-pumf /g/data/vk83/configurations/inputs/access-esm1p5/modern/pre-industrial/restart/atmosphere/PI-02.astart-01010101 > out
Fields (1114,1115,1116)
Field grid latitudes inconsistent (STASH grid: 23)
File : 145 points from -90.0, spacing 1.25
Field (Expected): 180 points from -89.5, spacing 1.25
Field (Lookup) : 180 points from 89.5, spacing -1.0
This will prevent mule writing a file.
Why does mule think the spacing should still be 1.25?
With a CM2 restart file mule gives warnings about river fields only if it can't find the STASHmaster file. E.g.
After setting UMDIR,
export UMDIR=~access/umdirthere are no warnings.However with ESM1.5 these problems persist
This will prevent mule writing a file.
Why does mule think the spacing should still be 1.25?