ERROR: No gridding cross-reference available when run onroad/RPV

SMOKE Run Errors and Warnings
1

Hi all,

When I ran onroad RPV, there was an error below, it may be related with mgref file, but I am not sure how to check if gridding cross-reference is available for some regions.

Any suggestion will be thankful.

File “MGREF” opened for input on unit: 96
…/ge_dat/gridding/mgref_onroad_MOVES3_23sep2021_v1.txt

 Generating unique lists from inventory data...
 Reading gridding cross-reference file...
 Processing gridding cross-reference file...
 Value for FULLSCC_ONLY:  Y returning TRUE
 Reading gridding surrogates header...

 File "SRGDESC" opened for input on unit:  95
 .../ge_dat/gridding/srgdesc_CONUS12_2017NEI_17dec2019_13may2021_v3.txt

 Reading gridding surrogate description file...
 Value for SMK_USE_FALLBACK not defined;returning default:   FALSE
 Value for SMK_DEFAULT_SRGID:  100
 Value for REPORT_DEFAULTS:  Y returning TRUE
 ERROR: No gridding cross-reference available (and no default) for:
      Region: 000000001001 Road Type: 21 Vtype: 2 SCC: 00000000002202210100
 ERROR: No gridding cross-reference available (and no default) for:
      Region: 000000001001 Road Type: 31 Vtype: 2 SCC: 00000000002202310100
 ERROR: No gridding cross-reference available (and no default) for:
      Region: 000000001001 Road Type: 32 Vtype: 2 SCC: 00000000002202320100
2

Hi,

Does anybody have idea about this error?
I tried other version’s mgref, surrogate… files in NEI2017, still not work.

Thank you.

3

What grid are you trying to run for? If it is 12US1 or 12US2, have other programs / processing streams that use surrogates run successfully? This issue could happen if the system could not find the surrogate files in the paths it was searching, as listed in the SRGDESC and/or another variable that says where it should look for the surrogates. Or perhaps if there is a permission problem reading the surrogates.

4

Thank you for this information. Sorry for the late reply.
I used US12KM_444X336. I just tested and got output for rwc and onroad RPH, RPP, RPD.

  1. The paths setting are
    setenv SRGDESC
    …{GE_DAT}/gridding/srgdesc_CONUS12_2017NEI_17dec2019_13may2021_v3.txt"
    setenv SRGPRO
    …{GE_DAT}/gridding/surrogates/CONUS12_2017NEI_04mar2021/USA_100_NOFILL.txt"
    And I double-checked there are those files in these paths.
    2)I used chmod +x -R and chmod -R 755 for the whole folder, still has these errors.
5

We suspect that your setup is a mix of MOVES2014-compatible files/settings and MOVES3-compatible files/settings. This would cause the diesel SCCs, which are part of RPV in MOVES2014 but not in MOVES3, to not be handled properly.

Can you please provide the Smkinven log and their run script? (Even though the error is with Grdmat, we think the cause goes back to Smkinven.)

6

Monthly_onroad_RPV_12US1_2019.csh (8.6 KB)
smkinven_RPV_onroad_nov_2019ge_cb6_19k.log.txt (24.4 KB)
Thank you for this information! I uploaded the smkinven log and run script for RPV

7

yes, they are mixed. So should I replace MOVE3 files with MOVE2014 files from other year’s NEI package?

8

If you are trying to emulate the 2019ge case, keep the MOVES3 files and use the MOVES3-compatible parameters from the 2016fj case / 2016v2 platform scripts. The 2016v2 platform scripts show the right settings to use for MOVES3. The EXCLUDE_REF_SCC_YN setting in particular is what caused this error. (For MOVES2014, this is set to N for RPV, but for MOVES3, it is set to Y for RPV.)

9

I see, thanks a lot for your help!

10

It works, thanks again.

11

Hi Alison,

I found there are zero for NO, NO2 and most species except some VOC species (BENZ, CH4_INV, ETH, ETHA, ETOH,IOLE, ISOP, MEOH,OLE… ) in RPV smoke output. Do you have any idea about the issue?

Thank you in advance.

12

In the latest configuration, RPV only includes evaporative processes while RPS (rate per start) includes processes that would create NOx.

This is why you should use the 2016v2 script configuration rather than 2017NEI, which was based on an earlier version of MOVES.

Have you tried downloading and using the 2016v2 scripts?

13

Yes, I checked most flags, let me replace all flags and try it.
Thank you for your quick reply!

14

I will try to use all onroad scripts in 2016v2 first. Thank you.

15

Please clarify whether you are trying to do a normal AQM-style CAP-focused run for CB6, or if you are trying to do something that includes more toxics pollutants as we would do to support AIrToxScreen.

16

I am trying to do a normal AQM-style CAP-focused run for CB6.

Thank you.

17

We recommend that you use the inputs and parameters from the 2016fj scripts (https://gaftp.epa.gov/Air/emismod/2016/v2/) with the exception of the 2019 activity data, EFTABLES, MCXREF/MFMREF (rep counties), and MRCLIST files which would be substituted with the 2019 versions of those

18

I see, thank you for this detailed information.

20

Sorry, one more error when I ran airport sector in smkmerge_airports_nov_2019ge_cb6_19k_20191124_US12KM_cmaq_cb6ae7.log
There are files in intermed/airports (ptmp_airports_nov_2019ge_cb6_19k_2019328.ncf ~2019334.ncf).
It seems that it can not use right name to find files.

 "PTMP_FRI" opened as OLD:READ-ONLY
 File name "/../smoke2019//2019ge_cb6_19k/intermed/airports/ptmp_airports_nov_2019ge_cb6_19k_2019330.ncf"
 File type GRDDED3
 Execution ID "????????????????"
 Grid name ""
 Dimensions: 62984 rows, 1 cols, 1 lays, 10 vbles
 NetCDF ID:    393216  opened as READONLY
 Starting date and time  2019330:000000 (0:00:00   Nov  26, 2019)
 Timestep                          010000 (1:00:00 hh:mm:ss)
 Maximum current record number        25
 PTMP_SAT        :/../smoke2019//2019ge_cb6_19k/intermed/airports/ptmp_airports_nov_2019ge_cb6_19k_.ncf

 >>--->> WARNING in subroutine OPENSET
 File not available.

 Could not open file set "PTMP_SAT".

 *** ERROR ABORT in subroutine OPENMRGIN
 Could not open file set "PTMP_SAT".

Annual_airports_daily_12US1_2019.csh (7.6 KB)
smkmerge_airports_nov_2019ge_cb6_19k_20191124_US12KM_cmaq_cb6ae7.log.txt (12.9 KB)
Thank you in advance.

21

First we recommend setting EPI_STDATE_TIME back to the original value, which is:

setenv EPI_STDATE_TIME “${BASE_YEAR}-01-01 00:00:00.0”

Even your modeling period starts on 11/24, you should keep EPI_STDATE_TIME set to 1/1, because some of the date settings may not work otherwise. The RUN_MONTHS and SPINUP_DURATION parameters are what should be used to select the time period instead of changing the start date and time.

Also, this may or may not be necessary, but for sectors like airports with representative dates (i.e. where M_TYPE != ‘all’), instead of RUN_MONTHS = 12 and SPINUP_DURATION = 7, we recommend using RUN_MONTHS = “11 12” and SPINUP_DURATION = 0 and just have SMOKE output emissions for all of the representative dates in November.