Thanks for the info. Both Temoral and Smkreport are Version SMOKEv4.8_Oct2020
After getting similar errors when trying to run the ptegu sector, I decided to compile SMOKEv4.7, which required both this post and this post to successfully compile on my system. With v4.7 both the ptegu and ptertac sectors finished successfully. Thanks!
Hi @bbaek
I have a similar issue. I did try your suggestions, but still getting the same error. Please see my errors here Source: Too many arguments, While Running Daily PTNONIPM Script 2016V3 - #16 by Iqbal
Would you please look at it? and provide any suggestions.
Thanks in advance
It seems you need to make sure you are using tcsh. On EPAâs system /bin/csh is linked to tcsh.
Removing REPCONFIG_TEMP from the run script should fix your new issue.
1 Like
Hi @eyth.alison @lizadams @bbaek
So, after commenting out REPCONFIG_TEMP, looks like daily scripts ran successfully (but with an error of ILLEGAL VARIABLE name ERROR: running m3stat_chk for 20160101]. The script only creates 1 output file only.
Pleas see the terminal output (last part):
You may use END_OF-FILE (control-D) to quit the program
during logical-name entry. Default responses are given in
brackets [LIKE THIS] and can be accepted by hitting the
key.at time 0:00:00 at time 1:00:00 at time 2:00:00 at time 3:00:00 at time 4:00:00 at time 5:00:00 at time 6:00:00 at time 7:00:00 at time 8:00:00 at time 9:00:00 at time 10:00:00 at time 11:00:00 at time 12:00:00 at time 13:00:00 at time 14:00:00 at time 15:00:00 at time 16:00:00 at time 17:00:00 at time 18:00:00 at time 19:00:00 at time 20:00:00 at time 21:00:00 at time 22:00:00 at time 23:00:00 at time 0:00:003.030u 0.094s 0:03.12 100.0% 0+0k 0+20240io 0pf+0w
now checking log file /Air/emismod/2016/v3/EV_TRIAL/2023gf_16j/intermed/ptnonipm/logs/smkmerge_ptnonipm_jan_2023gf_16j_20160101_12US2_WC_cmaq_cb6ae7.log
Now running M3STAT
Illegal variable name.
ERROR: running m3stat_chk for 20160101
log analyzer
Getting message data (might take some time)âŚ
grep: /Air/emismod/2016/v3/EV_TRIAL/2023gf_16j/intermed/ptnonipm/logs: Is a directory
grep: /Air/emismod/2016/v3/EV_TRIAL/2023gf_16j/intermed/ptnonipm/logs: Is a directory
Finished getting data
Classifying message typesâŚ
Total number of known messages: 58
Total number of unknown messages: 0
Level 3 analysisâŚ
Finished classifying message types
log analyzer
Getting message data (might take some time)âŚ
grep: /Air/emismod/2016/v3/EV_TRIAL/2023gf_16j/intermed/ptnonipm/logs: Is a directory
grep: /Air/emismod/2016/v3/EV_TRIAL/2023gf_16j/intermed/ptnonipm/logs: Is a directory
Finished getting data
Classifying message typesâŚ
Total number of known messages: 58
Total number of unknown messages: 0
Level 1 analysisâŚ
Finished classifying message types
Testing for exit priority <= 1
All message priorities > 1
Then I looked at the smoke_out folder, where I can see only one output file âinln_mole_ptnonipm_20160101_12US2_WC_cmaq_cb6ae7_2023gf_16j.ncfâ.
Then I looked at the level 1 and level 3 errors from log_analyzer:
./rep_logs_ptnonipm_2023gf_16j_12US2_WC_onetime_level3.csv:3,âValue for SMK_MAXERROR:â,156,âValue for SMK_MAXERROR: 10000â,/Air/emismod/2016/v3/EV_TRIAL/2023gf_16j/intermed/ptnonipm/logs/smkinven_ptnonipm_2023gf_16j.log
./rep_logs_ptnonipm_2023gf_16j_12US2_WC_onetime_level3.csv:3,âValue for SMK_MAXERROR:â,368,âValue for SMK_MAXERROR: 10000â,/Air/emismod/2016/v3/EV_TRIAL/2023gf_16j/intermed/ptnonipm/logs/spcmat_ptnonipm_2023gf_16j_cmaq_cb6ae7.log
./rep_logs_ptnonipm_2023gf_16j_12US2_WC_onetime_level3.csv:3,âValue for DEFAULT_CONV_FAC_ERROR: .',370,âValue for DEFAULT_CONV_FAC_ERROR: Y returning TRUEâ,/Air/emismod/2016/v3/EV_TRIAL/2023gf_16j/intermed/ptnonipm/logs/spcmat_ptnonipm_2023gf_16j_cmaq_cb6ae7.log
./rep_logs_ptnonipm_2023gf_16j_12US2_WC_onetime_level1.csv:3,True,2,âValue for SMK_MAXERROR:â,/Air/emismod/2016/v3/EV_TRIAL/2023gf_16j/intermed/ptnonipm/logs/smkinven_ptnonipm_2023gf_16j.log
./rep_logs_ptnonipm_2023gf_16j_12US2_WC_onetime_level1.csv:3,True,1,'Value for DEFAULT_CONV_FAC_ERROR: .â,/Air/emismod/2016/v3/EV_TRIAL/2023gf_16j/intermed/ptnonipm/logs/spcmat_ptnonipm_2023gf_16j_cmaq_cb6ae7.log
./rep_logs_ptnonipm_2023gf_16j_12US2_WC_byday_level1.csv:3,True,3,âValue for SMK_MAXERROR:â,/Air/emismod/2016/v3/EV_TRIAL/2023gf_16j/intermed/ptnonipm/logs/temporal_ptnonipm_jan_2023gf_16j_20160101.log
./rep_logs_ptnonipm_2023gf_16j_12US2_WC_byday_level1.csv:3,True,1,âValue for DEFAULT_CONV_FAC_ERROR: .',/Air/emismod/2016/v3/EV_TRIAL/2023gf_16j/intermed/ptnonipm/logs/spcmat_ptnonipm_2023gf_16j_cmaq_cb6ae7.log
./rep_logs_ptnonipm_2023gf_16j_12US2_WC_byday_level3.csv:3,âValue for SMK_MAXERROR:â,328,âValue for SMK_MAXERROR: 10000â,/Air/emismod/2016/v3/EV_TRIAL/2023gf_16j/intermed/ptnonipm/logs/temporal_ptnonipm_jan_2023gf_16j_20160101.log
./rep_logs_ptnonipm_2023gf_16j_12US2_WC_byday_level3.csv:3,âValue for SMK_MAXERROR:â,156,âValue for SMK_MAXERROR: 10000â,/Air/emismod/2016/v3/EV_TRIAL/2023gf_16j/intermed/ptnonipm/logs/smkinven_ptnonipm_2023gf_16j.log
./rep_logs_ptnonipm_2023gf_16j_12US2_WC_byday_level3.csv:3,âValue for SMK_MAXERROR:â,368,âValue for SMK_MAXERROR: 10000â,/Air/emismod/2016/v3/EV_TRIAL/2023gf_16j/intermed/ptnonipm/logs/spcmat_ptnonipm_2023gf_16j_cmaq_cb6ae7.log
./rep_logs_ptnonipm_2023gf_16j_12US2_WC_byday_level3.csv:3,'Value for DEFAULT_CONV_FAC_ERROR: .â,370,âValue for DEFAULT_CONV_FAC_ERROR: Y returning TRUEâ,/Air/emismod/2016/v3/EV_TRIAL/2023gf_16j/intermed/ptnonipm/logs/spcmat_ptnonipm_2023gf_16j_cmaq_cb6ae7.log
All the errors are either DEFUALT_CONV_FAC or SMK_MAXERROR, and these can be ignored, Am I right?
If so, Why smoke_out created only 1 output file?
Any suggestions would be greatly appreciated.
We think this could be due to another type of anomaly related to csh on your system.
M3stat is used for some error checking.
However, its failing is keeping the rest of the script/ year from running.
We recommend you turn m3stat off via the run_settings.txt file:
ptnonipm, 12US1, m3stat, ALL, 0, 0, N
If you are running a domain other than 12US1, put your domain name there in place of 12US1
[Noting this may impact other sectors that you run, if any].
Please let us know if this allows the script to run to completion.
Hi @eyth.alison
Using the run_settings.txt
I am still getting same error. I checked /intermed/ptnonipm/log to see if SMOKE programs ran successfully. All the programs (smkinven, spcmat, grdmat, smkreport,elevpoint, temporal, and smkmerge) ran successfully.
Here is the terminal output which is showing mtstat error (last part):
at time 21:00:00
at time 22:00:00
at time 23:00:00
at time 0:00:00
2.559u 0.043s 0:02.64 98.1% 0+0k 0+20232io 0pf+0w
SCRIPT NOTE: timetracker is replacing line 2 of the TIMELOG file
now checking log file /Air/emismod/2016/v3/EV_TRIAL/2023gf_16j/intermed/ptnonipm/logs/smkmerge_ptnonipm_jan_2023gf_16j_20160101_12US2_WC_cmaq_cb6ae7.log
Now running M3STAT
Illegal variable name.
ERROR: running m3stat_chk for 20160101
log analyzer
Getting message data (might take some time)âŚ
grep: /Air/emismod/2016/v3/EV_TRIAL/2023gf_16j/intermed/ptnonipm/logs: Is a directory
grep: /Air/emismod/2016/v3/EV_TRIAL/2023gf_16j/intermed/ptnonipm/logs: Is a directory
Finished getting data
Classifying message typesâŚ
Total number of known messages: 65
Total number of unknown messages: 0
Level 3 analysisâŚ
Finished classifying message types
log analyzer
Getting message data (might take some time)âŚ
grep: /Air/emismod/2016/v3/EV_TRIAL/2023gf_16j/intermed/ptnonipm/logs: Is a directory
grep: /Air/emismod/2016/v3/EV_TRIAL/2023gf_16j/intermed/ptnonipm/logs: Is a directory
Finished getting data
Classifying message typesâŚ
Total number of known messages: 65
Total number of unknown messages: 0
Level 1 analysisâŚ
Finished classifying message types
Testing for exit priority <= 1
All message priorities > 1
NOTE:
I added âsourceâ command before the last line ($RUNSCRIPTS **) of the âdailyâ script.
without âsourceâ command âdailyâ script does not run. It gives following error
/bin/ls: No match.
source: Too many arguments.
We suggest changing run settings grid to 12US2_WC
Also, just double checking â is this for ptnonipm or ptfire?
Hi @eyth.alison
Changing run settings grid didnât solve the issue. I used following run_settings
This is âptnonipmâ run.
The initial problem was âtoo many argumentsâ,
OK â we are unsure why the m3stat is still running.
Try changing the m3state script to use /bin/tcsh in the m3stat script, since thatâs the script that is failing here:
INSTALL_DIR/smoke4.9/scripts/run/m3stat_chk_v6.csh
If that doesnât work, edit INSTALL_DIR/smoke4.9/scripts/emf/smk_pt_annual_byday_emf.csh and set run_m3stat = N.
1 Like
Hi @eyth.alison ,
Success!
Changing m3stat script to /usr/bin/tcsh solves the issue. Now , ptnonipm script is running without any problems.
To get smoke_out file for EACH DAY:
I modified L_TYPE and M_TYPE to âallâ , removed setenv MRG_BYDAY âPâ line, and
modified this line
$RUNSCRIPTS/emf/smk_pt_annual_byday_emf.csh $REGION_ABBREV $REGION_IOAPI_GRIDNAME -m â$RUN_MONTHSâ $SPINUP_DURATION byday
with this:
$RUNSCRIPTS/emf/smk_pt_daily_emf.csh $REGION_ABBREV $REGION_IOAPI_GRIDNAME -m â$RUN_MONTHSâ $SPINUP_DURATION daily
and replaced âmwdss_Yâ to âallâ in the SECTORLIST file.
Are these correct modifications?
Thanks
Your changes will work to produce emissions every day. The 2016 platform uses representative days because the emissions will not vary for every day of the month.
This is described in the 2016v3 TSD. We are not sure if you expect different emission values each day using your own input data.
FYI, if you donât have custom day of month profiles and are using the ones that came with 2016v2 platform, a more efficient approach is to only change M_TYPE to âallâ and the SECTORLIST to âallâ, and kept everything else (L_TYPE, MRG_BYDAY, and the annual_byday run script) the same as before. Then, Temporal would still only run for representative days instead of daily (which is all that is needed from a temporalization perspective), but Smkmerge would run daily and create daily emissions.
1 Like