You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was looking at running a GCC model with RCP emissions however these files are not on the WashU data server despite being options in HEMCO_Config. After some searching I found the last model version to reference RCP emissions was 12.9.1 which was a bug fix to keep them working, I also discovered Issue #1847 which states that the RCP data was archived but can be retrieved from a link to Globus endpoint. Following this link leads to a page saying the linked endpoint has been deleted.
#1752 points to CMIP6 SSP scenarios being the future emissions which are being actively maintained and accessible on the Rochester servers.
It looks like the RCP option is now legacy but the HEMCO_Config file generated for run directories (as of 14.4) still contains the extension switches and configurations to use the RCP inventories.
If the RCP emissions are now defunct and SSP is the preferred method, it makes sense to remove the RCP entries from the HEMCO_Config.rc templates, the empty folder on the WashU server and the page on the wiki.
tagging @ltmurray as the future emissions in GEOS-Chem expert
What are the steps to reproduce the bug?
N/A
Please attach any relevant configuration and log files.
No response
What GEOS-Chem version were you using?
14.4
What environment were you running GEOS-Chem on?
Local cluster
What compiler and version were you using?
n/a
Will you be addressing this bug yourself?
No
In what configuration were you running GEOS-Chem?
GCClassic
What simulation were you running?
Full chemistry
As what resolution were you running GEOS-Chem?
4x5
What meterology fields did you use?
MERRA-2
Additional information
No response
The text was updated successfully, but these errors were encountered:
Thanks for pointing this out @r-pound. @yidant are the RCP files still available somewhere at WashU? The globus endpoint that Saptarshi pointed to in #1847 is no longer available.
I will defer to @ltmurray and the Emissions WG chairs (@eamarais, @jaegle, Jintai Lin) on recommendations for removing RCP entries from HEMCO_Config.rc in our next release.
Your name
Ryan Pound
Your affiliation
University of York
What happened? What did you expect to happen?
I was looking at running a GCC model with RCP emissions however these files are not on the WashU data server despite being options in HEMCO_Config. After some searching I found the last model version to reference RCP emissions was 12.9.1 which was a bug fix to keep them working, I also discovered Issue #1847 which states that the RCP data was archived but can be retrieved from a link to Globus endpoint. Following this link leads to a page saying the linked endpoint has been deleted.
#1752 points to CMIP6 SSP scenarios being the future emissions which are being actively maintained and accessible on the Rochester servers.
It looks like the RCP option is now legacy but the HEMCO_Config file generated for run directories (as of 14.4) still contains the extension switches and configurations to use the RCP inventories.
If the RCP emissions are now defunct and SSP is the preferred method, it makes sense to remove the RCP entries from the HEMCO_Config.rc templates, the empty folder on the WashU server and the page on the wiki.
tagging @ltmurray as the future emissions in GEOS-Chem expert
What are the steps to reproduce the bug?
N/A
Please attach any relevant configuration and log files.
No response
What GEOS-Chem version were you using?
14.4
What environment were you running GEOS-Chem on?
Local cluster
What compiler and version were you using?
n/a
Will you be addressing this bug yourself?
No
In what configuration were you running GEOS-Chem?
GCClassic
What simulation were you running?
Full chemistry
As what resolution were you running GEOS-Chem?
4x5
What meterology fields did you use?
MERRA-2
Additional information
No response
The text was updated successfully, but these errors were encountered: