Open laura-hyesung-yang opened 6 months ago
Thanks @laura-hyesung-yang for the update. Is that just kicking the can down the road though? I wonder if the Br2 and ClOO will blow up on another day. Something to watch for.
@yantosca Yes - it might be kicking the can down the road. I encountered this issue when my simulation began on 04/01/2016. I switched the Restart file name to be 04/02/2016 and timestamp to be 04/02/2016. Then I got the following message on the first day of simulation at 21:00.
Infinity in DO_CLOUD_CONVECTION!
K, IC, Q(K,IC): 11 30 NaN CFC11
NaN NaN NaN NaN NaN NaN 300.00000000000000 NaN
Infinity in DO_CLOUD_CONVECTION!
K, IC, Q(K,IC): 10 30 NaN CFC11
NaN NaN NaN NaN NaN NaN 300.00000000000000 NaN
Infinity in DO_CLOUD_CONVECTION!
K, IC, Q(K,IC): 11 30 NaN CFC11
NaN NaN NaN NaN NaN NaN 300.00000000000000 NaN
Infinity in DO_CLOUD_CONVECTION!
K, IC, Q(K,IC): 5 30 NaN CFC11
NaN NaN NaN NaN NaN NaN 300.00000000000000 NaN
Infinity in DO_CLOUD_CONVECTION!
K, IC, Q(K,IC): 5 30 NaN CFC11
NaN NaN NaN NaN NaN NaN 300.00000000000000 NaN
Infinity in DO_CLOUD_CONVECTION!
K, IC, Q(K,IC): 5 30 NaN CFC11
I've resubmitted the run so that my simulation starts on 05/01/2016. So far, it's running without these errors appearing for 2 days. But I will watch for it and keep you posted here!
@laura-hyesung-yang: Is this issue now resolved?
Name and Institution (Required)
Name: Laura Yang Institution: Harvard University GEOS-Chem version: 13.3.4
Description of your issue or question
I added two new chemical mechanisms to GEOS-Chem version 13.3.4 related to cloud chemistry. In
fullchem.eqn
, I added the following:MCO3 = MP : MCO3uptkByCloud( State_Het ); {2024/03/11; LHY}
CH2O = MDL : K_MDL;
I defined
FUNCTION MCO3uptkByCloud
infullchem_RateLawFuncs.F90
following theN2O5uptkByCloud
function.K_MDL
is defined infullchem_SulfurChemFuncs.F90
as a constant that depends on cloud fraction, temperature, and liquid water content (KPP_files.zip). Then I rebuilt KPP.When I run a 4x5 global run with these changes, the model ran successfully without failing. So, I generated boundary condition files from a 4x5 global run. Then I tried to run a 0.25 x 0.3125 nested simulation and the integration failing error showed up right after
GET_BOUNDARY_CONDITIONS
call was run (GC.log).When I ran the GCClassic version 13.3.4 without this chemical mechanism changed, it ran fine so this issue is possibly related to me adding the mechanism. Also, since the global run was OK but the nested run is being stuck, perhaps boundary condition files are the culprit. May I ask for advice on which to look into further?