All concentration files are correct, and the logs have not reported any errors. However, one day after the simulation started, mine was on the 10th day, O3_ ANX starts from a certain grid point in the simulation domain to 0. As the simulation continued, after another 7 days, O3_ BCO also began to become zero. There are also issues with other variables. Given that there were no issues with the results at first few days of the simulation, I guess my model settings should not have been wrong.
I have not been able to replicate this behavior on our local system here. Is there any way for you to share the INPUTS so that I may try your exact case? The best would be the smallest number of simulation days that start from clean initial conditions and progress in the the first occurrence of the problem.
@sergey, no, unfortunately I think @bandaoshutiao is encountering the problem with the newest code (CMAQv5.4.0.3), but can avoid this specific problem when downgrading to CMAQv5.3.2.
I have successfully executed CMAQ/DDM v5.2 and CMAQ/DDM v5.4.0.3 and obtained satisfactory results. In my practices, other versions of CMAQ, including CMAQ 5.3.2 with the DDM-3D, do not appear to be fully functional.
CMAQ/DDM v5.4 exhibits significantly elevated higher-order sensitivities. However, these issues have been addressed and resolved in CMAQ v5.4.0.3, as seen here. I do not have the problem posted here in utilizing CMAQ v5.4.0.3 with DDM-3D.
Thanks.
I ran this case locally and was able to trigger an instability in O3_ANX at hour 21. The rest of my results were without error. This is different from the other case reported here, but hopefully good enough to investigate. I will try to figure out what is causing it and will report back.
I found that the restart SENGRID file for the case you sent me already has bad value for some VS* species. Here is one example from m3stat command on SENGRID:
Variable: SVAVB1_BVX
3-D grid statistics
Max 1.30980E+22 @(c,r,l)=(172,61,20)
Min -2.38146E+22 @(c,r,l)=(171,60,17)
Mean -4.97627E+17
Sigma Infinity
Could you, please, go back further in time checking SENGRID restart files until you find a clean one?
It is possible that the issue originates in the sensitivity treatment of the organic PM module. However, I will need your help to track it down. Could you, please, go through the sensitivity output and see when in your simulation time species relating to organic PM first begin to show unreasonable behavior. Examining only the “ANX” sensitivity is sufficient. These species are listed below.
I would pick one of those variables and go back through the output files until you find a day that it breaks. Then, check the other variables to make sure they don’t break earlier.
