Skip to content
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 “KeyError: '.zmetadata'” is reported when running “xmitgcm llcreader demo” #329

Open
Hana0002 opened this issue Oct 18, 2023 · 5 comments

Comments

@Hana0002
Copy link

Hana0002 commented Oct 18, 2023

Dear xmitgcm community and any seniors who might be able to help me~

I am writing to seek assistance with a technical issue I have encountered while running “xmitgcm llcreader demo” with xmitgcm of python and jupyter of vscode.

I downloaded and used the demo you provided, and solved some problems with the package version. But I encountered the error "KeyError: '.zmetadata'". I didn't find a solution on the web. May I ask why this problem occurs? Is it because I'm running in the wrong environment?

I would greatly appreciate any guidance or suggestions you can provide to help me resolve this issue. Here's a screenshot of the errors I got from running the two demos separately.

Thank you in advance for your time and support. A sincere but green graduate student ~>_<~

截屏2023-10-18 17 58 37 截屏2023-10-18 17 58 47
@cspencerjones
Copy link
Contributor

I can confirm that I also get this error message when I try to use the ECCO data portal. It seems to me that this is because the mask data has either moved or disappeared from google cloud. We may be able to host this data elsewhere if I can find a copy. I will talk to @rabernat to see if this can be sorted out.

@rabernat
Copy link
Member

There mask data have not disappeared from google cloud. https://console.cloud.google.com/storage/browser/pangeo-ecco

@cspencerjones
Copy link
Contributor

Ahh ok - my bad. Updating the environment seems to resolve this error.

@auroralin0408
Copy link

I met the same error. What should I upgrade to resolve this error, could you please express more specificly? @cspencerjones

@cspencerjones
Copy link
Contributor

I suggest reinstalling your environment completely, since that is what I did to resolve the error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants