`e3sm_to_cmip` breaks with vertical dimension name with changes in `nco=5.14`

[tomvothecoder]

It turned out that the NCO version different changed the vertical dimension name, which resulted that error you found. I post this on the “nco” channel to see if Charlie has some suggestion. Below is what I posed on slack:

• here is a minor glitch @Mingxuan Wu and I are using e3sm_to_cmip to convert some atmospheric variables. When converting some 3D variables, we noticed the NCO vertically remaped files ends with dimension name lev using NCO 5.1.4 from e3sm_unified, and plev using 5.1.3, which is included in e3sm_to_cmip dev enviroment. The mapping file vrt_remap_plev19.nc does have plev as the dimension. I'm wondering if this is expected for the newer versions of NCO, if in this case, we perhaps need to update e3sm_to_cmip or its workflow for this change.

-- Originally from an email chain with @chengzhuzhang, @mingxuanwupnnl, and @TonyB9000

This was an inadvertent change to the default setting (regression).

Current Workaround

The current workaround is to install nco=5.1.3 explicitly with e3sm_to_cmip=1.9.1.

Example:

conda create -n e2c -c conda-forge e3sm_to_cmip=1.9.1 nco=5.1.3
conda activate e2c

Future Solution

Wait for nco=5.1.5 which should include the default as plev again.

[tomvothecoder]

@TonyB9000 and @chengzhuzhang, was this ever fixed in nco>=5.1.5? If so, I will close this issue.

[chengzhuzhang]

I believe so.