-
Notifications
You must be signed in to change notification settings - Fork 0
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
Comments
For river fields mule sets
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
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
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
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/umdir
there 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?
The text was updated successfully, but these errors were encountered: