I simulated two scenarios with CMAQ-ISAM respectively, and the main difference between the two scenarios is the emission inventory. The BASE scenario includes emissions from anthropogenic sources and natural sources, while the Background scenario only includes emissions from natural sources. Comparing the ISAM results of the two scenarios, it is found that the contribution of BCON changes. Is this normal? (The same BCON file is used for both scenarios)
Hello lotso,
yes, the results of the BCO tag (or other tags) can change between simulations if the number and/or definition of tags differs between simulations, even if the definition of the tag in question (like BCO) does not change between simulations. This is discussed on pages 4 - 7 of the ISAM chemistry supplement linked from the ISAM chapter of the users guide. This ISAM behavior was also discussed in posts 11 - 13 of this earlier thread.
Christian
Hello Christian,
Thank you very much for your answer. I would also like to ask why the value of O3 _ ICO is so large in my ISAM results (the spatial distribution of O3 _ ICO for both scenarios is shown in the figure)? How can I modify it?
Lotso
Hello Lotso,
What is your spin-up time? If the spin-up time is not long enough, it is likely that the contribution from the ICO will be high.
Haorui Wang
1 Like
Hello whr,
My spin-up time is 8 days.
Lotso
Hello Lotso,
I have done several long-term simulations in the Asian domain using CMAQ-ISAM, which may be helpful to you. Can you share your email address? I will contact you to get more details.
Haorui Wang
A spin-up period of 8 days is indeed on the short side for simulations that span a large geographical area like yours. As @whr noted, a longer spin-up period will reduce the magnitude of the ISAM ICO tag.
The exact length of the spin-up period will depend on domain size, season, and meteorological conditions. In some annual ISAM applications our group performed over the entire US, using a spin-up period of 1 month (starting on December 1 for an analysis period starting on January 1) was sufficient to reduce the ISAM O3_ICO tag to <= 1ppb throughout the domain.