-
Notifications
You must be signed in to change notification settings - Fork 66
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
open_mdsdataset dimension error #316
Comments
Can you share the code you are using to open the data? |
Sure, it's come up with a few iterations on the basic |
Hi all, I'm having the same issue. If someone has the solution, I'd appreciate hearing it! :) |
Hi @ruth-moorman, does it work if you add the arguments |
Hiya @timothyas sorry for the weird delay here, I ended up not working with that output but am now having the same issue with different output from an LLC540 configuration. Again, the issue is only occurring with 2D variables. In this case I know I should be using So for example I'm calling:
and getting
|
Hi @ruth-moorman, does it work to either not specify |
@timothyas thanks for the suggestion but it doesn't look like it's the i.e. this: |
Hi @ruth-moorman, too bad that wasn't the issue. I'm not really sure what's going on. I cannot reproduce the error using the curvilinear_leman dataset in xmitgcm's test suite. If there's any way you can make the data public, I'd be happy to help you out further. I'm also curious how/why you are using a curvilinear geometry with the llc540 geometry - is the entire model domain on just one of the llc faces? |
Hello!
I'm having an issue loading 2D fields from an LLC270 run.
All 3D variables are loading as expected but the 2D fields are giving the error:
ValueError: dimensions ('time', 'j', 'i') must have the same length as the number of data dimensions, ndim=2
The
.meta
files one these 2D fields look equivalent to that of other runs I have not had issues loading variables from, e.g.,so I am at a bit of a loss as to the issue. I've checked with the person who generated the data there should be only one timestamp (monthly) per
.data
file. Could someone help me understand where thedimensions=('time','j','i')
information is sourced from and whether there is a workaround that can prevent this clash?The text was updated successfully, but these errors were encountered: