Closed jedwards4b closed 1 year ago
I also tried in cesm2_3_beta08 and it doesn't give the mapping errors as above but it also doesn't modify the vertical coordinate.
Does this problem happen with both NUOPC and MCT? Currently, there is a prebeta CAM test that exercises this functionality:
<test compset="FDABIP04" grid="T85z60_T85_mg17" name="ERP_D_Ln9_Vmct" testmods="cam/outfrq9s">
<machines>
<machine name="izumi" compiler="nag" category="prebeta"/>
</machines>
</test>
Did this test run in the cesm2_3_beta08 tests?
@fischer-ncar ^
For cesm2_3_beta08
ERP_D_Ln9_Vmct.T85z60_T85_mg17.FDABIP04.izumi_nag.cam-outfrq9s ERP_D_Ln9_Vmct.T85z30_T85_mg17.FDABIP04.izumi_nag.cam-outfrq9s ERP_D_Ln9_Vmct.T85z60_T85_mg17.FHS94.izumi_nag.cam-outfrq9s ERP_D_Ln9_Vmct.T85z30_T85_mg17.FHS94.izumi_nag.cam-outfrq9s
All passed
The cam config commands for the FDABIP04 tests were.
/home/fischer/code/cesm2_3_alpha08d/components/cam/bld/configure -s -fc_type nag -dyn eul -hgrid 128x256 -cpl mct -usr_src /scratch/cluster/fischer/ERP_D_Ln9_Vmct.T85z30_T85_mg17.FDABIP04.izumi_nag.cam-outfrq9s.GC.c2_3_b08d_nag/SourceMods/src.cam -nlev 30 -spmd -nosmp -ocn socn -phys adiabatic
/home/fischer/code/cesm2_3_alpha08d/components/cam/bld/configure -s -fc_type nag -dyn eul -hgrid 128x256 -cpl mct -usr_src /scratch/cluster/fischer/ERP_D_Ln9_Vmct.T85z60_T85_mg17.FDABIP04.izumi_nag.cam-outfrq9s.GC.c2_3_b08d_nag/SourceMods/src.cam -nlev 60 -spmd -nosmp -ocn socn -phys adiabatic
Thank you @fischer-ncar Can you confirm that this works for f09z83_g17 when using mct but not when using nuopc.
For cesm2_3_beta08 f09z83_g17.B1850 I'm getting ncdata undefined errors. I'll try with an A compset.
For cesm2_3_beta08 B1850 and A for mct I'm getting the following error. ERROR: Need to provide valid mapping file between atm and ice in xml variable atm2ice_fmapname Then for nuopc, The A compset ran, the B1850 compset will build, but it needs 83 level inputfiles.
@fischer-ncar What I saw in nuopc was that it was simply ignoring the z83 setting - did you confirm that cam is set with -nlev=83?
@jedwards4b For B1850 nuopc, the cam configure script was setting "-nlev 83", and the error message I'm getting during the run is.
/glade/p/cesmdata/cseg/inputdata/atm/cam/topo/fv_0.9x1.25_nc3000_Nsw042_Nrs008_
Co060_Fi001_ZR_sgh30_24km_GRNL_c170103.nc
hycoef_read: ERROR: file lev does not match model. lev (file, model):
32 83
ERROR: hycoef_read: ERROR: file lev does not match model.
I guess I made a mistake then, could you try this in cesm2.1.4-rc11? If it works there we can close this issue.
For cesm2.1.4-rc11, -nlev 83 is being set for the cam configure script. But during build I'm getting
ERROR: Need to provide valid mapping file between atm and ice in xml variable atm2ice_smapname
okay that was the original error. Changing vertical levels should not require changing mapping files so this is a bug.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
I tried test ERP_Ln9_D.T85z60_T85_mg17.FDABIP04.cheyenne_intel.cam-outfrq9s in cesm2.3.beta12 and it works as expected.
There is a little known feature of the res argument that allows you to specify a non-standard vertical dimension argument, so for example f09z83_g17 should give you a case with 83 vertical levels, however testing in cesm2.1.4-rc11 seems to indicate that this option is broken in cesm2.1.