Can’t find any error in log when i running CCTM script

I was running CMAQv5.3.3 on the supercomputing platform, but the simulation unexpectedly terminated after about 30 seconds. There was no clear error message in the log file. Could you please help me identify the possible cause of this issue?
The output file size is only a few kilobytes. In addition, I recompiled the CMAQ-ISAM version of the model, but I have not enabled or used the ISAM features in this simulation.

Thank you very much.
CTM_LOG_000.v533_intel_2020case_20200105.txt (118.3 KB)
run_cctm_Bench_2016_12SE1.csh (35.6 KB)


Hello @sher,

have you examined all the processor log files and tried compiling the model in debug mode? These two steps described in our debugging tutorial may reveal more information about what is causing the problem you are encountering.

Examine all CTM_LOG files

Use debug mode

Thank you very much. I have reviewed all the log files and found this error. Could this be related to the emissions file? Also, I used grams and moles as units when processing the emission data. Are these units compatible with the CMAQ model?
CTM_LOG_004.v533_intel_2020case_20200105.txt (107.0 KB)

ERROR: Max number of EBI time step reductions exceeded
Convergence failure for cell ( 60, 39, 1)
Convergence failure for the following species:Init.Conc, Pred.Conc.
NO2 1.0000E+03 1.0000E+03 ppmV

 *** ERROR ABORT in subroutine HRSOLVER on PE 037
 ERROR: Stopping because of EBI convergence failures

PM3EXIT: DTBUF 0:00:00 Jan. 5, 2020
Date and time 0:00:00 Jan. 5, 2020 (2020005:000000)
This error happened yesterday.

The log file you attached shows a different error message

 *** ERROR ABORT in subroutine AQCHEM on PE 004          
 Maximum AQCHEM total iterations exceeded
PM3EXIT:  DTBUF 0:00:00   Jan. 5, 2020  
 Date and time 0:00:00   Jan. 5, 2020   (2020005:000000)

than the one you included in your post. If both of these were present in the same run, could you please post both of the log files in which they appeared?

As noted by @cgnolte in this thread when a user encountered the same type of crash, this typically points to bad input data. The NO2 mixing ratio of 1000 ppm you posted certainly points towards problems with the emissions.