-
Notifications
You must be signed in to change notification settings - Fork 32
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
Read UGRID files with transposed connectivity (i.e. fesom.mesh.diag) #1025
Conversation
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.
Good fix, FESOM stores elements each node is connected to aka adjacency and happy to see that we had the diag file in main for over a year. It wasn't tested.
test/grid_geoflow.exo is removed ? It shouldn't have been there in the first place. Anyways. I'll approve as this will enable newer changes.
Yeah, one of our testing scrips produces the |
One minor thing that could make it good would be to have something about transpose in the README |
Good idea. I'll add a note to it. |
I'm not sure if you've seen this PR, but we've already added and released support for reading the UGRID-compliant FESOM grid files. I haven't followed up with #1013 since merging this. However, I'll work on getting it in soon. |
Sounds good. I haven't been able to get uxarray working for fesom2 netcdf grids from the latest pypi release, but I can from your philipc2/fesom branch. Curious to know the timeline to have these features in the pypi index . |
I'm going to wrap up #1013 this week and aim to release it next week. |
Closes #282 #1026
Overview
fesom.mesh.diag.nc
grid file stores connectivity information in a transpose order ([3, n_face]
instead of[n_face, 3]
Plot of
fesom.mesh.diag.nc