Hello,
I’ve checked the log file and it’s saying the following error:
*** ERROR ABORT in subroutine GET_PT3D_EMIS on PE 016
Could not read BUTADIENE13 from STK_EMIS_01
PM3EXIT: DTBUF 0:02:00 Jan. 2, 2020
Date and time 0:02:00 Jan. 2, 2020 (2020002:000200)
Please see the log file. Any suggestions?
Regards
Rasel
CTM_LOG_016.v52_gcc_AQF5X_20200101.txt (714.4 KB)
Looking back at the initial log file you posted as well at this new one, it shows that all your emission files contain 25 hours but start at 2020001:000000 while you’re trying to run a 24 hour CMAQ simulation starting at 2002001:120000 which then crashes after midnight because the required emissions for the final 12 hours of your intended simulation time aren’t present in the emission input files.
"STK_EMIS_01" opened as OLD:READ-ONLY
File name "/scratch/mrasel/data/cmaq/tempcmaqdata/emis2020/ptnonipm/inln_mole_ptnonipm_20200101_AQF5X_cmaq_cb6_2016fh_16j.ncf"
File type GRDDED3
Execution ID "????????????????"
Grid name "AQF5X"
Dimensions: 220587 rows, 1 cols, 1 lays, 58 vbles
NetCDF ID: 2097152 opened as READONLY
Starting date and time 2020001:000000 (0:00:00 Jan. 1, 2020)
Timestep 010000 (1:00:00 hh:mm:ss)
Maximum current record number 25
The log files actually also show this warning for the gridded emissions file that indicate that your emissions do not cover the entire simulation period:
"EMIS_1" opened as OLD:READ-ONLY
File name "/scratch/mrasel/data/cmaq/tempcmaqdata/emis2020/all/emis_mole_all_20200101_AQF5X_nobeis_2016fh_16j.ncf"
File type GRDDED3
Execution ID "????????????????"
Grid name "AQF5X"
Dimensions: 265 rows, 442 cols, 1 lays, 62 vbles
NetCDF ID: 524288 opened as READONLY
Starting date and time 2020001:000000 (0:00:00 Jan. 1, 2020)
Timestep 010000 (1:00:00 hh:mm:ss)
Maximum current record number 25
Checking header data for file: EMIS_1
netCDF error number -40
Ending time not on file
To solve this, you would need to reprocess your emission inputs to match the 24 hour noon-to-noon periods for which you plan to run CMAQ, or to string them together into longer records like you apparently did for your MCIP files. Or you could adjust your CMAQ start hour to match those of your existing emissions. Either way, all of your inputs need to cover the entire 24 hour period you’re planning to run CMAQ for.
Thank you for your help. It worked. I’ve changed the starting date in my script and so far it’s looking good.
Hy,
In my CCTM run, the job gets terminated after 1-day simulation. CCTM_SENSGRID and CCTM_CGRID file are available in output directory for restart run. When I use grep -i error CTM_LOG* command it’s saying: " Performing Basic Error Checks for Emission Scaling Rules". Not sure how to resolve this. Any suggestion?
Please see the attached scripts and log file
Regards,
Rasel
CTM_LOG_000.v54_DDM3D_gcc_AQF5X_20191223.txt (663.7 KB)
run_cctm_rasel.csh_sbatch.txt (40.7 KB)
run_cmaq_rasel.sh.txt (759 Bytes)
|>--- PROGRAM COMPLETED SUCCESSFULLY ---<|
==============================================
Date and time 0:00:00 Dec. 24, 2019 (2019358:000000)
The elapsed time for this simulation was 5439.8 seconds.
The text “Performing Basic Error Checks for Emission Scaling Rules” is not an error, it is just a message indicating what the program is doing. Perhaps in the future, the message can be modified to state “Performing Basic Checks for Emission Scaling Rules” to avoid confusion.
Any idea why the run terminated after a 1-day simulation?
My log file is also showing this error:
|> Reading Emission Control Namelist:
+======================================
Performing Basic Error Checks for Emission Scaling Rules
GR_EM_SYM_DATE_0 | F
"GR_EMIS_001" opened as OLD:READ-ONLY
File name "/scratch/mrasel/cmaq-5.4/data_input/emis2020/all/emis_mole_all_20191225_AQF5X_nobeis_2016fh_16j.ncf"
File type GRDDED3
Execution ID "????????????????"
Grid name "AQF5X"
Dimensions: 265 rows, 442 cols, 1 lays, 62 vbles
NetCDF ID: 458752 opened as READONLY
Starting date and time 2019359:000000 (0:00:00 Dec. 25, 2019)
Timestep 010000 (1:00:00 hh:mm:ss)
Maximum current record number 25
INIT_CONC_1 :/scratch/mrasel/cmaq-5.4/data_output/cctm_out/CCTM_CGRID_v54_DDM3D_gcc_AQF5X_20191224.nc
>>--->> WARNING in subroutine OPEN3
File not available.
*** ERROR ABORT in subroutine gridded_files_se on PE 107
Open failure for INIT_CONC_1
PM3EXIT: date&time specified as 0
Date&time specified as 0
I am seeing the CGRID file is available in output directory.
Thanks
Rasel
You are using a different method to control the START_DATE and NEW_START environment variables.
In your Bash script you are setting date1=20191223 as START_DATE, and NEW_START as false
date1=20191223
NEW_START="FALSE"
Setting NEW_START FALSE means that the IC and BC files will be read from the previous days output.
I don’t know that using the bash script to set the START_DATE and NEW_START variables would cause an issue, but it is worth taking a look.
“INIT_CONC_1” opened as OLD:READ-ONLY
File name “/scratch/mrasel/cmaq-5.4/data_output/cctm_out/CCTM_CGRID_v54_DDM3D_gcc_AQF5X_20191222.nc”
File type GRDDED3
Execution ID “CMAQ_CCTMv54_DDM3D_sha=ecedee6bf9_mrasel_20221109_034504_114303151”
This appears to be working for the START_DATE = 20191223
#> Set Start and End Days for looping
setenv NEW_START ${2} #FALSE #TRUE #> Set to FALSE for model restart
echo "NEW START date in CCTM script is $NEW_START"
In the Csh script, there is an increment for START_DATE
#> The next simulation day will, by definition, be a restart
setenv NEW_START false
#> Increment both Gregorian and Julian Days
set TODAYG = `date -ud "${TODAYG}+1days" +%Y-%m-%d` #> Add a day for tomorrow
set TODAYJ = `date -ud "${TODAYG}" +%Y%j` #> Convert YYYY-MM-DD to YYYYJJJ
end #Loop to the next Simulation Day
Perhaps there is something that fails after the START_DATE is incremented?
It may be that you have another CTM_LOG_000* file for the second day that has an error in it.
Do you see a log file for the next day? CTM_LOG_000.v54_DDM3D_gcc_AQF5X_20191224
Can you grep that file for errors?
Hy,
Please see the attached script now. The log file is giving the same error:
*** ERROR ABORT in subroutine gridded_files_se on PE 106
Open failure for INIT_CONC_1
PM3EXIT: date&time specified as 0
Date&time specified as 0
The log file saying CGRID file not found but in my output directory I’m seeing that file is available.
Can you please let me know how to resolve this?
CTM_LOG_106.v54_DDM3D_gcc_AQF5X_20191226.txt (14.9 KB)
run_cctm_rasel.csh_sbatch.txt (40.7 KB)
