Closed ekluzek closed 1 year ago
The CDEPS issue this refers to is:
@ekluzek - I have incorporated a fix that is in the latest CDEPS tag cdeps0.12.47 that makes this case now work. I have compared the cply and cmeps test results and things look good. If you update to the cdeps tag - you will also need to update cime, ccs_config, cmeps and share in ctsm.
Perfect -- thank you! I'm assuming this means the nldas2 cases will have different answers?
Yes - using nuopc will always give you different answers. I have verified that the values coming in from the nldas2 forcings (that are on the same grid as the model) are only roundoff - however the aerosol forcings are mapped from a 2 degree grid to the nldas2 mesh - and since ESMF bilinear mapping is different than the internal cpl7 data model mapping - there will be differences.
@mvertens no I mean our non-DEBUG test cases we run with nldas2 with nuopc. Here are the two baselines for ctsm5.1.dev091 on cheyenne. I'm just wondering if I should expect answers to change when I run the test suite for these two tests...
/glade/p/cgd/tss/ctsm_baselines/ctsm5.1.dev091/SMS_Ld1_PS.nldas2_rnldas2_mnldas2.I2000Ctsm50NwpSpNldas.cheyenne_gnu.clm-default /glade/p/cgd/tss/ctsm_baselines/ctsm5.1.dev091/SMS_Ld1_PS.nldas2_rnldas2_mnldas2.I2000Ctsm50NwpSpNldasRs.cheyenne_gnu.clm-default
The underlying CDEPS issue was fixed. And this seems to have been fixed by ctsm5.1.dev116 so closing.
Brief summary of bug
The following test fails in datm when run in DEBUG mode
SMS_D_Ld1_PS.nldas2_rnldas2_mnldas2.I2000Ctsm50NwpSpNldasRs.cheyenne_intel.clm-default
General bug information
CTSM version you are using: ctsm5.1.dev091 Does this bug cause significantly incorrect results in the model's science? No
Configurations affected: nldas2 grid
Details of bug
It looks like the problem is inside of datm so hence may be a problem with CDEPS/datm rather than CTSM.
Important details of your setup / configuration so we can reproduce the bug
We do the above test without DEBUG mode for all tags. So it does run when done with DEBUG mode.
Important output or errors that show the problem