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

[BUG/ISSUE]: HEMCO WARNING: Diagnostics counter is zero - return empty array #45

Closed
ZitelyTzompa opened this issue Aug 4, 2020 · 3 comments
Assignees
Labels
category: Bug Something isn't working

Comments

@ZitelyTzompa
Copy link

Describe the bug

When running HEMCO standalone to read hourly emissions, I am getting a warning exactly in the first hour of each month (e.g. 2011-02-01 00:00:00) in HEMCO.log. Is there a way to skip these specific hours?

To Reproduce

I modified HEMCO_sa_Config.rc and HEMCO_Config.rc. Then I run HEMCO as explained below.

Run commands

  1. ./runHEMCO.sh > run.log

Expected behavior

Files with mean-monthly emissions should be produced. However, the emission files are full of zeros.

Error messages

HEMCO WARNING: Diagnostics counter is zero - return empty array: EmisSO2_Anthro
--> LOCATION: DiagnCont_PrepareOutput (hco_diagn_mod.F90)

Required information

Please include the following:

  • HEMCO standalone v2.2.0
    Branch: master
    Commit: Restore fix to hcoio_read_std_mod.F to exit search only if a field is to be interpolated and isn't discontinuous
    Date: Fri Jun 5 10:12:57 2020 -0400

Input and log files to attach

HEMCO_Config_ek_rwc.rc.txt
HEMCO_sa_Config.rc.txt
run.log.rwc.txt
HEMCO.log.rwc.txt

@ZitelyTzompa ZitelyTzompa added the category: Bug Something isn't working label Aug 4, 2020
@ZitelyTzompa
Copy link
Author

Hi HEMCO support team,
I was wondering if you have time to take a look at this problem.
Thanks,
Zitely

@lizziel
Copy link
Contributor

lizziel commented Aug 21, 2020

Hi @Zitely, could you also include your HEMCO_Diagn.rc file? This is the config file that specifies what HEMCO container should be output per diagnostic name. I wonder if the specification of category 2 in your HEMCO_Config_ek_rwc.rc file is not matching up with what is in HEMCO_Diagn.rc. Typically we use category 1 for anthropogenic emissions.

@lizziel lizziel self-assigned this Aug 21, 2020
@ZitelyTzompa
Copy link
Author

Hi @lizziel, thanks so much for your response. You were right! The category in HEMCO_Config did not match the one in HEMCO_Diagn. I changed it in the latter file and worked out perfectly.

Thanks again!!
Zitely

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category: Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants