I have been using the 2016v2 modeling platform for all other sectors (using the fy 2023 to represent 2021).
For the ptagfire sector specifically I am running into a speciation cross-reference issue (one of the many similar messages):
WARNING: Speciation profile " 95797" is not in profiles, but it was assigned
to source:
Region: 000000004003 Plant: AGAZ126109907 Char1: AGAZ126109907 Char2: 0226
Char3: 1261 Char4: 00000000002811020002 SCC: 00000000002811020002 POL: PM2_5
ERROR: No speciation cross-reference available (and no default) for:
Region: 000000004003 Plant: AGAZ126109907 Char1: AGAZ126109907 Char2: 0226
Char3: 1261 Char4: 00000000002811020002
SCC: 00000000002811020002 POL: PM2_5
It seems that the scc/region/pollutant combinations in the 2021 inventory files are not present in the the gsref file from the 2016v2 platform that I was using:
(gsref_ptagfire_cmaq_cb6ae7_2016fj_16j_nf.txt), which I think makes sense.
I next tried the gsref file (and invtable file) from the 2021 platform:
gsref_ptagfire_cmaq_cb6ae7_2021hb_cb6_21k_10nov2023.txt
invtable_2017_NATA_CMAQ_26apr2023_v7.txt
But, I get many similar messages:
WARNING: Speciation profile " 95809" is not in profiles, but it was assigned
to source:
Region: 000000004003 Plant: AGAZ126109907 Char1: AGAZ126109907 Char2: 0226
Char3: 1261 Char4: 00000000002811020002 SCC: 00000000002811020002 POL: PM2_5
ERROR: No speciation cross-reference available (and no default) for:
Region: 000000004003 Plant: AGAZ126109907 Char1: AGAZ126109907 Char2: 0226
Char3: 1261 Char4: 00000000002811020002
SCC: 00000000002811020002 POL: PM2_5
The gspro file I have been using is:
gspro_SAPRC07TC_AE7_SPECIATE_5_1.txt
Should I be using different files or is there a suggested work-around?
I am getting a ‘Server Not Found’ message for the 2021 package link you sent, but the folder name with the files I downloaded previously matches, so I think I was using the indicated gsref file (gsref_ptagfire_cmaq_cb6ae7_2021hb_cb6_21k_10nov2023.txt).
For the warning messages, that means the profile is not in my gspro file (gspro_SAPRC07TC_AE7_SPECIATE_5_1.txt), right? I could potentially substitute an alternative profile?
But for the error message, this indicates that the scc/region/pollutant combinations in the 2021 inventory files are not present in the the gsref file (gsref_ptagfire_cmaq_cb6ae7_2021hb_cb6_21k_10nov2023.txt), right? Or could it be some other issue?
Profile 95809 was added in SPECIATE 5.2 and is likely missing from your SPECIATE 5.1 labeled gspro. The recommended option is to run the S2S tool (CMAS: Community Modeling and Analysis System) to get an updated SAPRC gspro using SPECIATE 5.2 or later. The shortcut is to copy the profile from the gspro_ptagfire in the 2021 platform package into your SAPRC gspro.
I think that your gsref is being read correctly. You can verify the profile mapping by looking for the SCC/FIPS/pollutant combo in the text file. This particular profile is mapped at the state level so the FIPS will be “04000”.
I am running into a similar issue with the ptrxfire sector now:
WARNING: Speciation profile " 95861" is not in profiles, but it was assigned
to source:
Region: 000000004001 Plant: SF11E04137099 Char1: SF11C06422459 Char2: 1118
Char3: 228 Char4: 00000000002811015001 SCC: 00000000002811015001 POL: VOC
ERROR: No speciation cross-reference available (and no default) for:
Region: 000000004001 Plant: SF11E04137099 Char1: SF11C06422459 Char2: 1118
Char3: 228 Char4: 00000000002811015001
SCC: 00000000002811015001 POL: VOC
I copied the 95861 profiles from the 2021 ptfire-rx gspro file into my SAPRC gspro file, following shortcut solution for the ptagfire sector, but got the errors/warnings below. Should I have also modified the gscnv file (or some other file)?
I am working on getting familiar with and installing the S2S that was recommended, but wanted to ask if there was another quick solution.
I then get the following error (in the smkmerge.point log file):
Value for IOAPI_CHECK_HEADERS not defined;returning default: FALSE
Variable name VNAME3D( 91 ) = "SOAALK" duplicates VNAME3D( 83 ) = "SOAALK" in file "INLNTS_L"
Value for IOAPI_OFFSET_64 not defined;returning default: FALSE
Value for USR_DFLAT_LVL not defined; returning default: 2
Value for COMPRESS_NC not defined;returning default: TRUE
Value for IOAPI_CFMETA not defined;returning default: FALSE
Value for IOAPI_CMAQMETA not defined; returning defaultval ': 'NONE'
Value for IOAPI_CMAQMETA not defined; returning defaultval ': 'NONE'
Value for IOAPI_SMOKEMETA not defined; returning defaultval ': 'NONE'
Value for IOAPI_SMOKEMETA not defined; returning defaultval ': 'NONE'
Value for IOAPI_TEXTMETA not defined; returning defaultval ': 'NONE'
Value for IOAPI_TEXTMETA not defined; returning defaultval ': 'NONE'
Error creating netCDF variable SOAALK
netCDF error number -49 processing file "INLNTS_L"
NetCDF: Variable not found
Could not open file set "INLNTS_L".
*** ERROR ABORT in subroutine OPENMRGOUT
Could not open file set "INLNTS_L".
Earlier in the same log file there are many of these warnings that I don’t think I had seen before:
WARNING: Keep status at line 451 different from previously set status of “N” for CAS “14220178”.
WARNING: Different SPECIATE4 IDs for the same data name at line 352
Using code -9999 and ignoring code 298
WARNING: Different SPECIATE4 IDs for the same data name at line 570
Using code 524 and ignoring code 620
WARNING: Different descriptions for the same data name at line 570 .
Using description:
“M-xylene” and ignoring:
“O-xylene”.