Error emission in applying region scaling in emission control file

I am using the twoway coupled model CMAQv5.4 with WRF 4.4. In my simulation, when I apply emission scaling to species (e.g., ACORS) in region ‘shanghai’, the emissions of ACORS in all other regions except shanghai will be zero.

For example , in CMAQ_Control_DESID_saprc07tic_ae7i_aq.nml file:


If I multiply the ACORS emissions for the ‘Shanghai’ region by 0.7, then in my results, the ACORS emissions for all areas outside the ‘Shanghai’ grid will reduce by several orders of magnitude. Unless I create a region label and write it into the file for areas other than Shanghai.

This is my CMAQ_Control_DESID.nml:

This is my log:

Is this a bug? or just my mistake.

Hello,

The behavior you are describing sounds like a bug. If you have a file with a mask variable that is the inverse of your shanghai variable, and referring to this variable accomplishes your intended scaling, then I recommend proceeding with this solution for the time being.

If you have extra time, it would be good to confirm the nature of the possible bug, though. One helpful piece of data would be to output the emission diagnostics for ACORS and verify that the emissions outside Shanghai are shut off when Shanghai is scaled by 0.7.

Best regards,
Ben

Ah yes, thank you for your additional comment:

“I guess I know what happened. I uncomment ‘EVERYWHERE’ region label in my CMAQ_Control_DESID.nml . Due to some reason that I am not figure out, ‘EVERYWHERE’ region label seems have a conflict with EVERYWHERE in CMAQ_Control_DESID_saprc07tic_ae7i_aq.nml . In other words, ‘EVERYWHERE’ region label in CMAQ_Control_DESID.nml covers ‘EVERYWHERE’ in CMAQ_Control_DESID_saprc07tic_ae7i_aq.nml .”

That first line of the Desid_Reg_nml table in CMAQ_Ctonrol_DESID.nml should not be uncommented. Thank you for clarifying and following up. It appears that the code is working as intended.

Best,
Ben

2 Likes

Hi Murphy

My clarification is incorrect. In fact, even if I uncomment the first line, this error still exists. I think this bug does exist.

When I tried to open emission diagnosis, an error occurred while generating the diagnostic file (even if I did not use the emission scaling function, this error still exists). Do these errors indicate an issue with the emission file, even though I was able to successfully run the entire model without scaling.

Error:

     |> EMISSIONS DIAGNOSTIC REPORT:
     ==================================
 
       Diagnostic File:   AG
          Stream Members
               AG                              
          Diagnostic Species
 
       Diagnostic File:   BI
          Stream Members
               BI                              
          Diagnostic Species
 
       Diagnostic File:   DU
          Stream Members
               DU                              
          Diagnostic Species
              ^@^@^@^@^@^@^@^@         
 
       Diagnostic File:   IN
          Stream Members
               IN                              
          Diagnostic Species
               `??#^@^@^@^@            
 
       Diagnostic File:   IN
          Stream Members
               IN                              
          Diagnostic Species
 
       Diagnostic File:   RE
          Stream Members
               RE                              
          Diagnostic Species
              ???#^@^@^@^@          
 
       Diagnostic File:   IN
          Stream Members
               IN                              
          Diagnostic Species
 
       Diagnostic File:   IN
          Stream Members
               IN                              
          Diagnostic Species
 
       Diagnostic File:   TR
          Stream Members
               TR                              
          Diagnostic Species
               `??#^@^@^@^@            
 
       Diagnostic File:   WA
          Stream Members
               WA                              
          Diagnostic Species
 
       Diagnostic File:   IN
          Stream Members
               IN                              
          Diagnostic Species
                `??#^@^@^@^@            
 
       Diagnostic File:   ME
          Stream Members
               ME                              
          Diagnostic Species
 
       Diagnostic File:   LTNG
          Stream Members
               LTNG                            
          Diagnostic Species
 
       Diagnostic File:   SEASPRAY
          Stream Members
               SEASPRAY                        
          Diagnostic Species
      
     "DESID_001" opened as NEW(READ-WRITE )
     File name "/data6/sunzhixu/outdata/2022_aersol/reduction.test/CCTM_DESID1_AG_4.454_YRD04_20220315.nc"
     File type GRDDED3 
     Execution ID "????????????????"
     Grid name "YRD4km"
     Dimensions: 216 rows, 192 cols, 1 lays, 0 vbles
     NetCDF ID:        58  opened as READWRITE           
     Starting date and time  2022074:000000 (0:00:00   March 15, 2022)
     Timestep                          010000 (1:00:00 hh:mm:ss)
     Maximum current record number         0
      
     "DESID_002" opened as NEW(READ-WRITE )
     File name "/data6/sunzhixu/outdata/2022_aersol/reduction.test/CCTM_DESID1_BI_4.454_YRD04_20220315.nc"
     File type GRDDED3 
     Execution ID "????????????????"
     Grid name "YRD4km"
     Dimensions: 216 rows, 192 cols, 1 lays, 0 vbles
     NetCDF ID:        59  opened as READWRITE           
     Starting date and time  2022074:000000 (0:00:00   March 15, 2022)
     Timestep                          010000 (1:00:00 hh:mm:ss)
     Maximum current record number         0
     Error creating netCDF variable DESID_001=/data6
     netCDF error number  -59  processing file "DESID_003"
     NetCDF: Name contains illegal characters


     *** ERROR ABORT in subroutine OPEN_EMISS_DIAG on PE 000 
     Could not create the /data6/sunzhixu/outdata/2022_aersol/reduction.test/CCTM_DESID1_DU_4.454_YRD04_20220315.nc file


     *** ERROR ABORT in subroutine OPEN_EMISS_DIAG on PE 000 
     Could not create the /data6/sunzhixu/outdata/2022_aersol/reduction.test/CCTM_DESID1_DU_4.454_YRD04_20220315.nc file
     Date and time 0:00:00   March 15, 2022 (2022074:000000)

Hello,

Apologies for the delayed response. If you are continuing to struggle with this issue, I think there are some clues in the diagnostic output you provided. It seems like the diagnostic species you have selected in the DESID control file are not being interpreted correctly. This is the direct reason I believe the model is crashing.

If you post your CMAQ_Control_DESID.nml file, we may be able to isolate the issue.

Cheers,
Ben

Hi

It doesn’t matter.The issue of regional emission reduction still exists, but given my time, I did not continue to address it (and the issue about species not being explained ), but ignored this error according to the method I mentioned earlier.

shutiao