When running CCTM, is it possible to generate the output file with the data longer than one day?

Good evening CMAQ users:
I am trying to run CCTM for multiple days. However, I realize that in each loop, the boundary condition was reset.

#> Boundary conditions
set BCFILE = BCON_${YYYYMMDD}_bench.nc

Since I am using “profile” option to prepare BCON, and I found no matter which date, the concentrations at the boundary of the domain are exactly the same.
Thus, I tried to removed the “loop” and run for the multiple days. However, it seems that CMAQ only allow to generate the output file with the data of one day.
Is it possible to generate the output in the files with more than one day data, rather than generate the data of each day in each daily file? I mean, for example, if I run for 3 days, I expect to generate one file (e.g. CCTM_CONC_${CTM_APPL}.nc) that includes the one-hour concentration for all 3 days, rather than three files that includes the one-hour concentration of day1, day2, and day3 respectively.

Hi,

Yes, it is possible for CMAQ to be run and generate output for any configuration that you are able to script.
The key is to have coordination between the start date, end date, and the NSTEPS.
The NSTEPS variable determines how many timesteps are written to the output file.

#> Set Start and End Days for looping
setenv NEW_START TRUE #> Set to FALSE for model restart
set START_DATE = “2016-07-01” #> beginning date (July 1, 2016)
set END_DATE = “2016-07-01” #> ending date (July 14, 2016)

#> Set Timestepping Parameters
set STTIME = 000000 #> beginning GMT time (HHMMSS)
set NSTEPS = 240000 #> time duration (HHMMSS) for this run
set TSTEP = 010000 #> output time step interval (HHMMSS)

Hi Liz:

I may not clear enough. I know how to generate multiple day run. However, the output is one file for each day, so it will be multiple files for multiple days. I expect to generate one file with multiple days

Huan

Hi Huan,

If you set NSTEPS equal to 720000, then the output file will contain 72 hours, or all of the output for a 3 day run.

will that avoid the boundary condition to be reset at the end of each day?

Hi Huan,

The boundary condition file doesn’t get reset at the end of each day, only the initial condition file.

Liz

#> Set Start and End Days for looping
setenv NEW_START TRUE #> Set to FALSE for model restart
set START_DATE = “2016-01-01” #> beginning date (Jan 1, 2016)
set END_DATE = “2016-01-07” #> ending date (Jan 7, 2016)

#> Set Timestepping Parameters
set STTIME = 000000 #> beginning GMT time (HHMMSS)
set NSTEPS = 1680000 #> time duration (HHMMSS) for this run
set TSTEP = 010000 #> output time step interval (HHMMSS)

It could be run successfully if I set NSTEPS=240000. After setting to NSTEPS=1680000, it shows:

application called MPI_Abort(MPI_COMM_WORLD, 538976288) - process 0
[unset]: write_line error; fd=-1 buf=:cmd=abort exitcode=538976288
:
system msg for write_line failure : Bad file descriptor
0.22user 0.74system 0:01.14elapsed 84%CPU (0avgtext+0avgdata 1441988maxresident$
0inputs+16outputs (0major+331581minor)pagefaults 0swaps
date

If my understanding was correct. In order to run for 7 days (for example), I have to run BCON for these 7 days right? It has two options, “profile” and “m3conc”.
For “profile”, it is based on the mechanism I choose. And I compared the results from different dates, the concentrations are exactly the same.
For “m3conc”, the scripts shows:

if ( $BC == m3conc ) then
setenv CTM_CONC_1 $CMAQ_DATA/cctm/CCTM_d1bCONC.d1b

But I did not find out this file, shall I prepare from CCTM result? How could I extract the BC from CCTM result?

On the other hand, if I use “profile” option to prepare BCON, it may cause when running CCTM, when starting each loop, it will be set to the same BCON, since the concentrations of different dates are actually the same

No matter how, I don’t want the BCON be recalled each day, I just want it to be used at the beginning of simulation. Is it possible?

The standard CMAQ scripts are heavily hard-coded for running just one day at a time; however, the model itself is not.

It was part of the original systems requirements that CMAQ should be straghtforward to run for entire months, seasons, or years as single model-runs. Note however that you will need to prepare equally-long input files; M3Tools program m3cple (https://www.cmascenter.org/ioapi/documentation/all_versions/html/M3CPLE.html) is one of the tools which can be used for this purpose…

I am sure my emission file has the exactly same time steps as the mcip output files METCRO2, METCRO3D, METDOT3D and METBDY3D. The mcip output files GRIDBDY2D, GRIDCRO2D, and GRIDDOT2D, bcon and icon output files are time-independent.
However, when I tried to run single day, or multiple days in the loop (START_DATE=“2016-01-01”, END_DATE = “2016-12-30”, NSTEPS=240000), it was success. While, when I tried to run multiple days with the loop (START_DATE=“2016-01-01”, END_DATE = “2016-12-30”, NSTEPS=87600000, I have annually long emission and mcip), or removing the loop (START_DATE=“2016-01-01”, NSTEPS=87600000, comment out END_DATE and any other variables related to the loop, and I tested when NSTEPS=240000 it could be successfully run!), it was fail.