FATES doesn't work in branch runs

[samsrabin]

When trying to use FATES as part of a branch run, I get the following error:

forrtl: severe (151): allocatable array is already allocated
Image              PC                Routine            Line        Source
cesm.exe           0000000000983A08  edinitmod_mp_init         144  EDInitMod.F90
cesm.exe           00000000006403F4  clmfatesinterface        2089  clmfates_interfaceMod.F90
cesm.exe           00000000006063A6  clm_initializemod         757  clm_initializeMod.F90
cesm.exe           00000000005A8EA3  lnd_comp_nuopc_mp         658  lnd_comp_nuopc.F90

This is with CTSM tag ctsm5.3.009, FATES tag sci.1.78.3_api.36.1.0. It can be reproduced using the test ERI_Ld60.f45_f45_mg37.I2000Clm50FatesCruRsGs.derecho_intel.clm-Fates, which is the ERI version of an ERS test we already run as part of the fates suite.

Note parallel issue at ESCOMP/CTSM#2903.

[jennykowalcz]

Have also encountered this. The less strict hybrid mode does work though.

[XiulinGao]

I did encounter a similar issue when run with FATES API 36 (CTSM 5.2.013). If I want to do a hybrid run using restart file model build will fail warning that a restart file should not be defined when cold start is turned on. But I did turn it off.

[samsrabin]

@XiulinGao That's actually a separate issue that is now fixed in CTSM as of ctsm5.3.011.