I did a run in CCTM for 15 days. Now I want to continue for 16 days to complete 1 month (January) and I was wondering if I have to use the same BCON file as used for the first run, or instead, I could use a bcon file but using module m3conc. I reviewed the bcon script and the input required is a file called CCTM_d1bCONC.d1b. I was looking for it in the output file and I did not find it.
Could you please help me to understand what file is required?
Thanks for your time
CCTM stops running on long simulation
I am unsure as to exactly what you are trying to do.
I assume you used some kind of static profile boundary condition for the 15-day run. While you do not have to use the same BCON file for the second half of the month, it seems to me that is the most reasonable thing to do. Alternatively, if you have some better BCON data, I would use it for the entire month if possible.
In order to use your existing CCTM outputs to create boundary conditions for a new run, the new run must be entirely nested within the domain of the original simulation. (Otherwise, how can the simulation you have completed provide data along the boundary?) The time period must be restricted to the period for which you have run the first origination. And most importantly, you need meteorological and emissions input data on your nested grid.
Hello Mr Nolte:
First, I would like to apologize with you because I did not expressed my self as I wanted.
So, I ´ll try to do righ now.
First. I have just one domain (hemispheric domain of 108 km with 180 horizontal cells by 180 v vertical cells. So, I don´t work with nested domains.
My question was about when it is used the bcon module using m3conc type. It is just for nested domain or I can use in a single domain? Are this related??
I used profile type in BCON module before during the first 15 days. I ran that period because I have emission from SMOKE in that range of time.
The description of the BCON program provided here may help.
The BCON program creates input files for CMAQ that describe chemical lateral boundary conditions around the boundary (perimeter) of your modeling domain, using the vertical layer structure of your meteorological data. You can either create static (time-independent) files following some assumed vertical profile along the boundaries, or you can take some other time-varying data source, such as output from a coarser scale CTM simulation. In this time-varying mode, BCON creates time-varying (typically hourly, but this is configurable) files of species concentrations along the boundary of your designated modeling domain.