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] Online MEGAN diagnostics not working properly #91

Open
yantosca opened this issue Jul 20, 2021 · 2 comments
Open

[BUG/ISSUE] Online MEGAN diagnostics not working properly #91

yantosca opened this issue Jul 20, 2021 · 2 comments
Labels
category: Bug Something isn't working never stale Never label this issue as stale topic: Diagnostics Pertaining to HEMCO diagnostic outputs topic: HEMCO Extensions Pertaining to HEMCO extensions

Comments

@yantosca
Copy link
Contributor

Dylan Millet wrote:

I am using the online version of the megan emissions and I see that the standard HEMCO emission diagnostics do not work for this configuration.

There is a separate place in the megan module where emissions for some (non-standard) emissions are being saved out via Diagn_Create.

It seemed to me that the most straightforward way to save out the online MEGAN emissions for isoprene and other advected VOCs would be to add in additional calls to Diagn_Create.

However this is complicated by the fact that Diagn_Create is looking for single-precision input and many of the flux variables (e.g., Inst%FLUXISOP) are cast as double precision.

For my purposes I have kludged this by changing the relevant variables in megan_mod to single precision. But in general it might be worth creating an interface for Diagn_Create so that it can accept either sp or dp.

@yantosca yantosca added category: Bug Something isn't working topic: HEMCO Extensions Pertaining to HEMCO extensions labels Jul 20, 2021
@yantosca yantosca added the topic: Diagnostics Pertaining to HEMCO diagnostic outputs label Aug 5, 2021
@stale
Copy link

stale bot commented Sep 4, 2021

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 stale bot added the stale No recent activity on this issue label Sep 4, 2021
@yantosca yantosca added the never stale Never label this issue as stale label Sep 8, 2021
@stale stale bot removed the stale No recent activity on this issue label Sep 8, 2021
@drnimbusrain
Copy link

@yantosca @msulprizio

I have also been having some recent issues using the latest develop branch of the standalone HEMCO MEGANv2.1 extension (https://github.com/geoschem/HEMCO/blob/dev/src/Extensions/hcox_megan_mod.F90) and seemingly the diagnostic outputs for monoterpenes, e.g., MTPA, MTPO, LIMO, and SESQ.

In a test run using MERRA2 driving meteorology, all other MEGAN diagnostic variables (e.g., ISOP, ACET, etc.) seem to have good output data for my test run, but the four lumped monoterpene variables are always set to zero for all hours, with the following warnings in the my attached HEMCO log file:

HEMCO WARNING: Diagnostics counter is zero - return empty array: SESQ_MEGAN
--> LOCATION: DiagnCont_PrepareOutput (hco_diagn_mod.F90)
--- Added diagnostics: SESQ_MEGAN
HEMCO WARNING: Diagnostics counter is zero - return empty array: LIMO_MEGAN
--> LOCATION: DiagnCont_PrepareOutput (hco_diagn_mod.F90)
--- Added diagnostics: LIMO_MEGAN
HEMCO WARNING: Diagnostics counter is zero - return empty array: MTPO_MEGAN
--> LOCATION: DiagnCont_PrepareOutput (hco_diagn_mod.F90)
--- Added diagnostics: MTPO_MEGAN
HEMCO WARNING: Diagnostics counter is zero - return empty array: MTPA_MEGAN
--> LOCATION: DiagnCont_PrepareOutput (hco_diagn_mod.F90)

I also attach my HEMCO_sa MEGANv2.1 configuration files for this run.

HEMCO.log
HEMCO_Config.txt
HEMCO_sa_Diagn.txt
HEMCO_sa_Grid.txt
HEMCO_sa_Spec.txt
HEMCO_sa_Time.txt

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 never stale Never label this issue as stale topic: Diagnostics Pertaining to HEMCO diagnostic outputs topic: HEMCO Extensions Pertaining to HEMCO extensions
Projects
None yet
Development

No branches or pull requests

2 participants