Add CEDS 0.1 x 0.1 degree emissions

[yantosca]

Name and Institution (Required)

Name: Bob Yantosca
Institution: Harvard + GCST

Confirm you have reviewed the following documentation

• Contributing guidelines

Describe the update

This is the companion PR to #1745.

Expected changes

As described in #1745

Related Github Issue(s)

• Closes Adding CEDS at 0.1 degree as a global emission inventory #1745

Tagging @msulprizio

[yantosca]

@1Dandan @Ruijun-Dang: Just wanted to tag #1745 (comment) on this PR. Will await your feedback before proceeding.

[1Dandan]

Hi @yantosca @msulprizio, the seasonality problem as mentioned in #1745 should be fixed in the new version of v2024-06. File names remain the same as those in v2023-04, and thus all v2023-04 can be replaced by v2024-06 for HEMCO_Config.rc and ExtData.rc templates. Let me know if you want other inputs from me.

[1Dandan]

Hi @yantosca, I noticed that the CEDS 0.1 version is still v2023-04, which needs to be changed to v2024-06.
Also, I deleted all files at CEDS/v2023-04 at http://geoschemdata.wustl.edu/ExtData/HEMCO/CEDS/ to avoid any confusion as v2024-06 should be used instead.

[yantosca]

Thanks @1Dandan, yes I just rebased the existing code atop of dev/14.5.0. I'll push another commit to update the directory paths.

[yantosca]

@1Dandan: DIrectory paths updated in commit 91acc1a. Will start integration testing and fix any further issues that arise.

[yantosca]

All GEOS-Chem integration tests passed:

==============================================================================
GEOS-Chem Classic: Execution Test Results

GCClassic #0c22a3a GEOS-Chem submod update: PR #2352 post-merge fix (rebuild KPP files)
GEOS-Chem #769698837 Fix mismatching brackets in HEMCO_Config.rc template
HEMCO     #e68ebae HEMCO 3.9.2 release

Using 24 OpenMP threads
Number of execution tests: 28

Submitted as SLURM job: 43586737
==============================================================================

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%  All execution tests passed!  %%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

[viral211]

Hi @yantosca and @1Dandan, CEDS also identifies their versions with the release date (https://github.com/JGCRI/CEDS/releases) and users can confuse that with the folder names in our CEDS data directory. For example, CEDS had a new version called v_2024_04_01, but I think our folder v2024-06 has CEDS version v_2021_4_21 data. Could we display the CEDS version prominently to avoid any confusion? Thanks.

[1Dandan]

Thanks @viral211 for the suggestion. I agree that it is confusing as our processed version may conflict with the releasing date of the original version. I add a line in the README of This is a seasonality fixed version based on the original released version of v2021_4_21_Release (https://data.pnnl.gov/group/nodes/dataset/13488). Would you @viral211 @yantosca have further suggestions to make it clear?