-
Notifications
You must be signed in to change notification settings - Fork 143
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
Reconsider FieldSet.from_xarray_dataset()
#1940
Comments
FieldSet.from_xarray_dataset()
FieldSet.from_xarray_dataset()
With us moving towards xarray/uxarray adoption, this probably won't be needed. This being said, the assumption that a |
I see. I hadn't used open_mfdataset for combining along non-time dimensions, so I'm not entirely sure how it would work when U and V are stored in separate files. I think that you're right, we can investigate what this would look like v4 |
Documentation suggests that
In the example I wrote (under the "Re-working our example" header), the files that @danliba provided have
|
FieldSet.from_xarray_dataset()
fundamentally works off of the assumption that a single dataset contains all field information, which may not be correct as the field information can be scattered across multiple files which have different dimensions.I'm not sure how useful this abstraction is as a method due to this difference. May be worth considering removing outright, or just clearly documenting that its limited in scope.
Removal can be done at a later stage (removing this method now will just interfere with test cases that currently use it)
The text was updated successfully, but these errors were encountered: