Gregory Lemieux

> @bishtgautam We can go ahead and merge the work once the FATES part is merged. @bishtgautam I'm working on the final deconflict and test on the fates-side right now.

@sshu88 would you remove the "[WIP]" from the title now?

@bishtgautam we still need to update the pointer to the fates side, but the associated PR hasn't been merged yet. I'll give you a heads up when that happens

> Are the existing tests cover the new physics? Or, should we add a new test? We should add new tests, but I would like to defer that to a...

I'm running the land-developer tests and seeing two unexpected failures. I haven't looked into them much yet, but one is a fates smoke test failing during runtime in PhosphorusDynamicsMod and...

@sshu88 I created a [PR to your branch](https://github.com/sshu88/E3SM/pull/6) to update the fates pointer now that https://github.com/NGEET/fates/pull/888 is integrated on the fates-side. @bishtgautam I ran land developer tests on Cori and...

@bishtgautam this can be closed per #5429.

FYI, this should be fixed by https://github.com/NGEET/fates/pull/824 the next time we update to point the fates submodule to tag [sci.1.63.2_api.25.1.0](https://github.com/NGEET/fates/releases/tag/sci.1.63.2_api.25.1.0).

Updating to `ccs_config_cesm0.0.65` via #2000 now results in all the `nvhpc` tests on cheyenne failing run times. It is expected that updating to `cesm2_3_beta15` will resolve this.

> This would be useful! As a workaround, I'm now using the following shameful hack with IJulia 1.23.2: > > ```julia > using IJulia > jupyter = IJulia.find_jupyter_subcommand("")[1] > run(`$(jupyter)...