CESM2.2 series needs to point to an updated CMEPS/CDEPS

[ekluzek]

Summary of Issue:

cesm2_2_beta04 points to 471ac52 for CMEPS (in Externals_cime.cfg). At least some cases built with this can't even create the case.

Note that CTSM is using the CMEPS hash: 253f612acae07b2b1dc73c84f1bb30b8e1b86ddd which is functional for the following case.

Expected behavior and actual behavior: Expect the case to PASS, instead it FAILS as case create as below...

Steps to reproduce the problem. Include externals description file(s) and link to public repository):

on cheyenne
qcmd -- ./create_test SMS_D_Ld5_Vnuopc.f10_f10_musgs.I2000Clm50BgcCropGs.cheyenne_intel.clm-default -r .

What is the changeset ID of the code, and the machine you are using: ctsm1.0.dev092 (using cime5.8.19)

have you modified the code? If so, it must be committed and available for testing: No

Screen output or log file showing the error message and context:

.
.
.

Pes setting: tasks is {'NTASKS_ATM': -2, 'NTASKS_ICE': -2, 'NTASKS_CPL': -2, 'NTASKS_LND': -2, 'NTASKS_WAV': -2, 'NTASKS_ROF': -2, 'NTASKS_OCN': -2, 'NTASKS_GLC': -2}
Pes setting: threads is {'NTHRDS_ICE': 1, 'NTHRDS_ATM': 1, 'NTHRDS_ROF': 1, 'NTHRDS_LND': 1, 'NTHRDS_WAV': 1, 'NTHRDS_OCN': 1, 'NTHRDS_CPL': 1, 'NTHRDS_GLC': 1}
Pes setting: rootpe is {'ROOTPE_OCN': 0, 'ROOTPE_LND': 0, 'ROOTPE_ATM': 0, 'ROOTPE_ICE': 0, 'ROOTPE_WAV': 0, 'ROOTPE_CPL': 0, 'ROOTPE_ROF': 0, 'ROOTPE_GLC': 0}
Pes setting: pstrid is {}
Pes other settings: {}
Pes comments: none
Compset is: 2000_DATM%GSWP3v1_CLM50%BGC-CROP_SICE_SOCN_MOSART_SGLC_SWAV_SESP
Grid is: a%10x15_l%10x15_oi%null_r%r05_g%null_w%null_z%null_m%usgs
Components in compset are: ['datm', 'clm', 'sice', 'socn', 'mosart', 'sglc', 'swav', 'sesp', 'drv', 'dart']
No charge_account info available, using value from PROJECT
cesm model version found: ctsm1.0.dev091-9-g1f5afc67
Batch_system_type is pbs
ERROR: Looks like job groups have already been created

---

[gold2718]

Do we even want CMEPS in CESM 2.2?

[ekluzek]

@gold2718 I need to let others reply to that. But, I suspect you are correct for the CESM2.2.0 release -- we will NOT want it part of that. But, it is in now and I think they want it in now for testing. It can easily be removed in the release tag at the end. That's what would make the most sense to me.

[jedwards4b]

We are in a rapid development cycle in CMEPS and have not made any effort to maintain compatibility with the cesm2.2 - currently I believe that the cime trunk is consistent with the CMEPS trunk.

[mvertens]

Yes - that is correct.

…

On Fri, May 1, 2020 at 9:07 AM jedwards4b ***@***.***> wrote: We are in a rapid development cycle in CMEPS and have not made any effort to maintain compatibility with the cesm2.2 - currently I believe that the cime trunk is consistent with the CMEPS trunk. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#152 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB4XCEYYJCPW5TLIER3K55DRPLQRLANCNFSM4MSON63A> .

-- Mariana Vertenstein CESM Software Engineering Group Head National Center for Atmospheric Research Boulder, Colorado Office 303-497-1349 Email: [email protected]

[fischer-ncar]

@ekluzek the CMEPS hash was updated, is this still an issue for you?

[ekluzek]

It still fails as. it needed both a CMEPS update and CDEPS update. Now it's. working with #152