# Error while running CCTM : ERROR ABORT in subroutine RDBCON on PE 000 **URL:** \ **Category:** Run Time Errors and Issues\ **Tags:** cmaq\ **Created:** [May 26, 2023, 2:41pm UTC](https://forum.cmascenter.org/t/error-while-running-cctm-error-abort-in-subroutine-rdbcon-on-pe-000/4141 "2023-05-26T14:41:53Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![jisoo](https://avatars.discourse-cdn.com/v4/letter/j/6a8cbe/32.png) [@jisoo](https://forum.cmascenter.org/u/jisoo)\ **Post date:** [May 26, 2023, 2:41pm UTC](https://forum.cmascenter.org/t/error-while-running-cctm-error-abort-in-subroutine-rdbcon-on-pe-000/4141/1 "2023-05-26T14:41:54Z")
Hi. I have a problem with running cctm. Could you guide me, please? I succeed domain 4 with original scenario, but I have a problem with domain 4 with ‘gn scenario’. It isn’t a problem because of mcip file. I accidentally ran another file and overwritten the log file, so I can’t check the log file. Gn scenario’s SMOKE output file worked well until 3/31, but the error occurred from 3/25 in the middle of the cctm. * * * Timestep written to CTM\_DRY\_DEP\_1 for date and time 2019084:070000 after VDIFF G 1.8582305E-01 A 4.5467116E+09 N 4.7507964E-04 after COUPLE\_WR G 1.8891613E+03 A 4.7057763E+13 N 4.8308716E+00 after ADV G 1.8875485E+03 A 4.6783669E+13 N 4.8160534E+00 ``` H-eddy DT & integration steps: 1.5000000E+02 1 ``` after HDIFF G 1.8875498E+03 A 4.6783611E+13 N 4.8161445E+00 after DECOUPLE\_ G 1.8565609E-01 A 4.5201725E+09 N 4.7362616E-04 ``` Timestep written to CTM_WET_DEP_1 for date and time 2019084:070000 ``` after CLDPROC G 1.8565609E-01 A 4.5201725E+09 N 4.7362616E-04 after CHEM G 1.8567111E-01 A 4.5201725E+09 N 4.7362616E-04 ``` Timestep written to CTM_VIS_1 for date and time 2019084:070000 ``` after AERO G 1.8566473E-01 A 4.5034506E+09 N 4.7110961E-04 ``` After NEXTIME: returned JDATE, JTIME 2019084 070000 Timestep written to CTM_CONC_1 for date and time 2019084:070000 Timestep written to A_CONC_1 for date and time 2019084:060000 From ADVSTEP - date/time: 2019084/070000 Computed synchronization step (HHMMSS): 000230 Number of Synchronization steps: 24 Layer Advection per Sync Step (HHMMSS) Step 30 000050 3 29 000050 3 28 000030 5 27 000030 5 26 000030 5 25 000030 5 24 000030 5 23 000030 5 22 000030 5 21 000030 5 20 000030 5 19 000050 3 18 000050 3 17 000050 3 16 000115 2 15 000115 2 14 000115 2 13 000115 2 12 000230 1 11 000230 1 10 000230 1 9 000230 1 8 000230 1 7 000230 1 6 000230 1 5 000230 1 4 000230 1 3 000230 1 2 000230 1 1 000230 1 Maximum eddy diffusivity of: 196.45 (m**2/sec) at col, row, layer: 12, 11, 6 corresponding to a free tropospheric wind shear of: 1.25255E-03 (/sec), a bulk Richardson Number of: 1.0336 , and pot. temps. in layer and layer+1: 285.91 285.92 ``` NCVGT: : NetCDF: Index exceeds dimension bound after VDIFF G 1.8565699E-01 A 4.5064300E+09 N 4.7329758E-04 NCVGT: : NetCDF: Index exceeds dimension bound after COUPLE\_WR G 1.8874601E+03 A 4.6619991E+13 N 4.8127422E+00 netCDF error number -40 ``` >>--->> WARNING in subroutine RDTFLAG Error reading netCDF time step flag for BNDY_GASC_1 M3WARN: DTBUF 8:00:00 March 25, 2019 >>--->> WARNING in subroutine READBNDY Failed to read NO2 from file BNDY_GASC_1 M3WARN: DTBUF 8:00:00 March 25, 2019 ``` NCVGT: : NetCDF: Index exceeds dimension bound \>\>—\>\> WARNING in subroutine PINTERPB Subroutine READBNDY failed. M3WARN: DTBUF 7:01:15 March 25, 2019 ``` *** ERROR ABORT in subroutine RDBCON on PE 000 Could not read NO2 from BNDY_GASC_1 Date and time 7:01:15 March 25, 2019 (2019084:070115) ``` NCVGT: : NetCDF: Index exceeds dimension bound NCVGT: : NetCDF: Index exceeds dimension bound NCVGT: : NetCDF: Index exceeds dimension bound NCVGT: : NetCDF: Index exceeds dimension bound NCVGT: : NetCDF: Index exceeds dimension bound application called MPI\_Abort(MPI\_COMM\_WORLD, 0) - process 6 application called MPI\_Abort(MPI\_COMM\_WORLD, 0) - process 9 application called MPI\_Abort(MPI\_COMM\_WORLD, 0) - process 14 application called MPI\_Abort(MPI\_COMM\_WORLD, 0) - process 0 application called MPI\_Abort(MPI\_COMM\_WORLD, 0) - process 2 application called MPI\_Abort(MPI\_COMM\_WORLD, 0) - process 7 application called MPI\_Abort(MPI\_COMM\_WORLD, 0) - process 1 application called MPI\_Abort(MPI\_COMM\_WORLD, 0) - process 8 NCVGT: : NetCDF: Index exceeds dimension bound application called MPI\_Abort(MPI\_COMM\_WORLD, 0) - process 3 NCVGT: : NetCDF: Index exceeds dimension bound application called MPI\_Abort(MPI\_COMM\_WORLD, 0) - process 4 NCVGT: : NetCDF: Index exceeds dimension bound application called MPI\_Abort(MPI\_COMM\_WORLD, 0) - process 19 NCVGT: : NetCDF: Index exceeds dimension bound 2769140.149u 6940.625s 31:22:36.26 2457.6% 0+0k 41982992+236265216io 252pf+0w date Fri May 26 18:15:32 KST 2023 exit ---
**Author:** ![cjcoats](https://avatars.discourse-cdn.com/v4/letter/c/ac8455/32.png) [@cjcoats](https://forum.cmascenter.org/u/cjcoats)\ **Post date:** [May 26, 2023, 3:12pm UTC](https://forum.cmascenter.org/t/error-while-running-cctm-error-abort-in-subroutine-rdbcon-on-pe-000/4141/2 "2023-05-26T15:12:07Z")
The log messages indicate that the time 8:00:00 March 25, 2019 is out-of-range for the `BNDY_GASC_1` file. Easy check on that: run M3Tools program _ **m3stat** _ on that file and see whether it complains about that date&time. If so, it’s the file at fault; if not, it’s something about your processor set-up. ---
**Author:** ![jisoo](https://avatars.discourse-cdn.com/v4/letter/j/6a8cbe/32.png) [@jisoo](https://forum.cmascenter.org/u/jisoo)\ **Post date:** [May 26, 2023, 3:24pm UTC](https://forum.cmascenter.org/t/error-while-running-cctm-error-abort-in-subroutine-rdbcon-on-pe-000/4141/3 "2023-05-26T15:24:44Z")
Thanks for your reply. By the way, is m3stat a program installed by default in CMAQ? Where and how can the program be executed? ---
**Author:** ![cjcoats](https://avatars.discourse-cdn.com/v4/letter/c/ac8455/32.png) [@cjcoats](https://forum.cmascenter.org/u/cjcoats)\ **Post date:** [May 26, 2023, 3:33pm UTC](https://forum.cmascenter.org/t/error-while-running-cctm-error-abort-in-subroutine-rdbcon-on-pe-000/4141/4 "2023-05-26T15:33:32Z")
It is built by default as part of the I/O API (see [https://cjcoats.github.io/ioapi/AA.html](https://cjcoats.github.io/ioapi/AA.html) or [https://www.cmascenter.org/ioapi/documentation/all\_versions/html/AA.html](https://www.cmascenter.org/ioapi/documentation/all_versions/html/AA.html), of which CMAQ is one of several clients (including, among others, the SMOKE emissions model).