DustDead extension ignores USTAR read from meteorology

[yuanjianz]

Your name

Yuanjian Zhang

Your affiliation

WashU

What happened? What did you expect to happen?

USTAR is one of the most significant variables used in DustDead dust emission. Currently, DustDead is calculating its own friction velocity WND_FRC from reference wind at 10m with a reference roughness length.

HEMCO/src/Extensions/hcox_dustdead_mod.F

Lines 1482 to 1497 in 3bd40ad

	!=================================================================
	! Surface exchange properties over erodible surfaces
	! DO NEED THIS: Compute Monin-Obukhov and Friction velocities
	! appropriate for dust producing regions.
	!
	! Now calling Stripped down (adiabatic) version tdf 10/27/2K3
	! rgh_mmn_mbl parameter included directly in blm_mbl
	!=================================================================
	CALL BLM_MBL(
	& HcoState,
	& FLG_MBL_SLICE, ! I [flg] Mobilization candidate flag
	& RGH_MMN, ! I [m] Roughness length momentum, Z0,m
	& WND_RFR, ! I [m s-1] 10 m wind speed
	& MNO_LNG, ! O [m] Monin-Obukhov length
	& WND_FRC,
	& RC ) ! O [m s-1] Surface friction velocity, U*

HEMCO/src/Extensions/hcox_dustdead_mod.F

Lines 2707 to 2709 in 3bd40ad

	! Roughness length momentum for erodible surfaces [m]
	! MaB95 p. 16420, GMB98 p. 6205
	REAL*8, PARAMETER :: RGH_MMN_MBL = 100.0d-6

USTAR and Z0 read from meteorology is only read but ignored in following calculation.

HEMCO/src/Extensions/hcox_dustdead_mod.F

Lines 1467 to 1480 in 3bd40ad

	!=================================================================
	! Introduce Ustar and Z0 from GEOS data
	!=================================================================
	DO I = 1, HcoState%NX
	! Just assign for flag mobilisation candidates
	IF ( FLG_MBL_SLICE(I) ) THEN
	WND_FRC_GEOS(I) = ExtState%USTAR%Arr%Val(I,LAT_IDX)
	Z0_GEOS(I) = ExtState%Z0%Arr%Val(I,LAT_IDX)
	ELSE
	WND_FRC_GEOS(I) = 0.0D0
	Z0_GEOS(I) = 0.0D0
	ENDIF
	ENDDO

Is there any historical reason for not using USTAR directly from GMAO, or is it just a bug?

What are the steps to reproduce the bug?

N/A

Please attach any relevant configuration and log files.

No response

What HEMCO version were you using?

3.9.0

What environment were you running HEMCO on?

Local cluster

What compiler and version were you using?

gcc 10.2.0

Will you be addressing this bug yourself?

Yes

In what configuration were you running HEMCO?

Standalone

As what resolution were you running HEMCO?

all

What meterology fields did you use?

Other (please explain in additional information section below)

Additional information

All meterology fields

[yantosca]

See comments on PR #279