Correct the issue that injection height has been artifically decreased by HEMCO

[jinlx]

Name and Institution (Required)

Name: Lixu Jin
Institution: University of Montana

Describe the update

This update reads injection heights to account for grid-dependent issues in GFAS, as detailed in Jin et al. (2023).

This update also requires that users create the corrected injection height data first, using the code in #2330. A better approach would be to have the data created and placed in the GEOS-Chem data portals for community use.

Expected changes

Correct the issue that injection height has been artifically decreased by HEMCO.

The independent injection height could be further used for other fire inventories.

Reference(s)

Jin, Lixu, et al. "Constraining emissions of volatile organic compounds from western US wildfires with WE-CAN and FIREX-AQ airborne observations." Atmospheric Chemistry and Physics 23.10 (2023): 5969-5991.

Related Github Issue

#2330

[yantosca]

@jinlx: Do you have the injection height files at 0.1 x 0.1 already made?

[jinlx]

@yantosca Apologies for my delayed response—I was traveling last month and wasn’t able to monitor my personal emails effectively. For the inj files, I did not use 0.1x0.1 because HEMCO regrids these as emissions, which could potentially reduce the values artificially. Instead, I generated emission-corrected inj at a nested resolution (25km) for my personal use. I can extend this adjustment to other GEOS-Chem resolutions, such as 0.5x0.65, 2x2.5, and 4x5. This modification would only require a simple edit in the HEMCO_Config.rc.

Change

300 GFAS_EMITL        $ROOT/GFAS/v2018-09/$YYYY/GFAS_$YYYY$MM.nc mami            2003-2023/1-12/1-31/0 C xy m 1

into

300 GFAS_EMITL_weight $ROOT/GFAS/v2024-04/$YYYY/GFAS_$YYYY$MM_hgts_$RES.nc mami_avg_weight 2003-2023/1-12/1-31/0 C xy m 1

[yantosca]

Thanks @jinlx. I was wondering which file to use with this PR. It would be good if we could use the highest resolution file for all cases, if that is possible, as that is the HEMCO philosophy.

[yantosca]

@jinlx: Just checking in on this PR again. We were unsure which resolution file(s) to use with this PR. Can you provide us with the proper file?

[yantosca]

NOTE: This PR affects the GFAS biomass burning which is not enabled in fullchem benchmarks. So we can label this as "no-diff-to-benchmark".

[lizziel]

@jinlx, will be you be able to work on this? We would like to bring this into the model but are waiting for a response (see earlier post from @yantosca).

[jinlx]

I was bad at monitoring github in the past months. Back to questions Bob asked:

I was wondering which file to use with this PR. It would be good if we could use the highest resolution file for all cases, if that is possible, as that is the HEMCO philosophy.

The approach I’ve been using involves having injection files of varying resolutions preloaded in the project storage with resolution-specific filenames. In HEMCO config, I reference a universal variable $RES, which allows flexibility without the need to manually edit configurations for each resolution.

I agree that it will be better to use the highest resolution files. But I am not sure if HEMCO will artificially decrease the inj value again when regriding from high to resolutions. May need a little efforts from people understand both injection and hemco well (?).

Can you provide us with the proper file?

I will provide corrected inj files in standard resolutions, i.g., 2x2.5, 4x5, 0.25x0.3125, and 0.5x0.625 here after AGU, so that people can use it whether if it is implemetned in the future versions.

Again, sorry for not staying on notifications well. I will set up notifications for my school email moving forward so I can respond more promptly.