Requested sample not found in file

[helpyuan]

Your name

liumy

Your affiliation

CAMS

Please provide a clear and concise description of your question or discussion topic.

When I run only CO2 with GCHP-14.4.1, the following error occurs:

I did not make any modifications to TIMES_diurnal_scale_factors.nc in HEMCO_Config.rc and Extdata.rc, and used the default configuration. Please tell me how to solve this problem.

GCHP log files:
allPEs.log.txt
ExtData.rc.txt
gchp.20190701_0000z.log.txt
HEMCO_Config.rc.txt
job.10457479.err.txt

TIMES_diurnal_scale_factors.nc:
TIMES_diurnal_scale_factors.nc.txt

[lizziel]

Hi @helpyuan, thanks for reporting this. This looks like a bug in the ExtData.rc file for carbon. The diurnal scale factor is for one day only, but the config file specifies refresh of F%y4-%m2-%d2T%h2:00:00. Try changing this to F2016-01-01T%h2:00:00 and see if that fixes it. We will put a fix on our end. It looks like the fossil fuel CO2 scale factor for weekly is also problematic.

Tagging @yantosca

[yantosca]

Thanks @lizziel. I'll implement a fix.

[helpyuan]

Thanks @lizziel. After changing to F2016-01-01T%h2:00:00, it can run successfully.

[lizziel]

Also note that the CO2_WEEKLY entry is wrong. It is a day-of-week scale factor file and so needs to have 'D' in the climatology column. We are going to test it out to make sure it works since this application is slightly different than the only other case of using day-of-week scale factors, which has monthly values rather than a single 7-day set for the whole year.

[helpyuan]

Thank you for the reminder @lizziel. Looking forward to your updates!

[lizziel]

I just updated the milestone for this fix to be 14.5.1. @yantosca, I can take care of this when I do other validation work for the carbon simulation in GCHP.

[lizziel]

Update: the diurnal scale factor fix will be in 14.5.0 and @msulprizio is now working on the weekly scale factor fix for release in 14.5.1. There are other fixes for the carbon simulation coming in 14.5.1 so I suggest waiting for that release.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. If there are no updates within 7 days it will be closed. You can add the "never stale" tag to prevent the issue from closing this issue.

[github-actions]

Closing due to inactivity