-
Notifications
You must be signed in to change notification settings - Fork 14
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
Assume mesh variables only in mesh file #97
Conversation
TestingThis PR passes PR and cosine_bell suites on chrys with intel-mpi |
I'm curious about the various |
The slightly preferred way to handle scope for an xarray dataset that isn't needed for the full scope of the function or method is something like:
In this case, I don't think we likely want to do that retroactively because it changes a lot of whitespace but I would consider it if it's important to you to have an indication of the scope of |
I'm happy to remove them if they're not necessary |
c00621f
to
7dbf393
Compare
@xylar ds.close gone now. Ready for re-review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wonderful! Thanks for making these changes and testing them thoroughly. This is a good idea for MPAS-Ocean and obviously a necessary change for OMEGA.
Thanks for engaging with my nit-picking on |
For OMEGA, mesh variables will be located in a separate netcdf file from the output. This PR always loads mesh variables from the mesh netcdf (usually
mesh.nc
orculled_mesh.nc
). Some of my changes from the init netcdf to the mesh netcdf file are unnecessary but I think it improves code clarity.Checklist
Testing
comment in the PR documents testing used to verify the changes