You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At initialization on startup the model reads in the time coordinate for all of the forcing files. It successfully goes through the majority of them, but times out near the end.
It's not clear to me what's different about these two tests than other tests that run successfully. Many tests on izumi are with CRU forcing, but still some are GSWP3 for this same resolution.
Important details of your setup / configuration so we can reproduce the bug
Brief summary of bug
There are two tests on izumi with NUOPC that I consistently get a timeout in MPI
when initially reading in datm forcing files
General bug information
CTSM version you are using: ctsm5.1.dev030 (what will be anyway)
Does this bug cause significantly incorrect results in the model's science? No
Configurations affected:
SMS_Ld5_D_P48x1_Vnuopc.f10_f10_mg37.IHistClm51Bgc.izumi_nag.clm-decStart
SMS_P48x1_D_Ld5_Vnuopc.f10_f10_mg37.I2000Clm50Cn.izumi_nag.clm-default
Details of bug
At initialization on startup the model reads in the time coordinate for all of the forcing files. It successfully goes through the majority of them, but times out near the end.
It's not clear to me what's different about these two tests than other tests that run successfully. Many tests on izumi are with CRU forcing, but still some are GSWP3 for this same resolution.
Important details of your setup / configuration so we can reproduce the bug
See this comment in PR #1309
#1309 (comment)
Important output or errors that show the problem
atm.log file:
cesm.log file:
The text was updated successfully, but these errors were encountered: