Francis Vitt

> I'm happy to test the impact of this bug fix, as I'm curious the impacts. Has anyone looked at that? @tilmes is testing fixes. Please coordinate with her.

@jedwards4b I don't understand why this is closed. There is a problem with the cesm2.2 on derecho. The zm fields have existed in cam for long before tag cam6_3_092. Prior...

It seems that the changes to `src/dynamics/fv/dyn_grid.F90` in cam tag cam6_3_008 fixes this issue. See issue https://github.com/ESCOMP/CAM/issues/282 The changes are: ``` diff --git a/src/dynamics/fv/dyn_grid.F90 b/src/dynamics/fv/dyn_grid.F90 index 722fd8e6..610df458 100644 --- a/src/dynamics/fv/dyn_grid.F90...

@npedatella Please try waccmx with the latest I have in sandbox `/glade/work/fvitt/cesm/cesm2.2.1_derecho`

@npedatella Correct me if I am mistaken, but I don't believe WACCMX in CESM2.2 is able to run in multi-instance mode. We did not have this capability until after the...

Should have been closed by https://github.com/ESCOMP/CAM/pull/915

I will hold off on this for now. However, I think the new TEM diags scheme can use the `*zm` history fields names. We just cannot use both the old...

"xhigh" for waccmx? FLT*=> model_top = 'low' FMT* => model_top = 'mid' FW* => model_top = 'high' FX* => model_top = 'xhigh'

@cacraigucar I will need to create the chemistry mechanism file and preprocess the pp_ code. I will provide a branch for the ghg_mam4 chemistry.

> @fvitt - Since you were the person who felt that some of the LT/MT variables should be in namelist_defaults, and made the change to move them, could you explain...