-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Error when using engine='scipy' reading CM2.6 ocean output #1704
Comments
Can you share an example file? Note that there are some performance improvements for |
Ok I just tried to read the files with the new RC. Same error. here is the output of
and here is an
I am unsure if I am allowed to share them publicly, is there another way to diagnose what is going on? Thanks a lot! |
Can you figure out which variable name it's erroring on? Try dropping into a debugger (e.g., It is not immediately obvious to me what the issue is with this file, but I suspect this is probably a SciPy issue given that |
I believe I solved the issue: It turns out the reason for the slow performance were inconsistencies in between different files (added data_vars and coords). Specifying I am not sure if that is a feasible option, but would it be possible to implement a check for such errors that displays a warning? The error regarding |
In your case, what would that have looked like? Many users have actually requested that xarray provide a more streamlined reader function that does less checking. Perhaps it would have been useful for you to have xarray raise an error when it encountered files that weren't consistent (either in the variable, dimensions, or coordinates)? |
Yes that would be phenomenal. It would be absolutely sufficient for this to be an optional step that needs to be activated with e.g. xr.open_mfdataset(filelist, full_check=True).
In my particular use case I encountered very long load times, and it would be great if in any such problematic cases there would be an easy way to activate a suite of verbose checks to quickly identify problems. For normal use these could be largely deactivated to achieve a fast and streamlined readin?
…Sent from my iPhone
On Nov 21, 2017, at 12:17 AM, Joe Hamman ***@***.***> wrote:
@jbusecke -
... would it be possible to implement a check for such errors that displays a warning?
In your case, what would that have looked like? Many users have actually requested that xarray provide a more streamlined reader function that does less checking. Perhaps it would have been useful for you to have xarray raise an error when it encountered files that weren't consistent (either in the variable, dimensions, or coordinates)?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Closing in favour of #1823 |
Code Sample, a copy-pastable example if possible
gives
xarray version: '0.9.6'
Problem description
I am trying to lazily read in a large number of high resolution ocean model output files. If I omit the
engine='scipy'
it works but takes forever.Is there a known reason why this would fail with the 'scipy' option?
I found #1313, and checked my conda environment:
I can also
import netCDF4
and also load a single file using netCDF, so I am unsure if this is the same error as in #1313I keep getting this error with some of the files for this particular model but not with others.
Any help would be greatly appreciated.
The text was updated successfully, but these errors were encountered: