-
Notifications
You must be signed in to change notification settings - Fork 7
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
[Bug]: Update license
attribute in default_metadata.json
(invalid with CMOR) -- actually need to update zppy
version
#243
Comments
@tomvothecoder tracking back the license change: E3SM-Project/CMIP6-Metadata#7 |
The left one matches e3sm_to_cmip/resources/default_metadata.json and the right one matches zppy/templates/e3sm_to_cmip/default_metadata.json. I provided direct hyperlinks to both. I think you're saying e3sm_to_cmip (left) is up-to-date, but that is the one failing with my run script. I am using these paths with the latest dev environment that includes CMOR_TABLES_DIR = "/lcrc/group/e3sm/diagnostics/cmip6-cmor-tables/Tables"
INPUT_DIR = "/lcrc/group/e3sm/ac.zhang40/zppy_test_complete_run_output/test-main2-20240216/v2.LR.historical_0201_try7/post/lnd/180x360_aave/ts/monthly/2yr"
OUTPUT_PATH = "/home/ac.tvo/E3SM-Project/e3sm_to_cmip/scripts/debug/549_zppy_ts"
# Fails with this path
METADATA_PATH = "/home/ac.tvo/E3SM-Project/e3sm_to_cmip/e3sm_to_cmip/resources/default_metadata.json"
# Succeeds with this path
# METADATA_PATH = "/home/ac.tvo/E3SM-Project/zppy/templates/e3sm_to_cmip/default_metadata.json" |
I'll do a git pull on EDIT: Nevermind I can't do a git pull on this repo because it is owned by Xylar. I'll try a local copy of the latest version. |
My findings:
|
Thanks for clarifying. It seems like the timing to update 1, and 3 could be tricky. I suppose we should update 1 first, and then update 3 once e3sm_unified is deployed with latest zppy? |
license
attribute in default_metadata.json
(invalid with CMOR)license
attribute in default_metadata.json
(invalid with CMOR) -- actually need to update zppy
version
We can do this after the next E3SM-Unified release to avoid any additional headaches. 1 and 3 need to be updated at the same time. The latest version of This issue can be transferred over to |
What happened?
The
license
attribute is considered invalid with CMOR now.There is a difference between the
default_metadata.json
ofe3sm_to_cmip
(left) andzppy
(right):I ran e3ms_to_cmip with both versions of that file. The
e3sm_to_cmip
version fails because of thelicense
attribute being considered invalid withcmor.write
, while thezppy
version succeeds.What did you expect to happen? Are there are possible answers you came across?
Update the
license
attribute to match zppy's version.Minimal Complete Verifiable Example (MVCE)
Relevant log output
Anything else we need to know?
No response
Environment
Latest version of e3sm_to_cmip and
master
branchThe text was updated successfully, but these errors were encountered: