Hello,
I am trying to run m3diff to compare two files. When I use the command:
m3diff infileA infileB trialfile1 DEFAULT
it gives me a result for option 1: difference A-B
But I want to get output directly using the ‘m3diff’ command for another option
such as for option 13: difference normalized by joint root mean square (A-B)/RMS(A&B),
What should be the command (what replacement I need to make at ’ m3diff infileA infileB filename DEFAULT’ command?
Thanks in advance
From the m3diff splash screen:
USAGE: m3diff [INFILEA INFILEB [REPORTFILE]] [DEFAULT]
(and then answer the prompts).
It is standard usage that items in square-brackets are options which may be omitted, depending upon the functionality desired, just as you’d get for man ls:
…
NAME
ls - list directory contents
SYNOPSIS
ls [OPTION]... [FILE]...
So:
Hello @cjcoats
Thank you for the response. I have tried to run for the (A-B)/RMS, I got the output file and value of (A-B)/RMS for some hours [ for example, in Date and time 2016122:140000 (14:00:00 May 1, 2016)], but I see ‘nowhere defined’ for most of the hours.
What does that mean?
FILE A: infileA (/home/Michael/Documents/SMOKE/ptegu2028EPA/2028fh1_ussa_16j/12US2/cmaq_cb6/ptegu_summer/inln_mole_ptegu_summer_20160501_12US2_cmaq_cb6_2028fh1_ussa_16j.ncf)
FILE B: infileB (/home/Michael/Documents/SMOKE/2016setupEPA/2028fh1_16j/smoke_out/2028fh1_16j/12US2/cmaq_cb6/ptegu_summer/inln_mole_ptegu_summer_20160501_12US2_cmaq_cb6_2028fh1_16j.ncf)
Date and time 2016122:000000 (0:00:00 May 1, 2016)
A:infileA/PNO3 vs B:infileB/PNO3 vs (A - B)/RMS
MAX @( C, R, L) Min @( C, R, L) Mean Sigma
A 1.53403E-01@( 1,5048, 1) 0.00000E+00@( 1, 2, 1) 2.31730E-03 9.71841E-03
B 1.53403E-01@( 1,5048, 1) 0.00000E+00@( 1, 2, 1) 2.31730E-03 9.71841E-03
A:B nowhere defined
Date and time 2016122:010000 (1:00:00 May 1, 2016)
A:infileA/PNO3 vs B:infileB/PNO3 vs (A - B)/RMS
MAX @( C, R, L) Min @( C, R, L) Mean Sigma
A 1.55679E-01@( 1,4677, 1) 0.00000E+00@( 1, 2, 1) 2.26388E-03 9.55581E-03
B 1.55679E-01@( 1,4677, 1) 0.00000E+00@( 1, 2, 1) 2.26388E-03 9.55581E-03
A:B nowhere defined
Date and time 2016122:020000 (2:00:00 May 1, 2016)
A:infileA/PNO3 vs B:infileB/PNO3 vs (A - B)/RMS
MAX @( C, R, L) Min @( C, R, L) Mean Sigma
A 1.52306E-01@( 1,5048, 1) 0.00000E+00@( 1, 2, 1) 2.09591E-03 9.07732E-03
B 1.52306E-01@( 1,5048, 1) 0.00000E+00@( 1, 2, 1) 2.09591E-03 9.07732E-03
A:B nowhere defined
Date and time 2016122:030000 (3:00:00 May 1, 2016)
A:infileA/PNO3 vs B:infileB/PNO3 vs (A - B)/RMS
MAX @( C, R, L) Min @( C, R, L) Mean Sigma
A 1.50989E-01@( 1,5048, 1) 0.00000E+00@( 1, 2, 1) 1.93973E-03 8.71401E-03
B 1.50989E-01@( 1,5048, 1) 0.00000E+00@( 1, 2, 1) 1.93973E-03 8.71401E-03
A:B nowhere defined
Date and time 2016122:040000 (4:00:00 May 1, 2016)
A:infileA/PNO3 vs B:infileB/PNO3 vs (A - B)/RMS
MAX @( C, R, L) Min @( C, R, L) Mean Sigma
A 1.22527E-01@( 1,1186, 1) 0.00000E+00@( 1, 2, 1) 2.31184E-03 8.63564E-03
B 1.22527E-01@( 1,1186, 1) 0.00000E+00@( 1, 2, 1) 2.31184E-03 8.63564E-03
A:B nowhere defined
Date and time 2016122:050000 (5:00:00 May 1, 2016)
A:infileA/PNO3 vs B:infileB/PNO3 vs (A - B)/RMS
MAX @( C, R, L) Min @( C, R, L) Mean Sigma
A 1.19901E-01@( 1,3218, 1) 0.00000E+00@( 1, 2, 1) 2.43350E-03 8.60292E-03
B 1.19901E-01@( 1,3218, 1) 0.00000E+00@( 1, 2, 1) 2.43350E-03 8.60292E-03
A:B nowhere defined
Date and time 2016122:060000 (6:00:00 May 1, 2016)
A:infileA/PNO3 vs B:infileB/PNO3 vs (A - B)/RMS
MAX @( C, R, L) Min @( C, R, L) Mean Sigma
A 1.19901E-01@( 1,3218, 1) 0.00000E+00@( 1, 2, 1) 2.38268E-03 8.47896E-03
B 1.19901E-01@( 1,3218, 1) 0.00000E+00@( 1, 2, 1) 2.38268E-03 8.47896E-03
A:B nowhere defined
Date and time 2016122:070000 (7:00:00 May 1, 2016)
A:infileA/PNO3 vs B:infileB/PNO3 vs (A - B)/RMS
MAX @( C, R, L) Min @( C, R, L) Mean Sigma
A 1.19901E-01@( 1,3218, 1) 0.00000E+00@( 1, 2, 1) 2.39249E-03 8.33209E-03
B 1.19901E-01@( 1,3218, 1) 0.00000E+00@( 1, 2, 1) 2.39249E-03 8.33209E-03
A:B 1.07691E-13@( 1,5144, 1) -1.61536E-13@( 1,3050, 1) 1.54516E-16 5.62495E-15
Date and time 2016122:080000 (8:00:00 May 1, 2016)
A:infileA/PNO3 vs B:infileB/PNO3 vs (A - B)/RMS
MAX @( C, R, L) Min @( C, R, L) Mean Sigma
A 1.19901E-01@( 1,3218, 1) 0.00000E+00@( 1, 2, 1) 2.35877E-03 8.13209E-03
B 1.19901E-01@( 1,3218, 1) 0.00000E+00@( 1, 2, 1) 2.35877E-03 8.13209E-03
A:B 1.28129E-14@( 1, 964, 1) -2.05006E-13@( 1,4573, 1) -5.13213E-16 7.03397E-15
Date and time 2016122:090000 (9:00:00 May 1, 2016)
A:infileA/PNO3 vs B:infileB/PNO3 vs (A - B)/RMS
MAX @( C, R, L) Min @( C, R, L) Mean Sigma
A 1.19901E-01@( 1,3218, 1) 0.00000E+00@( 1, 3, 1) 2.35852E-03 8.04598E-03
B 1.19901E-01@( 1,3218, 1) 0.00000E+00@( 1, 3, 1) 2.35852E-03 8.04598E-03
A:B 2.48843E-14@( 1,6736, 1) -9.95370E-14@( 1,1694, 1) -3.57539E-16 3.42499E-15
Date and time 2016122:100000 (10:00:00 May 1, 2016)
A:infileA/PNO3 vs B:infileB/PNO3 vs (A - B)/RMS
MAX @( C, R, L) Min @( C, R, L) Mean Sigma
A 1.19101E-01@( 1,3218, 1) 0.00000E+00@( 1, 3, 1) 2.40932E-03 8.07130E-03
B 1.19101E-01@( 1,3218, 1) 0.00000E+00@( 1, 3, 1) 2.40932E-03 8.07130E-03
A:B 4.92981E-14@( 1,2571, 1) -4.92981E-14@( 1,3600, 1) 3.88855E-17 2.47441E-15
Date and time 2016122:110000 (11:00:00 May 1, 2016)
A:infileA/PNO3 vs B:infileB/PNO3 vs (A - B)/RMS
MAX @( C, R, L) Min @( C, R, L) Mean Sigma
A 1.22462E-01@( 1,1185, 1) 0.00000E+00@( 1, 3, 1) 2.54976E-03 8.39297E-03
B 1.22462E-01@( 1,1185, 1) 0.00000E+00@( 1, 3, 1) 2.54976E-03 8.39297E-03
A:B 2.02182E-13@( 1,6063, 1) -5.05454E-14@( 1,1096, 1) 6.09208E-16 7.34216E-15
Date and time 2016122:120000 (12:00:00 May 1, 2016)
A:infileA/PNO3 vs B:infileB/PNO3 vs (A - B)/RMS
MAX @( C, R, L) Min @( C, R, L) Mean Sigma
A 1.22321E-01@( 1,1185, 1) 0.00000E+00@( 1, 3, 1) 2.78017E-03 8.85163E-03
B 1.22321E-01@( 1,1185, 1) 0.00000E+00@( 1, 3, 1) 2.78017E-03 8.85163E-03
A:B 1.05633E-13@( 1, 526, 1) -2.11265E-13@( 1,1948, 1) -1.20013E-15 1.25221E-14
Date and time 2016122:130000 (13:00:00 May 1, 2016)
A:infileA/PNO3 vs B:infileB/PNO3 vs (A - B)/RMS
MAX @( C, R, L) Min @( C, R, L) Mean Sigma
A 1.20610E-01@( 1,1186, 1) 0.00000E+00@( 1, 3, 1) 3.00866E-03 9.19386E-03
B 1.20610E-01@( 1,1186, 1) 0.00000E+00@( 1, 3, 1) 3.00866E-03 9.19386E-03
A:B 5.50559E-14@( 1,6065, 1) -2.20224E-13@( 1,1901, 1) -1.40327E-15 1.10704E-14
Date and time 2016122:140000 (14:00:00 May 1, 2016)
A:infileA/PNO3 vs B:infileB/PNO3 vs (A - B)/RMS
MAX @( C, R, L) Min @( C, R, L) Mean Sigma
A 1.20067E-01@( 1,1185, 1) 0.00000E+00@( 1, 3, 1) 3.27775E-03 9.57892E-03
B 1.20067E-01@( 1,1185, 1) 0.00000E+00@( 1, 3, 1) 3.27775E-03 9.57892E-03
A:B 4.59290E-13@( 1,2627, 1) -4.59290E-13@( 1,4573, 1) -8.77645E-16 2.43779E-14
Date and time 2016122:150000 (15:00:00 May 1, 2016)
A:infileA/PNO3 vs B:infileB/PNO3 vs (A - B)/RMS
MAX @( C, R, L) Min @( C, R, L) Mean Sigma
A 1.19901E-01@( 1,3218, 1) 0.00000E+00@( 1, 3, 1) 3.60413E-03 1.00923E-02
B 1.19901E-01@( 1,3218, 1) 0.00000E+00@( 1, 3, 1) 3.60413E-03 1.00923E-02
A:B nowhere defined
Date and time 2016122:160000 (16:00:00 May 1, 2016)
A:infileA/PNO3 vs B:infileB/PNO3 vs (A - B)/RMS
MAX @( C, R, L) Min @( C, R, L) Mean Sigma
A 1.19101E-01@( 1,3218, 1) 0.00000E+00@( 1, 3, 1) 3.91088E-03 1.06102E-02
B 1.19101E-01@( 1,3218, 1) 0.00000E+00@( 1, 3, 1) 3.91088E-03 1.06102E-02
A:B nowhere defined
Date and time 2016122:170000 (17:00:00 May 1, 2016)
A:infileA/PNO3 vs B:infileB/PNO3 vs (A - B)/RMS
MAX @( C, R, L) Min @( C, R, L) Mean Sigma
A 1.19901E-01@( 1,3218, 1) 0.00000E+00@( 1, 3, 1) 4.14485E-03 1.09885E-02
B 1.19901E-01@( 1,3218, 1) 0.00000E+00@( 1, 3, 1) 4.14485E-03 1.09885E-02
A:B nowhere defined
Date and time 2016122:180000 (18:00:00 May 1, 2016)
A:infileA/PNO3 vs B:infileB/PNO3 vs (A - B)/RMS
MAX @( C, R, L) Min @( C, R, L) Mean Sigma
A 1.19901E-01@( 1,3218, 1) 0.00000E+00@( 1, 3, 1) 4.32975E-03 1.12711E-02
B 1.19901E-01@( 1,3218, 1) 0.00000E+00@( 1, 3, 1) 4.32975E-03 1.12711E-02
A:B 2.77111E-13@( 1,1450, 1) -8.31333E-13@( 1, 897, 1) -2.77016E-15 2.86165E-14
Date and time 2016122:190000 (19:00:00 May 1, 2016)
A:infileA/PNO3 vs B:infileB/PNO3 vs (A - B)/RMS
MAX @( C, R, L) Min @( C, R, L) Mean Sigma
A 1.35482E-01@( 1,1193, 1) 0.00000E+00@( 1, 3, 1) 4.46132E-03 1.16030E-02
B 1.35482E-01@( 1,1193, 1) 0.00000E+00@( 1, 3, 1) 4.46132E-03 1.16030E-02
A:B nowhere defined
Date and time 2016122:200000 (20:00:00 May 1, 2016)
A:infileA/PNO3 vs B:infileB/PNO3 vs (A - B)/RMS
MAX @( C, R, L) Min @( C, R, L) Mean Sigma
A 1.38163E-01@( 1,1193, 1) 0.00000E+00@( 1, 3, 1) 4.50789E-03 1.16479E-02
B 1.38163E-01@( 1,1193, 1) 0.00000E+00@( 1, 3, 1) 4.50789E-03 1.16479E-02
A:B nowhere defined
Date and time 2016122:210000 (21:00:00 May 1, 2016)
A:infileA/PNO3 vs B:infileB/PNO3 vs (A - B)/RMS
MAX @( C, R, L) Min @( C, R, L) Mean Sigma
A 1.32423E-01@( 1,1193, 1) 0.00000E+00@( 1, 3, 1) 4.49529E-03 1.16232E-02
B 1.32423E-01@( 1,1193, 1) 0.00000E+00@( 1, 3, 1) 4.49529E-03 1.16232E-02
A:B nowhere defined
Date and time 2016122:220000 (22:00:00 May 1, 2016)
A:infileA/PNO3 vs B:infileB/PNO3 vs (A - B)/RMS
MAX @( C, R, L) Min @( C, R, L) Mean Sigma
A 1.31677E-01@( 1,5048, 1) 0.00000E+00@( 1, 3, 1) 4.40284E-03 1.14851E-02
B 1.31677E-01@( 1,5048, 1) 0.00000E+00@( 1, 3, 1) 4.40284E-03 1.14851E-02
A:B nowhere defined
Date and time 2016122:230000 (23:00:00 May 1, 2016)
A:infileA/PNO3 vs B:infileB/PNO3 vs (A - B)/RMS
MAX @( C, R, L) Min @( C, R, L) Mean Sigma
A 1.38041E-01@( 1,5048, 1) 0.00000E+00@( 1, 3, 1) 4.24098E-03 1.12824E-02
B 1.38041E-01@( 1,5048, 1) 0.00000E+00@( 1, 3, 1) 4.24098E-03 1.12824E-02
A:B nowhere defined
Date and time 2016123:000000 (0:00:00 May 2, 2016)
A:infileA/PNO3 vs B:infileB/PNO3 vs (A - B)/RMS
MAX @( C, R, L) Min @( C, R, L) Mean Sigma
A 1.42430E-01@( 1,5048, 1) 0.00000E+00@( 1, 3, 1) 4.03304E-03 1.11350E-02
B 1.42430E-01@( 1,5048, 1) 0.00000E+00@( 1, 3, 1) 4.03304E-03 1.11350E-02
A:B nowhere defined
Date and time 2016123:010000 (1:00:00 May 2, 2016)
A:infileA/PNO3 vs B:infileB/PNO3 vs (A - B)/RMS
MAX @( C, R, L) Min @( C, R, L) Mean Sigma
“Difference normalized by pointwise mean” is the appropriate measure to see whether these files are the same up to round-off error, not “difference normalized by RMS”.
On the other hand,
suggests that there are NaNs in at least one of the files. What does m3stat say --does it also find NaNs?
Hello @cjcoats
I am not sure what to look at or what command to apply for the ‘m3stat’;
I ran m3stat infileA , and then choose ‘Default Y’ option. Please see the output for both infileA m3stat_infileA.txt (299.7 KB) , NOTE:infileA is the EPA output from 2016v1.
When I run m3stat infileB (infileB is the output from my run), I get the following error:
[Michael@ADEQPlanning Linux2_x86_64gfort]$ echo infileB
/home/Michael/Documents/SMOKE/2016setupEPA/2028fh1_16j/smoke_out/2028fh1_16j/12US2/cmaq_cb6/ptegu_summer/inln_mole_ptegu_summer_20160501_12US2_cmaq_cb6_2028fh1_16j.ncf
[Michael@ADEQPlanning Linux2_x86_64gfort] m3stat infileB
This program uses the EPA-AREAL/MCNC-EnvPgms/BAMS Models-3
I/O Applications Programming Interface, [I/O API] which is
built on top of the netCDF I/O library (Copyright 1993, 1996
University Corporation for Atmospheric Research/Unidata
Program) and the PVM parallel-programming library (from
Oak Ridge National Laboratory).
Copyright (C) 1992-2002 MCNC,
(C) 1992-2018 Carlie J. Coats, Jr.,
(C) 2003-2012 Baron Advanced Meteorological Systems, LLC, and
(C) 2014-2020 UNC Institute for the Environment.
Released under the GNU LGPL License, version 2.1. See URL
https://www.gnu.org/licenses/old-licenses/lgpl-2.1.html
for conditions of use.
ioapi-3.2: $Id: init3.F90 185 2020-08-28 16:49:45Z coats $
Version with PARMS3.EXT/PARAMETER::MXVARS3= 2048
netCDF version 4.7.4 of Apr 7 2021 16:50:09 $
Missing environment variable EXECUTION_ID
Program M3STAT to compute statistics of selected variables
from a user-specified GRIDDED, BOUNDARY, CUSTOM, IDDATA, or
SPARSE-MATRIX Models-3 file.
You need to have assigned a logical name to the physical
file name of the input file, and optionally the report file
according to Models-3 conventions, using the operation
"setenv <lname> <pname>".
You will have the choice of either the default analysis,
which computes statistics for the variables in the file, or
customized analysis in which you select lists of variables
to be analyzed, and the thresholds to be applied to each.
USAGE: m3stat [INFILE [REPORTFILE]] [DEFAULT]
(and then answer the prompts).
Note that RUNLEN=0 for single-step runs ("fenceposts"...)
See URL
https://www.cmascenter.org/ioapi/documentation/3.1/html#tools
Program copyright (C) 1992-2002 MCNC, (C) 1995-2013
Carlie J. Coats, Jr., and (C) 2002-2010 Baron Advanced
Meteorological Systems, LLC. Released under Version 2
of the GNU General Public License. See enclosed GPL.txt, or
URL http://www.gnu.org/copyleft/gpl.html
Comments and questions are welcome and can be sent to
Carlie J. Coats, Jr. carlie@jyarborough.com
or
UNC Institute for the Environment
137 E. Franklin St. Suite 602 Room 613-C
Campus Box 1105
Chapel Hill, NC 27599-1105
Program version:
$Id:: m3stat.f 117 2019-06-15 14:56:29Z coats $
Error opening file at path-name:
netCDF error number -51 processing file "infileB"
NetCDF: Unknown file format
NetCDF: Unknown file format
/home/Michael/Documents/SMOKE/2016setupEPA/2028fh1_16j/smoke_out/2028fh1_16j/12US2/cmaq_cb6/ptegu_summer/inln_mole_ptegu_summer_20160501_12US2_cmaq_cb6_2028fh1_16j.ncf
*** ERROR ABORT in subroutine M3STAT
Could not open input file "infileB"
Please help
So the same build of m3stat and m3diff (using the same netCDF and I/O API libraries ande the same compiler) has one of them accepting the file, and the other rejecting it? …and were the same libraries used for the SMOKE-build that generated it? That is really strange.
…and if so, what does ncdump -k say about the file?
…and where did the netCDF library come from? Was it built according to the I/O API build-istructions https://cjcoats.github.io/ioapi/AVAIL.html#ncf4
NetCDF Version 4.x have lots of additional build options, that will require a complex set of additional libraries in your Makefiles and all other model-building systems . It is recommended that you disable these options by adding the command-line flags below to your netCDF configure command:
--disable-netcdf4 --disable-dap
Hi @cjcoats
I have built netcdf, ioapi3.2 using gfortran compiler. and yes, I followed instruction from the link you mentioned. I added --disable-netcdf4 --disable-dap option .
ncdump -k is not working. please see below:
[Michael@ADEQPlanning Linux2_x86_64gfort]$ echo $infileA
/home/Michael/Documents/SMOKE/ptegu2028EPA/2028fh1_ussa_16j/12US2/cmaq_cb6/ptegu_summer/inln_mole_ptegu_summer_20160501_12US2_cmaq_cb6_2028fh1_ussa_16j.ncf
[Michael@ADEQPlanning Linux2_x86_64gfort]$ echo $infileB
/home/Michael/Documents/SMOKE/2016setupEPA/2028fh1_16j/smoke_out/2028fh1_16j/12US2/cmaq_cb6/ptegu_summer/inln_mole_ptegu_summer_20160501_12US2_cmaq_cb6_2028fh1_16j.ncf
[Michael@ADEQPlanning Linux2_x86_64gfort] which ncdump
/home/Michael/Documents/netcdf/bin/ncdump
[Michael@ADEQPlanning Linux2_x86_64gfort] ncdump -k infileA
ncdump: infileA: infileA: No such file or directory
[Michael@ADEQPlanning Linux2_x86_64gfort]$ ncdump -k infileB
ncdump: infileB: infileB: No such file or directory
You need ncdump $INFILEA – ncdump uses physical path-names instead of logical names.
Hi @cjcoats ,
Please see the output of ncdump -k $infileA
which gives me output ‘64-bit offset’ [infileA is the EPA file], but for my run output infileB is giving error ‘netcdf:unknown file format’ error
’
That says the trouble is the INFILEB input-file. You might re-consider everything that went into constructing it – something is wrong somewhere there.
Hello @cjcoats
I have double checked the inputs that were used for the SMOKE run, I haven’t found any concerns. I have used everything as EPA (didn’t change anything except SMOKE and ioapi directories). My scripts and procedure used for the run, can be found here: SMOKE run issues for EPA 2016v1 2028 platform - #2 by cjcoats
When I was double checking I found out a directory called ‘intermed’ where I can see ‘m3stat_logs’ generated while I run SMOKE.
I examined the ‘m3stat_logs’ m3stat_ptegu_summer_may_20160501_12US2_cmaq_cb6_2028fh1_16j_inln.log.txt (6.3 KB) m3stat_ptegu_summer_may_20160501_12US2_cmaq_cb6_2028fh1_16j_inln.rpt.txt (288.0 KB) , I didn’t see any error log.
Please help
Thank you
Hello @cjcoats
I find out the the size (289k) of ‘infileB’ which is ‘inln_mole_ptegu_summer_20160501_12US2_cmaq_cb6_2028fh1_16j.ncf’ is less than the other files(36MB).
The ncdump -k command is giving error for the 20160501, but no-errors for other files.
I don’t understand why 20160501 file size is different?, What mistakes I am making?. I haven’t change anything in the scripts and ‘directory definition’ files except directories Annual_ptegu_daily_summer_12US2_2028fh1_16j.csh.txt (7.5 KB) Annual_ptegu_onetime_summer_12US2_2028fh1_16j.csh.txt (7.5 KB) directory_definitions_12US2.TXT (3.9 KB)
Would you please help me?
Thank you
So the inln_mole_ptegu_summer_20160501 file is clearly bad. At this point, this is no longer an m3diff problem and needs to be given a new(SMOKE relatedf) subject, so that the SMOKE experts can help.
So this is a file you created and is different in size from other files for the same month?
Thank you for the suggestions. I greatly appreciate that
Hi @eyth.alison
Yes, I have created May-September files (total 153 files). Only 20160501 is different size.
@Iqbal I would suggest for you to manually remove that 20160501 file and then regenerate it with successful runs of SMOKE programs. Check your Temporal and Smkmerge log files for May 1, 2016. I am guessing there was an error occurred.
Hello @bbaek
Thank you for the response. I have done following:
I use command ./May1st_Annual_ptegu_onetime… script first
Then used same command for the ‘daily script’
directory_definitions_12US2.TXT (3.9 KB) May1st_Annual_ptegu_daily_summer_12US2_2028fh1_16j.csh.txt (7.5 KB)
May1st_Annual_ptegu_onetime_summer_12US2_2028fh1_16j.csh.txt (7.5 KB)
I get following messages in the terminal after ‘daily’ script run
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 this file rep_logs_ptegu_20160501_2028fh1_16j_12US2_summer_level1.csv.txt (4.9 KB) where I can see DEFAULT_CONV_FAC_ERROR not defined and Value for SMK_MAXERROR
Then I checked ‘smoke_out’ folder, where I can see file size is now same as EPA file for 20160501
Then I checked log files for ‘temporal’ & ’ Smkmerge’ where I don’t see any errors temporal_ptegu_20160501_may_2028fh1_16j_20160501.log.txt (575.5 KB) smkmerge_ptegu_20160501_may_2028fh1_16j_20160501_12US2_cmaq_cb6.txt.log.txt (86.0 KB)
Then I tried to run ‘m3diff’ where I can see the same error I was getting previously compar.txt (10.1 KB) A:B nowhere defined’
—>> WARNING in subroutine WRITE3
Variable SO2 not in file: OFILE
M3WARN: DTBUF 0:00:00 May 1, 2016 (2016122:000000)
Could not write “SO2” to “OFILE” for 0:00:00 May 1, 2016
—>> WARNING in subroutine WRITE3
Variable SO2 not in file: OFILE
M3WARN: DTBUF 1:00:00 May 1, 2016 (2016122:010000)
Could not write “SO2” to “OFILE” for 1:00:00 May 1, 2016
—>> WARNING in subroutine WRITE3
Variable SO2 not in file: OFILE
M3WARN: DTBUF 2:00:00 May 1, 2016 (2016122:020000)
Could not write “SO2” to “OFILE” for 2:00:00 May 1, 2016
—>> WARNING in subroutine WRITE3
Variable SO2 not in file: OFILE
M3WARN: DTBUF 3:00:00 May 1, 2016 (2016122:030000)
Could not write “SO2” to “OFILE” for 3:00:00 May 1, 2016
—>> WARNING in subroutine WRITE3
Variable SO2 not in file: OFILE
M3WARN: DTBUF 4:00:00 May 1, 2016 (2016122:040000)
Could not write “SO2” to “OFILE” for 4:00:00 May 1, 2016
—>> WARNING in subroutine WRITE3
Variable SO2 not in file: OFILE
M3WARN: DTBUF 5:00:00 May 1, 2016 (2016122:050000)
Could not write “SO2” to “OFILE” for 5:00:00 May 1, 2016
@Iqbal @cjcoats Looks like you are trying to run m3diff on inline emissions input for those point elevated sources. The structure of inline output files are not comparable with m3diff. If you really want to compare the inline emissions files, you need to first use a SMOKE tool called inline2D tool to convert current inline emissions to a 2d hourly emissions.
https://www.cmascenter.org/smoke/documentation/4.8.1/html/ch05s03s07.html
After you convert both A and B inline emission files into the correct IOAPI format 2d hourly gridded emissions, you can m3diff them to see the differences between A and B files.
Hello @bbaek , I will try to use inline2D. I have some questions:
Is there any other ways that I can compare my output vs EPA?
Is my procedure for SMOKE run for ptegu sector correct?
what is DEFAULT_CONV_FAC_ERROR not defined and Value for SMK_MAXERROR and ERROR: At least one message’s priority is less than or equal to the exit priority: 1?
