# SMOKE ptegu ERROR

**URL:** <https://forum.cmascenter.org/t/smoke-ptegu-error/4496>\
**Category:** SMOKE\
**Created:** [October 19, 2023, 2:45pm UTC](https://forum.cmascenter.org/t/smoke-ptegu-error/4496 "2023-10-19T14:45:59Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![lwu127](https://avatars.discourse-cdn.com/v4/letter/l/ea666f/32.png) [@lwu127](https://forum.cmascenter.org/u/lwu127)\
**Post date:** [October 19, 2023, 2:45pm UTC](https://forum.cmascenter.org/t/smoke-ptegu-error/4496/1 "2023-10-19T14:45:59Z")

</div>

Hi everyone,

I am using NEI 2017 platform and SMOKE-4.7. The following error appears when i run Annual\_ptegu\_onetime\_12US1\_2017gb\_17j.csh:

SCRIPT ERROR: timetracker script found multiple existing entries  
for the following primary keys in the file already:  
Sector = ptegu  
Job Name = Annual\_area  
Program = smkreport  
Run Date = inv  
This should not happen, so script does not know how to  
replace the entries for these keys  
ERROR: Problem calling timetracker from qa\_run script  
ERROR: Running qa\_run for invgrid  
grep: /glade/derecho/scratch/hmao/SMOKE-4.7/2017gb\_17j/intermed/ptegu/logs: Is a directory  
grep: /glade/derecho/scratch/hmao/SMOKE-4.7/2017gb\_17j/intermed/ptegu/logs: Is a directory  
log analyzer  
Getting message data (might take some time)…  
Finished getting data  
Classifying message types…  
Total number of known messages: 139  
Total number of unknown messages: 0  
Level 3 analysis…  
Finished classifying message types  
grep: /glade/derecho/scratch/hmao/SMOKE-4.7/2017gb\_17j/intermed/ptegu/logs: Is a directory  
grep: /glade/derecho/scratch/hmao/SMOKE-4.7/2017gb\_17j/intermed/ptegu/logs: Is a directory  
log analyzer  
Getting message data (might take some time)…  
Finished getting data  
Classifying message types…  
Total number of known messages: 139  
Total number of unknown messages: 0  
Level 1 analysis…  
Finished classifying message types  
Testing for exit priority \<= 1  
All message priorities \> 1

There are 8 files under /intermed/ptegu/logs and all log files showed Normal Completion:  
grdmat\_ptegu\_2017gb\_17j\_US12NE.log  
smkreport\_ptegu\_2017gb\_17j\_inv3.log  
spcmat\_ptegu\_2017gb\_17j\_cmaq\_cb6ae7.log  
helper\_scripts\_list\_ptegu\_2017gb\_17j\_US12NE\_onetime.txt  
smkreport\_ptegu\_2017gb\_17j\_invgrid.log  
timelog\_ptegu\_2017gb\_17j\_US12NE\_onetime.txt  
smkinven\_ptegu\_2017gb\_17j.log  
smkreport\_ptegu\_2017gb\_17j\_inv.log

Did the run succeed or not? What caused that ERROR message?

Thanks,  
Lin

---

<div class="post-metadata">

**Author:** ![lizadams](https://avatars.discourse-cdn.com/v4/letter/l/49beb7/32.png) [@lizadams](https://forum.cmascenter.org/u/lizadams)\
**Post date:** [November 10, 2023, 8:54pm UTC](https://forum.cmascenter.org/t/smoke-ptegu-error/4496/2 "2023-11-10T20:54:23Z")

</div>

If you get normal termination for the logs, then your run was successful. I am not sure that it is worth trying to diagnose why the qa\_run scripts failed, but perhaps @huytran6583 or @cseppan can help.

---

<div class="post-metadata">

**Author:** ![mroark](https://avatars.discourse-cdn.com/v4/letter/m/57b2e6/32.png) [@mroark](https://forum.cmascenter.org/u/mroark)\
**Post date:** [November 16, 2023, 10:16pm UTC](https://forum.cmascenter.org/t/smoke-ptegu-error/4496/3 "2023-11-16T22:16:27Z")

</div>

I’m guessing one of the smkreports failed. (I do not see the elevpoint log.) Check at the bottom of the smkreport logs, if there isn’t an indication of successful completion, then the smkreport stopped and failed. Perhaps there’s a failure in smkreport\_ptegu\_2017gb\_17j\_invgrid.log?

If there is a failure, you can safely remove the repconfig that was used in the failed smkreport process, mentioned in the logfile, from the run scripts, and run elevpoint using runsettings.txt ( or delete the ptegu directory and rerun from scratch ).

Smkreports are useful for QA purposes and REPCONFIGs are the smkreport configuration for each report. Removing the REPCONFIG will mean that a report is not created, but the smkreports are not required for SMOKE to complete.