How to get mass emissions diagnostic file using in-line biogenic emissions with CMAQv5.4/MEGANv3.2?

CMAQ
1

Hi,

I noticed that we can get BEIS mass emissions diagnostic file with the following setting in the run script when we run CMAQv5.4 using in-line biogenic emissions with BEIS4.

setenv B3GTS_DIAG Y #> BEIS mass emissions diagnostic file [ default: N ] [ default: N ]

I can’t help wondering how to get the same file when we run CMAQ using in-line biogenic emissions with MEGANv3.2.

Thank you very much.

2

Hi Feng,

no, there is no corresponding option to output mass-based diagnostic emission files for the MEGANv3.2 inline option, but you can use DESID to output mole based diagnostic emission files. Please see the discussion in this other thread for further details.

Christian

2 Likes
3

Hi Christian,

Thank you so much for the updates. It is very helpful to get idea how to control diagnostic emission files.

The option ‘COLSUM’ in DESID control file means the summed throughout each vertical column according to Appendix B: Emissions Input and Control in CMAQ User’s Guide. However, biogenic emissions only happen on the surface or the first model layer. Should we use LAYER1 (but it is not shown in your message) or D2 instead? What is difference between 2D and LAYER1? Is the following option correct for biogenic emissions?

Desid_Diag_Fmt_Nml(1) = ‘COLSUM’ ! Options: 2D, 2DCOL, 3D

Thanks.

Feng

4

Hi Feng,

All of these options should give you the same result for biogenics. We updated the names of the options between v5.3 and v5.4 so 2D was updated to LAYER1, and 2DCOL was updated to COLSUM.

I recommend using COLSUM only because it will also give you the total if you happen to use it for a different source that has emissions aloft.

Cheers,
Ben Murphy

1 Like
5

Hi Ben,

I got your point.

Thank you very much for your response and the updates about the options.

Feng

6

Hi Ben,

I submitted a job immediately after received your confirmation about the option of COLSUM. I got the following error message after the model crashed.

  |> Reading Emission Control Namelist:
 +======================================

 Performing Basic Error Checks for Emission Scaling Rules

 ERROR: There was a syntax error reading the number of Diagnostic Rules for
   use by the DESID module. Please check the format of each line for syntax
   errors. The invalid line was likely:
      Desid_Diag_Streams_Nml(1,:)= 'MIOG'                                                                                                                                                                  


 *** ERROR ABORT in subroutine DESID_READ_NAMEL on PE 000
 CMAQ must Crash until you fix Desid_N_Diag_Rules

Please see the settings in my DESID control file as below

&Desid_DiagVars
Desid_N_Diag_Rules = 1 ! Exact Number of Diagnostic Rules Below
Desid_Max_Diag_Streams=20 ! Maximum number of species variables on all rules
! below (do not count expansions)
Desid_Max_Diag_Spec = 80 ! Maximum number of species variables on all rules
! below (do not count expansions)
Desid_Diag_Streams_Nml(1,:)= ‘MIOG’
Desid_Diag_Fmt_Nml(1) = ‘COLSUM’ ! Options: 2D, 2DCOL, 3D
Desid_Diag_Spec_Nml(1,: ) = ‘ALL’

/

7

Hi Feng,

No big deal. You’re missing a couple of key lines. In a new line after the second occurrence of “! below (do not count expansions)”, enter the following lines:

/
&Desid_Diag

That should piece everything together.
Best,
Ben

8

Hi Ben,

Yes, you are right, that error is gone.

But the model is crashed again due to the new error message as below. Note that my WRF run is based on Noah LSM

 *** ERROR ABORT in subroutine BDSNPHRNO on PE 000
 BDSNP Soil NO is only compatible with PX version

WRF outputs using Noah LSM (MCIP output: METCRO2D ) do not include WSAT ( soil saturation from PX LSM). I am wondering if WSAT must be available for both MEGAN and BEIS4 if BDSNP is turned on.

MEGAN 3.2 gives the option of using either the Yienger and Levy approach or the BDSNP approach as it is implemented in CMAQ. However, we have to run WRF with PX_LSM if we wan to use BDSNP approach for calculating soil NO emissions, is that right?

Please see settings in my current CMAQ run script which led to errors above.

setenv PX_VERSION N #> WRF PX LSM
setenv CLM_VERSION N #> WRF CLM LSM
setenv NOAH_VERSION Y #> WRF NOAH LSM

Thank you very much.

9

That PX constraint comes from MEGAN 3.2, but the MEGAN implementation in CMAQ should be able to use NOAH LSM if you comment out these lines in BDSNP_MOD.F

C ! make sure it only runs with PX version
IF( .NOT. PX_LSM ) THEN
MESG = “BDSNP Soil NO is only compatible with PX version”
CALL M3EXIT( PNAME, JDATE, JTIME, MESG, 2)
END IF

This check was left in place pending further testing. The WSAT values are different for NOAH. There is also some inconsistency in the design. PX uses soil moisture for the top 1 cm, while in the NOAH top layer is 10 cm thick. The amount of NO produced by the BDSNP model is dependent on the frequency of drying/wetting in that top layer. The original implementation of BDSNP used 2 cm soil depth from GEOS-Chem, so possibly less pulsing than what you would see with PX but more pulsing than you would get with NOAH.

Proceed with caution and make sure the soil NO emissions look reasonable for your application.

3 Likes
10

Hello Jeff,

Thank you very much for your response and comments about top layer soil moisture required by BDSNP approach. It is interesting. I will get more details about BDSNP scheme. BTW, we use NOAH land surface model in WRF because the model performance is better than other runs with different LSMs.

In order to keep model running with NOAH, we can either comment out lines 192 - 195 in BDSNP_MOD.F according to you suggestion or keep PX_VERSION = Y in run script.

In addition I did not find the logical definition of NOAH_VERSION in BDSNP_MOD.F and megan_hrno_mod.F. I have no idea how NOAH_VERSION Y in run script works.

I will get back to you after I have the model run and get results successfully.

Thank you very much.