[QUESTION] How to define new Extension number in HEMCO for online emission calculation

[debatoshpartha]

Description of the Issue:

When we perform online emission calculation in HEMCO (like lightnox), there are different ExtNr defined in HEMCO_Config.rc file those are also included in HEMCO_Diagn.rc. My question is, are the ExtNr arbitrary or there is a module that we can use to define new extension number?

For the first possibility (that the ExtNr are arbitrary), I have tried defining my ExtState collection of hcox_state_mod.F90 in HEMCO_Config.rc file with the ExtNr 132 (see below) and also included it in HEMCO_Diagn.rc file as well (attached) but HEMCO is not picking up my newly written HEMCO extension code (for emission calculation) associated with this ExtNr and the diagnostic output is coming out as zero. Am I missing something?

[yantosca]

Thanks for your patience @debatoshpartha. We are a little bit swamped on this end trying to get the 14.0.0 release out.

Extension numbers in HEMCO are local to the HEMCO_Config.rc file that you are using. So they are arbitrary. As long as you don't define more than one extension with the same number in the same HEMCO_Config.rc file it should be fine.

I would start with setting verbose:3 warnings:3 in your HEMCO_Config.rc file and that should tell you if diagnostics are getting populated. You might also want to take a look at some of the other extensions as well. I think you will need to make sure the extensions are added to the HEMCO state object (HcoState) so that emissions can be updated.

Also tagging @msulprizio @Jourdan-He @SaptSinha.

[debatoshpartha]

Hello Mr. @yantosca and all, the XNOx extension was defined in HEMCO state object (HcoState) and is included in the HEMCO_Config.rc file as well. I have tried to set verbose:3 warnings:3 but the simulation doesn't go through and stops at the below step. What can I do in this situation?

********************************************
* B e g i n   T i m e   S t e p p i n g !! *
********************************************

---> DATE: 2014/01/03  UTC: 00:00  X-HRS:      0.000000
 HEMCO already called for this timestep. Returning.
===============================================================================
TPCORE_FVDAS (based on GMI) Tracer Transport Module successfully initialized
===============================================================================
HEMCO (VOLCANO): Opening /wsu/home/groups/yhgroup/ExtData/HEMCO/VOLCANO/v2019-08/2014/01/so2_volcanic_emissions_Carns.20140103$
--- Initialize surface boundary conditions from input file ---

(I have followed lightnox module to include a new source emission of NOx and attaching the new hemco extension code here)

hcox_emisx_mod.txt

[stale[bot]]

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 Stale bot from closing this issue.

[stale[bot]]

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 Stale bot from closing this issue.

[msulprizio]

Hi @debatoshpartha. Were you able to resolve this?

[stale[bot]]

Closing due to inactivity