Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem with mule validation of ESM1.5 river model fields #8

Open
MartinDix opened this issue Oct 29, 2024 · 2 comments
Open

Problem with mule validation of ESM1.5 river model fields #8

MartinDix opened this issue Oct 29, 2024 · 2 comments

Comments

@MartinDix
Copy link
Contributor

MartinDix commented Oct 29, 2024

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?

@MartinDix
Copy link
Contributor Author

MartinDix commented Oct 29, 2024

For river fields mule sets

            lon_start_exp = 0.5
            lat_start_exp = -89.5
            n_row_exp = 180
            n_col_exp = 360
            lon_spacing_exp = 1.0
            lat_spacing_exp = 1.0

However in ESM1.5 the river grid latitudes are reversed. It's this that causes the validation failure rather than the spacing.

leoberhelman added a commit that referenced this issue Oct 31, 2024
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
leoberhelman added a commit that referenced this issue Nov 4, 2024
I have made some adjustments to convert to using mule. Note that this implementation still will not work till Issue #8 is solved
@MartinDix
Copy link
Contributor Author

Demo of a brute force override of the mule validation e7af97d

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant