SMOKE run issues for EPA 2016v1 2028 platform

SMOKE Emissions Inventory
, , ,
1

Hello,
I have installed SMOKE v4.7 using gfortran compiler for a test run. My goal is to get exact same output as EPA for the ‘ptegu_summer’ sector of ‘2028fh1_16j’ case from here ftp://newftp.epa.gov/air/emismod/2016/v1/

Here is what I did:

  1. I downloaded ftp://newftp.epa.gov/air/emismod/2016/v1/smoke_2016v1_platform_core_04feb2020.zip and ftp://newftp.epa.gov/air/emismod/2016/v1/postv1_updates/ptegu_2023_2028/

  2. Then I modified ’ directory_definitions_12US2.csh’ file directory_definitions_12US2.TXT (3.9 KB) from here as my system setup /2028fh1_16j/scripts . I choose ’ 12US2’ directory definitions file because the SMOKE out file for this sector named as inln_mole_ptegu_summer_20160930_12US2_cmaq_cb6_2028fh1_ussa_16j.ncf
    screenshot 1

    Screenshot from 2021-04-08 15-41-45
    Screenshot from 2021-04-08 15-41-45966×162 48.3 KB
    in here ftp://newftp.epa.gov/air/emismod/2016/v1/postv1_updates/ptegu_2023_2028/2028fh1_ptegu_summer_CMAQ_ready.tar.gz

  3. Then I just modified ’ source’ file name as ’ source …/directory_definitions_12US2.csh’ in the /2028/fh1_16j/scripts/point/Annual_ptegu_onetime_summer_12US1_2028fh1_16j.csh and rename it as 'Annual_ptegu_onetime_summer_12US2_2028fh1_16j.csh’Annual_ptegu_onetime_summer_12US2_2028fh1_16j.csh.txt (7.5 KB) .

  4. Then I ran the ‘onetime time script’ from step-3 as mentioned it here to run ‘onetime’ script first ftp://newftp.epa.gov/air/emismod/2016/v1/README_2016_v1_platform_package_14feb2020.txt

  5. Then I followed same procedure for the ‘daily script’ / 2028/fh1_16j/scripts/point/Annual_ptegu_daily_summer_12US2_2028fh1_16j.csh Annual_ptegu_daily_summer_12US2_2028fh1_16j.csh.txt (7.5 KB) and I ran the script.

After finishing the step-5, I see output is generated
screenshot 2

Screenshot from 2021-04-08 15-00-18
Screenshot from 2021-04-08 15-00-181000×161 7.91 KB
which shows the file size are same as EPA outputs(screebshot 1).

Ques: How do I compare if both results are same or not?

Even though I could generate the output (screenshot 2), But I got the following error at the end of the step-5 run:

Classifying message types…
Total number of known messages: 16101
Total number of unknown messages: 5
Level 3 analysis…
Finished classifying message types
log analyzer
**Getting message data (might take some time)… **
grep: /home/Michael/Documents/SMOKE/2016setupEPA/2028fh1_16j/intermed/ptegu_summer/logs: Is a directory
grep: /home/Michael/Documents/SMOKE/2016setupEPA/2028fh1_16j/intermed/ptegu_summer/logs: Is a directory
Finished getting data
Classifying message types…
Total number of known messages: 16101
Total number of unknown messages: 5
Level 1 analysis…
Finished classifying message types
Testing for exit priority <= 1
ERROR: At least one message’s priority is less than or equal to the exit priority: 1
ERROR: Level 1 errors or Level 0 warnings found. Check log files, fix inputs, and rerun.

I checked the log files for level 1 error here /2028fh1_16j/reports/log_analyzer, where I see two level 1 files rep_logs_ptegu_summer_2028fh1_16j_12US2_onetime_level1.csv.txt (2.6 KB) rep_logs_ptegu_summer_2028fh1_16j_12US2_summer_level1.csv.txt (5.7 KB) , and the error messages are
DEFAULT_CONV_FAC_ERROR not defined and Value for SMK_MAXERROR

Would you please help me understanding whether my method is correct and suggest me the ways to solving the error?

Thank you

2

Well, there is one simple brute-force way to see if you are getting either exactly the same thing (which is problematical, given that round-off error is a reality with computer arithmetic), or within tolerances for round-off error: use I/O API M3Tools program m3diff:

  • if the per-timestep root mean square simple difference (“A-B”) is zero, then the data are identical;
  • if the per-timestep root mean square normalized difference ("(A-B)/((A+B)/2)") is less than 1.0e-6, then the files agree to within round-off error tolerances
2 Likes
3

Sorry for the late reply, I have been working with ‘m3diff’ as your suggestions.
so, What does the following error means

ERROR: At least one message’s priority is less than or equal to the exit priority: 1
ERROR: Level 1 errors or Level 0 warnings found. Check log files, fix inputs, and rerun.
The logs file are rep_logs_ptegu_summer_2028fh1_16j_12US2_summer_level1.csv.txt (5.7 KB) rep_logs_ptegu_summer_2028fh1_16j_12US2_onetime_level1.csv.txt (2.6 KB)

The error message in these files are
DEFAULT_CONV_FAC_ERROR not defined and Value for SMK_MAXERROR

4