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
ERP_P72x2_Ld30.f45_f45_mg37.I2000Clm51FatesRs.cheyenne_intel.clm-mimicsFatesCold
has been failing at SETUP (previously as a clm50 test and as a clm51 test as of today)
with Fire emission can NOT be on when FATES is also on.
This is an EXPECTED FAILURE. I looked into it a bit and wanted to post thoughts on fixing it.
General bug information
CTSM version you are using: [output of git describe]
ctsm5.1.dev153
Does this bug cause significantly incorrect results in the model's science?
No, but it prevents testing of mimics/fates.
Configurations affected:
mimics and fates on at the same time.
Details of bug
Fixing this may require pointing the mimics testmod to /basic instead of /default to avoid setting -fire_emis; however, the fix would affect all mimics tests, so I wanted to look more carefully whether this is ok to do.
The test is now ERP_P256x2_Ld30.f45_f45_mg37.I2000Clm60FatesRs.derecho_intel.clm-mimicsFatesCold
The test fails again with Fire emission can NOT be on when FATES is also on but now we have an easy way to turn off fireemis
The test ERP_P256x2_Ld30.f45_f45_mg37.I2000Clm60FatesRs.derecho_intel.clm-mimicsFatesCold--clm-nofireemis
fails with the CH4 error mentioned in the previous post (see a troubleshooting suggestion there): CH4 Conservation Error in CH4Mod during diffusion, nstep, c, errch4 (mol /m^2.timestep) 1 2 NaN
The same test in debug mode ERP_D_P256x2_Ld30.f45_f45_mg37.I2000Clm60FatesRs.derecho_intel.clm-mimicsFatesCold--clm-nofireemis gives this traceback
Rosie's email titled CLM-FATES-CN-MIMICS+ reminded me that this issue (i.e. getting MIMICS to work with FATES) had fallen off my radar. I'm adding to my Sprint board for visibility and @wwieder and/or @adrifoster feel free to assign a milestone to clarify the urgency.
changed the title [-]EXPECTED FAILURE: ERP_P72x2_Ld30.f45_f45_mg37.I2000Clm51FatesRs.cheyenne_intel.clm-mimicsFatesCold[/-][+]EXPECTED FAILURE: ERP_P256x2_Ld30.f45_f45_mg37.I2000Clm60FatesRs.derecho_intel.clm-mimicsFatesCold[/+]on May 19, 2026
Activity
slevis-lmwg commentedon Nov 21, 2023
I found additional problem-solving notes for this failing test in this issue.
slevis-lmwg commentedon Feb 14, 2024
UPDATE:
ERP_P256x2_Ld30.f45_f45_mg37.I2000Clm51FatesRs.derecho_intel.clm-mimicsFatesColdI would first remove the P256x2 and try again in case the error message is a "red herring."
slevis-lmwg commentedon Jul 31, 2025
UPDATE:
ERP_P256x2_Ld30.f45_f45_mg37.I2000Clm60FatesRs.derecho_intel.clm-mimicsFatesColdFire emission can NOT be on when FATES is also onbut now we have an easy way to turn off fireemisERP_P256x2_Ld30.f45_f45_mg37.I2000Clm60FatesRs.derecho_intel.clm-mimicsFatesCold--clm-nofireemisfails with the CH4 error mentioned in the previous post (see a troubleshooting suggestion there):
CH4 Conservation Error in CH4Mod during diffusion, nstep, c, errch4 (mol /m^2.timestep) 1 2 NaNERP_D_P256x2_Ld30.f45_f45_mg37.I2000Clm60FatesRs.derecho_intel.clm-mimicsFatesCold--clm-nofireemisgives this tracebackslevis-lmwg commentedon May 13, 2026
Rosie's email titled CLM-FATES-CN-MIMICS+ reminded me that this issue (i.e. getting MIMICS to work with FATES) had fallen off my radar. I'm adding to my Sprint board for visibility and @wwieder and/or @adrifoster feel free to assign a milestone to clarify the urgency.
[-]EXPECTED FAILURE: ERP_P72x2_Ld30.f45_f45_mg37.I2000Clm51FatesRs.cheyenne_intel.clm-mimicsFatesCold[/-][+]EXPECTED FAILURE: ERP_P256x2_Ld30.f45_f45_mg37.I2000Clm60FatesRs.derecho_intel.clm-mimicsFatesCold[/+]